Repository navigation
Unblock GitHub Actions queue retries - #464
Merged
Merged
Conversation
Use smaller jobs pages, share bounded pending retries between failed and unfinished runs, and recognize terminal job evidence when GitHub retains a stale status. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: dce070cb-ab76-4725-80eb-0db99ed545b4
Pull request dashboard statusMerged · refreshed 2026-10-14 16:48 UTC Status above doesn't look right?
|
Contributor
There was a problem hiding this comment.
🔵 Needs a closer look
Recovery and budget headroom remain unverified under the production collector credentials.
0 open findings
What changed in this PR
Improves queue collection resilience against jobs-API failures and stale job statuses.
Changes:
- Uses 50-job pagination with completeness checks.
- Fairly allocates pending-run retries and clears resolved errors.
- Recognizes terminal jobs with stale
in_progressstatuses and adds coverage.
| File | Description |
|---|---|
.github/scripts/github-actions-queue/collect.py |
Implements pagination, retry allocation, and terminal-state handling. |
.github/scripts/github-actions-queue/test_collect.py |
Tests the new collection behavior and edge cases. |
github-actions-queue/README.md |
Documents updated collector semantics. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
maryliag
approved these changes
Oct 14, 2026
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.
Keep saved queue runs moving despite jobs-API 502s and stale GitHub job statuses, without increasing the collection budget or dropping attempts.
A finalized raw record can retain GitHub's stale status when completion evidence is present:
{"job_status":"in_progress","job_conclusion":"success","job_completed_at":"2026-08-13T06:53:33Z"}filter=alland the unique-job completeness check. Repository and workflow-run pages stay at 100.in_progressstatus only when they also have a completion timestamp and a terminal conclusion. Preserve GitHub's reported status in raw records.Preserves the checkpointing and anti-starvation fixes from #377, live-first collection and budgets from #385, bounded transport retries from #392, and runnerless/negative-queue filtering from #394 and #412. No state migration or snapshot-writer changes are required.
Smaller pages recovered complete job lists for representative failing runs using operator credentials. Recovery under the collector App's credentials remains unverified; GitHub's underlying 502 cause is not established.