Make durability-fence and consumer-atomicity fixture custody explicit; remove 21 inherited warnings - #96
Merged
Conversation
Seven held-operation scenarios spawn requests or queue operations that must run concurrently with a held dispatch or commit, and every handle is joined after the release. Narrow test-only expectations now name that custody and the reason each long scenario keeps its causal sequence together, and the spawn sites are registered with their fixture owners. No assertion, failpoint or scenario identity changes; the test inventory is unchanged because only non-executable attributes were added. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
sorenbs
marked this pull request as ready for review
September 11, 2026 13:03
This was referenced Sep 11, 2026
Merged
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
1 participant
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.
Seven held-operation scenarios in the durability-fence and consumer-atomicity fixtures spawn requests or queue operations that must run concurrently with a held dispatch or held commit, and every handle is already joined after the release. Narrow test-only expectations now name that custody and the reason each long scenario keeps its causal sequence together, and the seven spawn sites are registered with their fixture owners and counts. No assertion, failpoint, scenario identity or production source changes, and the test inventory is unchanged because only non-executable attributes were added.
Addresses 21 additional inherited warnings on the merged slate head (#95): 8 custody and 3 size expectations in
durability_fences.rs, 6 custody and 4 size expectations inconsumer_atomicity.rs. Both active platform diagnostic ledgers are pruned; the prune also records the mergedhttp_rig_buildsize metric (162 lines) that two merged fixture PRs had each reduced independently. The frozen adoption inventories are unchanged. Targetsslate.Validation: common quality passes with pinned Clippy and ratchets at 1,548 remaining occurrences on this branch, and all 12 durability-fence and consumer-atomicity scenarios pass in release. Exact-head CI is pending, so this remains a draft.
🤖 Generated with Claude Code