Repository navigation
Add repository-owned upload resilience checks - #1176
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
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.
Moves the first six executable resilience checks into the CLI repository under the shared
.sdkharness/tests.tsvcontract. The checks execute this checkout's CLI against the harness-provided loopback simulator and private fault-control listener.Scenarios:
Verification:
pytest -q test/unit/test_sdkharness_resilience.py: 11 passedThe sole failure is
upload.retry_408: both implementations observe one upload attempt and no recovery. Its dependency root cause is already tracked in Backblaze/b2-sdk-python#605. This PR preserves the finding; it does not hide or fix it.