You're viewing a single thread.
View all comments
75
comments
Ever work?
2 0 ReplyDisturbingly, yes
11 0 ReplyEvery sufficiently complicated system is indistinguishable from being alive, and living beings need some warm-up time.
1 0 Reply
All the time. Causes include:
- Test depends on an external system (database, package manager)
- Race conditions
- Failing the test cleared bad state (test expects test data not to be in the system and clears it when it exits)
- Failing test set up unknown prerequisite (Build 2 tests depends on changes in Build 1 but build system built them out of order)
- External forces messing with the test runner (test machine going to sleep or running out of resources)
We call those "flaky tests" and only fail a build if a given test cannot pass after 2 retries. (We also flag the test runs for manual review)
7 0 ReplyI mean
maybe
4 0 ReplyNot with code, but i write a lot of LaTeX and that often starts working on second compilation
1 0 Reply
You've viewed 75 comments.
Scroll to top