Repository navigation
test: check multi-node file histories against the documented guarantees - #156
Merged
Merged
Conversation
…ed guarantees Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ing a local write, and track the checker in the manifest Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 16, 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
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.
A Jepsen-style checker for the cross-node guarantees in the docs. Clients on 2-4 mounts hammer 5 shared names with create, write, read, stat, readdir, unlink and rename, recording every call's start and end on one clock.
history.Checkthen flags what no allowed order explains:-attr-timeoutplus slack;open(O_CREAT)withoutO_EXCL;Porcupine wasn't a fit: the guarantees are windowed, not linearizable.
TestCoherenceHistoryruns only withGCFS_HISTORY=1, because main fails it today (findings in the PM's notes: cross-file reads, a block leak, EISDIR from open, EEXIST). Fixes come next, each rerun under this checker. The checker's own unit tests always run.Per the PM, a read split at 4 KB boundaries while a write on the same node overlaps it is allowed, and OPERATIONS.md now says so. Mid-sector tears stay violations.
🤖 Generated with Claude Code