Repository navigation
Conversation
This branch has not been deployed
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 process can exit between the legacy merge's delete, append, and WAL-drain commits. These subprocess tests terminate at both durable write boundaries, then reopen the same shard and recover without appending new data. They check updated and untouched contents, pending-generation drain, physical fragment row counts, and repeated recovery.
Fault hooks exist only in unit-test builds. This is stacked on the explicit WAL replay change in #387; it does not qualify concurrent legacy writers, uncertain object-store acknowledgements, or production process retirement.
Validation: 2 crash-boundary tests passed; the subprocess helper is ignored in the parent suite and invoked explicitly by each test.
git diff --checkpassed.