Repository navigation
fix(ci): read run jobs 50 at a time so the queue evidence read succeeds - #653
Conversation
Pages of 100 jobs on the full catalogue run fail with HTTP 502 on every attempt, which turns a fully green run red at the summary step. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai review |
Code coverage overviewLanguages: Go, C# Go / code-coverage/test
C# / code-coverage/dotnet
Go / code-coverage/go
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📜 Recent review details
📝 Walkthrough
Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to
|
Readiness at
|
|
Why
The required check on the main branch has been red since this morning even though every test job passed. Its last step reads the list of jobs in the run, and GitHub fails that read every time when it asks for 100 jobs at once on the full test catalogue, so the check gives up and reports failure.
What
The job list is now read 50 jobs at a time, which GitHub answers reliably. The same change is made in the Go cache check, which reads the same list. The check still refuses to pass on an incomplete list.
No issue: trivial fix.