I work in test automation, mostly browser tests, which means I have a collection of horror stories about tests that pass nine times and fail the tenth.
My current rule: a flaky test is a bug report with bad manners. Either the test has a hidden dependency (time, order, shared data, an animation), or the product has a real race that the test is brave enough to find occasionally. Deleting it is the one response that is never right.