Repository navigation
ci: a job stuck with no runner no longer cancels jobs running on a mini #16479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
0e707c9
test(ci): a stuck side job must not cancel a sibling running on a mini
teamleaderleo ae11ab6
ci: never rescue a stuck job while a sibling runs on a persistent runner
teamleaderleo 8370637
ci: a sibling on a mini no longer hides a refused or held job
teamleaderleo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
P2: A stuck job held back by a mini-running sibling has no recovery path once the watch's deadline passes. The watch loop returns "stop: watch limit reached" with nothing cancelled, and later sweepers skip this run as soon as its marker passes SWEEP_MAX_AGE_SECONDS (150 min; sweep() drops marked runs whose
createdis older thanoldest). If the pool stays busy past that point the shard waits indefinitely and is never rescued or re-run. The narrower new case this hold also enables: if the run reaches "completed" while the held job is still queued with no runner (a third sibling fails, or a newer push/concurrency cancels the run), the loop'sfinished and not any(refused(job)...)stop fires and the queued shard ends up cancelled without any re-run — an outcome the "assessed before this hold" carve-outs (refused, held-in-setup) don't cover, and one a plain budget rescue previously prevented. Consider letting a held stuck job survive the deadline (re-adopt in-progress runs regardless of marker age, or treat the hold like the refusal path and finish it within a grace window), so a sibling that finishes late still gets its shard rescued.Prompt for AI agents