ci(probe): widened ESP Windows job on plain main (do not merge) - #522
ci(probe): widened ESP Windows job on plain main (do not merge)#522adamgell wants to merge 1 commit into
Conversation
Temporary probe for the PR #460 loader failure: PR #460's widened ESP Windows job dies launching the app_lib unit-test exe with STATUS_ENTRYPOINT_NOT_FOUND, while main's narrow job passes the same step cold. This branch is main plus only the workflow widening; if its ESP job fails the same way, the widened job itself breaks the loader and PR #460's code is exonerated. Not for merge. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
Probe complete: reproduced the four sccm_client_management_fixture_contract path-separator failures on plain main + widened job, confirming the latent Windows bug lives on main (fix rides PR #460 as commit 46e7a6a). The app_lib loader question was answered separately by a dumpbin diagnostic on the #460 branch; the target-dir isolation fix is on that branch. |
Probe for the PR #460
STATUS_ENTRYPOINT_NOT_FOUNDfailure: main + only the widened ESP Windows steps from #460. If the ESP job here fails the same way, the widened job itself is the trigger and #460's code is exonerated. Will be closed after one CI cycle.🤖 Generated with Claude Code