Repository navigation
Test CIFS canonical marker updates during shallow-storage migration - #40
Merged
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.
Regression tests for production PR #39. The positive test simulates CIFS denying direct overwrite of an existing canonical marker while permitting same-directory temporary creation and atomic replacement. A second test verifies that a failed replacement leaves the original marker intact and cleans the temporary file.
Merge order: merge production PR #39 before this test PR so the canonical test-suite harness stays green against master.
Verification: the positive test fails against unchanged master and passes against #39. Full test-suite against #39: 251 passed, 4 skipped.