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

Hierarchical checkbox cascade: Cascade erases protected or unrelated checks · case 01

Cascade erases protected or unrelated checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38402

Hierarchical checkbox cascade: Cascade erases protected or unrelated checks · case 02

Cascade erases protected or unrelated checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38403

Hierarchical checkbox cascade: Cascade erases protected or unrelated checks · case 03

Cascade erases protected or unrelated checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38404

Hierarchical checkbox cascade: Cascade erases protected or unrelated checks · case 04

Cascade erases protected or unrelated checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38405

Hierarchical checkbox cascade: Cascade erases protected or unrelated checks · case 05

Cascade erases protected or unrelated checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38406

Hierarchical checkbox cascade: Disabled or already complete branch is recascaded · case 01

Disabled or already complete branch is recascaded produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38407

Hierarchical checkbox cascade: Disabled or already complete branch is recascaded · case 02

Disabled or already complete branch is recascaded produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38408

Hierarchical checkbox cascade: Disabled or already complete branch is recascaded · case 03

Disabled or already complete branch is recascaded produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38409

Hierarchical checkbox cascade: Disabled or already complete branch is recascaded · case 04

Disabled or already complete branch is recascaded produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38410

Hierarchical checkbox cascade: Disabled or already complete branch is recascaded · case 05

Disabled or already complete branch is recascaded produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38411

Hierarchical checkbox cascade: Cascaded leaves fail to merge with retained checks · case 01

Cascaded leaves fail to merge with retained checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38412

Hierarchical checkbox cascade: Cascaded leaves fail to merge with retained checks · case 02

Cascaded leaves fail to merge with retained checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38413

Hierarchical checkbox cascade: Cascaded leaves fail to merge with retained checks · case 03

Cascaded leaves fail to merge with retained checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38414

Hierarchical checkbox cascade: Cascaded leaves fail to merge with retained checks · case 04

Cascaded leaves fail to merge with retained checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38415

Hierarchical checkbox cascade: Cascaded leaves fail to merge with retained checks · case 05

Cascaded leaves fail to merge with retained checks produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38416

Hierarchical checkbox cascade: Parent summary uses stale or protected leaves · case 01

Parent summary uses stale or protected leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38417

Hierarchical checkbox cascade: Parent summary uses stale or protected leaves · case 02

Parent summary uses stale or protected leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38418

Hierarchical checkbox cascade: Parent summary uses stale or protected leaves · case 03

Parent summary uses stale or protected leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38419

Hierarchical checkbox cascade: Parent summary uses stale or protected leaves · case 04

Parent summary uses stale or protected leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38420

Hierarchical checkbox cascade: Parent summary uses stale or protected leaves · case 05

Parent summary uses stale or protected leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38421

Hierarchical checkbox cascade: Empty or unloaded branch reports fully checked · case 01

Empty or unloaded branch reports fully checked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38422

Hierarchical checkbox cascade: Empty or unloaded branch reports fully checked · case 02

Empty or unloaded branch reports fully checked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38423

Hierarchical checkbox cascade: Empty or unloaded branch reports fully checked · case 03

Empty or unloaded branch reports fully checked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38424

Hierarchical checkbox cascade: Empty or unloaded branch reports fully checked · case 04

Empty or unloaded branch reports fully checked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38425

Hierarchical checkbox cascade: Empty or unloaded branch reports fully checked · case 05

Empty or unloaded branch reports fully checked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38426

Hierarchical checkbox cascade: Mixed state ignores branch completeness · case 01

Mixed state ignores branch completeness produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38427

Hierarchical checkbox cascade: Mixed state ignores branch completeness · case 02

Mixed state ignores branch completeness produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38428

Hierarchical checkbox cascade: Mixed state ignores branch completeness · case 03

Mixed state ignores branch completeness produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38429

Hierarchical checkbox cascade: Mixed state ignores branch completeness · case 04

Mixed state ignores branch completeness produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38430

Hierarchical checkbox cascade: Mixed state ignores branch completeness · case 05

Mixed state ignores branch completeness produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38431

Hierarchical checkbox cascade: Indeterminate parent state is serialized as unchecked · case 01

Indeterminate parent state is serialized as unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38432

Hierarchical checkbox cascade: Indeterminate parent state is serialized as unchecked · case 02

Indeterminate parent state is serialized as unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38433

Hierarchical checkbox cascade: Indeterminate parent state is serialized as unchecked · case 03

Indeterminate parent state is serialized as unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38434

Hierarchical checkbox cascade: Indeterminate parent state is serialized as unchecked · case 04

Indeterminate parent state is serialized as unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38435

Hierarchical checkbox cascade: Indeterminate parent state is serialized as unchecked · case 05

Indeterminate parent state is serialized as unchecked produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38436

Hierarchical checkbox cascade: Change notification reports final membership rather than changed leaves · case 01

Change notification reports final membership rather than changed leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38437

Hierarchical checkbox cascade: Change notification reports final membership rather than changed leaves · case 02

Change notification reports final membership rather than changed leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38438

Hierarchical checkbox cascade: Change notification reports final membership rather than changed leaves · case 03

Change notification reports final membership rather than changed leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38439

Hierarchical checkbox cascade: Change notification reports final membership rather than changed leaves · case 04

Change notification reports final membership rather than changed leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38440

Hierarchical checkbox cascade: Change notification reports final membership rather than changed leaves · case 05

Change notification reports final membership rather than changed leaves produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38441

Virtual tree sibling metadata: Logical sibling position becomes recycled slot number · case 01

Logical sibling position becomes recycled slot number produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38442

Virtual tree sibling metadata: Logical sibling position becomes recycled slot number · case 02

Logical sibling position becomes recycled slot number produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38443

Virtual tree sibling metadata: Logical sibling position becomes recycled slot number · case 03

Logical sibling position becomes recycled slot number produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38444

Virtual tree sibling metadata: Logical sibling position becomes recycled slot number · case 04

Logical sibling position becomes recycled slot number produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38445

Virtual tree sibling metadata: Logical sibling position becomes recycled slot number · case 05

Logical sibling position becomes recycled slot number produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38446

Virtual tree sibling metadata: Unknown or virtual sibling set gets a false size · case 01

Unknown or virtual sibling set gets a false size produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38447

Virtual tree sibling metadata: Unknown or virtual sibling set gets a false size · case 02

Unknown or virtual sibling set gets a false size produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38448

Virtual tree sibling metadata: Unknown or virtual sibling set gets a false size · case 03

Unknown or virtual sibling set gets a false size produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38449

Virtual tree sibling metadata: Unknown or virtual sibling set gets a false size · case 04

Unknown or virtual sibling set gets a false size produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38450

Virtual tree sibling metadata: Unknown or virtual sibling set gets a false size · case 05

Unknown or virtual sibling set gets a false size produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38451

Virtual tree sibling metadata: Virtual row loses hierarchical level · case 01

Virtual row loses hierarchical level produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38452

Virtual tree sibling metadata: Virtual row loses hierarchical level · case 02

Virtual row loses hierarchical level produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38453

Virtual tree sibling metadata: Virtual row loses hierarchical level · case 03

Virtual row loses hierarchical level produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38454

Virtual tree sibling metadata: Virtual row loses hierarchical level · case 04

Virtual row loses hierarchical level produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38455

Virtual tree sibling metadata: Virtual row loses hierarchical level · case 05

Virtual row loses hierarchical level produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38456

Virtual tree sibling metadata: Root ownership and branch ownership are conflated · case 01

Root ownership and branch ownership are conflated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38457

Virtual tree sibling metadata: Root ownership and branch ownership are conflated · case 02

Root ownership and branch ownership are conflated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38458

Virtual tree sibling metadata: Root ownership and branch ownership are conflated · case 03

Root ownership and branch ownership are conflated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38459

Virtual tree sibling metadata: Root ownership and branch ownership are conflated · case 04

Root ownership and branch ownership are conflated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38460

Virtual tree sibling metadata: Root ownership and branch ownership are conflated · case 05

Root ownership and branch ownership are conflated produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38461

Virtual tree sibling metadata: Leaf receives an expansion attribute · case 01

Leaf receives an expansion attribute produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38462

Virtual tree sibling metadata: Leaf receives an expansion attribute · case 02

Leaf receives an expansion attribute produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38463

Virtual tree sibling metadata: Leaf receives an expansion attribute · case 03

Leaf receives an expansion attribute produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38464

Virtual tree sibling metadata: Leaf receives an expansion attribute · case 04

Leaf receives an expansion attribute produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38465

Virtual tree sibling metadata: Leaf receives an expansion attribute · case 05

Leaf receives an expansion attribute produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38466

Virtual tree sibling metadata: Selection follows a recycled slot · case 01

Selection follows a recycled slot produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38467

Virtual tree sibling metadata: Selection follows a recycled slot · case 02

Selection follows a recycled slot produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38468

Virtual tree sibling metadata: Selection follows a recycled slot · case 03

Selection follows a recycled slot produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38469

Virtual tree sibling metadata: Selection follows a recycled slot · case 04

Selection follows a recycled slot produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38470

Virtual tree sibling metadata: Selection follows a recycled slot · case 05

Selection follows a recycled slot produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38471

Virtual tree sibling metadata: Active row follows viewport position · case 01

Active row follows viewport position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38472

Virtual tree sibling metadata: Active row follows viewport position · case 02

Active row follows viewport position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38473

Virtual tree sibling metadata: Active row follows viewport position · case 03

Active row follows viewport position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38474

Virtual tree sibling metadata: Active row follows viewport position · case 04

Active row follows viewport position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38475

Virtual tree sibling metadata: Active row follows viewport position · case 05

Active row follows viewport position produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38476

Virtual tree sibling metadata: Active-descendant identity collides across tree instances · case 01

Active-descendant identity collides across tree instances produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38477

Virtual tree sibling metadata: Active-descendant identity collides across tree instances · case 02

Active-descendant identity collides across tree instances produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38478

Virtual tree sibling metadata: Active-descendant identity collides across tree instances · case 03

Active-descendant identity collides across tree instances produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38479

Virtual tree sibling metadata: Active-descendant identity collides across tree instances · case 04

Active-descendant identity collides across tree instances produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38480

Virtual tree sibling metadata: Active-descendant identity collides across tree instances · case 05

Active-descendant identity collides across tree instances produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38481

Virtual tree sibling metadata: Virtual row index drops the offscreen prefix · case 01

Virtual row index drops the offscreen prefix produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38482

Virtual tree sibling metadata: Virtual row index drops the offscreen prefix · case 02

Virtual row index drops the offscreen prefix produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38483

Virtual tree sibling metadata: Virtual row index drops the offscreen prefix · case 03

Virtual row index drops the offscreen prefix produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38484

Virtual tree sibling metadata: Virtual row index drops the offscreen prefix · case 04

Virtual row index drops the offscreen prefix produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38485

Virtual tree sibling metadata: Virtual row index drops the offscreen prefix · case 05

Virtual row index drops the offscreen prefix produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38486

Virtual tree sibling metadata: Leaf or idle branch is exposed as busy · case 01

Leaf or idle branch is exposed as busy produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38487

Virtual tree sibling metadata: Leaf or idle branch is exposed as busy · case 02

Leaf or idle branch is exposed as busy produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38488

Virtual tree sibling metadata: Leaf or idle branch is exposed as busy · case 03

Leaf or idle branch is exposed as busy produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38489

Virtual tree sibling metadata: Leaf or idle branch is exposed as busy · case 04

Leaf or idle branch is exposed as busy produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38490

Virtual tree sibling metadata: Leaf or idle branch is exposed as busy · case 05

Leaf or idle branch is exposed as busy produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38491

Lazy tree branch request lifecycle: Branch request identity omits an epoch or token · case 01

Branch request identity omits an epoch or token produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38492

Lazy tree branch request lifecycle: Branch request identity omits an epoch or token · case 02

Branch request identity omits an epoch or token produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38493

Lazy tree branch request lifecycle: Branch request identity omits an epoch or token · case 03

Branch request identity omits an epoch or token produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38494

Lazy tree branch request lifecycle: Branch request identity omits an epoch or token · case 04

Branch request identity omits an epoch or token produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38495

Lazy tree branch request lifecycle: Branch request identity omits an epoch or token · case 05

Branch request identity omits an epoch or token produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38496

Lazy tree branch request lifecycle: Closed or removed branch accepts a page · case 01

Closed or removed branch accepts a page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38497

Lazy tree branch request lifecycle: Closed or removed branch accepts a page · case 02

Closed or removed branch accepts a page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38498

Lazy tree branch request lifecycle: Closed or removed branch accepts a page · case 03

Closed or removed branch accepts a page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38499

Lazy tree branch request lifecycle: Closed or removed branch accepts a page · case 04

Closed or removed branch accepts a page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38500

Lazy tree branch request lifecycle: Closed or removed branch accepts a page · case 05

Closed or removed branch accepts a page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ 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 ↗