pitlaneCI on self-hosted runners
Median target metEvery GitHub Actions job that lands on a pitlane runner is measured from the moment it queues to the moment it runs. These are the last 24h across every repository the runners serve, rewritten every minute.
Queue wait, median
target under 5 s
Queue wait, p90
target under 30 s
Jobs in the window
2,152 finished, 2 failed with the runner suspected
What the numbers mean
The queue wait is the time between GitHub creating a job and a runner starting it: the whole of the wait a developer sees before their logs begin. The median is the typical job; p90 is the slow tail, the wait nine jobs in ten beat. The targets are the ones the runners are tuned to, and the badge turns from green to grey the moment the supervisor stops writing.
A job the runner itself is suspected of failing counts as runner-suspected; the rest of the failures belong to the code under test.
Put it on a README
The badge is fetched live and never committed. It links back to this page.
[](https://pitlane.askalf.org/)