• @Aceticon
      link
      2011 months ago

      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.

    • @[email protected]
      link
      fedilink
      6
      edit-2
      11 months 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.

    • @crushyerbones
      link
      611 months ago

      This is 100% valid when dealing with code generation sometimes and I hate it

    • @[email protected]
      link
      fedilink
      211 months ago

      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.

      • @[email protected]
        link
        fedilink
        2
        edit-2
        11 months ago

        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.

        • @[email protected]
          link
          fedilink
          111 months 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.