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 49847ef
Browse filesBrowse the repository at this point in the historyBrowse files
CI: hermetic spawns in vlt test commons (#823) (#1488)
* Start fix for #823 (slice 10)
Assisted-by: Claude Code:claude-opus-5-5
* Spawn vlt test children through hermetic builder
The vlt e2e, hosted and vendor test helpers each started socket-patch
with a bare Command::new and their own SOCKET_* sweep. Those copies
had drifted from tests/common/hermetic.rs: none removed flag-bound
vars set in-process after the sweep, none used the hostile seeds that
catch a dropped scrub, and the hosted helper left an ambient
SOCKET_TELEMETRY_DISABLED=0 in place.
All three now build on hermetic::command and keep only their own
vlt and proxy scrubs. They leave PENDING_RAW_SPAWNS, so the ratchet
keeps them hermetic.
Refs #823
Assisted-by: Claude Code:claude-opus-5-5
* Keep test opt-outs after the vlt env scrub
The shared vlt scrub also removes SOCKET_* vars, so running it on a
socket-patch child built by the hermetic builder would turn telemetry
and the update check back on. Add a vlt scrub that leaves SOCKET_* to
the builder, as the bun suites already have, and use it for the vlt
e2e CLI child instead of re-applying the opt-outs by hand.
Refs #823
Assisted-by: Claude Code:claude-opus-5-5
---------
Co-authored-by: Claude <noreply@anthropic.com>
0 commit comments