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 coordination lease: One owner releases another owner lease · case 01
The lease release operation is admitted even though one owner releases another owner lease.
Release a coordination lease: One owner releases another owner lease · case 02
The lease release operation is admitted even though one owner releases another owner lease.
Release a coordination lease: One owner releases another owner lease · case 03
The lease release operation is admitted even though one owner releases another owner lease.
Release a coordination lease: One owner releases another owner lease · case 04
The lease release operation is admitted even though one owner releases another owner lease.
Release a coordination lease: One owner releases another owner lease · case 05
The lease release operation is admitted even though one owner releases another owner lease.
Release a coordination lease: A delayed release deletes a later acquisition by the same owner · case 01
The lease release operation is admitted even though a delayed release deletes a later acquisition by the same owner.
Release a coordination lease: A delayed release deletes a later acquisition by the same owner · case 02
The lease release operation is admitted even though a delayed release deletes a later acquisition by the same owner.
Release a coordination lease: A delayed release deletes a later acquisition by the same owner · case 03
The lease release operation is admitted even though a delayed release deletes a later acquisition by the same owner.
Release a coordination lease: A delayed release deletes a later acquisition by the same owner · case 04
The lease release operation is admitted even though a delayed release deletes a later acquisition by the same owner.
Release a coordination lease: A delayed release deletes a later acquisition by the same owner · case 05
The lease release operation is admitted even though a delayed release deletes a later acquisition by the same owner.
Release a coordination lease: A release applies to a different leased resource · case 01
The lease release operation is admitted even though a release applies to a different leased resource.
Release a coordination lease: A release applies to a different leased resource · case 02
The lease release operation is admitted even though a release applies to a different leased resource.
Release a coordination lease: A release applies to a different leased resource · case 03
The lease release operation is admitted even though a release applies to a different leased resource.
Release a coordination lease: A release applies to a different leased resource · case 04
The lease release operation is admitted even though a release applies to a different leased resource.
Release a coordination lease: A release applies to a different leased resource · case 05
The lease release operation is admitted even though a release applies to a different leased resource.
Release a coordination lease: Retried release decrements live-lease accounting twice · case 01
The lease release operation is admitted even though retried release decrements live-lease accounting twice.
Release a coordination lease: Retried release decrements live-lease accounting twice · case 02
The lease release operation is admitted even though retried release decrements live-lease accounting twice.
Release a coordination lease: Retried release decrements live-lease accounting twice · case 03
The lease release operation is admitted even though retried release decrements live-lease accounting twice.
Release a coordination lease: Retried release decrements live-lease accounting twice · case 04
The lease release operation is admitted even though retried release decrements live-lease accounting twice.
Release a coordination lease: Retried release decrements live-lease accounting twice · case 05
The lease release operation is admitted even though retried release decrements live-lease accounting twice.
Release a coordination lease: Release removes successor state after ownership transfer · case 01
The lease release operation is admitted even though release removes successor state after ownership transfer.
Release a coordination lease: Release removes successor state after ownership transfer · case 02
The lease release operation is admitted even though release removes successor state after ownership transfer.
Release a coordination lease: Release removes successor state after ownership transfer · case 03
The lease release operation is admitted even though release removes successor state after ownership transfer.
Release a coordination lease: Release removes successor state after ownership transfer · case 04
The lease release operation is admitted even though release removes successor state after ownership transfer.
Release a coordination lease: Release removes successor state after ownership transfer · case 05
The lease release operation is admitted even though release removes successor state after ownership transfer.
Steal a task from another worker deque: A thief executes a task already started by its owner · case 01
The work steal operation is admitted even though a thief executes a task already started by its owner.
Steal a task from another worker deque: A thief executes a task already started by its owner · case 02
The work steal operation is admitted even though a thief executes a task already started by its owner.
Steal a task from another worker deque: A thief executes a task already started by its owner · case 03
The work steal operation is admitted even though a thief executes a task already started by its owner.
Steal a task from another worker deque: A thief executes a task already started by its owner · case 04
The work steal operation is admitted even though a thief executes a task already started by its owner.
Steal a task from another worker deque: A thief executes a task already started by its owner · case 05
The work steal operation is admitted even though a thief executes a task already started by its owner.
Steal a task from another worker deque: A thief uses a deque position after the deque changed · case 01
The work steal operation is admitted even though a thief uses a deque position after the deque changed.
Steal a task from another worker deque: A thief uses a deque position after the deque changed · case 02
The work steal operation is admitted even though a thief uses a deque position after the deque changed.
Steal a task from another worker deque: A thief uses a deque position after the deque changed · case 03
The work steal operation is admitted even though a thief uses a deque position after the deque changed.
Steal a task from another worker deque: A thief uses a deque position after the deque changed · case 04
The work steal operation is admitted even though a thief uses a deque position after the deque changed.
Steal a task from another worker deque: A thief uses a deque position after the deque changed · case 05
The work steal operation is admitted even though a thief uses a deque position after the deque changed.
Steal a task from another worker deque: A worker steals a task requiring unsupported capabilities · case 01
The work steal operation is admitted even though a worker steals a task requiring unsupported capabilities.
Steal a task from another worker deque: A worker steals a task requiring unsupported capabilities · case 02
The work steal operation is admitted even though a worker steals a task requiring unsupported capabilities.
Steal a task from another worker deque: A worker steals a task requiring unsupported capabilities · case 03
The work steal operation is admitted even though a worker steals a task requiring unsupported capabilities.
Steal a task from another worker deque: A worker steals a task requiring unsupported capabilities · case 04
The work steal operation is admitted even though a worker steals a task requiring unsupported capabilities.
Steal a task from another worker deque: A worker steals a task requiring unsupported capabilities · case 05
The work steal operation is admitted even though a worker steals a task requiring unsupported capabilities.
Steal a task from another worker deque: A pinned task leaves its required execution locality · case 01
The work steal operation is admitted even though a pinned task leaves its required execution locality.
Steal a task from another worker deque: A pinned task leaves its required execution locality · case 02
The work steal operation is admitted even though a pinned task leaves its required execution locality.
Steal a task from another worker deque: A pinned task leaves its required execution locality · case 03
The work steal operation is admitted even though a pinned task leaves its required execution locality.
Steal a task from another worker deque: A pinned task leaves its required execution locality · case 04
The work steal operation is admitted even though a pinned task leaves its required execution locality.
Steal a task from another worker deque: A pinned task leaves its required execution locality · case 05
The work steal operation is admitted even though a pinned task leaves its required execution locality.
Steal a task from another worker deque: Work stealing exceeds the thief execution slots · case 01
The work steal operation is admitted even though work stealing exceeds the thief execution slots.
Steal a task from another worker deque: Work stealing exceeds the thief execution slots · case 02
The work steal operation is admitted even though work stealing exceeds the thief execution slots.
Steal a task from another worker deque: Work stealing exceeds the thief execution slots · case 03
The work steal operation is admitted even though work stealing exceeds the thief execution slots.
Steal a task from another worker deque: Work stealing exceeds the thief execution slots · case 04
The work steal operation is admitted even though work stealing exceeds the thief execution slots.
Steal a task from another worker deque: Work stealing exceeds the thief execution slots · case 05
The work steal operation is admitted even though work stealing exceeds the thief execution slots.
Complete a streaming checkpoint barrier: A checkpoint completes before every input channel reaches its barrier · case 01
The checkpoint barrier operation is admitted even though a checkpoint completes before every input channel reaches its barrier.
Complete a streaming checkpoint barrier: A checkpoint completes before every input channel reaches its barrier · case 02
The checkpoint barrier operation is admitted even though a checkpoint completes before every input channel reaches its barrier.
Complete a streaming checkpoint barrier: A checkpoint completes before every input channel reaches its barrier · case 03
The checkpoint barrier operation is admitted even though a checkpoint completes before every input channel reaches its barrier.
Complete a streaming checkpoint barrier: A checkpoint completes before every input channel reaches its barrier · case 04
The checkpoint barrier operation is admitted even though a checkpoint completes before every input channel reaches its barrier.
Complete a streaming checkpoint barrier: A checkpoint completes before every input channel reaches its barrier · case 05
The checkpoint barrier operation is admitted even though a checkpoint completes before every input channel reaches its barrier.
Complete a streaming checkpoint barrier: Barriers from different checkpoint rounds are combined · case 01
The checkpoint barrier operation is admitted even though barriers from different checkpoint rounds are combined.
Complete a streaming checkpoint barrier: Barriers from different checkpoint rounds are combined · case 02
The checkpoint barrier operation is admitted even though barriers from different checkpoint rounds are combined.
Complete a streaming checkpoint barrier: Barriers from different checkpoint rounds are combined · case 03
The checkpoint barrier operation is admitted even though barriers from different checkpoint rounds are combined.
Complete a streaming checkpoint barrier: Barriers from different checkpoint rounds are combined · case 04
The checkpoint barrier operation is admitted even though barriers from different checkpoint rounds are combined.
Complete a streaming checkpoint barrier: Barriers from different checkpoint rounds are combined · case 05
The checkpoint barrier operation is admitted even though barriers from different checkpoint rounds are combined.
Complete a streaming checkpoint barrier: A checkpoint is acknowledged while state exists only in memory · case 01
The checkpoint barrier operation is admitted even though a checkpoint is acknowledged while state exists only in memory.
Complete a streaming checkpoint barrier: A checkpoint is acknowledged while state exists only in memory · case 02
The checkpoint barrier operation is admitted even though a checkpoint is acknowledged while state exists only in memory.
Complete a streaming checkpoint barrier: A checkpoint is acknowledged while state exists only in memory · case 03
The checkpoint barrier operation is admitted even though a checkpoint is acknowledged while state exists only in memory.
Complete a streaming checkpoint barrier: A checkpoint is acknowledged while state exists only in memory · case 04
The checkpoint barrier operation is admitted even though a checkpoint is acknowledged while state exists only in memory.
Complete a streaming checkpoint barrier: A checkpoint is acknowledged while state exists only in memory · case 05
The checkpoint barrier operation is admitted even though a checkpoint is acknowledged while state exists only in memory.
Complete a streaming checkpoint barrier: Unaligned checkpoint omits messages already in transit · case 01
The checkpoint barrier operation is admitted even though unaligned checkpoint omits messages already in transit.
Complete a streaming checkpoint barrier: Unaligned checkpoint omits messages already in transit · case 02
The checkpoint barrier operation is admitted even though unaligned checkpoint omits messages already in transit.
Complete a streaming checkpoint barrier: Unaligned checkpoint omits messages already in transit · case 03
The checkpoint barrier operation is admitted even though unaligned checkpoint omits messages already in transit.
Complete a streaming checkpoint barrier: Unaligned checkpoint omits messages already in transit · case 04
The checkpoint barrier operation is admitted even though unaligned checkpoint omits messages already in transit.
Complete a streaming checkpoint barrier: Unaligned checkpoint omits messages already in transit · case 05
The checkpoint barrier operation is admitted even though unaligned checkpoint omits messages already in transit.
Complete a streaming checkpoint barrier: Upstream progress commits before the transactional sink prepares · case 01
The checkpoint barrier operation is admitted even though upstream progress commits before the transactional sink prepares.
Complete a streaming checkpoint barrier: Upstream progress commits before the transactional sink prepares · case 02
The checkpoint barrier operation is admitted even though upstream progress commits before the transactional sink prepares.
Complete a streaming checkpoint barrier: Upstream progress commits before the transactional sink prepares · case 03
The checkpoint barrier operation is admitted even though upstream progress commits before the transactional sink prepares.
Complete a streaming checkpoint barrier: Upstream progress commits before the transactional sink prepares · case 04
The checkpoint barrier operation is admitted even though upstream progress commits before the transactional sink prepares.
Complete a streaming checkpoint barrier: Upstream progress commits before the transactional sink prepares · case 05
The checkpoint barrier operation is admitted even though upstream progress commits before the transactional sink prepares.
Cut traffic to a replacement region: Cutover loses writes beyond the destination applied watermark · case 01
The regional cutover operation is admitted even though cutover loses writes beyond the destination applied watermark.
Cut traffic to a replacement region: Cutover loses writes beyond the destination applied watermark · case 02
The regional cutover operation is admitted even though cutover loses writes beyond the destination applied watermark.
Cut traffic to a replacement region: Cutover loses writes beyond the destination applied watermark · case 03
The regional cutover operation is admitted even though cutover loses writes beyond the destination applied watermark.
Cut traffic to a replacement region: Cutover loses writes beyond the destination applied watermark · case 04
The regional cutover operation is admitted even though cutover loses writes beyond the destination applied watermark.
Cut traffic to a replacement region: Cutover loses writes beyond the destination applied watermark · case 05
The regional cutover operation is admitted even though cutover loses writes beyond the destination applied watermark.
Cut traffic to a replacement region: Both regions accept writes during a single-writer cutover · case 01
The regional cutover operation is admitted even though both regions accept writes during a single-writer cutover.
Cut traffic to a replacement region: Both regions accept writes during a single-writer cutover · case 02
The regional cutover operation is admitted even though both regions accept writes during a single-writer cutover.
Cut traffic to a replacement region: Both regions accept writes during a single-writer cutover · case 03
The regional cutover operation is admitted even though both regions accept writes during a single-writer cutover.
Cut traffic to a replacement region: Both regions accept writes during a single-writer cutover · case 04
The regional cutover operation is admitted even though both regions accept writes during a single-writer cutover.
Cut traffic to a replacement region: Both regions accept writes during a single-writer cutover · case 05
The regional cutover operation is admitted even though both regions accept writes during a single-writer cutover.
Cut traffic to a replacement region: Application traffic arrives before regional dependencies are ready · case 01
The regional cutover operation is admitted even though application traffic arrives before regional dependencies are ready.
Cut traffic to a replacement region: Application traffic arrives before regional dependencies are ready · case 02
The regional cutover operation is admitted even though application traffic arrives before regional dependencies are ready.
Cut traffic to a replacement region: Application traffic arrives before regional dependencies are ready · case 03
The regional cutover operation is admitted even though application traffic arrives before regional dependencies are ready.
Cut traffic to a replacement region: Application traffic arrives before regional dependencies are ready · case 04
The regional cutover operation is admitted even though application traffic arrives before regional dependencies are ready.
Cut traffic to a replacement region: Application traffic arrives before regional dependencies are ready · case 05
The regional cutover operation is admitted even though application traffic arrives before regional dependencies are ready.
Cut traffic to a replacement region: Destination capacity cannot serve the transferred load · case 01
The regional cutover operation is admitted even though destination capacity cannot serve the transferred load.
Cut traffic to a replacement region: Destination capacity cannot serve the transferred load · case 02
The regional cutover operation is admitted even though destination capacity cannot serve the transferred load.
Cut traffic to a replacement region: Destination capacity cannot serve the transferred load · case 03
The regional cutover operation is admitted even though destination capacity cannot serve the transferred load.
Cut traffic to a replacement region: Destination capacity cannot serve the transferred load · case 04
The regional cutover operation is admitted even though destination capacity cannot serve the transferred load.
Cut traffic to a replacement region: Destination capacity cannot serve the transferred load · case 05
The regional cutover operation is admitted even though destination capacity cannot serve the transferred load.
Cut traffic to a replacement region: A delayed cutover command reverses a newer regional decision · case 01
The regional cutover operation is admitted even though a delayed cutover command reverses a newer regional decision.
Cut traffic to a replacement region: A delayed cutover command reverses a newer regional decision · case 02
The regional cutover operation is admitted even though a delayed cutover command reverses a newer regional decision.
Cut traffic to a replacement region: A delayed cutover command reverses a newer regional decision · case 03
The regional cutover operation is admitted even though a delayed cutover command reverses a newer regional decision.
Cut traffic to a replacement region: A delayed cutover command reverses a newer regional decision · case 04
The regional cutover operation is admitted even though a delayed cutover command reverses a newer regional decision.
Cut traffic to a replacement region: A delayed cutover command reverses a newer regional decision · case 05
The regional cutover operation is admitted even though a delayed cutover command reverses a newer regional decision.
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 ↗