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 cfd4eaa
Browse filesBrowse the repository at this point in the historyBrowse files
CI: hermetic spawns in redirect build tests (#823) (#1457)
* Spawn redirect build test children hermetically
Five e2e_redirect_*_build suites (cargo, composer, gem, maven, npm)
started socket-patch with a bare Command::new and their own SOCKET_*
scrub. The copies disagreed: composer and maven removed every SOCKET_*
var, the others kept SOCKET_NO_CONFIG, and none forced the update
notifier off.
Their run helpers now go through tests/common/hermetic.rs, and the
files leave PENDING_RAW_SPAWNS (79 -> 74) so the ratchet keeps them
hermetic. The gem suite's BUNDLE_MIRROR__ scrub and the maven suite's
M2_HOME removal stay. Refs #823.
Assisted-by: Claude Code:claude-opus-5-5
* Scrub every ambient BUNDLE_* in gem redirect runs
The gem redirect suite's socket-patch runs removed only BUNDLE_MIRROR__*
vars. An ambient BUNDLE_GEMFILE, BUNDLE_PATH or BUNDLE_APP_CONFIG still
reached the crawler and could point it at a different Gemfile or gem
store than the fixture install used. Use hermetic::Extra::Bundle, which
removes every BUNDLE_* var; tests that need one still pass it in.
Assisted-by: Claude Code:claude-opus-5-5
---------
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments