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

Quasi Newton update admits nonpositive curvature · case 01

Quasi Newton update admits nonpositive curvature.

Optimization solver contracts● Open access↗
FA-12002

Quasi Newton update admits nonpositive curvature · case 02

Quasi Newton update admits nonpositive curvature.

Optimization solver contracts◈ Members↗
FA-12003

Quasi Newton update admits nonpositive curvature · case 03

Quasi Newton update admits nonpositive curvature.

Optimization solver contracts◈ Members↗
FA-12004

Quasi Newton update admits nonpositive curvature · case 04

Quasi Newton update admits nonpositive curvature.

Optimization solver contracts◈ Members↗
FA-12005

Quasi Newton update admits nonpositive curvature · case 05

Quasi Newton update admits nonpositive curvature.

Optimization solver contracts◈ Members↗
FA-12006

Branch and bound prunes against an infeasible incumbent · case 01

Branch and bound prunes against an infeasible incumbent.

Optimization solver contracts● Open access↗
FA-12007

Branch and bound prunes against an infeasible incumbent · case 02

Branch and bound prunes against an infeasible incumbent.

Optimization solver contracts◈ Members↗
FA-12008

Branch and bound prunes against an infeasible incumbent · case 03

Branch and bound prunes against an infeasible incumbent.

Optimization solver contracts◈ Members↗
FA-12009

Branch and bound prunes against an infeasible incumbent · case 04

Branch and bound prunes against an infeasible incumbent.

Optimization solver contracts◈ Members↗
FA-12010

Branch and bound prunes against an infeasible incumbent · case 05

Branch and bound prunes against an infeasible incumbent.

Optimization solver contracts◈ Members↗
FA-12011

Simplex leaving row includes nonlimiting coefficients · case 01

Simplex leaving row includes nonlimiting coefficients.

Optimization solver contracts● Open access↗
FA-12012

Simplex leaving row includes nonlimiting coefficients · case 02

Simplex leaving row includes nonlimiting coefficients.

Optimization solver contracts◈ Members↗
FA-12013

Simplex leaving row includes nonlimiting coefficients · case 03

Simplex leaving row includes nonlimiting coefficients.

Optimization solver contracts◈ Members↗
FA-12014

Simplex leaving row includes nonlimiting coefficients · case 04

Simplex leaving row includes nonlimiting coefficients.

Optimization solver contracts◈ Members↗
FA-12015

Simplex leaving row includes nonlimiting coefficients · case 05

Simplex leaving row includes nonlimiting coefficients.

Optimization solver contracts◈ Members↗
FA-12016

Conjugate gradient search direction uses the residual delta · case 01

Conjugate gradient search direction uses the residual delta.

Optimization solver contracts● Open access↗
FA-12017

Conjugate gradient search direction uses the residual delta · case 02

Conjugate gradient search direction uses the residual delta.

Optimization solver contracts◈ Members↗
FA-12018

Conjugate gradient search direction uses the residual delta · case 03

Conjugate gradient search direction uses the residual delta.

Optimization solver contracts◈ Members↗
FA-12019

Conjugate gradient search direction uses the residual delta · case 04

Conjugate gradient search direction uses the residual delta.

Optimization solver contracts◈ Members↗
FA-12020

Conjugate gradient search direction uses the residual delta · case 05

Conjugate gradient search direction uses the residual delta.

Optimization solver contracts◈ Members↗
FA-12021

Trust region accepts steps with a nondecreasing model · case 01

Trust region accepts steps with a nondecreasing model.

Optimization solver contracts● Open access↗
FA-12022

Trust region accepts steps with a nondecreasing model · case 02

Trust region accepts steps with a nondecreasing model.

Optimization solver contracts◈ Members↗
FA-12023

Trust region accepts steps with a nondecreasing model · case 03

Trust region accepts steps with a nondecreasing model.

Optimization solver contracts◈ Members↗
FA-12024

Trust region accepts steps with a nondecreasing model · case 04

Trust region accepts steps with a nondecreasing model.

Optimization solver contracts◈ Members↗
FA-12025

Trust region accepts steps with a nondecreasing model · case 05

Trust region accepts steps with a nondecreasing model.

Optimization solver contracts◈ Members↗
FA-12026

Constraint violation is traded away by objective weighting · case 01

Constraint violation is traded away by objective weighting.

Optimization solver contracts● Open access↗
FA-12027

Constraint violation is traded away by objective weighting · case 02

Constraint violation is traded away by objective weighting.

Optimization solver contracts◈ Members↗
FA-12028

Constraint violation is traded away by objective weighting · case 03

Constraint violation is traded away by objective weighting.

Optimization solver contracts◈ Members↗
FA-12029

Constraint violation is traded away by objective weighting · case 04

Constraint violation is traded away by objective weighting.

Optimization solver contracts◈ Members↗
FA-12030

Constraint violation is traded away by objective weighting · case 05

Constraint violation is traded away by objective weighting.

Optimization solver contracts◈ Members↗
FA-12031

Coordinate descent sweep reads stale coordinates · case 01

Coordinate descent sweep reads stale coordinates.

Optimization solver contracts● Open access↗
FA-12032

Coordinate descent sweep reads stale coordinates · case 02

Coordinate descent sweep reads stale coordinates.

Optimization solver contracts◈ Members↗
FA-12033

Coordinate descent sweep reads stale coordinates · case 03

Coordinate descent sweep reads stale coordinates.

Optimization solver contracts◈ Members↗
FA-12034

Coordinate descent sweep reads stale coordinates · case 04

Coordinate descent sweep reads stale coordinates.

Optimization solver contracts◈ Members↗
FA-12035

Coordinate descent sweep reads stale coordinates · case 05

Coordinate descent sweep reads stale coordinates.

Optimization solver contracts◈ Members↗
FA-12036

Iteration exhaustion is reported as convergence · case 01

Iteration exhaustion is reported as convergence.

Optimization solver contracts● Open access↗
FA-12037

Iteration exhaustion is reported as convergence · case 02

Iteration exhaustion is reported as convergence.

Optimization solver contracts◈ Members↗
FA-12038

Iteration exhaustion is reported as convergence · case 03

Iteration exhaustion is reported as convergence.

Optimization solver contracts◈ Members↗
FA-12039

Iteration exhaustion is reported as convergence · case 04

Iteration exhaustion is reported as convergence.

Optimization solver contracts◈ Members↗
FA-12040

Iteration exhaustion is reported as convergence · case 05

Iteration exhaustion is reported as convergence.

Optimization solver contracts◈ Members↗
FA-12041

Arrival time makes an old measurement look fresh · case 01

Delayed sensor samples enter the current fusion window.

Sensor fusion consistency● Open access↗
FA-12042

Arrival time makes an old measurement look fresh · case 02

Delayed sensor samples enter the current fusion window.

Sensor fusion consistency◈ Members↗
FA-12043

Arrival time makes an old measurement look fresh · case 03

Delayed sensor samples enter the current fusion window.

Sensor fusion consistency◈ Members↗
FA-12044

Arrival time makes an old measurement look fresh · case 04

Delayed sensor samples enter the current fusion window.

Sensor fusion consistency◈ Members↗
FA-12045

Arrival time makes an old measurement look fresh · case 05

Delayed sensor samples enter the current fusion window.

Sensor fusion consistency◈ Members↗
FA-12046

Sensor clock offset is applied with the wrong sign · case 01

Cross-sensor association rejects simultaneous samples.

Sensor fusion consistency● Open access↗
FA-12047

Sensor clock offset is applied with the wrong sign · case 02

Cross-sensor association rejects simultaneous samples.

Sensor fusion consistency◈ Members↗
FA-12048

Sensor clock offset is applied with the wrong sign · case 03

Cross-sensor association rejects simultaneous samples.

Sensor fusion consistency◈ Members↗
FA-12049

Sensor clock offset is applied with the wrong sign · case 04

Cross-sensor association rejects simultaneous samples.

Sensor fusion consistency◈ Members↗
FA-12050

Sensor clock offset is applied with the wrong sign · case 05

Cross-sensor association rejects simultaneous samples.

Sensor fusion consistency◈ Members↗
FA-12051

Repeated sensor packet is counted as independent evidence · case 01

Retransmission artificially increases measurement information.

Sensor fusion consistency● Open access↗
FA-12052

Repeated sensor packet is counted as independent evidence · case 02

Retransmission artificially increases measurement information.

Sensor fusion consistency◈ Members↗
FA-12053

Repeated sensor packet is counted as independent evidence · case 03

Retransmission artificially increases measurement information.

Sensor fusion consistency◈ Members↗
FA-12054

Repeated sensor packet is counted as independent evidence · case 04

Retransmission artificially increases measurement information.

Sensor fusion consistency◈ Members↗
FA-12055

Repeated sensor packet is counted as independent evidence · case 05

Retransmission artificially increases measurement information.

Sensor fusion consistency◈ Members↗
FA-12056

Correlated estimates lose shared uncertainty during fusion · case 01

Reported fused uncertainty is smaller than the shared sensor noise.

Sensor fusion consistency● Open access↗
FA-12057

Correlated estimates lose shared uncertainty during fusion · case 02

Reported fused uncertainty is smaller than the shared sensor noise.

Sensor fusion consistency◈ Members↗
FA-12058

Correlated estimates lose shared uncertainty during fusion · case 03

Reported fused uncertainty is smaller than the shared sensor noise.

Sensor fusion consistency◈ Members↗
FA-12059

Correlated estimates lose shared uncertainty during fusion · case 04

Reported fused uncertainty is smaller than the shared sensor noise.

Sensor fusion consistency◈ Members↗
FA-12060

Correlated estimates lose shared uncertainty during fusion · case 05

Reported fused uncertainty is smaller than the shared sensor noise.

Sensor fusion consistency◈ Members↗
FA-12061

Missing measurement axis resets a tracked component · case 01

A sensor observing only one axis overwrites the other estimate.

Sensor fusion consistency● Open access↗
FA-12062

Missing measurement axis resets a tracked component · case 02

A sensor observing only one axis overwrites the other estimate.

Sensor fusion consistency◈ Members↗
FA-12063

Missing measurement axis resets a tracked component · case 03

A sensor observing only one axis overwrites the other estimate.

Sensor fusion consistency◈ Members↗
FA-12064

Missing measurement axis resets a tracked component · case 04

A sensor observing only one axis overwrites the other estimate.

Sensor fusion consistency◈ Members↗
FA-12065

Missing measurement axis resets a tracked component · case 05

A sensor observing only one axis overwrites the other estimate.

Sensor fusion consistency◈ Members↗
FA-12066

Measurement channel permutation leaves covariance behind · case 01

An uncertainty belongs to the wrong sensor channel.

Sensor fusion consistency● Open access↗
FA-12067

Measurement channel permutation leaves covariance behind · case 02

An uncertainty belongs to the wrong sensor channel.

Sensor fusion consistency◈ Members↗
FA-12068

Measurement channel permutation leaves covariance behind · case 03

An uncertainty belongs to the wrong sensor channel.

Sensor fusion consistency◈ Members↗
FA-12069

Measurement channel permutation leaves covariance behind · case 04

An uncertainty belongs to the wrong sensor channel.

Sensor fusion consistency◈ Members↗
FA-12070

Measurement channel permutation leaves covariance behind · case 05

An uncertainty belongs to the wrong sensor channel.

Sensor fusion consistency◈ Members↗
FA-12071

Innovation gate ignores uncertainty in the predicted state · case 01

Plausible measurements are rejected when prediction uncertainty grows.

Sensor fusion consistency● Open access↗
FA-12072

Innovation gate ignores uncertainty in the predicted state · case 02

Plausible measurements are rejected when prediction uncertainty grows.

Sensor fusion consistency◈ Members↗
FA-12073

Innovation gate ignores uncertainty in the predicted state · case 03

Plausible measurements are rejected when prediction uncertainty grows.

Sensor fusion consistency◈ Members↗
FA-12074

Innovation gate ignores uncertainty in the predicted state · case 04

Plausible measurements are rejected when prediction uncertainty grows.

Sensor fusion consistency◈ Members↗
FA-12075

Innovation gate ignores uncertainty in the predicted state · case 05

Plausible measurements are rejected when prediction uncertainty grows.

Sensor fusion consistency◈ Members↗
FA-12076

Dropped samples do not accumulate process uncertainty · case 01

Prediction confidence remains too high after a long acquisition gap.

Sensor fusion consistency● Open access↗
FA-12077

Dropped samples do not accumulate process uncertainty · case 02

Prediction confidence remains too high after a long acquisition gap.

Sensor fusion consistency◈ Members↗
FA-12078

Dropped samples do not accumulate process uncertainty · case 03

Prediction confidence remains too high after a long acquisition gap.

Sensor fusion consistency◈ Members↗
FA-12079

Dropped samples do not accumulate process uncertainty · case 04

Prediction confidence remains too high after a long acquisition gap.

Sensor fusion consistency◈ Members↗
FA-12080

Dropped samples do not accumulate process uncertainty · case 05

Prediction confidence remains too high after a long acquisition gap.

Sensor fusion consistency◈ Members↗
FA-12081

Delayed measurement is applied at the current state epoch · case 01

A late position fix pulls the present estimate backwards along the trajectory.

Sensor fusion consistency● Open access↗
FA-12082

Delayed measurement is applied at the current state epoch · case 02

A late position fix pulls the present estimate backwards along the trajectory.

Sensor fusion consistency◈ Members↗
FA-12083

Delayed measurement is applied at the current state epoch · case 03

A late position fix pulls the present estimate backwards along the trajectory.

Sensor fusion consistency◈ Members↗
FA-12084

Delayed measurement is applied at the current state epoch · case 04

A late position fix pulls the present estimate backwards along the trajectory.

Sensor fusion consistency◈ Members↗
FA-12085

Delayed measurement is applied at the current state epoch · case 05

A late position fix pulls the present estimate backwards along the trajectory.

Sensor fusion consistency◈ Members↗
FA-12086

Calibration scales measurements but leaves their variances in raw units · case 01

Fusion weights change when an equivalent sensor representation changes units.

Sensor fusion consistency● Open access↗
FA-12087

Calibration scales measurements but leaves their variances in raw units · case 02

Fusion weights change when an equivalent sensor representation changes units.

Sensor fusion consistency◈ Members↗
FA-12088

Calibration scales measurements but leaves their variances in raw units · case 03

Fusion weights change when an equivalent sensor representation changes units.

Sensor fusion consistency◈ Members↗
FA-12089

Calibration scales measurements but leaves their variances in raw units · case 04

Fusion weights change when an equivalent sensor representation changes units.

Sensor fusion consistency◈ Members↗
FA-12090

Calibration scales measurements but leaves their variances in raw units · case 05

Fusion weights change when an equivalent sensor representation changes units.

Sensor fusion consistency◈ Members↗
FA-12091

Optical camera coordinates are mistaken for forward-left-up coordinates · case 01

Optical camera coordinates are mistaken for forward-left-up coordinates.

Robotics frame conventions● Open access↗
FA-12092

Optical camera coordinates are mistaken for forward-left-up coordinates · case 02

Optical camera coordinates are mistaken for forward-left-up coordinates.

Robotics frame conventions◈ Members↗
FA-12093

Optical camera coordinates are mistaken for forward-left-up coordinates · case 03

Optical camera coordinates are mistaken for forward-left-up coordinates.

Robotics frame conventions◈ Members↗
FA-12094

Optical camera coordinates are mistaken for forward-left-up coordinates · case 04

Optical camera coordinates are mistaken for forward-left-up coordinates.

Robotics frame conventions◈ Members↗
FA-12095

Optical camera coordinates are mistaken for forward-left-up coordinates · case 05

Optical camera coordinates are mistaken for forward-left-up coordinates.

Robotics frame conventions◈ Members↗
FA-12096

North-east-down positions are labeled as east-north-up · case 01

North-east-down positions are labeled as east-north-up.

Robotics frame conventions● Open access↗
FA-12097

North-east-down positions are labeled as east-north-up · case 02

North-east-down positions are labeled as east-north-up.

Robotics frame conventions◈ Members↗
FA-12098

North-east-down positions are labeled as east-north-up · case 03

North-east-down positions are labeled as east-north-up.

Robotics frame conventions◈ Members↗
FA-12099

North-east-down positions are labeled as east-north-up · case 04

North-east-down positions are labeled as east-north-up.

Robotics frame conventions◈ Members↗
FA-12100

North-east-down positions are labeled as east-north-up · case 05

North-east-down positions are labeled as east-north-up.

Robotics frame conventions◈ 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 ↗