Repository navigation
fleet-report: count jobs running inside runs GitHub still lists as queued - #34
Merged
Merged
Conversation
…eued GitHub keeps a run queued while some of its jobs run and others wait for a runner, for minutes. Reading in-progress runs alone saw 14.75 jobs on average while 19.25 ran (8 live rounds, 2026-10-31), so the runners-in-use line and the measured CI hours read low. Read queued runs' jobs too and record the share in running_in_queued_runs so older readings can be told apart. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Problem
occupancy_readingcounts jobs only in runs with statusin_progress. GitHub keeps a runqueuedwhile some of its jobs are running and others still wait for a runner, for minutes at a time. Those running jobs were never counted, so "Runners in use while work waits" sat near 14 of 20 and the measured CI hours read low.Evidence (2026-10-31)
queuedruns, 19.25 in total.Change
running.running_in_queued_runsfield, per repo and in total, so readings from before and after can be told apart.queuednow also includes waiting jobs from queued runs, so it rises from this reading on.Not fixed here
Checks
pytest tests: 162 passed, 5 skipped. The same read in thechurnPR gave old 15.4, new 19.5, uncapped 20.25 on live GitHub.Rollout
No install step: the sampler on nyx fetches
fleet_report.pyfrommainon every run, so this applies at the first reading after merge.Cost
One more API call per queued run per reading, about 15 to 60 calls every 15 minutes when busy.
Companion: squid-protocol/promoter-bot
fix/occupancy-queued-runs.🤖 Generated with Claude Code