How Many CI Minutes Are Flaky Tests Wasting?

How to Use This Tool

Quantify rerun capacity consumed by nondeterministic test failures. Flaky failures feel like isolated annoyances, but their reruns consume build capacity and interrupt engineers across every pull request.

Why Flaky Test Waste needs more than a raw total

Run count multiplied by observed flake incidence and rerun duration gives a conservative capacity cost before engineering interruption is added. For this page, the useful comparison is estimated wasted ci minutes, not whichever input happens to be largest. The Flaky Test Waste result answers the decision in the heading and should not be reused as a score for a different workflow.

The exact Flaky Test Waste formula

Wasted CI minutes equal workflow runs multiplied by flaky-failure rate and average rerun duration. The visible fields are CI workflow runs, Flaky-failure rate and Average rerun duration. For Flaky Test Waste, read each printed unit before entry and make the values describe one transaction, cohort or reporting window. If those scopes differ, the displayed estimated wasted ci minutes may be arithmetically valid but operationally meaningless.

Interpreting estimated wasted ci minutes

Rank the tests responsible for the most rerun minutes and quarantine only with an owner and removal date while root causes are fixed. The ten-percent comparison is deliberately narrow: it tests the influence of ci workflow runs and is neither a forecast nor a confidence interval. Preserve the values used, their dates and the resulting decision so a later reviewer can reproduce why Flaky Test Waste supported the choice.

What this Flaky Test Waste model leaves out

This excludes engineer waiting time, parallel-run billing differences, false investigations and failures that require more than one rerun. That is where Flaky Test Waste stops being trustworthy. If an excluded factor could reverse estimated wasted ci minutes, extend the model explicitly or use the authoritative account system instead of hiding the factor inside an unexplained adjustment.

Evidence and independent verification

The reference reviewed for Flaky Test Waste is GitHub Docs — Managing billing for GitHub Actions. GitHub Docs — Managing billing for GitHub Actions supports the named definition or rule but does not supply private values for estimated wasted ci minutes. Before acting on the result, reconcile the worked example with the relevant dashboard, invoice, export or measurement.

Private, reproducible calculation

Flaky Test Waste runs its arithmetic in the current browser tab and requests no login or API key. That keeps the Flaky Test Waste inputs away from the site's calculation server, while leaving the user responsible for detecting stale data or a changed platform rule. When an assumption changes, reopen GitHub Docs — Managing billing for GitHub Actions and rerun the saved Flaky Test Waste scenario.