Fix or quarantine flaky tests immediately

A test that fails randomly teaches everyone to click "re-run" without reading the failure. After a few weeks, real failures get re-run too, and the suite stops protecting you.

Treat a flaky test as a production bug:

1. When a test fails and then passes on retry with no code change, flag it.
2. Move it out of the blocking suite into a quarantine job that still runs and reports.
3. Assign an owner and a deadline; delete the test if nobody will fix it.
4. Fix the usual causes: shared state between tests, real clocks and timeouts, test order, network calls.

Automatic retries can hide flakiness entirely. If your tool retries failed tests, make it report the retry so you still see the pattern.

To check, count re-runs per week in your CI system. A rising number is the clearest sign of flakiness.