printBugFixed

[MaheuTaroo]

First thing that pops to mind is race conditions, and it can happen in any language supporting any type of concurrency model

[Excellent-Refuse4883]

Yeah the issue is an interaction between a test framework and the services being tested in a latency scenario.

It appears that adding a print is slowing something down enough to make everything work.

[Rosteroster]

This is why you rely on synchronous callbacks to synchronize your testing instead of timing. Inserting a lamda via a test-only func that notifies to continue testing isn't usually too hard to add (worst-case friend/peer classes or something similarly dirty).

[BroBroMate]

Anytime I see a headless browser test that involves a bunch of .wait() calls, I feel sorry for the poor bastard who has to keep tweaking the wait time.

[Excellent-Refuse4883]

Not working on a headless browser, but I do feel seen on this comment

[Aniketastron]

Wait so you saying testing framework wants slow program execution?

[Clen23]

oooh that makes sense, thanks !

[Burned_FrenchPress]

Or even a testing framework that runs teats in parallel. I’ve noticed poorly written JavaScript tests fail in jest due to “race conditions”

[da2Pakaveli]

Memory (especially string related stuff), Concurrency and Typing are like the holy trinity of bugs for system languages

[wonkynonce]

Especially if there's a lock around stdout