FlakeRadar

Shows whether a red pull request failed on a known flaky test or a real break, so you know when a re-run is worth it.

When a pull request goes red, it is hard to tell whether you broke something or hit a known flake, so people re-run CI and hope. FlakeRadar answers that on the pull request page. Click FlakeRadar on a GitHub pull request. It reads the failing checks, compares them with the recent runs and failing tests on the default branch, and gives each failing check one verdict: - Failing on the default branch: the branch is already red, so your change is not the cause. - Known flake: a matching test failed and then passed on the same commit before. - New failure: nothing in the history matches. Look at your change. - Inconclusive: there is not enough history to say. Each verdict comes with its evidence, with links to the runs behind it. For a known flake you can re-run only the failed jobs in one click: this is off until you turn it on in settings, and it needs a token with Actions read and write. Free works on public repositories with 30 days of history. Pro adds private repositories, 90 days of history, pinned repositories and flake alerts for $19/month. Pro also gives you a leaderboard of the flakiest jobs and tests in each pinned repository with a 30 and 90 day trend, notifications when a pinned repository spikes, and a CSV or Markdown export with a prefilled GitHub issue. Your data: - You add a GitHub token. It is stored on this device and is sent only to api.github.com. - FlakeRadar reads the address of the tab only after you click it on that tab. It reads no page content. - No analytics and no telemetry. FlakeRadar is not affiliated with or endorsed by GitHub.