FAILURE MAP

Understand the failure.
Verify the repair.

Small, reproducible software failures. The broken implementation, the fix that didn’t work, and the one that passed—preserved together.

Explore the cases ↓How results are verified ↗
100840Executable case variants
20168Distinct failure mechanisms
302520Executed implementations
20168Open-access cases

WHAT THE ARCHIVE CONTAINS

100840 executable cases. 20168 are open.

Every case records the implementation that fails, the fix that did not work, and the repair that passed its checks—with recorded outputs and source hashes. This release adds 100840 cases across 20168 failure mechanisms and 254 domains.

The open tier gives you the failure and the unsuccessful fix for one case in every mechanism. The remaining 80672 cases, 5 variants per mechanism, are member-only: the verified repair, its recorded checks, and the full fixture suite are held in the member archive. Read the methodology ↗

A RECORD OF WHAT WENT WRONG

Browse the archive / 100840

Python · Standard library
REFERENCEFAILURE MECHANISMDOMAINACCESS
FA-401

Install a replicated state snapshot: A snapshot rolls back applied state · case 01

The snapshot install operation is admitted even though a snapshot rolls back applied state.

Replication● Open access↗
FA-402

Install a replicated state snapshot: A snapshot rolls back applied state · case 02

The snapshot install operation is admitted even though a snapshot rolls back applied state.

Replication◈ Members↗
FA-403

Install a replicated state snapshot: A snapshot rolls back applied state · case 03

The snapshot install operation is admitted even though a snapshot rolls back applied state.

Replication◈ Members↗
FA-404

Install a replicated state snapshot: A snapshot rolls back applied state · case 04

The snapshot install operation is admitted even though a snapshot rolls back applied state.

Replication◈ Members↗
FA-405

Install a replicated state snapshot: A snapshot rolls back applied state · case 05

The snapshot install operation is admitted even though a snapshot rolls back applied state.

Replication◈ Members↗
FA-406

Install a replicated state snapshot: An incomplete snapshot replaces the live state · case 01

The snapshot install operation is admitted even though an incomplete snapshot replaces the live state.

Replication● Open access↗
FA-407

Install a replicated state snapshot: An incomplete snapshot replaces the live state · case 02

The snapshot install operation is admitted even though an incomplete snapshot replaces the live state.

Replication◈ Members↗
FA-408

Install a replicated state snapshot: An incomplete snapshot replaces the live state · case 03

The snapshot install operation is admitted even though an incomplete snapshot replaces the live state.

Replication◈ Members↗
FA-409

Install a replicated state snapshot: An incomplete snapshot replaces the live state · case 04

The snapshot install operation is admitted even though an incomplete snapshot replaces the live state.

Replication◈ Members↗
FA-410

Install a replicated state snapshot: An incomplete snapshot replaces the live state · case 05

The snapshot install operation is admitted even though an incomplete snapshot replaces the live state.

Replication◈ Members↗
FA-411

Install a replicated state snapshot: Corrupt snapshot contents become authoritative · case 01

The snapshot install operation is admitted even though corrupt snapshot contents become authoritative.

Replication● Open access↗
FA-412

Install a replicated state snapshot: Corrupt snapshot contents become authoritative · case 02

The snapshot install operation is admitted even though corrupt snapshot contents become authoritative.

Replication◈ Members↗
FA-413

Install a replicated state snapshot: Corrupt snapshot contents become authoritative · case 03

The snapshot install operation is admitted even though corrupt snapshot contents become authoritative.

Replication◈ Members↗
FA-414

Install a replicated state snapshot: Corrupt snapshot contents become authoritative · case 04

The snapshot install operation is admitted even though corrupt snapshot contents become authoritative.

Replication◈ Members↗
FA-415

Install a replicated state snapshot: Corrupt snapshot contents become authoritative · case 05

The snapshot install operation is admitted even though corrupt snapshot contents become authoritative.

Replication◈ Members↗
FA-416

Install a replicated state snapshot: The snapshot omits its membership configuration · case 01

The snapshot install operation is admitted even though the snapshot omits its membership configuration.

Replication● Open access↗
FA-417

Install a replicated state snapshot: The snapshot omits its membership configuration · case 02

The snapshot install operation is admitted even though the snapshot omits its membership configuration.

Replication◈ Members↗
FA-418

Install a replicated state snapshot: The snapshot omits its membership configuration · case 03

The snapshot install operation is admitted even though the snapshot omits its membership configuration.

Replication◈ Members↗
FA-419

Install a replicated state snapshot: The snapshot omits its membership configuration · case 04

The snapshot install operation is admitted even though the snapshot omits its membership configuration.

Replication◈ Members↗
FA-420

Install a replicated state snapshot: The snapshot omits its membership configuration · case 05

The snapshot install operation is admitted even though the snapshot omits its membership configuration.

Replication◈ Members↗
FA-421

Install a replicated state snapshot: Snapshot metadata refers to a different log term · case 01

The snapshot install operation is admitted even though snapshot metadata refers to a different log term.

Replication● Open access↗
FA-422

Install a replicated state snapshot: Snapshot metadata refers to a different log term · case 02

The snapshot install operation is admitted even though snapshot metadata refers to a different log term.

Replication◈ Members↗
FA-423

Install a replicated state snapshot: Snapshot metadata refers to a different log term · case 03

The snapshot install operation is admitted even though snapshot metadata refers to a different log term.

Replication◈ Members↗
FA-424

Install a replicated state snapshot: Snapshot metadata refers to a different log term · case 04

The snapshot install operation is admitted even though snapshot metadata refers to a different log term.

Replication◈ Members↗
FA-425

Install a replicated state snapshot: Snapshot metadata refers to a different log term · case 05

The snapshot install operation is admitted even though snapshot metadata refers to a different log term.

Replication◈ Members↗
FA-426

Admit a leader log append: An old leader appends entries after a term change · case 01

The append log operation is admitted even though an old leader appends entries after a term change.

Consensus● Open access↗
FA-427

Admit a leader log append: An old leader appends entries after a term change · case 02

The append log operation is admitted even though an old leader appends entries after a term change.

Consensus◈ Members↗
FA-428

Admit a leader log append: An old leader appends entries after a term change · case 03

The append log operation is admitted even though an old leader appends entries after a term change.

Consensus◈ Members↗
FA-429

Admit a leader log append: An old leader appends entries after a term change · case 04

The append log operation is admitted even though an old leader appends entries after a term change.

Consensus◈ Members↗
FA-430

Admit a leader log append: An old leader appends entries after a term change · case 05

The append log operation is admitted even though an old leader appends entries after a term change.

Consensus◈ Members↗
FA-431

Admit a leader log append: An append references a missing predecessor index · case 01

The append log operation is admitted even though an append references a missing predecessor index.

Consensus● Open access↗
FA-432

Admit a leader log append: An append references a missing predecessor index · case 02

The append log operation is admitted even though an append references a missing predecessor index.

Consensus◈ Members↗
FA-433

Admit a leader log append: An append references a missing predecessor index · case 03

The append log operation is admitted even though an append references a missing predecessor index.

Consensus◈ Members↗
FA-434

Admit a leader log append: An append references a missing predecessor index · case 04

The append log operation is admitted even though an append references a missing predecessor index.

Consensus◈ Members↗
FA-435

Admit a leader log append: An append references a missing predecessor index · case 05

The append log operation is admitted even though an append references a missing predecessor index.

Consensus◈ Members↗
FA-436

Admit a leader log append: An append attaches to a conflicting predecessor term · case 01

The append log operation is admitted even though an append attaches to a conflicting predecessor term.

Consensus● Open access↗
FA-437

Admit a leader log append: An append attaches to a conflicting predecessor term · case 02

The append log operation is admitted even though an append attaches to a conflicting predecessor term.

Consensus◈ Members↗
FA-438

Admit a leader log append: An append attaches to a conflicting predecessor term · case 03

The append log operation is admitted even though an append attaches to a conflicting predecessor term.

Consensus◈ Members↗
FA-439

Admit a leader log append: An append attaches to a conflicting predecessor term · case 04

The append log operation is admitted even though an append attaches to a conflicting predecessor term.

Consensus◈ Members↗
FA-440

Admit a leader log append: An append attaches to a conflicting predecessor term · case 05

The append log operation is admitted even though an append attaches to a conflicting predecessor term.

Consensus◈ Members↗
FA-441

Admit a leader log append: Conflict truncation removes a committed entry · case 01

The append log operation is admitted even though conflict truncation removes a committed entry.

Consensus● Open access↗
FA-442

Admit a leader log append: Conflict truncation removes a committed entry · case 02

The append log operation is admitted even though conflict truncation removes a committed entry.

Consensus◈ Members↗
FA-443

Admit a leader log append: Conflict truncation removes a committed entry · case 03

The append log operation is admitted even though conflict truncation removes a committed entry.

Consensus◈ Members↗
FA-444

Admit a leader log append: Conflict truncation removes a committed entry · case 04

The append log operation is admitted even though conflict truncation removes a committed entry.

Consensus◈ Members↗
FA-445

Admit a leader log append: Conflict truncation removes a committed entry · case 05

The append log operation is admitted even though conflict truncation removes a committed entry.

Consensus◈ Members↗
FA-446

Admit a leader log append: Incoming log entries contain an index gap · case 01

The append log operation is admitted even though incoming log entries contain an index gap.

Consensus● Open access↗
FA-447

Admit a leader log append: Incoming log entries contain an index gap · case 02

The append log operation is admitted even though incoming log entries contain an index gap.

Consensus◈ Members↗
FA-448

Admit a leader log append: Incoming log entries contain an index gap · case 03

The append log operation is admitted even though incoming log entries contain an index gap.

Consensus◈ Members↗
FA-449

Admit a leader log append: Incoming log entries contain an index gap · case 04

The append log operation is admitted even though incoming log entries contain an index gap.

Consensus◈ Members↗
FA-450

Admit a leader log append: Incoming log entries contain an index gap · case 05

The append log operation is admitted even though incoming log entries contain an index gap.

Consensus◈ Members↗
FA-451

Serve a linearizable read at a confirmed index: A leader reads before committing an entry in its term · case 01

The read index operation is admitted even though a leader reads before committing an entry in its term.

Consensus● Open access↗
FA-452

Serve a linearizable read at a confirmed index: A leader reads before committing an entry in its term · case 02

The read index operation is admitted even though a leader reads before committing an entry in its term.

Consensus◈ Members↗
FA-453

Serve a linearizable read at a confirmed index: A leader reads before committing an entry in its term · case 03

The read index operation is admitted even though a leader reads before committing an entry in its term.

Consensus◈ Members↗
FA-454

Serve a linearizable read at a confirmed index: A leader reads before committing an entry in its term · case 04

The read index operation is admitted even though a leader reads before committing an entry in its term.

Consensus◈ Members↗
FA-455

Serve a linearizable read at a confirmed index: A leader reads before committing an entry in its term · case 05

The read index operation is admitted even though a leader reads before committing an entry in its term.

Consensus◈ Members↗
FA-456

Serve a linearizable read at a confirmed index: A read uses a response set lacking a voting majority · case 01

The read index operation is admitted even though a read uses a response set lacking a voting majority.

Consensus● Open access↗
FA-457

Serve a linearizable read at a confirmed index: A read uses a response set lacking a voting majority · case 02

The read index operation is admitted even though a read uses a response set lacking a voting majority.

Consensus◈ Members↗
FA-458

Serve a linearizable read at a confirmed index: A read uses a response set lacking a voting majority · case 03

The read index operation is admitted even though a read uses a response set lacking a voting majority.

Consensus◈ Members↗
FA-459

Serve a linearizable read at a confirmed index: A read uses a response set lacking a voting majority · case 04

The read index operation is admitted even though a read uses a response set lacking a voting majority.

Consensus◈ Members↗
FA-460

Serve a linearizable read at a confirmed index: A read uses a response set lacking a voting majority · case 05

The read index operation is admitted even though a read uses a response set lacking a voting majority.

Consensus◈ Members↗
FA-461

Serve a linearizable read at a confirmed index: The state machine has not applied the confirmed read index · case 01

The read index operation is admitted even though the state machine has not applied the confirmed read index.

Consensus● Open access↗
FA-462

Serve a linearizable read at a confirmed index: The state machine has not applied the confirmed read index · case 02

The read index operation is admitted even though the state machine has not applied the confirmed read index.

Consensus◈ Members↗
FA-463

Serve a linearizable read at a confirmed index: The state machine has not applied the confirmed read index · case 03

The read index operation is admitted even though the state machine has not applied the confirmed read index.

Consensus◈ Members↗
FA-464

Serve a linearizable read at a confirmed index: The state machine has not applied the confirmed read index · case 04

The read index operation is admitted even though the state machine has not applied the confirmed read index.

Consensus◈ Members↗
FA-465

Serve a linearizable read at a confirmed index: The state machine has not applied the confirmed read index · case 05

The read index operation is admitted even though the state machine has not applied the confirmed read index.

Consensus◈ Members↗
FA-466

Serve a linearizable read at a confirmed index: A delayed response confirms another read request · case 01

The read index operation is admitted even though a delayed response confirms another read request.

Consensus● Open access↗
FA-467

Serve a linearizable read at a confirmed index: A delayed response confirms another read request · case 02

The read index operation is admitted even though a delayed response confirms another read request.

Consensus◈ Members↗
FA-468

Serve a linearizable read at a confirmed index: A delayed response confirms another read request · case 03

The read index operation is admitted even though a delayed response confirms another read request.

Consensus◈ Members↗
FA-469

Serve a linearizable read at a confirmed index: A delayed response confirms another read request · case 04

The read index operation is admitted even though a delayed response confirms another read request.

Consensus◈ Members↗
FA-470

Serve a linearizable read at a confirmed index: A delayed response confirms another read request · case 05

The read index operation is admitted even though a delayed response confirms another read request.

Consensus◈ Members↗
FA-471

Serve a linearizable read at a confirmed index: A read completes after the leader observed a higher term · case 01

The read index operation is admitted even though a read completes after the leader observed a higher term.

Consensus● Open access↗
FA-472

Serve a linearizable read at a confirmed index: A read completes after the leader observed a higher term · case 02

The read index operation is admitted even though a read completes after the leader observed a higher term.

Consensus◈ Members↗
FA-473

Serve a linearizable read at a confirmed index: A read completes after the leader observed a higher term · case 03

The read index operation is admitted even though a read completes after the leader observed a higher term.

Consensus◈ Members↗
FA-474

Serve a linearizable read at a confirmed index: A read completes after the leader observed a higher term · case 04

The read index operation is admitted even though a read completes after the leader observed a higher term.

Consensus◈ Members↗
FA-475

Serve a linearizable read at a confirmed index: A read completes after the leader observed a higher term · case 05

The read index operation is admitted even though a read completes after the leader observed a higher term.

Consensus◈ Members↗
FA-476

Promise a proposal ballot: An acceptor promises a ballot below its durable promise · case 01

The acceptor prepare operation is admitted even though an acceptor promises a ballot below its durable promise.

Consensus● Open access↗
FA-477

Promise a proposal ballot: An acceptor promises a ballot below its durable promise · case 02

The acceptor prepare operation is admitted even though an acceptor promises a ballot below its durable promise.

Consensus◈ Members↗
FA-478

Promise a proposal ballot: An acceptor promises a ballot below its durable promise · case 03

The acceptor prepare operation is admitted even though an acceptor promises a ballot below its durable promise.

Consensus◈ Members↗
FA-479

Promise a proposal ballot: An acceptor promises a ballot below its durable promise · case 04

The acceptor prepare operation is admitted even though an acceptor promises a ballot below its durable promise.

Consensus◈ Members↗
FA-480

Promise a proposal ballot: An acceptor promises a ballot below its durable promise · case 05

The acceptor prepare operation is admitted even though an acceptor promises a ballot below its durable promise.

Consensus◈ Members↗
FA-481

Promise a proposal ballot: A prepare message targets a different consensus instance · case 01

The acceptor prepare operation is admitted even though a prepare message targets a different consensus instance.

Consensus● Open access↗
FA-482

Promise a proposal ballot: A prepare message targets a different consensus instance · case 02

The acceptor prepare operation is admitted even though a prepare message targets a different consensus instance.

Consensus◈ Members↗
FA-483

Promise a proposal ballot: A prepare message targets a different consensus instance · case 03

The acceptor prepare operation is admitted even though a prepare message targets a different consensus instance.

Consensus◈ Members↗
FA-484

Promise a proposal ballot: A prepare message targets a different consensus instance · case 04

The acceptor prepare operation is admitted even though a prepare message targets a different consensus instance.

Consensus◈ Members↗
FA-485

Promise a proposal ballot: A prepare message targets a different consensus instance · case 05

The acceptor prepare operation is admitted even though a prepare message targets a different consensus instance.

Consensus◈ Members↗
FA-486

Promise a proposal ballot: A promise response escapes before its durable write · case 01

The acceptor prepare operation is admitted even though a promise response escapes before its durable write.

Consensus● Open access↗
FA-487

Promise a proposal ballot: A promise response escapes before its durable write · case 02

The acceptor prepare operation is admitted even though a promise response escapes before its durable write.

Consensus◈ Members↗
FA-488

Promise a proposal ballot: A promise response escapes before its durable write · case 03

The acceptor prepare operation is admitted even though a promise response escapes before its durable write.

Consensus◈ Members↗
FA-489

Promise a proposal ballot: A promise response escapes before its durable write · case 04

The acceptor prepare operation is admitted even though a promise response escapes before its durable write.

Consensus◈ Members↗
FA-490

Promise a proposal ballot: A promise response escapes before its durable write · case 05

The acceptor prepare operation is admitted even though a promise response escapes before its durable write.

Consensus◈ Members↗
FA-491

Promise a proposal ballot: The response omits an already accepted value · case 01

The acceptor prepare operation is admitted even though the response omits an already accepted value.

Consensus● Open access↗
FA-492

Promise a proposal ballot: The response omits an already accepted value · case 02

The acceptor prepare operation is admitted even though the response omits an already accepted value.

Consensus◈ Members↗
FA-493

Promise a proposal ballot: The response omits an already accepted value · case 03

The acceptor prepare operation is admitted even though the response omits an already accepted value.

Consensus◈ Members↗
FA-494

Promise a proposal ballot: The response omits an already accepted value · case 04

The acceptor prepare operation is admitted even though the response omits an already accepted value.

Consensus◈ Members↗
FA-495

Promise a proposal ballot: The response omits an already accepted value · case 05

The acceptor prepare operation is admitted even though the response omits an already accepted value.

Consensus◈ Members↗
FA-496

Promise a proposal ballot: A prepare is counted under the wrong voting epoch · case 01

The acceptor prepare operation is admitted even though a prepare is counted under the wrong voting epoch.

Consensus● Open access↗
FA-497

Promise a proposal ballot: A prepare is counted under the wrong voting epoch · case 02

The acceptor prepare operation is admitted even though a prepare is counted under the wrong voting epoch.

Consensus◈ Members↗
FA-498

Promise a proposal ballot: A prepare is counted under the wrong voting epoch · case 03

The acceptor prepare operation is admitted even though a prepare is counted under the wrong voting epoch.

Consensus◈ Members↗
FA-499

Promise a proposal ballot: A prepare is counted under the wrong voting epoch · case 04

The acceptor prepare operation is admitted even though a prepare is counted under the wrong voting epoch.

Consensus◈ Members↗
FA-500

Promise a proposal ballot: A prepare is counted under the wrong voting epoch · case 05

The acceptor prepare operation is admitted even though a prepare is counted under the wrong voting epoch.

Consensus◈ Members↗

INSPECTABLE BY DESIGN

Every result has a runnable source.

Runnable implementations with recorded outputs, source hashes, and explicit contracts. Related variants share a failure mechanism and belong together in evaluation splits.

Read the methodology ↗