0 min/mo
recoverable · across 3 patterns
Rough estimate from wall-clock run time at standard Linux pricing. Matrix/parallel jobs and your actual runners will differ.
13.0%
failure rate, 30d
38m
avg time to recover from a failure
12 workflows · 46 runs (1.5/day) · 3,347 CI-min (wall-clock) · ≈$20 at paid-Linux rates (30d)
Waste detected
Biggest wins first, each with the exact config fix.
No job timeout · Package Devcontainers Reusable
~0 min/mo
No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15No job timeout · CI Ubuntu Focal
~0 min/mo
No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15No job timeout · CI Ubuntu Jammy
~0 min/mo
No job sets `timeout-minutes`, so a hung step can run to GitHub's 6-hour default. Add `timeout-minutes` to each job.
jobs:
build:
runs-on: ubuntu-latest
timeout-minutes: 15Want this on every push?
This scorecard is a one-time snapshot. Install the free GitHub App to track this repo continuously: new regressions caught as they land, trends over time, on your public and private repos. Team adds the offending commit on the PR + Slack alerts.
Install & monitor this repo →Not ready to install? Get this report by email. No spam, unsubscribe anytime.
Add the badge to your README
Live CI-health badge → 
[](https://gitspider.com/scan/mc-rtc/mc-rtc-superbuild)