You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b0f1739
Browse filesBrowse the repository at this point in the historyBrowse files
The previous fix deleted both guard variables at one spawn site. A reviewer
pointed out the class of bug survives: the nearby re-entry tests assert status
126, so an inherited depth offset leaves them passing for entirely the wrong
reason, and the next test to spawn a shim starts the cycle again.
shimChildEnv strips PID, DEPTH and PROBE_ACTIVE in one place, mirroring what
probeUnixShimInstall already does before spawning its probe. The second spawn
site at line 291 had the same gap - it deleted only the pid - so it was quietly
depth-sensitive too.
What this buys is that a green run means what it says. Before, these tests
measured whatever shim ancestry the developer's shell happened to carry, and
were green in CI only because CI has no shimmed ancestor.
0 commit comments