docs(evidence): re-verify CI queue re-starvation item — already resolved (queue empty at 03:45Z) - #224
Conversation
…ved, 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>
|
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: 37 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 |
… 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>
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
…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
Summary
Re-verification of improvement-loop item: "The CI queue has re-starved past the closed 1126 acceptance: 9 runs queued up to 2h03m".
Verdict: already resolved — no repo change required. Confirms PR #214 and PR #217.
Live evidence (2026-08-15 ~03:45Z, GitHub API)
netcup-rs2000-tinystudio-verify1(self-hosted Linux X64 vps-verify tinystudio-io) andnetcup-rs2000-tinystudio-verify2(self-hosted Linux X64 vps-verify tinystudio-io-verify2)ci.ymlandsecret-scan.ymlboth route through sharedvps-verifylabel — engages both runners.github/workflows/*(all 14 open PRs scanned)tinystudio-io-verify1matrix label that caused the zombie queue) is CLOSED, not mergedRoot cause (prior close-outs)
The 9-run / 2h03m queue was PR #206's per-instance matrix routing its
verify/Gitleakslegs to a label no registered runner carries; every push to its branch spawned 2 zombie jobs. The intended capacity outcome is already achieved by main's shared-label routing.Files
.lane/reports/ci-starvation-rereverify-lane1-20260815.md