Skip to content

test: isolate Pi message tests in hermetic child processes - #111

Closed
Florious95 wants to merge 1 commit into
fix/grok-inspect-project-trustfrom
fix/r6-pi-hermetic-boundary
Closed

test: isolate Pi message tests in hermetic child processes#111
Florious95 wants to merge 1 commit into
fix/grok-inspect-project-trustfrom
fix/r6-pi-hermetic-boundary

Conversation

@Florious95

Copy link
Copy Markdown
Owner

Owns the R6 isolation-guard red from the v0.5.69 full run.

  • adds exact-child HermeticTestEnv boundaries only to the two Pi tests
  • R6 1/1, Pi dual 1/1, Pi executable 4/4, bypass tooth 1/1
  • no product behavior change

Base: five-provider-PR stack head 7e2c65d.

@Florious95

Copy link
Copy Markdown
Owner Author

Absorption audit: this PR is fully present in the composed release v0.5.69 (peeled SHA 6e9391d5374bc669ec48bfce11d785c0db97fea0) and carried by v0.5.71 (ad1f1874144066c4bf48e0c2e88801c1c7edaf4b). Composition receipt patch-id matches: e30ba2ca35528b3f3bfd0b9462c25d4264e0bdcb5b15012a; the composed release receipt/history records the same exact hermetic Pi fixture file bytes. Closing without merge; the stale stacked-base nonzero diff is not evidence against absorption. The frozen head before closure is e30ba2ca40a22d30d39c32b22f62ec92445c43c2.

@Florious95 Florious95 closed this Aug 31, 2026
@Florious95
Florious95 deleted the fix/r6-pi-hermetic-boundary branch August 31, 2026 11:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant