Linked by Thom Holwerda on Mon 26th Feb 2018 18:13 UTC

Flaky failures are the worst. In this particular investigation, which spanned twenty months, we suspected hardware failure, compiler bugs, linker bugs, and other possibilities. Jumping too quickly to blaming hardware or build tools is a classic mistake, but in this case the mistake was that we weren’t thinking big enough. Yes, there was a linker bug, but we were also lucky enough to have hit a Windows kernel bug which is triggered by linkers!

Permalink for comment 654187
To read all comments associated with this story, please click here.
RE[3]: NT is still garbage
by avgalen on Tue 27th Feb 2018 19:42 UTC in reply to "RE[2]: NT is still garbage"
Member since:

You don't need a unit test

Maybe you didn't know it, but /s indicates sarcasm. Of course there wasn't a unit test for it because the circumstances are way to extreme for a unittest.

just a system design that doesn't constantly thrash disk like a retard.

It isn't a system design that trashes the disk like a retard. The guy is compiling Chrome which normally trashes the entire system (under Linux as well). The mentioned bug has the specifics that "if the system is under very heavy disk I/O load"

This architecturally can not happen on Linux.

Of course it can. There is nothing in the architecture of Linux that prevents 1 usermode process from taking up almost all the systems resources, effectively blocking a 2nd usermode process from performing well. Just like under Windows this is the normal behavior and as long as the OS is still capable of controlling both usermode processes they will both continue to run and do their work. Now there are certainly differences in how cpu/mem/io/caches are allocated but those differences cannot guarantee that both programs will get enough resources.

(here is a nice, although dated, architectural comparison with some scheduler characteristics:

Reply Parent Score: 4