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

Hover-open deadline is recalculated after delayed event delivery · case 01

Hover-open deadline is recalculated after delayed event delivery.

Menu interactions● Open access↗
FA-32702

Hover-open deadline is recalculated after delayed event delivery · case 02

Hover-open deadline is recalculated after delayed event delivery.

Menu interactions◈ Members↗
FA-32703

Hover-open deadline is recalculated after delayed event delivery · case 03

Hover-open deadline is recalculated after delayed event delivery.

Menu interactions◈ Members↗
FA-32704

Hover-open deadline is recalculated after delayed event delivery · case 04

Hover-open deadline is recalculated after delayed event delivery.

Menu interactions◈ Members↗
FA-32705

Hover-open deadline is recalculated after delayed event delivery · case 05

Hover-open deadline is recalculated after delayed event delivery.

Menu interactions◈ Members↗
FA-32706

Replacing one hover timer retains stale timer ownership · case 01

Replacing one hover timer retains stale timer ownership.

Menu interactions● Open access↗
FA-32707

Replacing one hover timer retains stale timer ownership · case 02

Replacing one hover timer retains stale timer ownership.

Menu interactions◈ Members↗
FA-32708

Replacing one hover timer retains stale timer ownership · case 03

Replacing one hover timer retains stale timer ownership.

Menu interactions◈ Members↗
FA-32709

Replacing one hover timer retains stale timer ownership · case 04

Replacing one hover timer retains stale timer ownership.

Menu interactions◈ Members↗
FA-32710

Replacing one hover timer retains stale timer ownership · case 05

Replacing one hover timer retains stale timer ownership.

Menu interactions◈ Members↗
FA-32711

Returning to a submenu fails to cancel its pending close · case 01

Returning to a submenu fails to cancel its pending close.

Menu interactions● Open access↗
FA-32712

Returning to a submenu fails to cancel its pending close · case 02

Returning to a submenu fails to cancel its pending close.

Menu interactions◈ Members↗
FA-32713

Returning to a submenu fails to cancel its pending close · case 03

Returning to a submenu fails to cancel its pending close.

Menu interactions◈ Members↗
FA-32714

Returning to a submenu fails to cancel its pending close · case 04

Returning to a submenu fails to cancel its pending close.

Menu interactions◈ Members↗
FA-32715

Returning to a submenu fails to cancel its pending close · case 05

Returning to a submenu fails to cancel its pending close.

Menu interactions◈ Members↗
FA-32716

Menu hover scheduler skips jobs exactly at the deadline · case 01

Menu hover scheduler skips jobs exactly at the deadline.

Menu interactions● Open access↗
FA-32717

Menu hover scheduler skips jobs exactly at the deadline · case 02

Menu hover scheduler skips jobs exactly at the deadline.

Menu interactions◈ Members↗
FA-32718

Menu hover scheduler skips jobs exactly at the deadline · case 03

Menu hover scheduler skips jobs exactly at the deadline.

Menu interactions◈ Members↗
FA-32719

Menu hover scheduler skips jobs exactly at the deadline · case 04

Menu hover scheduler skips jobs exactly at the deadline.

Menu interactions◈ Members↗
FA-32720

Menu hover scheduler skips jobs exactly at the deadline · case 05

Menu hover scheduler skips jobs exactly at the deadline.

Menu interactions◈ Members↗
FA-32721

Submenu leave timer ignores a longer active intent corridor · case 01

Submenu leave timer ignores a longer active intent corridor.

Menu interactions● Open access↗
FA-32722

Submenu leave timer ignores a longer active intent corridor · case 02

Submenu leave timer ignores a longer active intent corridor.

Menu interactions◈ Members↗
FA-32723

Submenu leave timer ignores a longer active intent corridor · case 03

Submenu leave timer ignores a longer active intent corridor.

Menu interactions◈ Members↗
FA-32724

Submenu leave timer ignores a longer active intent corridor · case 04

Submenu leave timer ignores a longer active intent corridor.

Menu interactions◈ Members↗
FA-32725

Submenu leave timer ignores a longer active intent corridor · case 05

Submenu leave timer ignores a longer active intent corridor.

Menu interactions◈ Members↗
FA-32726

Queued hover event opens a submenu after pointer departure · case 01

Queued hover event opens a submenu after pointer departure.

Menu interactions● Open access↗
FA-32727

Queued hover event opens a submenu after pointer departure · case 02

Queued hover event opens a submenu after pointer departure.

Menu interactions◈ Members↗
FA-32728

Queued hover event opens a submenu after pointer departure · case 03

Queued hover event opens a submenu after pointer departure.

Menu interactions◈ Members↗
FA-32729

Queued hover event opens a submenu after pointer departure · case 04

Queued hover event opens a submenu after pointer departure.

Menu interactions◈ Members↗
FA-32730

Queued hover event opens a submenu after pointer departure · case 05

Queued hover event opens a submenu after pointer departure.

Menu interactions◈ Members↗
FA-32731

Menu hit routing chooses the oldest surface instead of the topmost · case 01

Menu hit routing chooses the oldest surface instead of the topmost.

Menu interactions● Open access↗
FA-32732

Menu hit routing chooses the oldest surface instead of the topmost · case 02

Menu hit routing chooses the oldest surface instead of the topmost.

Menu interactions◈ Members↗
FA-32733

Menu hit routing chooses the oldest surface instead of the topmost · case 03

Menu hit routing chooses the oldest surface instead of the topmost.

Menu interactions◈ Members↗
FA-32734

Menu hit routing chooses the oldest surface instead of the topmost · case 04

Menu hit routing chooses the oldest surface instead of the topmost.

Menu interactions◈ Members↗
FA-32735

Menu hit routing chooses the oldest surface instead of the topmost · case 05

Menu hit routing chooses the oldest surface instead of the topmost.

Menu interactions◈ Members↗
FA-32736

Raising an existing menu creates a duplicate surface entry · case 01

Raising an existing menu creates a duplicate surface entry.

Menu interactions● Open access↗
FA-32737

Raising an existing menu creates a duplicate surface entry · case 02

Raising an existing menu creates a duplicate surface entry.

Menu interactions◈ Members↗
FA-32738

Raising an existing menu creates a duplicate surface entry · case 03

Raising an existing menu creates a duplicate surface entry.

Menu interactions◈ Members↗
FA-32739

Raising an existing menu creates a duplicate surface entry · case 04

Raising an existing menu creates a duplicate surface entry.

Menu interactions◈ Members↗
FA-32740

Raising an existing menu creates a duplicate surface entry · case 05

Raising an existing menu creates a duplicate surface entry.

Menu interactions◈ Members↗
FA-32741

Removing a parent popup leaves child surfaces registered · case 01

Removing a parent popup leaves child surfaces registered.

Menu interactions● Open access↗
FA-32742

Removing a parent popup leaves child surfaces registered · case 02

Removing a parent popup leaves child surfaces registered.

Menu interactions◈ Members↗
FA-32743

Removing a parent popup leaves child surfaces registered · case 03

Removing a parent popup leaves child surfaces registered.

Menu interactions◈ Members↗
FA-32744

Removing a parent popup leaves child surfaces registered · case 04

Removing a parent popup leaves child surfaces registered.

Menu interactions◈ Members↗
FA-32745

Removing a parent popup leaves child surfaces registered · case 05

Removing a parent popup leaves child surfaces registered.

Menu interactions◈ Members↗
FA-32746

Cascade root identity is replaced by its nearest parent · case 01

Cascade root identity is replaced by its nearest parent.

Menu interactions● Open access↗
FA-32747

Cascade root identity is replaced by its nearest parent · case 02

Cascade root identity is replaced by its nearest parent.

Menu interactions◈ Members↗
FA-32748

Cascade root identity is replaced by its nearest parent · case 03

Cascade root identity is replaced by its nearest parent.

Menu interactions◈ Members↗
FA-32749

Cascade root identity is replaced by its nearest parent · case 04

Cascade root identity is replaced by its nearest parent.

Menu interactions◈ Members↗
FA-32750

Cascade root identity is replaced by its nearest parent · case 05

Cascade root identity is replaced by its nearest parent.

Menu interactions◈ Members↗
FA-32751

Nested menu surface levels ignore the reserved z-order stride · case 01

Nested menu surface levels ignore the reserved z-order stride.

Menu interactions● Open access↗
FA-32752

Nested menu surface levels ignore the reserved z-order stride · case 02

Nested menu surface levels ignore the reserved z-order stride.

Menu interactions◈ Members↗
FA-32753

Nested menu surface levels ignore the reserved z-order stride · case 03

Nested menu surface levels ignore the reserved z-order stride.

Menu interactions◈ Members↗
FA-32754

Nested menu surface levels ignore the reserved z-order stride · case 04

Nested menu surface levels ignore the reserved z-order stride.

Menu interactions◈ Members↗
FA-32755

Nested menu surface levels ignore the reserved z-order stride · case 05

Nested menu surface levels ignore the reserved z-order stride.

Menu interactions◈ Members↗
FA-32756

Detached menu root still references a removed host · case 01

Detached menu root still references a removed host.

Menu interactions● Open access↗
FA-32757

Detached menu root still references a removed host · case 02

Detached menu root still references a removed host.

Menu interactions◈ Members↗
FA-32758

Detached menu root still references a removed host · case 03

Detached menu root still references a removed host.

Menu interactions◈ Members↗
FA-32759

Detached menu root still references a removed host · case 04

Detached menu root still references a removed host.

Menu interactions◈ Members↗
FA-32760

Detached menu root still references a removed host · case 05

Detached menu root still references a removed host.

Menu interactions◈ Members↗
FA-32761

Right submenu placement forgets the owner-edge overlap · case 01

Right submenu placement forgets the owner-edge overlap.

Menu interactions● Open access↗
FA-32762

Right submenu placement forgets the owner-edge overlap · case 02

Right submenu placement forgets the owner-edge overlap.

Menu interactions◈ Members↗
FA-32763

Right submenu placement forgets the owner-edge overlap · case 03

Right submenu placement forgets the owner-edge overlap.

Menu interactions◈ Members↗
FA-32764

Right submenu placement forgets the owner-edge overlap · case 04

Right submenu placement forgets the owner-edge overlap.

Menu interactions◈ Members↗
FA-32765

Right submenu placement forgets the owner-edge overlap · case 05

Right submenu placement forgets the owner-edge overlap.

Menu interactions◈ Members↗
FA-32766

Left submenu placement applies overlap in the wrong direction · case 01

Left submenu placement applies overlap in the wrong direction.

Menu interactions● Open access↗
FA-32767

Left submenu placement applies overlap in the wrong direction · case 02

Left submenu placement applies overlap in the wrong direction.

Menu interactions◈ Members↗
FA-32768

Left submenu placement applies overlap in the wrong direction · case 03

Left submenu placement applies overlap in the wrong direction.

Menu interactions◈ Members↗
FA-32769

Left submenu placement applies overlap in the wrong direction · case 04

Left submenu placement applies overlap in the wrong direction.

Menu interactions◈ Members↗
FA-32770

Left submenu placement applies overlap in the wrong direction · case 05

Left submenu placement applies overlap in the wrong direction.

Menu interactions◈ Members↗
FA-32771

Clipped submenu chooses the smaller side when neither side fits · case 01

Clipped submenu chooses the smaller side when neither side fits.

Menu interactions● Open access↗
FA-32772

Clipped submenu chooses the smaller side when neither side fits · case 02

Clipped submenu chooses the smaller side when neither side fits.

Menu interactions◈ Members↗
FA-32773

Clipped submenu chooses the smaller side when neither side fits · case 03

Clipped submenu chooses the smaller side when neither side fits.

Menu interactions◈ Members↗
FA-32774

Clipped submenu chooses the smaller side when neither side fits · case 04

Clipped submenu chooses the smaller side when neither side fits.

Menu interactions◈ Members↗
FA-32775

Clipped submenu chooses the smaller side when neither side fits · case 05

Clipped submenu chooses the smaller side when neither side fits.

Menu interactions◈ Members↗
FA-32776

Submenu content starts below the owning row due to padding · case 01

Submenu content starts below the owning row due to padding.

Menu interactions● Open access↗
FA-32777

Submenu content starts below the owning row due to padding · case 02

Submenu content starts below the owning row due to padding.

Menu interactions◈ Members↗
FA-32778

Submenu content starts below the owning row due to padding · case 03

Submenu content starts below the owning row due to padding.

Menu interactions◈ Members↗
FA-32779

Submenu content starts below the owning row due to padding · case 04

Submenu content starts below the owning row due to padding.

Menu interactions◈ Members↗
FA-32780

Submenu content starts below the owning row due to padding · case 05

Submenu content starts below the owning row due to padding.

Menu interactions◈ Members↗
FA-32781

Portaled submenu mixes root-relative and screen coordinates · case 01

Portaled submenu mixes root-relative and screen coordinates.

Menu interactions● Open access↗
FA-32782

Portaled submenu mixes root-relative and screen coordinates · case 02

Portaled submenu mixes root-relative and screen coordinates.

Menu interactions◈ Members↗
FA-32783

Portaled submenu mixes root-relative and screen coordinates · case 03

Portaled submenu mixes root-relative and screen coordinates.

Menu interactions◈ Members↗
FA-32784

Portaled submenu mixes root-relative and screen coordinates · case 04

Portaled submenu mixes root-relative and screen coordinates.

Menu interactions◈ Members↗
FA-32785

Portaled submenu mixes root-relative and screen coordinates · case 05

Portaled submenu mixes root-relative and screen coordinates.

Menu interactions◈ Members↗
FA-32786

Menu bridge hit region ignores its horizontal bounds · case 01

Menu bridge hit region ignores its horizontal bounds.

Menu interactions● Open access↗
FA-32787

Menu bridge hit region ignores its horizontal bounds · case 02

Menu bridge hit region ignores its horizontal bounds.

Menu interactions◈ Members↗
FA-32788

Menu bridge hit region ignores its horizontal bounds · case 03

Menu bridge hit region ignores its horizontal bounds.

Menu interactions◈ Members↗
FA-32789

Menu bridge hit region ignores its horizontal bounds · case 04

Menu bridge hit region ignores its horizontal bounds.

Menu interactions◈ Members↗
FA-32790

Menu bridge hit region ignores its horizontal bounds · case 05

Menu bridge hit region ignores its horizontal bounds.

Menu interactions◈ Members↗
FA-32791

Context invocation resolves to a distant ancestor menu · case 01

Context invocation resolves to a distant ancestor menu.

Menu interactions● Open access↗
FA-32792

Context invocation resolves to a distant ancestor menu · case 02

Context invocation resolves to a distant ancestor menu.

Menu interactions◈ Members↗
FA-32793

Context invocation resolves to a distant ancestor menu · case 03

Context invocation resolves to a distant ancestor menu.

Menu interactions◈ Members↗
FA-32794

Context invocation resolves to a distant ancestor menu · case 04

Context invocation resolves to a distant ancestor menu.

Menu interactions◈ Members↗
FA-32795

Context invocation resolves to a distant ancestor menu · case 05

Context invocation resolves to a distant ancestor menu.

Menu interactions◈ Members↗
FA-32796

Excluded context owner is still used to build a menu · case 01

Excluded context owner is still used to build a menu.

Menu interactions● Open access↗
FA-32797

Excluded context owner is still used to build a menu · case 02

Excluded context owner is still used to build a menu.

Menu interactions◈ Members↗
FA-32798

Excluded context owner is still used to build a menu · case 03

Excluded context owner is still used to build a menu.

Menu interactions◈ Members↗
FA-32799

Excluded context owner is still used to build a menu · case 04

Excluded context owner is still used to build a menu.

Menu interactions◈ Members↗
FA-32800

Excluded context owner is still used to build a menu · case 05

Excluded context owner is still used to build a menu.

Menu interactions◈ 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 ↗