docs(evidence): close out the CI queue re-starvation — PR #206's unregistered runner label is the queue source - #214
Conversation
…gistered runner label is the queue source Main's shared vps-verify label already routes verify/Gitleaks across both runner instances (netcup-rs2000-tinystudio-verify1/2, live-verified). The re-starvation backing item 1126's closeout is PR #206's per-instance matrix: its tinystudio-io-verify1 leg matches no registered runner and queues forever on every push to that branch (9 queued runs, oldest 2h03m). Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Warning Review limit reached
Next review available in: 46 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (1)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
…ved by PR #214 close-out (#217) Live queue check (2026-08-14 23:50Z): 11 queued runs all seconds old on normal PR branches, zero runs on PR #206's branch, both vps-verify runners online and engaged (main push on verify1, PR #112 on verify2). The item's 2h03m / 9-run observation was PR #206's unregistered tinystudio-io-verify1 matrix label, closed out by PR #214; the queue has not re-starved since. Co-authored-by: nish3451 <nish3451@users.noreply.github.com> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
…ved (queue empty at 03:45Z) (#224) * docs(evidence): re-verify CI queue re-starvation item — already resolved, queue empty at 03:45Z Live check (2026-08-15 03:45Z): zero queued and zero in-progress runs, both vps-verify runners online and engaged (recent main push drained in ~16s, the 03:01Z 8-PR batch in <=9m across both runners). The item's 9-run / 2h03m observation was PR #206's unregistered tinystudio-io-verify1 matrix label, closed out by PR #214 and re-verified by PR #217; PR #206 is CLOSED, no open PR touches .github/workflows/*. No repo change required. Co-authored-by: CommandCodeBot <noreply@commandcode.ai> * docs(evidence): record 04:01Z wave observation — queue drained, PR #224 CI green Observed the 04:01Z concurrent 8-run wave live: 4 queued at peak, oldest wait ~14m, fully drained by 04:15:28Z. PR #224's own verify+Gitleaks passed (verify on netcup-rs2000-tinystudio-verify1, Gitleaks picked up at 04:10Z). Max wait orders of magnitude below the item's 2h03m; no re-starvation. Co-authored-by: CommandCodeBot <noreply@commandcode.ai> --------- Co-authored-by: nish3451 <nish3451@users.noreply.github.com> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
…ved (both runners online, queue drains in minutes) (#283) Re-confirms PRs #214/#217/#224: main's shared vps-verify label reaches both self-hosted runners; the ~60 queued observation was the 19:01Z wave of ~30 PRs × 2 jobs, drained in ~10 minutes with zero queue left. No workflow change required. Co-authored-by: minimax-vps <minimax-vps@local> Co-authored-by: CommandCodeBot <noreply@commandcode.ai>
1 participant
Closes the lane-1 re-starvation item: "The CI queue has re-starved past the closed 1126 acceptance: 9 runs queued up to 2h03m".
Root cause (live-verified)
Main already routes both required jobs across two runner instances via the shared
vps-verifylabel — runs execute on bothnetcup-rs2000-tinystudio-verify1and-verify2(verified on runs 31846412323 and 31846416272).The re-starvation is PR #206's per-instance matrix: it routes to label
tinystudio-io-verify1, which no runner registers (verify1's per-instance label istinystudio-io; verify2's istinystudio-io-verify2). Every push to that branch spawns 2 matrix legs that can never be scheduled — 7 of the 9 queued runs (18:00–21:01Z) are #206's branch. Its check rollup shows the verify1 legs QUEUED forever.Change
vps-verifylabel already engages both runners (the correct capacity fix for item 1126)..lane/reports/ci-starvation-requeue-cleanup-lane1-20260815.md.Verification
gh api .../actions/runners: verify1[self-hosted, Linux, X64, vps-verify, tinystudio-io], verify2[..., tinystudio-io-verify2]— notinystudio-io-verify1anywhere.gh run list --status queued: 9 queued, 7 from the ci: spread verify and Gitleaks across two runner instances #206 branch.e0ee160:verifysuccess,Gitleakssuccess.