this post was submitted on 24 Jan 2024
991 points (98.2% liked)

Programmer Humor

18970 readers
475 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 7 months ago (3 children)
[–] [email protected] 5 points 7 months ago* (last edited 7 months ago)

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)

[–] [email protected] 3 points 7 months ago
[–] [email protected] 1 points 7 months ago

Not with code, but i write a lot of LaTeX and that often starts working on second compilation