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

Energy saving car shutdown: reactivation trigger · case 01

A car is reactivated at exactly 45 s, or reactivation runs past the fleet size.

Elevator dispatch scheduling● Open access↗
FA-67802

Energy saving car shutdown: reactivation trigger · case 02

A car is reactivated at exactly 45 s, or reactivation runs past the fleet size.

Elevator dispatch scheduling◈ Members↗
FA-67803

Energy saving car shutdown: reactivation trigger · case 03

A car is reactivated at exactly 45 s, or reactivation runs past the fleet size.

Elevator dispatch scheduling◈ Members↗
FA-67804

Energy saving car shutdown: reactivation trigger · case 04

A car is reactivated at exactly 45 s, or reactivation runs past the fleet size.

Elevator dispatch scheduling◈ Members↗
FA-67805

Energy saving car shutdown: reactivation trigger · case 05

A car is reactivated at exactly 45 s, or reactivation runs past the fleet size.

Elevator dispatch scheduling◈ Members↗
FA-67806

Energy saving car shutdown: timer restart after shutdown · case 01

Cars are shut down on every quiet sample after the first shutdown.

Elevator dispatch scheduling● Open access↗
FA-67807

Energy saving car shutdown: timer restart after shutdown · case 02

Cars are shut down on every quiet sample after the first shutdown.

Elevator dispatch scheduling◈ Members↗
FA-67808

Energy saving car shutdown: timer restart after shutdown · case 03

Cars are shut down on every quiet sample after the first shutdown.

Elevator dispatch scheduling◈ Members↗
FA-67809

Energy saving car shutdown: timer restart after shutdown · case 04

Cars are shut down on every quiet sample after the first shutdown.

Elevator dispatch scheduling◈ Members↗
FA-67810

Energy saving car shutdown: timer restart after shutdown · case 05

Cars are shut down on every quiet sample after the first shutdown.

Elevator dispatch scheduling◈ Members↗
FA-67811

Energy saving car shutdown: minimum fleet guard · case 01

The group shuts down below the minimum number of active cars.

Elevator dispatch scheduling● Open access↗
FA-67812

Energy saving car shutdown: minimum fleet guard · case 02

The group shuts down below the minimum number of active cars.

Elevator dispatch scheduling◈ Members↗
FA-67813

Energy saving car shutdown: minimum fleet guard · case 03

The group shuts down below the minimum number of active cars.

Elevator dispatch scheduling◈ Members↗
FA-67814

Energy saving car shutdown: minimum fleet guard · case 04

The group shuts down below the minimum number of active cars.

Elevator dispatch scheduling◈ Members↗
FA-67815

Energy saving car shutdown: minimum fleet guard · case 05

The group shuts down below the minimum number of active cars.

Elevator dispatch scheduling◈ Members↗
FA-67816

Energy saving car shutdown: timer clearing on demand · case 01

A brief quiet spell after busy traffic triggers a shutdown.

Elevator dispatch scheduling● Open access↗
FA-67817

Energy saving car shutdown: timer clearing on demand · case 02

A brief quiet spell after busy traffic triggers a shutdown.

Elevator dispatch scheduling◈ Members↗
FA-67818

Energy saving car shutdown: timer clearing on demand · case 03

A brief quiet spell after busy traffic triggers a shutdown.

Elevator dispatch scheduling◈ Members↗
FA-67819

Energy saving car shutdown: timer clearing on demand · case 04

A brief quiet spell after busy traffic triggers a shutdown.

Elevator dispatch scheduling◈ Members↗
FA-67820

Energy saving car shutdown: timer clearing on demand · case 05

A brief quiet spell after busy traffic triggers a shutdown.

Elevator dispatch scheduling◈ Members↗
FA-67821

Encoder position and door zone detection: pulse unit conversion · case 01

The car position drifts or barely moves with encoder pulses.

Elevator dispatch scheduling● Open access↗
FA-67822

Encoder position and door zone detection: pulse unit conversion · case 02

The car position drifts or barely moves with encoder pulses.

Elevator dispatch scheduling◈ Members↗
FA-67823

Encoder position and door zone detection: pulse unit conversion · case 03

The car position drifts or barely moves with encoder pulses.

Elevator dispatch scheduling◈ Members↗
FA-67824

Encoder position and door zone detection: pulse unit conversion · case 04

The car position drifts or barely moves with encoder pulses.

Elevator dispatch scheduling◈ Members↗
FA-67825

Encoder position and door zone detection: pulse unit conversion · case 05

The car position drifts or barely moves with encoder pulses.

Elevator dispatch scheduling◈ Members↗
FA-67826

Encoder position and door zone detection: magnet correction · case 01

Passing a door-zone magnet throws the position far off.

Elevator dispatch scheduling● Open access↗
FA-67827

Encoder position and door zone detection: magnet correction · case 02

Passing a door-zone magnet throws the position far off.

Elevator dispatch scheduling◈ Members↗
FA-67828

Encoder position and door zone detection: magnet correction · case 03

Passing a door-zone magnet throws the position far off.

Elevator dispatch scheduling◈ Members↗
FA-67829

Encoder position and door zone detection: magnet correction · case 04

Passing a door-zone magnet throws the position far off.

Elevator dispatch scheduling◈ Members↗
FA-67830

Encoder position and door zone detection: magnet correction · case 05

Passing a door-zone magnet throws the position far off.

Elevator dispatch scheduling◈ Members↗
FA-67831

Encoder position and door zone detection: door zone test · case 01

A car exactly at the zone edge is reported between floors.

Elevator dispatch scheduling● Open access↗
FA-67832

Encoder position and door zone detection: door zone test · case 02

A car exactly at the zone edge is reported between floors.

Elevator dispatch scheduling◈ Members↗
FA-67833

Encoder position and door zone detection: door zone test · case 03

A car exactly at the zone edge is reported between floors.

Elevator dispatch scheduling◈ Members↗
FA-67834

Encoder position and door zone detection: door zone test · case 04

A car exactly at the zone edge is reported between floors.

Elevator dispatch scheduling◈ Members↗
FA-67835

Encoder position and door zone detection: door zone test · case 05

A car exactly at the zone edge is reported between floors.

Elevator dispatch scheduling◈ Members↗
FA-67836

Encoder position and door zone detection: millimetre rounding · case 01

Positions just short of the zone edge are rounded into it.

Elevator dispatch scheduling● Open access↗
FA-67837

Encoder position and door zone detection: millimetre rounding · case 02

Positions just short of the zone edge are rounded into it.

Elevator dispatch scheduling◈ Members↗
FA-67838

Encoder position and door zone detection: millimetre rounding · case 03

Positions just short of the zone edge are rounded into it.

Elevator dispatch scheduling◈ Members↗
FA-67839

Encoder position and door zone detection: millimetre rounding · case 04

Positions just short of the zone edge are rounded into it.

Elevator dispatch scheduling◈ Members↗
FA-67840

Encoder position and door zone detection: millimetre rounding · case 05

Positions just short of the zone edge are rounded into it.

Elevator dispatch scheduling◈ Members↗
FA-67841

Webster cycle length: critical ratio sums every lane group of a phase · case 01

Webster cycle length returns a wrong result when critical ratio sums every lane group of a phase.

Traffic signal timing plans● Open access↗
FA-67842

Webster cycle length: critical ratio sums every lane group of a phase · case 02

Webster cycle length returns a wrong result when critical ratio sums every lane group of a phase.

Traffic signal timing plans◈ Members↗
FA-67843

Webster cycle length: critical ratio sums every lane group of a phase · case 03

Webster cycle length returns a wrong result when critical ratio sums every lane group of a phase.

Traffic signal timing plans◈ Members↗
FA-67844

Webster cycle length: critical ratio sums every lane group of a phase · case 04

Webster cycle length returns a wrong result when critical ratio sums every lane group of a phase.

Traffic signal timing plans◈ Members↗
FA-67845

Webster cycle length: critical ratio sums every lane group of a phase · case 05

Webster cycle length returns a wrong result when critical ratio sums every lane group of a phase.

Traffic signal timing plans◈ Members↗
FA-67846

Webster cycle length: lost time is counted once per cycle instead of once per phase · case 01

Webster cycle length returns a wrong result when lost time is counted once per cycle instead of once per phase.

Traffic signal timing plans● Open access↗
FA-67847

Webster cycle length: lost time is counted once per cycle instead of once per phase · case 02

Webster cycle length returns a wrong result when lost time is counted once per cycle instead of once per phase.

Traffic signal timing plans◈ Members↗
FA-67848

Webster cycle length: lost time is counted once per cycle instead of once per phase · case 03

Webster cycle length returns a wrong result when lost time is counted once per cycle instead of once per phase.

Traffic signal timing plans◈ Members↗
FA-67849

Webster cycle length: lost time is counted once per cycle instead of once per phase · case 04

Webster cycle length returns a wrong result when lost time is counted once per cycle instead of once per phase.

Traffic signal timing plans◈ Members↗
FA-67850

Webster cycle length: lost time is counted once per cycle instead of once per phase · case 05

Webster cycle length returns a wrong result when lost time is counted once per cycle instead of once per phase.

Traffic signal timing plans◈ Members↗
FA-67851

Webster cycle length: the constant 5 s is scaled together with lost time · case 01

Webster cycle length returns a wrong result when the constant 5 s is scaled together with lost time.

Traffic signal timing plans● Open access↗
FA-67852

Webster cycle length: the constant 5 s is scaled together with lost time · case 02

Webster cycle length returns a wrong result when the constant 5 s is scaled together with lost time.

Traffic signal timing plans◈ Members↗
FA-67853

Webster cycle length: the constant 5 s is scaled together with lost time · case 03

Webster cycle length returns a wrong result when the constant 5 s is scaled together with lost time.

Traffic signal timing plans◈ Members↗
FA-67854

Webster cycle length: the constant 5 s is scaled together with lost time · case 04

Webster cycle length returns a wrong result when the constant 5 s is scaled together with lost time.

Traffic signal timing plans◈ Members↗
FA-67855

Webster cycle length: the constant 5 s is scaled together with lost time · case 05

Webster cycle length returns a wrong result when the constant 5 s is scaled together with lost time.

Traffic signal timing plans◈ Members↗
FA-67856

Webster cycle length: the computed cycle is rounded down to a 5 s multiple · case 01

Webster cycle length returns a wrong result when the computed cycle is rounded down to a 5 s multiple.

Traffic signal timing plans● Open access↗
FA-67857

Webster cycle length: the computed cycle is rounded down to a 5 s multiple · case 02

Webster cycle length returns a wrong result when the computed cycle is rounded down to a 5 s multiple.

Traffic signal timing plans◈ Members↗
FA-67858

Webster cycle length: the computed cycle is rounded down to a 5 s multiple · case 03

Webster cycle length returns a wrong result when the computed cycle is rounded down to a 5 s multiple.

Traffic signal timing plans◈ Members↗
FA-67859

Webster cycle length: the computed cycle is rounded down to a 5 s multiple · case 04

Webster cycle length returns a wrong result when the computed cycle is rounded down to a 5 s multiple.

Traffic signal timing plans◈ Members↗
FA-67860

Webster cycle length: the computed cycle is rounded down to a 5 s multiple · case 05

Webster cycle length returns a wrong result when the computed cycle is rounded down to a 5 s multiple.

Traffic signal timing plans◈ Members↗
FA-67861

Webster cycle length: the oversaturation guard only trips above Y = 1 · case 01

Webster cycle length returns a wrong result when the oversaturation guard only trips above Y = 1.

Traffic signal timing plans● Open access↗
FA-67862

Webster cycle length: the oversaturation guard only trips above Y = 1 · case 02

Webster cycle length returns a wrong result when the oversaturation guard only trips above Y = 1.

Traffic signal timing plans◈ Members↗
FA-67863

Webster cycle length: the oversaturation guard only trips above Y = 1 · case 03

Webster cycle length returns a wrong result when the oversaturation guard only trips above Y = 1.

Traffic signal timing plans◈ Members↗
FA-67864

Webster cycle length: the oversaturation guard only trips above Y = 1 · case 04

Webster cycle length returns a wrong result when the oversaturation guard only trips above Y = 1.

Traffic signal timing plans◈ Members↗
FA-67865

Webster cycle length: the oversaturation guard only trips above Y = 1 · case 05

Webster cycle length returns a wrong result when the oversaturation guard only trips above Y = 1.

Traffic signal timing plans◈ Members↗
FA-67866

Webster cycle length: the cycle is not capped at the controller maximum · case 01

Webster cycle length returns a wrong result when the cycle is not capped at the controller maximum.

Traffic signal timing plans● Open access↗
FA-67867

Webster cycle length: the cycle is not capped at the controller maximum · case 02

Webster cycle length returns a wrong result when the cycle is not capped at the controller maximum.

Traffic signal timing plans◈ Members↗
FA-67868

Webster cycle length: the cycle is not capped at the controller maximum · case 03

Webster cycle length returns a wrong result when the cycle is not capped at the controller maximum.

Traffic signal timing plans◈ Members↗
FA-67869

Webster cycle length: the cycle is not capped at the controller maximum · case 04

Webster cycle length returns a wrong result when the cycle is not capped at the controller maximum.

Traffic signal timing plans◈ Members↗
FA-67870

Webster cycle length: the cycle is not capped at the controller maximum · case 05

Webster cycle length returns a wrong result when the cycle is not capped at the controller maximum.

Traffic signal timing plans◈ Members↗
FA-67871

Green split allocation: the whole cycle is distributed as green · case 01

Green split allocation returns a wrong result when the whole cycle is distributed as green.

Traffic signal timing plans● Open access↗
FA-67872

Green split allocation: the whole cycle is distributed as green · case 02

Green split allocation returns a wrong result when the whole cycle is distributed as green.

Traffic signal timing plans◈ Members↗
FA-67873

Green split allocation: the whole cycle is distributed as green · case 03

Green split allocation returns a wrong result when the whole cycle is distributed as green.

Traffic signal timing plans◈ Members↗
FA-67874

Green split allocation: the whole cycle is distributed as green · case 04

Green split allocation returns a wrong result when the whole cycle is distributed as green.

Traffic signal timing plans◈ Members↗
FA-67875

Green split allocation: the whole cycle is distributed as green · case 05

Green split allocation returns a wrong result when the whole cycle is distributed as green.

Traffic signal timing plans◈ Members↗
FA-67876

Green split allocation: leftover seconds go to the smallest remainders · case 01

Green split allocation returns a wrong result when leftover seconds go to the smallest remainders.

Traffic signal timing plans● Open access↗
FA-67877

Green split allocation: leftover seconds go to the smallest remainders · case 02

Green split allocation returns a wrong result when leftover seconds go to the smallest remainders.

Traffic signal timing plans◈ Members↗
FA-67878

Green split allocation: leftover seconds go to the smallest remainders · case 03

Green split allocation returns a wrong result when leftover seconds go to the smallest remainders.

Traffic signal timing plans◈ Members↗
FA-67879

Green split allocation: leftover seconds go to the smallest remainders · case 04

Green split allocation returns a wrong result when leftover seconds go to the smallest remainders.

Traffic signal timing plans◈ Members↗
FA-67880

Green split allocation: leftover seconds go to the smallest remainders · case 05

Green split allocation returns a wrong result when leftover seconds go to the smallest remainders.

Traffic signal timing plans◈ Members↗
FA-67881

Green split allocation: base shares are rounded to nearest before remainder distribution · case 01

Green split allocation returns a wrong result when base shares are rounded to nearest before remainder distribution.

Traffic signal timing plans● Open access↗
FA-67882

Green split allocation: base shares are rounded to nearest before remainder distribution · case 02

Green split allocation returns a wrong result when base shares are rounded to nearest before remainder distribution.

Traffic signal timing plans◈ Members↗
FA-67883

Green split allocation: base shares are rounded to nearest before remainder distribution · case 03

Green split allocation returns a wrong result when base shares are rounded to nearest before remainder distribution.

Traffic signal timing plans◈ Members↗
FA-67884

Green split allocation: base shares are rounded to nearest before remainder distribution · case 04

Green split allocation returns a wrong result when base shares are rounded to nearest before remainder distribution.

Traffic signal timing plans◈ Members↗
FA-67885

Green split allocation: base shares are rounded to nearest before remainder distribution · case 05

Green split allocation returns a wrong result when base shares are rounded to nearest before remainder distribution.

Traffic signal timing plans◈ Members↗
FA-67886

Green split allocation: critical flow ratios are read as den over num · case 01

Green split allocation returns a wrong result when critical flow ratios are read as den over num.

Traffic signal timing plans● Open access↗
FA-67887

Green split allocation: critical flow ratios are read as den over num · case 02

Green split allocation returns a wrong result when critical flow ratios are read as den over num.

Traffic signal timing plans◈ Members↗
FA-67888

Green split allocation: critical flow ratios are read as den over num · case 03

Green split allocation returns a wrong result when critical flow ratios are read as den over num.

Traffic signal timing plans◈ Members↗
FA-67889

Green split allocation: critical flow ratios are read as den over num · case 04

Green split allocation returns a wrong result when critical flow ratios are read as den over num.

Traffic signal timing plans◈ Members↗
FA-67890

Green split allocation: critical flow ratios are read as den over num · case 05

Green split allocation returns a wrong result when critical flow ratios are read as den over num.

Traffic signal timing plans◈ Members↗
FA-67891

Green split allocation: feasibility compares the single largest minimum with G · case 01

Green split allocation returns a wrong result when feasibility compares the single largest minimum with G.

Traffic signal timing plans● Open access↗
FA-67892

Green split allocation: feasibility compares the single largest minimum with G · case 02

Green split allocation returns a wrong result when feasibility compares the single largest minimum with G.

Traffic signal timing plans◈ Members↗
FA-67893

Green split allocation: feasibility compares the single largest minimum with G · case 03

Green split allocation returns a wrong result when feasibility compares the single largest minimum with G.

Traffic signal timing plans◈ Members↗
FA-67894

Green split allocation: feasibility compares the single largest minimum with G · case 04

Green split allocation returns a wrong result when feasibility compares the single largest minimum with G.

Traffic signal timing plans◈ Members↗
FA-67895

Green split allocation: feasibility compares the single largest minimum with G · case 05

Green split allocation returns a wrong result when feasibility compares the single largest minimum with G.

Traffic signal timing plans◈ Members↗
FA-67896

Green split allocation: minimum green seconds are taken from the longest green regardless of its own minimum · case 01

Green split allocation returns a wrong result when minimum green seconds are taken from the longest green regardless of its own minimum.

Traffic signal timing plans● Open access↗
FA-67897

Green split allocation: minimum green seconds are taken from the longest green regardless of its own minimum · case 02

Green split allocation returns a wrong result when minimum green seconds are taken from the longest green regardless of its own minimum.

Traffic signal timing plans◈ Members↗
FA-67898

Green split allocation: minimum green seconds are taken from the longest green regardless of its own minimum · case 03

Green split allocation returns a wrong result when minimum green seconds are taken from the longest green regardless of its own minimum.

Traffic signal timing plans◈ Members↗
FA-67899

Green split allocation: minimum green seconds are taken from the longest green regardless of its own minimum · case 04

Green split allocation returns a wrong result when minimum green seconds are taken from the longest green regardless of its own minimum.

Traffic signal timing plans◈ Members↗
FA-67900

Green split allocation: minimum green seconds are taken from the longest green regardless of its own minimum · case 05

Green split allocation returns a wrong result when minimum green seconds are taken from the longest green regardless of its own minimum.

Traffic signal timing plans◈ 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 ↗