A flaky test passes and fails on the same code. Nothing changed, but the build is red. You click "re-run", it goes green, and you move on.

I read about a dev team whose tests kept failing on the same commit. They spent a lot of time re-running and investigating why it happened.

So I started FlakeSince , a free, self-hosted tool that finds flaky tests in CI. Most free tools tell you a test is flaky today . FlakeSince keeps the pass/fail history of every normal CI run, so it can also estimate since which commit a test became flaky, without re-running anything.

How it works

A GitHub Action uploads the JUnit XML files from your test run (Gradle, Maven Surefire, pytest or go-junit-report).

A small Go ingest service checks the API key, parses the XML and puts one message per CI run on a queue. It answers 202 Accepted as soon as the run is safely queued.

Amazon SQS holds the message.…