· javascript

Your CI Retries are Hiding Real Bugs

If you start a Playwright project with npm init playwright@latest, the config it writes retries failing tests twice on CI.


That’s a sensible default for a browser suite. Now say a product bug makes one test fail one run in five.

With two retries, the test fails all three attempts only 0.2 × 0.2 × 0.2 = 0.8% of the time, so the build stays green in 99.2% of runs. I planted such a bug in a small service and ran its test suite 41,200 times.

Retries hid the bug about as often as the arithmetic predicts, while the test reports flagged the bug’s test as flaky in about one green build in five. Below are the numbers and the quarantine policy I’d build on them: Who owns a quarantined test, how long it may stay and how it gets out.

Earlier coverage

Related coverage

Also worth reading

  1. angular 22.3.0-next.4 released
  2. Britain on notice: AI-powered ransomware attacks to arrive by 2028
  3. The Dawn of the AIDLC: Insights From the All-Day AI Virtual Hackathon
  4. Fast Code, Slow Feedback: Fixing CI for the Age of AI Agents
  5. The New Frontier: Managing Human+AI Agent Software Development Teams