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 ↗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
Release a distributed generation barrier: A barrier opens before enough distinct participants arrive · case 01
The barrier release operation is admitted even though a barrier opens before enough distinct participants arrive.
Release a distributed generation barrier: A barrier opens before enough distinct participants arrive · case 02
The barrier release operation is admitted even though a barrier opens before enough distinct participants arrive.
Release a distributed generation barrier: A barrier opens before enough distinct participants arrive · case 03
The barrier release operation is admitted even though a barrier opens before enough distinct participants arrive.
Release a distributed generation barrier: A barrier opens before enough distinct participants arrive · case 04
The barrier release operation is admitted even though a barrier opens before enough distinct participants arrive.
Release a distributed generation barrier: A barrier opens before enough distinct participants arrive · case 05
The barrier release operation is admitted even though a barrier opens before enough distinct participants arrive.
Release a distributed generation barrier: Arrivals from another barrier round count toward this round · case 01
The barrier release operation is admitted even though arrivals from another barrier round count toward this round.
Release a distributed generation barrier: Arrivals from another barrier round count toward this round · case 02
The barrier release operation is admitted even though arrivals from another barrier round count toward this round.
Release a distributed generation barrier: Arrivals from another barrier round count toward this round · case 03
The barrier release operation is admitted even though arrivals from another barrier round count toward this round.
Release a distributed generation barrier: Arrivals from another barrier round count toward this round · case 04
The barrier release operation is admitted even though arrivals from another barrier round count toward this round.
Release a distributed generation barrier: Arrivals from another barrier round count toward this round · case 05
The barrier release operation is admitted even though arrivals from another barrier round count toward this round.
Release a distributed generation barrier: Unregistered arrivals manufacture barrier completion · case 01
The barrier release operation is admitted even though unregistered arrivals manufacture barrier completion.
Release a distributed generation barrier: Unregistered arrivals manufacture barrier completion · case 02
The barrier release operation is admitted even though unregistered arrivals manufacture barrier completion.
Release a distributed generation barrier: Unregistered arrivals manufacture barrier completion · case 03
The barrier release operation is admitted even though unregistered arrivals manufacture barrier completion.
Release a distributed generation barrier: Unregistered arrivals manufacture barrier completion · case 04
The barrier release operation is admitted even though unregistered arrivals manufacture barrier completion.
Release a distributed generation barrier: Unregistered arrivals manufacture barrier completion · case 05
The barrier release operation is admitted even though unregistered arrivals manufacture barrier completion.
Release a distributed generation barrier: A failed barrier round is released as successful · case 01
The barrier release operation is admitted even though a failed barrier round is released as successful.
Release a distributed generation barrier: A failed barrier round is released as successful · case 02
The barrier release operation is admitted even though a failed barrier round is released as successful.
Release a distributed generation barrier: A failed barrier round is released as successful · case 03
The barrier release operation is admitted even though a failed barrier round is released as successful.
Release a distributed generation barrier: A failed barrier round is released as successful · case 04
The barrier release operation is admitted even though a failed barrier round is released as successful.
Release a distributed generation barrier: A failed barrier round is released as successful · case 05
The barrier release operation is admitted even though a failed barrier round is released as successful.
Release a distributed generation barrier: Waiters proceed before the generation release is durable · case 01
The barrier release operation is admitted even though waiters proceed before the generation release is durable.
Release a distributed generation barrier: Waiters proceed before the generation release is durable · case 02
The barrier release operation is admitted even though waiters proceed before the generation release is durable.
Release a distributed generation barrier: Waiters proceed before the generation release is durable · case 03
The barrier release operation is admitted even though waiters proceed before the generation release is durable.
Release a distributed generation barrier: Waiters proceed before the generation release is durable · case 04
The barrier release operation is admitted even though waiters proceed before the generation release is durable.
Release a distributed generation barrier: Waiters proceed before the generation release is durable · case 05
The barrier release operation is admitted even though waiters proceed before the generation release is durable.
Apply a remote conditional state update: A stale writer replaces a newer revision · case 01
The compare and swap operation is admitted even though a stale writer replaces a newer revision.
Apply a remote conditional state update: A stale writer replaces a newer revision · case 02
The compare and swap operation is admitted even though a stale writer replaces a newer revision.
Apply a remote conditional state update: A stale writer replaces a newer revision · case 03
The compare and swap operation is admitted even though a stale writer replaces a newer revision.
Apply a remote conditional state update: A stale writer replaces a newer revision · case 04
The compare and swap operation is admitted even though a stale writer replaces a newer revision.
Apply a remote conditional state update: A stale writer replaces a newer revision · case 05
The compare and swap operation is admitted even though a stale writer replaces a newer revision.
Apply a remote conditional state update: Delete and recreate produces an ABA match on reused revision · case 01
The compare and swap operation is admitted even though delete and recreate produces an aba match on reused revision.
Apply a remote conditional state update: Delete and recreate produces an ABA match on reused revision · case 02
The compare and swap operation is admitted even though delete and recreate produces an aba match on reused revision.
Apply a remote conditional state update: Delete and recreate produces an ABA match on reused revision · case 03
The compare and swap operation is admitted even though delete and recreate produces an aba match on reused revision.
Apply a remote conditional state update: Delete and recreate produces an ABA match on reused revision · case 04
The compare and swap operation is admitted even though delete and recreate produces an aba match on reused revision.
Apply a remote conditional state update: Delete and recreate produces an ABA match on reused revision · case 05
The compare and swap operation is admitted even though delete and recreate produces an aba match on reused revision.
Apply a remote conditional state update: A create-only write replaces an existing object · case 01
The compare and swap operation is admitted even though a create-only write replaces an existing object.
Apply a remote conditional state update: A create-only write replaces an existing object · case 02
The compare and swap operation is admitted even though a create-only write replaces an existing object.
Apply a remote conditional state update: A create-only write replaces an existing object · case 03
The compare and swap operation is admitted even though a create-only write replaces an existing object.
Apply a remote conditional state update: A create-only write replaces an existing object · case 04
The compare and swap operation is admitted even though a create-only write replaces an existing object.
Apply a remote conditional state update: A create-only write replaces an existing object · case 05
The compare and swap operation is admitted even though a create-only write replaces an existing object.
Apply a remote conditional state update: A conditional update performs an illegal lifecycle transition · case 01
The compare and swap operation is admitted even though a conditional update performs an illegal lifecycle transition.
Apply a remote conditional state update: A conditional update performs an illegal lifecycle transition · case 02
The compare and swap operation is admitted even though a conditional update performs an illegal lifecycle transition.
Apply a remote conditional state update: A conditional update performs an illegal lifecycle transition · case 03
The compare and swap operation is admitted even though a conditional update performs an illegal lifecycle transition.
Apply a remote conditional state update: A conditional update performs an illegal lifecycle transition · case 04
The compare and swap operation is admitted even though a conditional update performs an illegal lifecycle transition.
Apply a remote conditional state update: A conditional update performs an illegal lifecycle transition · case 05
The compare and swap operation is admitted even though a conditional update performs an illegal lifecycle transition.
Apply a remote conditional state update: A successful update fails to advance the revision · case 01
The compare and swap operation is admitted even though a successful update fails to advance the revision.
Apply a remote conditional state update: A successful update fails to advance the revision · case 02
The compare and swap operation is admitted even though a successful update fails to advance the revision.
Apply a remote conditional state update: A successful update fails to advance the revision · case 03
The compare and swap operation is admitted even though a successful update fails to advance the revision.
Apply a remote conditional state update: A successful update fails to advance the revision · case 04
The compare and swap operation is admitted even though a successful update fails to advance the revision.
Apply a remote conditional state update: A successful update fails to advance the revision · case 05
The compare and swap operation is admitted even though a successful update fails to advance the revision.
Commit a two-phase transaction: Commit proceeds while a participant has not prepared · case 01
The distributed transaction operation is admitted even though commit proceeds while a participant has not prepared.
Commit a two-phase transaction: Commit proceeds while a participant has not prepared · case 02
The distributed transaction operation is admitted even though commit proceeds while a participant has not prepared.
Commit a two-phase transaction: Commit proceeds while a participant has not prepared · case 03
The distributed transaction operation is admitted even though commit proceeds while a participant has not prepared.
Commit a two-phase transaction: Commit proceeds while a participant has not prepared · case 04
The distributed transaction operation is admitted even though commit proceeds while a participant has not prepared.
Commit a two-phase transaction: Commit proceeds while a participant has not prepared · case 05
The distributed transaction operation is admitted even though commit proceeds while a participant has not prepared.
Commit a two-phase transaction: A participant abort vote is ignored · case 01
The distributed transaction operation is admitted even though a participant abort vote is ignored.
Commit a two-phase transaction: A participant abort vote is ignored · case 02
The distributed transaction operation is admitted even though a participant abort vote is ignored.
Commit a two-phase transaction: A participant abort vote is ignored · case 03
The distributed transaction operation is admitted even though a participant abort vote is ignored.
Commit a two-phase transaction: A participant abort vote is ignored · case 04
The distributed transaction operation is admitted even though a participant abort vote is ignored.
Commit a two-phase transaction: A participant abort vote is ignored · case 05
The distributed transaction operation is admitted even though a participant abort vote is ignored.
Commit a two-phase transaction: Commit messages precede the durable coordinator decision · case 01
The distributed transaction operation is admitted even though commit messages precede the durable coordinator decision.
Commit a two-phase transaction: Commit messages precede the durable coordinator decision · case 02
The distributed transaction operation is admitted even though commit messages precede the durable coordinator decision.
Commit a two-phase transaction: Commit messages precede the durable coordinator decision · case 03
The distributed transaction operation is admitted even though commit messages precede the durable coordinator decision.
Commit a two-phase transaction: Commit messages precede the durable coordinator decision · case 04
The distributed transaction operation is admitted even though commit messages precede the durable coordinator decision.
Commit a two-phase transaction: Commit messages precede the durable coordinator decision · case 05
The distributed transaction operation is admitted even though commit messages precede the durable coordinator decision.
Commit a two-phase transaction: A newly enlisted participant is omitted from the decision · case 01
The distributed transaction operation is admitted even though a newly enlisted participant is omitted from the decision.
Commit a two-phase transaction: A newly enlisted participant is omitted from the decision · case 02
The distributed transaction operation is admitted even though a newly enlisted participant is omitted from the decision.
Commit a two-phase transaction: A newly enlisted participant is omitted from the decision · case 03
The distributed transaction operation is admitted even though a newly enlisted participant is omitted from the decision.
Commit a two-phase transaction: A newly enlisted participant is omitted from the decision · case 04
The distributed transaction operation is admitted even though a newly enlisted participant is omitted from the decision.
Commit a two-phase transaction: A newly enlisted participant is omitted from the decision · case 05
The distributed transaction operation is admitted even though a newly enlisted participant is omitted from the decision.
Commit a two-phase transaction: A recovered coordinator accepts the prior instance decision · case 01
The distributed transaction operation is admitted even though a recovered coordinator accepts the prior instance decision.
Commit a two-phase transaction: A recovered coordinator accepts the prior instance decision · case 02
The distributed transaction operation is admitted even though a recovered coordinator accepts the prior instance decision.
Commit a two-phase transaction: A recovered coordinator accepts the prior instance decision · case 03
The distributed transaction operation is admitted even though a recovered coordinator accepts the prior instance decision.
Commit a two-phase transaction: A recovered coordinator accepts the prior instance decision · case 04
The distributed transaction operation is admitted even though a recovered coordinator accepts the prior instance decision.
Commit a two-phase transaction: A recovered coordinator accepts the prior instance decision · case 05
The distributed transaction operation is admitted even though a recovered coordinator accepts the prior instance decision.
Resolve a prepared participant after recovery: An uncertain participant guesses commit without evidence · case 01
The prepared recovery operation is admitted even though an uncertain participant guesses commit without evidence.
Resolve a prepared participant after recovery: An uncertain participant guesses commit without evidence · case 02
The prepared recovery operation is admitted even though an uncertain participant guesses commit without evidence.
Resolve a prepared participant after recovery: An uncertain participant guesses commit without evidence · case 03
The prepared recovery operation is admitted even though an uncertain participant guesses commit without evidence.
Resolve a prepared participant after recovery: An uncertain participant guesses commit without evidence · case 04
The prepared recovery operation is admitted even though an uncertain participant guesses commit without evidence.
Resolve a prepared participant after recovery: An uncertain participant guesses commit without evidence · case 05
The prepared recovery operation is admitted even though an uncertain participant guesses commit without evidence.
Resolve a prepared participant after recovery: Recovery applies another transaction decision · case 01
The prepared recovery operation is admitted even though recovery applies another transaction decision.
Resolve a prepared participant after recovery: Recovery applies another transaction decision · case 02
The prepared recovery operation is admitted even though recovery applies another transaction decision.
Resolve a prepared participant after recovery: Recovery applies another transaction decision · case 03
The prepared recovery operation is admitted even though recovery applies another transaction decision.
Resolve a prepared participant after recovery: Recovery applies another transaction decision · case 04
The prepared recovery operation is admitted even though recovery applies another transaction decision.
Resolve a prepared participant after recovery: Recovery applies another transaction decision · case 05
The prepared recovery operation is admitted even though recovery applies another transaction decision.
Resolve a prepared participant after recovery: Recovery commits a transaction with no durable prepare record · case 01
The prepared recovery operation is admitted even though recovery commits a transaction with no durable prepare record.
Resolve a prepared participant after recovery: Recovery commits a transaction with no durable prepare record · case 02
The prepared recovery operation is admitted even though recovery commits a transaction with no durable prepare record.
Resolve a prepared participant after recovery: Recovery commits a transaction with no durable prepare record · case 03
The prepared recovery operation is admitted even though recovery commits a transaction with no durable prepare record.
Resolve a prepared participant after recovery: Recovery commits a transaction with no durable prepare record · case 04
The prepared recovery operation is admitted even though recovery commits a transaction with no durable prepare record.
Resolve a prepared participant after recovery: Recovery commits a transaction with no durable prepare record · case 05
The prepared recovery operation is admitted even though recovery commits a transaction with no durable prepare record.
Resolve a prepared participant after recovery: Recovery reverses a previously recorded final decision · case 01
The prepared recovery operation is admitted even though recovery reverses a previously recorded final decision.
Resolve a prepared participant after recovery: Recovery reverses a previously recorded final decision · case 02
The prepared recovery operation is admitted even though recovery reverses a previously recorded final decision.
Resolve a prepared participant after recovery: Recovery reverses a previously recorded final decision · case 03
The prepared recovery operation is admitted even though recovery reverses a previously recorded final decision.
Resolve a prepared participant after recovery: Recovery reverses a previously recorded final decision · case 04
The prepared recovery operation is admitted even though recovery reverses a previously recorded final decision.
Resolve a prepared participant after recovery: Recovery reverses a previously recorded final decision · case 05
The prepared recovery operation is admitted even though recovery reverses a previously recorded final decision.
Resolve a prepared participant after recovery: Prepared data becomes visible after losing its write locks · case 01
The prepared recovery operation is admitted even though prepared data becomes visible after losing its write locks.
Resolve a prepared participant after recovery: Prepared data becomes visible after losing its write locks · case 02
The prepared recovery operation is admitted even though prepared data becomes visible after losing its write locks.
Resolve a prepared participant after recovery: Prepared data becomes visible after losing its write locks · case 03
The prepared recovery operation is admitted even though prepared data becomes visible after losing its write locks.
Resolve a prepared participant after recovery: Prepared data becomes visible after losing its write locks · case 04
The prepared recovery operation is admitted even though prepared data becomes visible after losing its write locks.
Resolve a prepared participant after recovery: Prepared data becomes visible after losing its write locks · case 05
The prepared recovery operation is admitted even though prepared data becomes visible after losing its write locks.
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 ↗