Repository navigation
Test automatic recovery and legacy filesystem fallback - #52
Merged
Merged
Conversation
This was referenced Oct 27, 2026
TorecLuik
changed the title
TorecLuik
marked this pull request as ready for review
October 27, 2026 16:17
This was referenced Oct 27, 2026
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.
Exercise automatic result recovery on supported storage and legacy fallback when recovery requirements are unsupported. No deployment flag is required. Cover unsupported locks, file sync, atomic replacement and directory sync before queueing; saved plans, busy locks, permission/I/O/disk-full errors and failures after queueing cannot trigger fallback. Obsolete flag values do not affect the automatic path.
Merge this test-suite PR before scripts #50, then rerun #50's check. Assertions are capability-gated against older source revisions; no unpublished dependency is required. Tests remain separate from deployable scripts. Companion importer: #31.
Validation: new positive automatic-recovery and durable-write fallback tests observed red before implementation. Final Windows feature harness 370 passed, 7 skipped (including three POSIX-only directory-sync cases); all 51 recovery cases pass on Linux. Updated harness also passed against unchanged master (322 passed) and the previous remote feature revision (352 passed); new capabilities are skipped there. One unrelated Windows marker-replacement test encountered a transient permission error on an earlier run; the focused rerun and final full run passed without changes to that test or code.