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 workflow dependency join: A join proceeds before every required predecessor completes · case 01
The workflow join operation is admitted even though a join proceeds before every required predecessor completes.
Release a workflow dependency join: A join proceeds before every required predecessor completes · case 02
The workflow join operation is admitted even though a join proceeds before every required predecessor completes.
Release a workflow dependency join: A join proceeds before every required predecessor completes · case 03
The workflow join operation is admitted even though a join proceeds before every required predecessor completes.
Release a workflow dependency join: A join proceeds before every required predecessor completes · case 04
The workflow join operation is admitted even though a join proceeds before every required predecessor completes.
Release a workflow dependency join: A join proceeds before every required predecessor completes · case 05
The workflow join operation is admitted even though a join proceeds before every required predecessor completes.
Release a workflow dependency join: A success-only join treats failed predecessors as successful · case 01
The workflow join operation is admitted even though a success-only join treats failed predecessors as successful.
Release a workflow dependency join: A success-only join treats failed predecessors as successful · case 02
The workflow join operation is admitted even though a success-only join treats failed predecessors as successful.
Release a workflow dependency join: A success-only join treats failed predecessors as successful · case 03
The workflow join operation is admitted even though a success-only join treats failed predecessors as successful.
Release a workflow dependency join: A success-only join treats failed predecessors as successful · case 04
The workflow join operation is admitted even though a success-only join treats failed predecessors as successful.
Release a workflow dependency join: A success-only join treats failed predecessors as successful · case 05
The workflow join operation is admitted even though a success-only join treats failed predecessors as successful.
Release a workflow dependency join: A completion from a previous loop iteration satisfies the join · case 01
The workflow join operation is admitted even though a completion from a previous loop iteration satisfies the join.
Release a workflow dependency join: A completion from a previous loop iteration satisfies the join · case 02
The workflow join operation is admitted even though a completion from a previous loop iteration satisfies the join.
Release a workflow dependency join: A completion from a previous loop iteration satisfies the join · case 03
The workflow join operation is admitted even though a completion from a previous loop iteration satisfies the join.
Release a workflow dependency join: A completion from a previous loop iteration satisfies the join · case 04
The workflow join operation is admitted even though a completion from a previous loop iteration satisfies the join.
Release a workflow dependency join: A completion from a previous loop iteration satisfies the join · case 05
The workflow join operation is admitted even though a completion from a previous loop iteration satisfies the join.
Release a workflow dependency join: Duplicate predecessor events release the join twice · case 01
The workflow join operation is admitted even though duplicate predecessor events release the join twice.
Release a workflow dependency join: Duplicate predecessor events release the join twice · case 02
The workflow join operation is admitted even though duplicate predecessor events release the join twice.
Release a workflow dependency join: Duplicate predecessor events release the join twice · case 03
The workflow join operation is admitted even though duplicate predecessor events release the join twice.
Release a workflow dependency join: Duplicate predecessor events release the join twice · case 04
The workflow join operation is admitted even though duplicate predecessor events release the join twice.
Release a workflow dependency join: Duplicate predecessor events release the join twice · case 05
The workflow join operation is admitted even though duplicate predecessor events release the join twice.
Release a workflow dependency join: A cancelled required branch is silently omitted · case 01
The workflow join operation is admitted even though a cancelled required branch is silently omitted.
Release a workflow dependency join: A cancelled required branch is silently omitted · case 02
The workflow join operation is admitted even though a cancelled required branch is silently omitted.
Release a workflow dependency join: A cancelled required branch is silently omitted · case 03
The workflow join operation is admitted even though a cancelled required branch is silently omitted.
Release a workflow dependency join: A cancelled required branch is silently omitted · case 04
The workflow join operation is admitted even though a cancelled required branch is silently omitted.
Release a workflow dependency join: A cancelled required branch is silently omitted · case 05
The workflow join operation is admitted even though a cancelled required branch is silently omitted.
Renew a durable activity heartbeat: A previous activity attempt keeps the new attempt alive · case 01
The workflow heartbeat operation is admitted even though a previous activity attempt keeps the new attempt alive.
Renew a durable activity heartbeat: A previous activity attempt keeps the new attempt alive · case 02
The workflow heartbeat operation is admitted even though a previous activity attempt keeps the new attempt alive.
Renew a durable activity heartbeat: A previous activity attempt keeps the new attempt alive · case 03
The workflow heartbeat operation is admitted even though a previous activity attempt keeps the new attempt alive.
Renew a durable activity heartbeat: A previous activity attempt keeps the new attempt alive · case 04
The workflow heartbeat operation is admitted even though a previous activity attempt keeps the new attempt alive.
Renew a durable activity heartbeat: A previous activity attempt keeps the new attempt alive · case 05
The workflow heartbeat operation is admitted even though a previous activity attempt keeps the new attempt alive.
Renew a durable activity heartbeat: A heartbeat resurrects an activity after its timeout · case 01
The workflow heartbeat operation is admitted even though a heartbeat resurrects an activity after its timeout.
Renew a durable activity heartbeat: A heartbeat resurrects an activity after its timeout · case 02
The workflow heartbeat operation is admitted even though a heartbeat resurrects an activity after its timeout.
Renew a durable activity heartbeat: A heartbeat resurrects an activity after its timeout · case 03
The workflow heartbeat operation is admitted even though a heartbeat resurrects an activity after its timeout.
Renew a durable activity heartbeat: A heartbeat resurrects an activity after its timeout · case 04
The workflow heartbeat operation is admitted even though a heartbeat resurrects an activity after its timeout.
Renew a durable activity heartbeat: A heartbeat resurrects an activity after its timeout · case 05
The workflow heartbeat operation is admitted even though a heartbeat resurrects an activity after its timeout.
Renew a durable activity heartbeat: A late heartbeat regresses the resumable progress marker · case 01
The workflow heartbeat operation is admitted even though a late heartbeat regresses the resumable progress marker.
Renew a durable activity heartbeat: A late heartbeat regresses the resumable progress marker · case 02
The workflow heartbeat operation is admitted even though a late heartbeat regresses the resumable progress marker.
Renew a durable activity heartbeat: A late heartbeat regresses the resumable progress marker · case 03
The workflow heartbeat operation is admitted even though a late heartbeat regresses the resumable progress marker.
Renew a durable activity heartbeat: A late heartbeat regresses the resumable progress marker · case 04
The workflow heartbeat operation is admitted even though a late heartbeat regresses the resumable progress marker.
Renew a durable activity heartbeat: A late heartbeat regresses the resumable progress marker · case 05
The workflow heartbeat operation is admitted even though a late heartbeat regresses the resumable progress marker.
Renew a durable activity heartbeat: Heartbeat detail exceeds durable history payload limits · case 01
The workflow heartbeat operation is admitted even though heartbeat detail exceeds durable history payload limits.
Renew a durable activity heartbeat: Heartbeat detail exceeds durable history payload limits · case 02
The workflow heartbeat operation is admitted even though heartbeat detail exceeds durable history payload limits.
Renew a durable activity heartbeat: Heartbeat detail exceeds durable history payload limits · case 03
The workflow heartbeat operation is admitted even though heartbeat detail exceeds durable history payload limits.
Renew a durable activity heartbeat: Heartbeat detail exceeds durable history payload limits · case 04
The workflow heartbeat operation is admitted even though heartbeat detail exceeds durable history payload limits.
Renew a durable activity heartbeat: Heartbeat detail exceeds durable history payload limits · case 05
The workflow heartbeat operation is admitted even though heartbeat detail exceeds durable history payload limits.
Renew a durable activity heartbeat: Heartbeat renewal extends beyond schedule-to-close timeout · case 01
The workflow heartbeat operation is admitted even though heartbeat renewal extends beyond schedule-to-close timeout.
Renew a durable activity heartbeat: Heartbeat renewal extends beyond schedule-to-close timeout · case 02
The workflow heartbeat operation is admitted even though heartbeat renewal extends beyond schedule-to-close timeout.
Renew a durable activity heartbeat: Heartbeat renewal extends beyond schedule-to-close timeout · case 03
The workflow heartbeat operation is admitted even though heartbeat renewal extends beyond schedule-to-close timeout.
Renew a durable activity heartbeat: Heartbeat renewal extends beyond schedule-to-close timeout · case 04
The workflow heartbeat operation is admitted even though heartbeat renewal extends beyond schedule-to-close timeout.
Renew a durable activity heartbeat: Heartbeat renewal extends beyond schedule-to-close timeout · case 05
The workflow heartbeat operation is admitted even though heartbeat renewal extends beyond schedule-to-close timeout.
Acquire a distributed mutex: Acquisition steals a currently held mutex · case 01
The distributed lock operation is admitted even though acquisition steals a currently held mutex.
Acquire a distributed mutex: Acquisition steals a currently held mutex · case 02
The distributed lock operation is admitted even though acquisition steals a currently held mutex.
Acquire a distributed mutex: Acquisition steals a currently held mutex · case 03
The distributed lock operation is admitted even though acquisition steals a currently held mutex.
Acquire a distributed mutex: Acquisition steals a currently held mutex · case 04
The distributed lock operation is admitted even though acquisition steals a currently held mutex.
Acquire a distributed mutex: Acquisition steals a currently held mutex · case 05
The distributed lock operation is admitted even though acquisition steals a currently held mutex.
Acquire a distributed mutex: A newcomer bypasses the oldest eligible waiter · case 01
The distributed lock operation is admitted even though a newcomer bypasses the oldest eligible waiter.
Acquire a distributed mutex: A newcomer bypasses the oldest eligible waiter · case 02
The distributed lock operation is admitted even though a newcomer bypasses the oldest eligible waiter.
Acquire a distributed mutex: A newcomer bypasses the oldest eligible waiter · case 03
The distributed lock operation is admitted even though a newcomer bypasses the oldest eligible waiter.
Acquire a distributed mutex: A newcomer bypasses the oldest eligible waiter · case 04
The distributed lock operation is admitted even though a newcomer bypasses the oldest eligible waiter.
Acquire a distributed mutex: A newcomer bypasses the oldest eligible waiter · case 05
The distributed lock operation is admitted even though a newcomer bypasses the oldest eligible waiter.
Acquire a distributed mutex: An expired session acquires a new mutex · case 01
The distributed lock operation is admitted even though an expired session acquires a new mutex.
Acquire a distributed mutex: An expired session acquires a new mutex · case 02
The distributed lock operation is admitted even though an expired session acquires a new mutex.
Acquire a distributed mutex: An expired session acquires a new mutex · case 03
The distributed lock operation is admitted even though an expired session acquires a new mutex.
Acquire a distributed mutex: An expired session acquires a new mutex · case 04
The distributed lock operation is admitted even though an expired session acquires a new mutex.
Acquire a distributed mutex: An expired session acquires a new mutex · case 05
The distributed lock operation is admitted even though an expired session acquires a new mutex.
Acquire a distributed mutex: Reacquisition reuses the previous fencing token · case 01
The distributed lock operation is admitted even though reacquisition reuses the previous fencing token.
Acquire a distributed mutex: Reacquisition reuses the previous fencing token · case 02
The distributed lock operation is admitted even though reacquisition reuses the previous fencing token.
Acquire a distributed mutex: Reacquisition reuses the previous fencing token · case 03
The distributed lock operation is admitted even though reacquisition reuses the previous fencing token.
Acquire a distributed mutex: Reacquisition reuses the previous fencing token · case 04
The distributed lock operation is admitted even though reacquisition reuses the previous fencing token.
Acquire a distributed mutex: Reacquisition reuses the previous fencing token · case 05
The distributed lock operation is admitted even though reacquisition reuses the previous fencing token.
Acquire a distributed mutex: A request acquires a lock in another coordination namespace · case 01
The distributed lock operation is admitted even though a request acquires a lock in another coordination namespace.
Acquire a distributed mutex: A request acquires a lock in another coordination namespace · case 02
The distributed lock operation is admitted even though a request acquires a lock in another coordination namespace.
Acquire a distributed mutex: A request acquires a lock in another coordination namespace · case 03
The distributed lock operation is admitted even though a request acquires a lock in another coordination namespace.
Acquire a distributed mutex: A request acquires a lock in another coordination namespace · case 04
The distributed lock operation is admitted even though a request acquires a lock in another coordination namespace.
Acquire a distributed mutex: A request acquires a lock in another coordination namespace · case 05
The distributed lock operation is admitted even though a request acquires a lock in another coordination namespace.
Grant permits from a distributed semaphore: The grant exceeds the configured total permit count · case 01
The semaphore grant operation is admitted even though the grant exceeds the configured total permit count.
Grant permits from a distributed semaphore: The grant exceeds the configured total permit count · case 02
The semaphore grant operation is admitted even though the grant exceeds the configured total permit count.
Grant permits from a distributed semaphore: The grant exceeds the configured total permit count · case 03
The semaphore grant operation is admitted even though the grant exceeds the configured total permit count.
Grant permits from a distributed semaphore: The grant exceeds the configured total permit count · case 04
The semaphore grant operation is admitted even though the grant exceeds the configured total permit count.
Grant permits from a distributed semaphore: The grant exceeds the configured total permit count · case 05
The semaphore grant operation is admitted even though the grant exceeds the configured total permit count.
Grant permits from a distributed semaphore: A zero or negative grant corrupts permit accounting · case 01
The semaphore grant operation is admitted even though a zero or negative grant corrupts permit accounting.
Grant permits from a distributed semaphore: A zero or negative grant corrupts permit accounting · case 02
The semaphore grant operation is admitted even though a zero or negative grant corrupts permit accounting.
Grant permits from a distributed semaphore: A zero or negative grant corrupts permit accounting · case 03
The semaphore grant operation is admitted even though a zero or negative grant corrupts permit accounting.
Grant permits from a distributed semaphore: A zero or negative grant corrupts permit accounting · case 04
The semaphore grant operation is admitted even though a zero or negative grant corrupts permit accounting.
Grant permits from a distributed semaphore: A zero or negative grant corrupts permit accounting · case 05
The semaphore grant operation is admitted even though a zero or negative grant corrupts permit accounting.
Grant permits from a distributed semaphore: A retried grant allocates the same request twice · case 01
The semaphore grant operation is admitted even though a retried grant allocates the same request twice.
Grant permits from a distributed semaphore: A retried grant allocates the same request twice · case 02
The semaphore grant operation is admitted even though a retried grant allocates the same request twice.
Grant permits from a distributed semaphore: A retried grant allocates the same request twice · case 03
The semaphore grant operation is admitted even though a retried grant allocates the same request twice.
Grant permits from a distributed semaphore: A retried grant allocates the same request twice · case 04
The semaphore grant operation is admitted even though a retried grant allocates the same request twice.
Grant permits from a distributed semaphore: A retried grant allocates the same request twice · case 05
The semaphore grant operation is admitted even though a retried grant allocates the same request twice.
Grant permits from a distributed semaphore: A later small request overtakes the queued weighted head · case 01
The semaphore grant operation is admitted even though a later small request overtakes the queued weighted head.
Grant permits from a distributed semaphore: A later small request overtakes the queued weighted head · case 02
The semaphore grant operation is admitted even though a later small request overtakes the queued weighted head.
Grant permits from a distributed semaphore: A later small request overtakes the queued weighted head · case 03
The semaphore grant operation is admitted even though a later small request overtakes the queued weighted head.
Grant permits from a distributed semaphore: A later small request overtakes the queued weighted head · case 04
The semaphore grant operation is admitted even though a later small request overtakes the queued weighted head.
Grant permits from a distributed semaphore: A later small request overtakes the queued weighted head · case 05
The semaphore grant operation is admitted even though a later small request overtakes the queued weighted head.
Grant permits from a distributed semaphore: A session destroyed while waiting receives permits · case 01
The semaphore grant operation is admitted even though a session destroyed while waiting receives permits.
Grant permits from a distributed semaphore: A session destroyed while waiting receives permits · case 02
The semaphore grant operation is admitted even though a session destroyed while waiting receives permits.
Grant permits from a distributed semaphore: A session destroyed while waiting receives permits · case 03
The semaphore grant operation is admitted even though a session destroyed while waiting receives permits.
Grant permits from a distributed semaphore: A session destroyed while waiting receives permits · case 04
The semaphore grant operation is admitted even though a session destroyed while waiting receives permits.
Grant permits from a distributed semaphore: A session destroyed while waiting receives permits · case 05
The semaphore grant operation is admitted even though a session destroyed while waiting receives permits.
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 ↗