Flaky tests, or why not to ignore mysteries
· 7 min read
I spent a few weeks earlier this year [tracking down][1] a set of flaky
end-to-end tests where bpftrace would occasionally cease to print output. I
had gotten as far as figuring out std::cout had [badbit][0] set after a write
but had run out of ideas on how to debug it. At the time, because I could not
reproduce it locally, I had assumed it was an oddity with pipes and CI and
given up.
Except bugs never go away. They only lay dormant.