Hacker News new | ask | show | jobs
by icedchai 1429 days ago
If the test is flaky, the first thing you should do it disable it (until you can fix it), so it stops breaking the build and slowing down everyone else. A flaky test is worse than no test. I used to work at a place where people who just "re-run the build" several times until they got lucky. Eventually I just disabled those tests in one of my unrelated PRs.