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

Paged tree children accessibility merge: Page merge discards prior child record cache · case 01

Page merge discards prior child record cache produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38902

Paged tree children accessibility merge: Page merge discards prior child record cache · case 02

Page merge discards prior child record cache produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38903

Paged tree children accessibility merge: Page merge discards prior child record cache · case 03

Page merge discards prior child record cache produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38904

Paged tree children accessibility merge: Page merge discards prior child record cache · case 04

Page merge discards prior child record cache produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38905

Paged tree children accessibility merge: Page merge discards prior child record cache · case 05

Page merge discards prior child record cache produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38906

Paged tree children accessibility merge: Overlapping child refresh loses newest record · case 01

Overlapping child refresh loses newest record produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38907

Paged tree children accessibility merge: Overlapping child refresh loses newest record · case 02

Overlapping child refresh loses newest record produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38908

Paged tree children accessibility merge: Overlapping child refresh loses newest record · case 03

Overlapping child refresh loses newest record produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38909

Paged tree children accessibility merge: Overlapping child refresh loses newest record · case 04

Overlapping child refresh loses newest record produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38910

Paged tree children accessibility merge: Overlapping child refresh loses newest record · case 05

Overlapping child refresh loses newest record produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38911

Paged tree children accessibility merge: Existing child is mistaken for a new focus target · case 01

Existing child is mistaken for a new focus target produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38912

Paged tree children accessibility merge: Existing child is mistaken for a new focus target · case 02

Existing child is mistaken for a new focus target produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38913

Paged tree children accessibility merge: Existing child is mistaken for a new focus target · case 03

Existing child is mistaken for a new focus target produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38914

Paged tree children accessibility merge: Existing child is mistaken for a new focus target · case 04

Existing child is mistaken for a new focus target produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38915

Paged tree children accessibility merge: Existing child is mistaken for a new focus target · case 05

Existing child is mistaken for a new focus target produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38916

Paged tree children accessibility merge: Repeated page entry corrupts newly loaded child order · case 01

Repeated page entry corrupts newly loaded child order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38917

Paged tree children accessibility merge: Repeated page entry corrupts newly loaded child order · case 02

Repeated page entry corrupts newly loaded child order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38918

Paged tree children accessibility merge: Repeated page entry corrupts newly loaded child order · case 03

Repeated page entry corrupts newly loaded child order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38919

Paged tree children accessibility merge: Repeated page entry corrupts newly loaded child order · case 04

Repeated page entry corrupts newly loaded child order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38920

Paged tree children accessibility merge: Repeated page entry corrupts newly loaded child order · case 05

Repeated page entry corrupts newly loaded child order produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38921

Paged tree children accessibility merge: Rejected page consumes continuation cursor · case 01

Rejected page consumes continuation cursor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38922

Paged tree children accessibility merge: Rejected page consumes continuation cursor · case 02

Rejected page consumes continuation cursor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38923

Paged tree children accessibility merge: Rejected page consumes continuation cursor · case 03

Rejected page consumes continuation cursor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38924

Paged tree children accessibility merge: Rejected page consumes continuation cursor · case 04

Rejected page consumes continuation cursor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38925

Paged tree children accessibility merge: Rejected page consumes continuation cursor · case 05

Rejected page consumes continuation cursor produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38926

Paged tree children accessibility merge: Load-more state mishandles empty cursor or empty page · case 01

Load-more state mishandles empty cursor or empty page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38927

Paged tree children accessibility merge: Load-more state mishandles empty cursor or empty page · case 02

Load-more state mishandles empty cursor or empty page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38928

Paged tree children accessibility merge: Load-more state mishandles empty cursor or empty page · case 03

Load-more state mishandles empty cursor or empty page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38929

Paged tree children accessibility merge: Load-more state mishandles empty cursor or empty page · case 04

Load-more state mishandles empty cursor or empty page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38930

Paged tree children accessibility merge: Load-more state mishandles empty cursor or empty page · case 05

Load-more state mishandles empty cursor or empty page produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38931

Paged tree children accessibility merge: Logical child total is replaced by mounted count · case 01

Logical child total is replaced by mounted count produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38932

Paged tree children accessibility merge: Logical child total is replaced by mounted count · case 02

Logical child total is replaced by mounted count produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38933

Paged tree children accessibility merge: Logical child total is replaced by mounted count · case 03

Logical child total is replaced by mounted count produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38934

Paged tree children accessibility merge: Logical child total is replaced by mounted count · case 04

Logical child total is replaced by mounted count produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38935

Paged tree children accessibility merge: Logical child total is replaced by mounted count · case 05

Logical child total is replaced by mounted count produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38936

Paged tree children accessibility merge: Page focus skips first newly loaded child · case 01

Page focus skips first newly loaded child produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38937

Paged tree children accessibility merge: Page focus skips first newly loaded child · case 02

Page focus skips first newly loaded child produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38938

Paged tree children accessibility merge: Page focus skips first newly loaded child · case 03

Page focus skips first newly loaded child produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38939

Paged tree children accessibility merge: Page focus skips first newly loaded child · case 04

Page focus skips first newly loaded child produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38940

Paged tree children accessibility merge: Page focus skips first newly loaded child · case 05

Page focus skips first newly loaded child produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38941

Tree expansion undo journal: Undo applies a stale branch generation · case 01

Undo applies a stale branch generation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38942

Tree expansion undo journal: Undo applies a stale branch generation · case 02

Undo applies a stale branch generation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38943

Tree expansion undo journal: Undo applies a stale branch generation · case 03

Undo applies a stale branch generation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38944

Tree expansion undo journal: Undo applies a stale branch generation · case 04

Undo applies a stale branch generation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38945

Tree expansion undo journal: Undo applies a stale branch generation · case 05

Undo applies a stale branch generation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38946

Tree expansion undo journal: Undo restores oldest expansion transaction · case 01

Undo restores oldest expansion transaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38947

Tree expansion undo journal: Undo restores oldest expansion transaction · case 02

Undo restores oldest expansion transaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38948

Tree expansion undo journal: Undo restores oldest expansion transaction · case 03

Undo restores oldest expansion transaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38949

Tree expansion undo journal: Undo restores oldest expansion transaction · case 04

Undo restores oldest expansion transaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38950

Tree expansion undo journal: Undo restores oldest expansion transaction · case 05

Undo restores oldest expansion transaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38951

Tree expansion undo journal: Undo restores deleted branch or after-state · case 01

Undo restores deleted branch or after-state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38952

Tree expansion undo journal: Undo restores deleted branch or after-state · case 02

Undo restores deleted branch or after-state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38953

Tree expansion undo journal: Undo restores deleted branch or after-state · case 03

Undo restores deleted branch or after-state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38954

Tree expansion undo journal: Undo restores deleted branch or after-state · case 04

Undo restores deleted branch or after-state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38955

Tree expansion undo journal: Undo restores deleted branch or after-state · case 05

Undo restores deleted branch or after-state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38956

Tree expansion undo journal: Undo clears expansion forced by another interaction · case 01

Undo clears expansion forced by another interaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38957

Tree expansion undo journal: Undo clears expansion forced by another interaction · case 02

Undo clears expansion forced by another interaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38958

Tree expansion undo journal: Undo clears expansion forced by another interaction · case 03

Undo clears expansion forced by another interaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38959

Tree expansion undo journal: Undo clears expansion forced by another interaction · case 04

Undo clears expansion forced by another interaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38960

Tree expansion undo journal: Undo clears expansion forced by another interaction · case 05

Undo clears expansion forced by another interaction produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38961

Tree expansion undo journal: Effective expansion omits user or forced state · case 01

Effective expansion omits user or forced state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38962

Tree expansion undo journal: Effective expansion omits user or forced state · case 02

Effective expansion omits user or forced state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38963

Tree expansion undo journal: Effective expansion omits user or forced state · case 03

Effective expansion omits user or forced state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38964

Tree expansion undo journal: Effective expansion omits user or forced state · case 04

Effective expansion omits user or forced state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38965

Tree expansion undo journal: Effective expansion omits user or forced state · case 05

Effective expansion omits user or forced state produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38966

Tree expansion undo journal: Undo pops the wrong journal end · case 01

Undo pops the wrong journal end produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38967

Tree expansion undo journal: Undo pops the wrong journal end · case 02

Undo pops the wrong journal end produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38968

Tree expansion undo journal: Undo pops the wrong journal end · case 03

Undo pops the wrong journal end produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38969

Tree expansion undo journal: Undo pops the wrong journal end · case 04

Undo pops the wrong journal end produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38970

Tree expansion undo journal: Undo pops the wrong journal end · case 05

Undo pops the wrong journal end produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38971

Tree expansion undo journal: Undo loses existing redo transactions · case 01

Undo loses existing redo transactions produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38972

Tree expansion undo journal: Undo loses existing redo transactions · case 02

Undo loses existing redo transactions produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38973

Tree expansion undo journal: Undo loses existing redo transactions · case 03

Undo loses existing redo transactions produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38974

Tree expansion undo journal: Undo loses existing redo transactions · case 04

Undo loses existing redo transactions produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38975

Tree expansion undo journal: Undo loses existing redo transactions · case 05

Undo loses existing redo transactions produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38976

Tree expansion undo journal: Undo focus visibility ignores forced or closed ancestry · case 01

Undo focus visibility ignores forced or closed ancestry produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38977

Tree expansion undo journal: Undo focus visibility ignores forced or closed ancestry · case 02

Undo focus visibility ignores forced or closed ancestry produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38978

Tree expansion undo journal: Undo focus visibility ignores forced or closed ancestry · case 03

Undo focus visibility ignores forced or closed ancestry produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38979

Tree expansion undo journal: Undo focus visibility ignores forced or closed ancestry · case 04

Undo focus visibility ignores forced or closed ancestry produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38980

Tree expansion undo journal: Undo focus visibility ignores forced or closed ancestry · case 05

Undo focus visibility ignores forced or closed ancestry produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38981

Tree expansion undo journal: Undo forgets the prior row focus · case 01

Undo forgets the prior row focus produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38982

Tree expansion undo journal: Undo forgets the prior row focus · case 02

Undo forgets the prior row focus produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38983

Tree expansion undo journal: Undo forgets the prior row focus · case 03

Undo forgets the prior row focus produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38984

Tree expansion undo journal: Undo forgets the prior row focus · case 04

Undo forgets the prior row focus produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38985

Tree expansion undo journal: Undo forgets the prior row focus · case 05

Undo forgets the prior row focus produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38986

Tree expansion undo journal: Undo restores focus into a closed branch · case 01

Undo restores focus into a closed branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38987

Tree expansion undo journal: Undo restores focus into a closed branch · case 02

Undo restores focus into a closed branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38988

Tree expansion undo journal: Undo restores focus into a closed branch · case 03

Undo restores focus into a closed branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38989

Tree expansion undo journal: Undo restores focus into a closed branch · case 04

Undo restores focus into a closed branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38990

Tree expansion undo journal: Undo restores focus into a closed branch · case 05

Undo restores focus into a closed branch produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38991

Inline branch rename transaction: Rename reply targets a recycled row incarnation · case 01

Rename reply targets a recycled row incarnation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38992

Inline branch rename transaction: Rename reply targets a recycled row incarnation · case 02

Rename reply targets a recycled row incarnation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38993

Inline branch rename transaction: Rename reply targets a recycled row incarnation · case 03

Rename reply targets a recycled row incarnation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38994

Inline branch rename transaction: Rename reply targets a recycled row incarnation · case 04

Rename reply targets a recycled row incarnation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38995

Inline branch rename transaction: Rename reply targets a recycled row incarnation · case 05

Rename reply targets a recycled row incarnation produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38996

Inline branch rename transaction: Rename keeps inaccessible edge whitespace · case 01

Rename keeps inaccessible edge whitespace produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility● Open access↗
FA-38997

Inline branch rename transaction: Rename keeps inaccessible edge whitespace · case 02

Rename keeps inaccessible edge whitespace produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38998

Inline branch rename transaction: Rename keeps inaccessible edge whitespace · case 03

Rename keeps inaccessible edge whitespace produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-38999

Inline branch rename transaction: Rename keeps inaccessible edge whitespace · case 04

Rename keeps inaccessible edge whitespace produces the wrong hierarchical widget state in a regression fixture.

Tree accessibility◈ Members↗
FA-39000

Inline branch rename transaction: Rename keeps inaccessible edge whitespace · case 05

Rename keeps inaccessible edge whitespace 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 ↗