retrace.

Your test suite is lying to you about what's broken.

Retrace reads a failing CI run and tells you whether it's a real regression or one of the five usual suspects behind flaky tests — before you re-run the pipeline for the third time.

failure_log.txt
0 characters
Classification

Paste a log and classify it — nothing's been analyzed yet.

— —

—

Results will appear here as each log is classified.

Recent classifications

Nothing classified yet this session — results you run above will show up here.

Five reasons a test fails that have nothing to do with your code

Retrace checks for these patterns before it ever suggests a real regression.

race condition
The assertion runs before an async operation — a render, a fetch, a state update — has actually finished. Passes locally, fails under CI load.
hard-coded wait
A fixed sleep() or timeout was tuned for one machine's speed. Slower runners blow past it; faster ones pass by luck, not correctness.
test pollution
Shared state — a database row, a global, a file on disk — leaks between tests. The failure depends on run order, not on what you changed.
external dependency
A third-party API, DNS lookup, or unmocked network call timed out. The test is honestly reporting that something outside your code was unavailable.
resource contention
Parallel workers on the same CI box compete for CPU, memory, or ports. The test is correct; the environment couldn't keep up.

Flaky tests cost trust, not just time

Once a suite fails intermittently, engineers stop reading the red X. They re-run first and investigate never. That habit is what actually breaks quality gates — not the flakiness itself.

Retrace doesn't try to fix your tests. It reads the log, the stack trace, and the run history, and tells you which of the five categories the failure most likely belongs to, with the reasoning shown — not just a label.

1 in 3
CI failures in active repos are flaky, not a real break — teams re-run first and investigate rarely.
< 2 min
Target time from a red pipeline to a classified cause, using only the log Retrace already has.

Point Retrace at your next red build.

CI integration for GitHub Actions and Jenkins. No card required.