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

Foreign key orphans: Treats existing inactive parents as absent · case 01

The query violates its result contract: treats existing inactive parents as absent.

Schema migrations● Open access↗
FA-2702

Foreign key orphans: Treats existing inactive parents as absent · case 02

The query violates its result contract: treats existing inactive parents as absent.

Schema migrations◈ Members↗
FA-2703

Foreign key orphans: Treats existing inactive parents as absent · case 03

The query violates its result contract: treats existing inactive parents as absent.

Schema migrations◈ Members↗
FA-2704

Foreign key orphans: Treats existing inactive parents as absent · case 04

The query violates its result contract: treats existing inactive parents as absent.

Schema migrations◈ Members↗
FA-2705

Foreign key orphans: Treats existing inactive parents as absent · case 05

The query violates its result contract: treats existing inactive parents as absent.

Schema migrations◈ Members↗
FA-2706

Null backfill: Overwrites known zero values as if missing · case 01

The query violates its result contract: overwrites known zero values as if missing.

Schema migrations● Open access↗
FA-2707

Null backfill: Overwrites known zero values as if missing · case 02

The query violates its result contract: overwrites known zero values as if missing.

Schema migrations◈ Members↗
FA-2708

Null backfill: Overwrites known zero values as if missing · case 03

The query violates its result contract: overwrites known zero values as if missing.

Schema migrations◈ Members↗
FA-2709

Null backfill: Overwrites known zero values as if missing · case 04

The query violates its result contract: overwrites known zero values as if missing.

Schema migrations◈ Members↗
FA-2710

Null backfill: Overwrites known zero values as if missing · case 05

The query violates its result contract: overwrites known zero values as if missing.

Schema migrations◈ Members↗
FA-2711

Null backfill: Prioritizes fallback over existing values · case 01

The query violates its result contract: prioritizes fallback over existing values.

Schema migrations● Open access↗
FA-2712

Null backfill: Prioritizes fallback over existing values · case 02

The query violates its result contract: prioritizes fallback over existing values.

Schema migrations◈ Members↗
FA-2713

Null backfill: Prioritizes fallback over existing values · case 03

The query violates its result contract: prioritizes fallback over existing values.

Schema migrations◈ Members↗
FA-2714

Null backfill: Prioritizes fallback over existing values · case 04

The query violates its result contract: prioritizes fallback over existing values.

Schema migrations◈ Members↗
FA-2715

Null backfill: Prioritizes fallback over existing values · case 05

The query violates its result contract: prioritizes fallback over existing values.

Schema migrations◈ Members↗
FA-2716

Null backfill: Uses equality to NULL and never backfills · case 01

The query violates its result contract: uses equality to null and never backfills.

Schema migrations● Open access↗
FA-2717

Null backfill: Uses equality to NULL and never backfills · case 02

The query violates its result contract: uses equality to null and never backfills.

Schema migrations◈ Members↗
FA-2718

Null backfill: Uses equality to NULL and never backfills · case 03

The query violates its result contract: uses equality to null and never backfills.

Schema migrations◈ Members↗
FA-2719

Null backfill: Uses equality to NULL and never backfills · case 04

The query violates its result contract: uses equality to null and never backfills.

Schema migrations◈ Members↗
FA-2720

Null backfill: Uses equality to NULL and never backfills · case 05

The query violates its result contract: uses equality to null and never backfills.

Schema migrations◈ Members↗
FA-2721

Null backfill: Overwrites populated values during backfill · case 01

The query violates its result contract: overwrites populated values during backfill.

Schema migrations● Open access↗
FA-2722

Null backfill: Overwrites populated values during backfill · case 02

The query violates its result contract: overwrites populated values during backfill.

Schema migrations◈ Members↗
FA-2723

Null backfill: Overwrites populated values during backfill · case 03

The query violates its result contract: overwrites populated values during backfill.

Schema migrations◈ Members↗
FA-2724

Null backfill: Overwrites populated values during backfill · case 04

The query violates its result contract: overwrites populated values during backfill.

Schema migrations◈ Members↗
FA-2725

Null backfill: Overwrites populated values during backfill · case 05

The query violates its result contract: overwrites populated values during backfill.

Schema migrations◈ Members↗
FA-2726

Null backfill: Returns only updated rows and loses untouched records · case 01

The query violates its result contract: returns only updated rows and loses untouched records.

Schema migrations● Open access↗
FA-2727

Null backfill: Returns only updated rows and loses untouched records · case 02

The query violates its result contract: returns only updated rows and loses untouched records.

Schema migrations◈ Members↗
FA-2728

Null backfill: Returns only updated rows and loses untouched records · case 03

The query violates its result contract: returns only updated rows and loses untouched records.

Schema migrations◈ Members↗
FA-2729

Null backfill: Returns only updated rows and loses untouched records · case 04

The query violates its result contract: returns only updated rows and loses untouched records.

Schema migrations◈ Members↗
FA-2730

Null backfill: Returns only updated rows and loses untouched records · case 05

The query violates its result contract: returns only updated rows and loses untouched records.

Schema migrations◈ Members↗
FA-2731

Boolean backfill: Fills NULL without normalizing nonzero values · case 01

The query violates its result contract: fills null without normalizing nonzero values.

Schema migrations● Open access↗
FA-2732

Boolean backfill: Fills NULL without normalizing nonzero values · case 02

The query violates its result contract: fills null without normalizing nonzero values.

Schema migrations◈ Members↗
FA-2733

Boolean backfill: Fills NULL without normalizing nonzero values · case 03

The query violates its result contract: fills null without normalizing nonzero values.

Schema migrations◈ Members↗
FA-2734

Boolean backfill: Fills NULL without normalizing nonzero values · case 04

The query violates its result contract: fills null without normalizing nonzero values.

Schema migrations◈ Members↗
FA-2735

Boolean backfill: Fills NULL without normalizing nonzero values · case 05

The query violates its result contract: fills null without normalizing nonzero values.

Schema migrations◈ Members↗
FA-2736

Boolean backfill: Treats only literal one as true · case 01

The query violates its result contract: treats only literal one as true.

Schema migrations● Open access↗
FA-2737

Boolean backfill: Treats only literal one as true · case 02

The query violates its result contract: treats only literal one as true.

Schema migrations◈ Members↗
FA-2738

Boolean backfill: Treats only literal one as true · case 03

The query violates its result contract: treats only literal one as true.

Schema migrations◈ Members↗
FA-2739

Boolean backfill: Treats only literal one as true · case 04

The query violates its result contract: treats only literal one as true.

Schema migrations◈ Members↗
FA-2740

Boolean backfill: Treats only literal one as true · case 05

The query violates its result contract: treats only literal one as true.

Schema migrations◈ Members↗
FA-2741

Boolean backfill: Misclassifies negative true flags as false · case 01

The query violates its result contract: misclassifies negative true flags as false.

Schema migrations● Open access↗
FA-2742

Boolean backfill: Misclassifies negative true flags as false · case 02

The query violates its result contract: misclassifies negative true flags as false.

Schema migrations◈ Members↗
FA-2743

Boolean backfill: Misclassifies negative true flags as false · case 03

The query violates its result contract: misclassifies negative true flags as false.

Schema migrations◈ Members↗
FA-2744

Boolean backfill: Misclassifies negative true flags as false · case 04

The query violates its result contract: misclassifies negative true flags as false.

Schema migrations◈ Members↗
FA-2745

Boolean backfill: Misclassifies negative true flags as false · case 05

The query violates its result contract: misclassifies negative true flags as false.

Schema migrations◈ Members↗
FA-2746

Boolean backfill: Migrates unknown flags to true · case 01

The query violates its result contract: migrates unknown flags to true.

Schema migrations● Open access↗
FA-2747

Boolean backfill: Migrates unknown flags to true · case 02

The query violates its result contract: migrates unknown flags to true.

Schema migrations◈ Members↗
FA-2748

Boolean backfill: Migrates unknown flags to true · case 03

The query violates its result contract: migrates unknown flags to true.

Schema migrations◈ Members↗
FA-2749

Boolean backfill: Migrates unknown flags to true · case 04

The query violates its result contract: migrates unknown flags to true.

Schema migrations◈ Members↗
FA-2750

Boolean backfill: Migrates unknown flags to true · case 05

The query violates its result contract: migrates unknown flags to true.

Schema migrations◈ Members↗
FA-2751

Boolean backfill: Treats known false flags as true · case 01

The query violates its result contract: treats known false flags as true.

Schema migrations● Open access↗
FA-2752

Boolean backfill: Treats known false flags as true · case 02

The query violates its result contract: treats known false flags as true.

Schema migrations◈ Members↗
FA-2753

Boolean backfill: Treats known false flags as true · case 03

The query violates its result contract: treats known false flags as true.

Schema migrations◈ Members↗
FA-2754

Boolean backfill: Treats known false flags as true · case 04

The query violates its result contract: treats known false flags as true.

Schema migrations◈ Members↗
FA-2755

Boolean backfill: Treats known false flags as true · case 05

The query violates its result contract: treats known false flags as true.

Schema migrations◈ Members↗
FA-2756

Latest key deduplication: Keeps the oldest row rather than latest · case 01

The query violates its result contract: keeps the oldest row rather than latest.

Data systems● Open access↗
FA-2757

Latest key deduplication: Keeps the oldest row rather than latest · case 02

The query violates its result contract: keeps the oldest row rather than latest.

Data systems◈ Members↗
FA-2758

Latest key deduplication: Keeps the oldest row rather than latest · case 03

The query violates its result contract: keeps the oldest row rather than latest.

Data systems◈ Members↗
FA-2759

Latest key deduplication: Keeps the oldest row rather than latest · case 04

The query violates its result contract: keeps the oldest row rather than latest.

Data systems◈ Members↗
FA-2760

Latest key deduplication: Keeps the oldest row rather than latest · case 05

The query violates its result contract: keeps the oldest row rather than latest.

Data systems◈ Members↗
FA-2761

Latest key deduplication: Selects greatest measurement rather than greatest identity · case 01

The query violates its result contract: selects greatest measurement rather than greatest identity.

Data systems● Open access↗
FA-2762

Latest key deduplication: Selects greatest measurement rather than greatest identity · case 02

The query violates its result contract: selects greatest measurement rather than greatest identity.

Data systems◈ Members↗
FA-2763

Latest key deduplication: Selects greatest measurement rather than greatest identity · case 03

The query violates its result contract: selects greatest measurement rather than greatest identity.

Data systems◈ Members↗
FA-2764

Latest key deduplication: Selects greatest measurement rather than greatest identity · case 04

The query violates its result contract: selects greatest measurement rather than greatest identity.

Data systems◈ Members↗
FA-2765

Latest key deduplication: Selects greatest measurement rather than greatest identity · case 05

The query violates its result contract: selects greatest measurement rather than greatest identity.

Data systems◈ Members↗
FA-2766

Latest key deduplication: Deduplicates the whole relation as one group · case 01

The query violates its result contract: deduplicates the whole relation as one group.

Data systems● Open access↗
FA-2767

Latest key deduplication: Deduplicates the whole relation as one group · case 02

The query violates its result contract: deduplicates the whole relation as one group.

Data systems◈ Members↗
FA-2768

Latest key deduplication: Deduplicates the whole relation as one group · case 03

The query violates its result contract: deduplicates the whole relation as one group.

Data systems◈ Members↗
FA-2769

Latest key deduplication: Deduplicates the whole relation as one group · case 04

The query violates its result contract: deduplicates the whole relation as one group.

Data systems◈ Members↗
FA-2770

Latest key deduplication: Deduplicates the whole relation as one group · case 05

The query violates its result contract: deduplicates the whole relation as one group.

Data systems◈ Members↗
FA-2771

Latest key deduplication: Drops the NULL-key group during survivor lookup · case 01

The query violates its result contract: drops the null-key group during survivor lookup.

Data systems● Open access↗
FA-2772

Latest key deduplication: Drops the NULL-key group during survivor lookup · case 02

The query violates its result contract: drops the null-key group during survivor lookup.

Data systems◈ Members↗
FA-2773

Latest key deduplication: Drops the NULL-key group during survivor lookup · case 03

The query violates its result contract: drops the null-key group during survivor lookup.

Data systems◈ Members↗
FA-2774

Latest key deduplication: Drops the NULL-key group during survivor lookup · case 04

The query violates its result contract: drops the null-key group during survivor lookup.

Data systems◈ Members↗
FA-2775

Latest key deduplication: Drops the NULL-key group during survivor lookup · case 05

The query violates its result contract: drops the null-key group during survivor lookup.

Data systems◈ Members↗
FA-2776

Latest key deduplication: Deduplicates by both key and payload · case 01

The query violates its result contract: deduplicates by both key and payload.

Data systems● Open access↗
FA-2777

Latest key deduplication: Deduplicates by both key and payload · case 02

The query violates its result contract: deduplicates by both key and payload.

Data systems◈ Members↗
FA-2778

Latest key deduplication: Deduplicates by both key and payload · case 03

The query violates its result contract: deduplicates by both key and payload.

Data systems◈ Members↗
FA-2779

Latest key deduplication: Deduplicates by both key and payload · case 04

The query violates its result contract: deduplicates by both key and payload.

Data systems◈ Members↗
FA-2780

Latest key deduplication: Deduplicates by both key and payload · case 05

The query violates its result contract: deduplicates by both key and payload.

Data systems◈ Members↗
FA-2781

Check constraint validation: Treats unknown CHECK results as violations · case 01

The query violates its result contract: treats unknown check results as violations.

Schema migrations● Open access↗
FA-2782

Check constraint validation: Treats unknown CHECK results as violations · case 02

The query violates its result contract: treats unknown check results as violations.

Schema migrations◈ Members↗
FA-2783

Check constraint validation: Treats unknown CHECK results as violations · case 03

The query violates its result contract: treats unknown check results as violations.

Schema migrations◈ Members↗
FA-2784

Check constraint validation: Treats unknown CHECK results as violations · case 04

The query violates its result contract: treats unknown check results as violations.

Schema migrations◈ Members↗
FA-2785

Check constraint validation: Treats unknown CHECK results as violations · case 05

The query violates its result contract: treats unknown check results as violations.

Schema migrations◈ Members↗
FA-2786

Check constraint validation: Mistakes a valid boundary zero for a violation · case 01

The query violates its result contract: mistakes a valid boundary zero for a violation.

Schema migrations● Open access↗
FA-2787

Check constraint validation: Mistakes a valid boundary zero for a violation · case 02

The query violates its result contract: mistakes a valid boundary zero for a violation.

Schema migrations◈ Members↗
FA-2788

Check constraint validation: Mistakes a valid boundary zero for a violation · case 03

The query violates its result contract: mistakes a valid boundary zero for a violation.

Schema migrations◈ Members↗
FA-2789

Check constraint validation: Mistakes a valid boundary zero for a violation · case 04

The query violates its result contract: mistakes a valid boundary zero for a violation.

Schema migrations◈ Members↗
FA-2790

Check constraint validation: Mistakes a valid boundary zero for a violation · case 05

The query violates its result contract: mistakes a valid boundary zero for a violation.

Schema migrations◈ Members↗
FA-2791

Check constraint validation: Inverts the check and reports valid positive rows · case 01

The query violates its result contract: inverts the check and reports valid positive rows.

Schema migrations● Open access↗
FA-2792

Check constraint validation: Inverts the check and reports valid positive rows · case 02

The query violates its result contract: inverts the check and reports valid positive rows.

Schema migrations◈ Members↗
FA-2793

Check constraint validation: Inverts the check and reports valid positive rows · case 03

The query violates its result contract: inverts the check and reports valid positive rows.

Schema migrations◈ Members↗
FA-2794

Check constraint validation: Inverts the check and reports valid positive rows · case 04

The query violates its result contract: inverts the check and reports valid positive rows.

Schema migrations◈ Members↗
FA-2795

Check constraint validation: Inverts the check and reports valid positive rows · case 05

The query violates its result contract: inverts the check and reports valid positive rows.

Schema migrations◈ Members↗
FA-2796

Check constraint validation: Validates flag instead of the migrated measurement · case 01

The query violates its result contract: validates flag instead of the migrated measurement.

Schema migrations● Open access↗
FA-2797

Check constraint validation: Validates flag instead of the migrated measurement · case 02

The query violates its result contract: validates flag instead of the migrated measurement.

Schema migrations◈ Members↗
FA-2798

Check constraint validation: Validates flag instead of the migrated measurement · case 03

The query violates its result contract: validates flag instead of the migrated measurement.

Schema migrations◈ Members↗
FA-2799

Check constraint validation: Validates flag instead of the migrated measurement · case 04

The query violates its result contract: validates flag instead of the migrated measurement.

Schema migrations◈ Members↗
FA-2800

Check constraint validation: Validates flag instead of the migrated measurement · case 05

The query violates its result contract: validates flag instead of the migrated measurement.

Schema migrations◈ 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 ↗