A Go test that passed 40,000 times, then lost a write under load
Why timing bugs in distributed systems hide from normal tests, and how deterministic simulation testing makes them replayable

Series
Bugs in distributed systems often fail a test once and never again. This series is about catching them in Go so that every failure replays exactly from a seed. It follows faultline, the open-source deterministic simulation testing tool I'm building, from the problem to real runs against etcd/raft.

Why timing bugs in distributed systems hide from normal tests, and how deterministic simulation testing makes them replayable

A shorter election timeout tested under faults in faultline v0.1.1, with the one seed that took 1.78 seconds replayed
