JPDev@programming.dev to Programmer Humor@programming.dev · 7 months agoBug Fixingprogramming.devimagemessage-square74fedilinkarrow-up11.03Karrow-down119
arrow-up11.01Karrow-down1imageBug Fixingprogramming.devJPDev@programming.dev to Programmer Humor@programming.dev · 7 months agomessage-square74fedilink
minus-squaregandalf_der_12te@feddit.delinkfedilinkarrow-up1·edit-27 months agoEvery sufficiently complicated system is indistinguishable from being alive, and living beings need some warm-up time.
minus-squareCodeMonkey@programming.devlinkfedilinkarrow-up7·edit-27 months agoAll 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)
minus-squareDroggelbecher@lemmy.worldlinkfedilinkarrow-up1·7 months agoNot with code, but i write a lot of LaTeX and that often starts working on second compilation
Ever work?
Disturbingly, yes
Every sufficiently complicated system is indistinguishable from being alive, and living beings need some warm-up time.
All the time. Causes include:
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)
I mean
maybe
Not with code, but i write a lot of LaTeX and that often starts working on second compilation