Repository navigation
fix(scripts): retry failed strategy checks - #52
Merged
Merged
Conversation
http_get retries requests; check-all checks a failed package again.
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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.
http_getinscripts/lib.shrunscurl -sfL --max-time 30 --retry 2 --retry-delay 5 --retry-connrefused, and every strategy andgithub_apisend their requests through it. A test intests/strategies.batsfails when a strategy callscurlitself.kde-tarball.shnow sourceslib.shfor it.check-all.shchecks a package once more when its check failed within the time budget, after the other packages and a pause ofAURTOMATOR_RECHECK_DELAYseconds (60 by default), and keeps the second result. A check that ran out of its budget is not repeated. The loop body becamerun_package, and every mode counts the errors from the statuses.From 2026-07-26 to 2026-09-29, 14 runs in noctuum/sibyl failed five or six packages at once with
Failed to fetch, and each package opened an issue.