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-46501

Copy-on-write treats two owners as exclusive · case 01

Copy-on-write treats two owners as exclusive.

Bounded deques● Open access↗
FA-46502

Copy-on-write treats two owners as exclusive · case 02

Copy-on-write treats two owners as exclusive.

Bounded deques◈ Members↗
FA-46503

Copy-on-write treats two owners as exclusive · case 03

Copy-on-write treats two owners as exclusive.

Bounded deques◈ Members↗
FA-46504

Copy-on-write treats two owners as exclusive · case 04

Copy-on-write treats two owners as exclusive.

Bounded deques◈ Members↗
FA-46505

Copy-on-write treats two owners as exclusive · case 05

Copy-on-write treats two owners as exclusive.

Bounded deques◈ Members↗
FA-46506

Detached deque write targets the head regardless of logical index · case 01

Detached deque write targets the head regardless of logical index.

Bounded deques● Open access↗
FA-46507

Detached deque write targets the head regardless of logical index · case 02

Detached deque write targets the head regardless of logical index.

Bounded deques◈ Members↗
FA-46508

Detached deque write targets the head regardless of logical index · case 03

Detached deque write targets the head regardless of logical index.

Bounded deques◈ Members↗
FA-46509

Detached deque write targets the head regardless of logical index · case 04

Detached deque write targets the head regardless of logical index.

Bounded deques◈ Members↗
FA-46510

Detached deque write targets the head regardless of logical index · case 05

Detached deque write targets the head regardless of logical index.

Bounded deques◈ Members↗
FA-46511

Copy-on-write exposes detached writes through the old view · case 01

Copy-on-write exposes detached writes through the old view.

Bounded deques● Open access↗
FA-46512

Copy-on-write exposes detached writes through the old view · case 02

Copy-on-write exposes detached writes through the old view.

Bounded deques◈ Members↗
FA-46513

Copy-on-write exposes detached writes through the old view · case 03

Copy-on-write exposes detached writes through the old view.

Bounded deques◈ Members↗
FA-46514

Copy-on-write exposes detached writes through the old view · case 04

Copy-on-write exposes detached writes through the old view.

Bounded deques◈ Members↗
FA-46515

Copy-on-write exposes detached writes through the old view · case 05

Copy-on-write exposes detached writes through the old view.

Bounded deques◈ Members↗
FA-46516

Copy-on-write detachment releases every old owner · case 01

Copy-on-write detachment releases every old owner.

Bounded deques● Open access↗
FA-46517

Copy-on-write detachment releases every old owner · case 02

Copy-on-write detachment releases every old owner.

Bounded deques◈ Members↗
FA-46518

Copy-on-write detachment releases every old owner · case 03

Copy-on-write detachment releases every old owner.

Bounded deques◈ Members↗
FA-46519

Copy-on-write detachment releases every old owner · case 04

Copy-on-write detachment releases every old owner.

Bounded deques◈ Members↗
FA-46520

Copy-on-write detachment releases every old owner · case 05

Copy-on-write detachment releases every old owner.

Bounded deques◈ Members↗
FA-46521

Copy-on-write clone inherits the old sharing count · case 01

Copy-on-write clone inherits the old sharing count.

Bounded deques● Open access↗
FA-46522

Copy-on-write clone inherits the old sharing count · case 02

Copy-on-write clone inherits the old sharing count.

Bounded deques◈ Members↗
FA-46523

Copy-on-write clone inherits the old sharing count · case 03

Copy-on-write clone inherits the old sharing count.

Bounded deques◈ Members↗
FA-46524

Copy-on-write clone inherits the old sharing count · case 04

Copy-on-write clone inherits the old sharing count.

Bounded deques◈ Members↗
FA-46525

Copy-on-write clone inherits the old sharing count · case 05

Copy-on-write clone inherits the old sharing count.

Bounded deques◈ Members↗
FA-46526

Copy-on-write clone retains old storage identity · case 01

Copy-on-write clone retains old storage identity.

Bounded deques● Open access↗
FA-46527

Copy-on-write clone retains old storage identity · case 02

Copy-on-write clone retains old storage identity.

Bounded deques◈ Members↗
FA-46528

Copy-on-write clone retains old storage identity · case 03

Copy-on-write clone retains old storage identity.

Bounded deques◈ Members↗
FA-46529

Copy-on-write clone retains old storage identity · case 04

Copy-on-write clone retains old storage identity.

Bounded deques◈ Members↗
FA-46530

Copy-on-write clone retains old storage identity · case 05

Copy-on-write clone retains old storage identity.

Bounded deques◈ Members↗
FA-46531

Exclusive deque writes consume unused storage IDs · case 01

Exclusive deque writes consume unused storage IDs.

Bounded deques● Open access↗
FA-46532

Exclusive deque writes consume unused storage IDs · case 02

Exclusive deque writes consume unused storage IDs.

Bounded deques◈ Members↗
FA-46533

Exclusive deque writes consume unused storage IDs · case 03

Exclusive deque writes consume unused storage IDs.

Bounded deques◈ Members↗
FA-46534

Exclusive deque writes consume unused storage IDs · case 04

Exclusive deque writes consume unused storage IDs.

Bounded deques◈ Members↗
FA-46535

Exclusive deque writes consume unused storage IDs · case 05

Exclusive deque writes consume unused storage IDs.

Bounded deques◈ Members↗
FA-46536

Deque range view pins the block at its exclusive stop · case 01

Deque range view pins the block at its exclusive stop.

Bounded deques● Open access↗
FA-46537

Deque range view pins the block at its exclusive stop · case 02

Deque range view pins the block at its exclusive stop.

Bounded deques◈ Members↗
FA-46538

Deque range view pins the block at its exclusive stop · case 03

Deque range view pins the block at its exclusive stop.

Bounded deques◈ Members↗
FA-46539

Deque range view pins the block at its exclusive stop · case 04

Deque range view pins the block at its exclusive stop.

Bounded deques◈ Members↗
FA-46540

Deque range view pins the block at its exclusive stop · case 05

Deque range view pins the block at its exclusive stop.

Bounded deques◈ Members↗
FA-46541

Deque block view overwrites existing pin counts · case 01

Deque block view overwrites existing pin counts.

Bounded deques● Open access↗
FA-46542

Deque block view overwrites existing pin counts · case 02

Deque block view overwrites existing pin counts.

Bounded deques◈ Members↗
FA-46543

Deque block view overwrites existing pin counts · case 03

Deque block view overwrites existing pin counts.

Bounded deques◈ Members↗
FA-46544

Deque block view overwrites existing pin counts · case 04

Deque block view overwrites existing pin counts.

Bounded deques◈ Members↗
FA-46545

Deque block view overwrites existing pin counts · case 05

Deque block view overwrites existing pin counts.

Bounded deques◈ Members↗
FA-46546

Deque block view reuses its parent identity · case 01

Deque block view reuses its parent identity.

Bounded deques● Open access↗
FA-46547

Deque block view reuses its parent identity · case 02

Deque block view reuses its parent identity.

Bounded deques◈ Members↗
FA-46548

Deque block view reuses its parent identity · case 03

Deque block view reuses its parent identity.

Bounded deques◈ Members↗
FA-46549

Deque block view reuses its parent identity · case 04

Deque block view reuses its parent identity.

Bounded deques◈ Members↗
FA-46550

Deque block view reuses its parent identity · case 05

Deque block view reuses its parent identity.

Bounded deques◈ Members↗
FA-46551

Deque block view consumes one ID per selected block · case 01

Deque block view consumes one ID per selected block.

Bounded deques● Open access↗
FA-46552

Deque block view consumes one ID per selected block · case 02

Deque block view consumes one ID per selected block.

Bounded deques◈ Members↗
FA-46553

Deque block view consumes one ID per selected block · case 03

Deque block view consumes one ID per selected block.

Bounded deques◈ Members↗
FA-46554

Deque block view consumes one ID per selected block · case 04

Deque block view consumes one ID per selected block.

Bounded deques◈ Members↗
FA-46555

Deque block view consumes one ID per selected block · case 05

Deque block view consumes one ID per selected block.

Bounded deques◈ Members↗
FA-46556

Deque view binds its owner to the first selected block · case 01

Deque view binds its owner to the first selected block.

Bounded deques● Open access↗
FA-46557

Deque view binds its owner to the first selected block · case 02

Deque view binds its owner to the first selected block.

Bounded deques◈ Members↗
FA-46558

Deque view binds its owner to the first selected block · case 03

Deque view binds its owner to the first selected block.

Bounded deques◈ Members↗
FA-46559

Deque view binds its owner to the first selected block · case 04

Deque view binds its owner to the first selected block.

Bounded deques◈ Members↗
FA-46560

Deque view binds its owner to the first selected block · case 05

Deque view binds its owner to the first selected block.

Bounded deques◈ Members↗
FA-46561

Deque snapshot view is accidentally write-enabled · case 01

Deque snapshot view is accidentally write-enabled.

Bounded deques● Open access↗
FA-46562

Deque snapshot view is accidentally write-enabled · case 02

Deque snapshot view is accidentally write-enabled.

Bounded deques◈ Members↗
FA-46563

Deque snapshot view is accidentally write-enabled · case 03

Deque snapshot view is accidentally write-enabled.

Bounded deques◈ Members↗
FA-46564

Deque snapshot view is accidentally write-enabled · case 04

Deque snapshot view is accidentally write-enabled.

Bounded deques◈ Members↗
FA-46565

Deque snapshot view is accidentally write-enabled · case 05

Deque snapshot view is accidentally write-enabled.

Bounded deques◈ Members↗
FA-46566

Deque block view reports the parent directory length · case 01

Deque block view reports the parent directory length.

Bounded deques● Open access↗
FA-46567

Deque block view reports the parent directory length · case 02

Deque block view reports the parent directory length.

Bounded deques◈ Members↗
FA-46568

Deque block view reports the parent directory length · case 03

Deque block view reports the parent directory length.

Bounded deques◈ Members↗
FA-46569

Deque block view reports the parent directory length · case 04

Deque block view reports the parent directory length.

Bounded deques◈ Members↗
FA-46570

Deque block view reports the parent directory length · case 05

Deque block view reports the parent directory length.

Bounded deques◈ Members↗
FA-46571

Deque retirement clears the neighboring slot instead of its target · case 01

Deque retirement clears the neighboring slot instead of its target.

Bounded deques● Open access↗
FA-46572

Deque retirement clears the neighboring slot instead of its target · case 02

Deque retirement clears the neighboring slot instead of its target.

Bounded deques◈ Members↗
FA-46573

Deque retirement clears the neighboring slot instead of its target · case 03

Deque retirement clears the neighboring slot instead of its target.

Bounded deques◈ Members↗
FA-46574

Deque retirement clears the neighboring slot instead of its target · case 04

Deque retirement clears the neighboring slot instead of its target.

Bounded deques◈ Members↗
FA-46575

Deque retirement clears the neighboring slot instead of its target · case 05

Deque retirement clears the neighboring slot instead of its target.

Bounded deques◈ Members↗
FA-46576

Deque retirement advances every slot generation · case 01

Deque retirement advances every slot generation.

Bounded deques● Open access↗
FA-46577

Deque retirement advances every slot generation · case 02

Deque retirement advances every slot generation.

Bounded deques◈ Members↗
FA-46578

Deque retirement advances every slot generation · case 03

Deque retirement advances every slot generation.

Bounded deques◈ Members↗
FA-46579

Deque retirement advances every slot generation · case 04

Deque retirement advances every slot generation.

Bounded deques◈ Members↗
FA-46580

Deque retirement advances every slot generation · case 05

Deque retirement advances every slot generation.

Bounded deques◈ Members↗
FA-46581

Retired deque slot is prepended to FIFO reuse order · case 01

Retired deque slot is prepended to FIFO reuse order.

Bounded deques● Open access↗
FA-46582

Retired deque slot is prepended to FIFO reuse order · case 02

Retired deque slot is prepended to FIFO reuse order.

Bounded deques◈ Members↗
FA-46583

Retired deque slot is prepended to FIFO reuse order · case 03

Retired deque slot is prepended to FIFO reuse order.

Bounded deques◈ Members↗
FA-46584

Retired deque slot is prepended to FIFO reuse order · case 04

Retired deque slot is prepended to FIFO reuse order.

Bounded deques◈ Members↗
FA-46585

Retired deque slot is prepended to FIFO reuse order · case 05

Retired deque slot is prepended to FIFO reuse order.

Bounded deques◈ Members↗
FA-46586

Deque retirement treats free-list length as live occupancy · case 01

Deque retirement treats free-list length as live occupancy.

Bounded deques● Open access↗
FA-46587

Deque retirement treats free-list length as live occupancy · case 02

Deque retirement treats free-list length as live occupancy.

Bounded deques◈ Members↗
FA-46588

Deque retirement treats free-list length as live occupancy · case 03

Deque retirement treats free-list length as live occupancy.

Bounded deques◈ Members↗
FA-46589

Deque retirement treats free-list length as live occupancy · case 04

Deque retirement treats free-list length as live occupancy.

Bounded deques◈ Members↗
FA-46590

Deque retirement treats free-list length as live occupancy · case 05

Deque retirement treats free-list length as live occupancy.

Bounded deques◈ Members↗
FA-46591

Retirement receipt records the replacement handle generation · case 01

Retirement receipt records the replacement handle generation.

Bounded deques● Open access↗
FA-46592

Retirement receipt records the replacement handle generation · case 02

Retirement receipt records the replacement handle generation.

Bounded deques◈ Members↗
FA-46593

Retirement receipt records the replacement handle generation · case 03

Retirement receipt records the replacement handle generation.

Bounded deques◈ Members↗
FA-46594

Retirement receipt records the replacement handle generation · case 04

Retirement receipt records the replacement handle generation.

Bounded deques◈ Members↗
FA-46595

Retirement receipt records the replacement handle generation · case 05

Retirement receipt records the replacement handle generation.

Bounded deques◈ Members↗
FA-46596

Retired deque handle remains marked usable · case 01

Retired deque handle remains marked usable.

Bounded deques● Open access↗
FA-46597

Retired deque handle remains marked usable · case 02

Retired deque handle remains marked usable.

Bounded deques◈ Members↗
FA-46598

Retired deque handle remains marked usable · case 03

Retired deque handle remains marked usable.

Bounded deques◈ Members↗
FA-46599

Retired deque handle remains marked usable · case 04

Retired deque handle remains marked usable.

Bounded deques◈ Members↗
FA-46600

Retired deque handle remains marked usable · case 05

Retired deque handle remains marked usable.

Bounded deques◈ 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 ↗