▲ 1029 ▼ Bug Fixing (programming.dev) submitted 2 years ago by JPDev@programming.dev to c/programmer_humor@programming.dev 73 comments fedilink hide all child comments
[–] Blackmist@feddit.uk 61 points 2 years ago (8 children) Yeah, but sometimes it works. permalink fedilink source hideshow 16 child comments replies: [–] Aceticon@lemmy.world 20 points 2 years ago (1 child) It's even worse then: that means it's probably a race condition and do you really want to run the risk of having it randomly fail in Production or during an important presentation? Also race conditions generally are way harder to figure out and fix that the more "reliable" kind of bug. permalink fedilink source parent hideshow 2 child comments replies: [–] dev_null@lemmy.ml 1 point 2 years ago Or it was an issue with code generation, or something in the environment changed. permalink fedilink source parent [–] noddy@beehaw.org 9 points 2 years ago Good luck figuring out why it sometimes doesn't work 🙃 permalink fedilink source parent [–] CanadaPlus@futurology.today 9 points 2 years ago Mmm, race conditions, just like mama used to make. permalink fedilink source parent [–] Octopus1348@lemy.lol 7 points 2 years ago* There was that kind of bug in Linux and a person restarted it idk how much (iirc around 2k times) just to debug it. permalink fedilink source parent [–] crushyerbones@lemmy.world 6 points 2 years ago This is 100% valid when dealing with code generation sometimes and I hate it permalink fedilink source parent [–] KairuByte@lemmy.dbzer0.com 2 points 2 years ago (1 child) Legit happens without a race condition if you’ve improperly linked libraries that need to be built in a specific order. I’ve seen more than one solution that needed to be run multiple times, or built project by project, in order to work. permalink fedilink source parent hideshow 2 child comments replies: [–] abraxas@sh.itjust.works 2 points 2 years ago* (1 child) Isn't that the definition of a race condition, though? In this case, the builds are racing and your success is tied to the builds happening to happen at the right times. Or do you mean "builds 1 and 2 kick off at the same time, but build 1 fails unless build 2 is done. If you run it twice, build 2 does "no change" and you're fine"? Then that's legit. permalink fedilink source parent hideshow 2 child comments replies: [–] KairuByte@lemmy.dbzer0.com 1 point 2 years ago Yup, it’s that second one. 0% chance of success until all dependencies are built, then the final run has a 100% chance to work. permalink fedilink source parent [+] Theharpyeagle@lemmy.world 1 point 2 years ago [deleted] permalink fedilink source parent [–] wewlad@hexbear.net 1 point 2 years ago We call this sort of test "fuzzy". If it's really bad they call it by my own personal identifier of "unstable". permalink fedilink source parent
[–] Aceticon@lemmy.world 20 points 2 years ago (1 child) It's even worse then: that means it's probably a race condition and do you really want to run the risk of having it randomly fail in Production or during an important presentation? Also race conditions generally are way harder to figure out and fix that the more "reliable" kind of bug. permalink fedilink source parent hideshow 2 child comments replies: [–] dev_null@lemmy.ml 1 point 2 years ago Or it was an issue with code generation, or something in the environment changed. permalink fedilink source parent
[–] dev_null@lemmy.ml 1 point 2 years ago Or it was an issue with code generation, or something in the environment changed. permalink fedilink source parent
[–] noddy@beehaw.org 9 points 2 years ago Good luck figuring out why it sometimes doesn't work 🙃 permalink fedilink source parent
[–] CanadaPlus@futurology.today 9 points 2 years ago Mmm, race conditions, just like mama used to make. permalink fedilink source parent
[–] Octopus1348@lemy.lol 7 points 2 years ago* There was that kind of bug in Linux and a person restarted it idk how much (iirc around 2k times) just to debug it. permalink fedilink source parent
[–] crushyerbones@lemmy.world 6 points 2 years ago This is 100% valid when dealing with code generation sometimes and I hate it permalink fedilink source parent
[–] KairuByte@lemmy.dbzer0.com 2 points 2 years ago (1 child) Legit happens without a race condition if you’ve improperly linked libraries that need to be built in a specific order. I’ve seen more than one solution that needed to be run multiple times, or built project by project, in order to work. permalink fedilink source parent hideshow 2 child comments replies: [–] abraxas@sh.itjust.works 2 points 2 years ago* (1 child) Isn't that the definition of a race condition, though? In this case, the builds are racing and your success is tied to the builds happening to happen at the right times. Or do you mean "builds 1 and 2 kick off at the same time, but build 1 fails unless build 2 is done. If you run it twice, build 2 does "no change" and you're fine"? Then that's legit. permalink fedilink source parent hideshow 2 child comments replies: [–] KairuByte@lemmy.dbzer0.com 1 point 2 years ago Yup, it’s that second one. 0% chance of success until all dependencies are built, then the final run has a 100% chance to work. permalink fedilink source parent
[–] abraxas@sh.itjust.works 2 points 2 years ago* (1 child) Isn't that the definition of a race condition, though? In this case, the builds are racing and your success is tied to the builds happening to happen at the right times. Or do you mean "builds 1 and 2 kick off at the same time, but build 1 fails unless build 2 is done. If you run it twice, build 2 does "no change" and you're fine"? Then that's legit. permalink fedilink source parent hideshow 2 child comments replies: [–] KairuByte@lemmy.dbzer0.com 1 point 2 years ago Yup, it’s that second one. 0% chance of success until all dependencies are built, then the final run has a 100% chance to work. permalink fedilink source parent
[–] KairuByte@lemmy.dbzer0.com 1 point 2 years ago Yup, it’s that second one. 0% chance of success until all dependencies are built, then the final run has a 100% chance to work. permalink fedilink source parent
[–] wewlad@hexbear.net 1 point 2 years ago We call this sort of test "fuzzy". If it's really bad they call it by my own personal identifier of "unstable". permalink fedilink source parent