fix: add fail-closed M5 eight-cell stability profile - #73
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Evidence boundary
This responds to the completed M5 soak series:
This is the final code-side stability attempt before development pauses. Native M5 soak evidence is still required after merge; the PR does not claim the freezes are eliminated.
TDD and verification
python3 tests/run_all.py— OVERALL PASSpython3 -m compileall -q hyperwall tests scripts— PASSbash -n soak_wall.sh— PASSgit diff --check— PASSRuntime behavior on the target
The startup log will report both:
Stable direct-only profile: ...Stable direct-only pool: admitted N/M items ...Use
HYPERWALL_STABLE_DIRECT_ONLY=0as the rollback switch.