Cap backup-test retry loop to stop multi-hour hangs#158
Merged
Conversation
The test wrapped each backup.sh call in a 50x readiness loop written for the old single-shot ensure_repo. Since ensure_repo now retries internally (30x/5s) to ride out S3 warmup, the two loops multiplied: a broken-S3 run ground on for ~2.5h (up to CI's 6h cap) instead of failing in ~5min. ensure_repo already owns the warmup wait, so drop the outer loop to 3 attempts - enough to absorb a transient post-readiness hiccup without re-nesting the retries. Refs #155. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
The test wrapped each backup.sh call in a 50x readiness loop written for the old single-shot ensure_repo. Since ensure_repo now retries internally (30x/5s) to ride out S3 warmup, the two loops multiplied: a broken-S3 run ground on for ~2.5h (up to CI's 6h cap) instead of failing in ~5min.
ensure_repo already owns the warmup wait, so drop the outer loop to 3 attempts - enough to absorb a transient post-readiness hiccup without re-nesting the retries. Refs #155.