alt Hacker News> Whenever a CI run fails, we can re-run it. If it passes the second time, we are sure it was flaky.
Or you have a concurrency issue in your production code?
Replies
fxwin • today at 3:00 PM
I thought that line was kind of funny: When a CI run fails, you don't rerun it and wait for the result, you rerun it and check why the original run failed in the meantime. Is it flaky? Is it a pipeline issue? Connectivity issue? Did some Key expire?
If you just rerun and don't go to find out what exactly caused CI to fail, you end up at the author's conclusion:
> (but it could also just have been flaky again).
cestith • today at 2:54 PM
It's possibly something else nondeterministic, which may be even more subtle from an external look than a race condition. That should be rare, but it’s been known to happen.
Then the test is still flaky. If there's a bug you want the test to consistently fail, not just sometimes.