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

Check constraint validation: Requires a value to be negative and NULL simultaneously · case 01

The query violates its result contract: requires a value to be negative and null simultaneously.

Schema migrations● Open access↗
FA-2802

Check constraint validation: Requires a value to be negative and NULL simultaneously · case 02

The query violates its result contract: requires a value to be negative and null simultaneously.

Schema migrations◈ Members↗
FA-2803

Check constraint validation: Requires a value to be negative and NULL simultaneously · case 03

The query violates its result contract: requires a value to be negative and null simultaneously.

Schema migrations◈ Members↗
FA-2804

Check constraint validation: Requires a value to be negative and NULL simultaneously · case 04

The query violates its result contract: requires a value to be negative and null simultaneously.

Schema migrations◈ Members↗
FA-2805

Check constraint validation: Requires a value to be negative and NULL simultaneously · case 05

The query violates its result contract: requires a value to be negative and null simultaneously.

Schema migrations◈ Members↗
FA-2806

Migration join backfill: Backfills each row with the entire reference-table total · case 01

The query violates its result contract: backfills each row with the entire reference-table total.

Schema migrations● Open access↗
FA-2807

Migration join backfill: Backfills each row with the entire reference-table total · case 02

The query violates its result contract: backfills each row with the entire reference-table total.

Schema migrations◈ Members↗
FA-2808

Migration join backfill: Backfills each row with the entire reference-table total · case 03

The query violates its result contract: backfills each row with the entire reference-table total.

Schema migrations◈ Members↗
FA-2809

Migration join backfill: Backfills each row with the entire reference-table total · case 04

The query violates its result contract: backfills each row with the entire reference-table total.

Schema migrations◈ Members↗
FA-2810

Migration join backfill: Backfills each row with the entire reference-table total · case 05

The query violates its result contract: backfills each row with the entire reference-table total.

Schema migrations◈ Members↗
FA-2811

Migration join backfill: Deduplicates equal reference contributions during backfill · case 01

The query violates its result contract: deduplicates equal reference contributions during backfill.

Schema migrations● Open access↗
FA-2812

Migration join backfill: Deduplicates equal reference contributions during backfill · case 02

The query violates its result contract: deduplicates equal reference contributions during backfill.

Schema migrations◈ Members↗
FA-2813

Migration join backfill: Deduplicates equal reference contributions during backfill · case 03

The query violates its result contract: deduplicates equal reference contributions during backfill.

Schema migrations◈ Members↗
FA-2814

Migration join backfill: Deduplicates equal reference contributions during backfill · case 04

The query violates its result contract: deduplicates equal reference contributions during backfill.

Schema migrations◈ Members↗
FA-2815

Migration join backfill: Deduplicates equal reference contributions during backfill · case 05

The query violates its result contract: deduplicates equal reference contributions during backfill.

Schema migrations◈ Members↗
FA-2816

Migration join backfill: Invents zero for unmatched or unknown-only references · case 01

The query violates its result contract: invents zero for unmatched or unknown-only references.

Schema migrations● Open access↗
FA-2817

Migration join backfill: Invents zero for unmatched or unknown-only references · case 02

The query violates its result contract: invents zero for unmatched or unknown-only references.

Schema migrations◈ Members↗
FA-2818

Migration join backfill: Invents zero for unmatched or unknown-only references · case 03

The query violates its result contract: invents zero for unmatched or unknown-only references.

Schema migrations◈ Members↗
FA-2819

Migration join backfill: Invents zero for unmatched or unknown-only references · case 04

The query violates its result contract: invents zero for unmatched or unknown-only references.

Schema migrations◈ Members↗
FA-2820

Migration join backfill: Invents zero for unmatched or unknown-only references · case 05

The query violates its result contract: invents zero for unmatched or unknown-only references.

Schema migrations◈ Members↗
FA-2821

Migration join backfill: Loses source records with no reference match · case 01

The query violates its result contract: loses source records with no reference match.

Schema migrations● Open access↗
FA-2822

Migration join backfill: Loses source records with no reference match · case 02

The query violates its result contract: loses source records with no reference match.

Schema migrations◈ Members↗
FA-2823

Migration join backfill: Loses source records with no reference match · case 03

The query violates its result contract: loses source records with no reference match.

Schema migrations◈ Members↗
FA-2824

Migration join backfill: Loses source records with no reference match · case 04

The query violates its result contract: loses source records with no reference match.

Schema migrations◈ Members↗
FA-2825

Migration join backfill: Loses source records with no reference match · case 05

The query violates its result contract: loses source records with no reference match.

Schema migrations◈ Members↗
FA-2826

Migration join backfill: Matches NULL keys despite the ordinary equality contract · case 01

The query violates its result contract: matches null keys despite the ordinary equality contract.

Schema migrations● Open access↗
FA-2827

Migration join backfill: Matches NULL keys despite the ordinary equality contract · case 02

The query violates its result contract: matches null keys despite the ordinary equality contract.

Schema migrations◈ Members↗
FA-2828

Migration join backfill: Matches NULL keys despite the ordinary equality contract · case 03

The query violates its result contract: matches null keys despite the ordinary equality contract.

Schema migrations◈ Members↗
FA-2829

Migration join backfill: Matches NULL keys despite the ordinary equality contract · case 04

The query violates its result contract: matches null keys despite the ordinary equality contract.

Schema migrations◈ Members↗
FA-2830

Migration join backfill: Matches NULL keys despite the ordinary equality contract · case 05

The query violates its result contract: matches null keys despite the ordinary equality contract.

Schema migrations◈ Members↗
FA-2831

Canonical combining marks remain out of order · case 01

Canonical combining marks remain out of order.

Unicode● Open access↗
FA-2832

Canonical combining marks remain out of order · case 02

Canonical combining marks remain out of order.

Unicode◈ Members↗
FA-2833

Canonical combining marks remain out of order · case 03

Canonical combining marks remain out of order.

Unicode◈ Members↗
FA-2834

Canonical combining marks remain out of order · case 04

Canonical combining marks remain out of order.

Unicode◈ Members↗
FA-2835

Canonical combining marks remain out of order · case 05

Canonical combining marks remain out of order.

Unicode◈ Members↗
FA-2836

Compatibility ligatures survive a search key · case 01

Compatibility ligatures survive a search key.

Unicode● Open access↗
FA-2837

Compatibility ligatures survive a search key · case 02

Compatibility ligatures survive a search key.

Unicode◈ Members↗
FA-2838

Compatibility ligatures survive a search key · case 03

Compatibility ligatures survive a search key.

Unicode◈ Members↗
FA-2839

Compatibility ligatures survive a search key · case 04

Compatibility ligatures survive a search key.

Unicode◈ Members↗
FA-2840

Compatibility ligatures survive a search key · case 05

Compatibility ligatures survive a search key.

Unicode◈ Members↗
FA-2841

Hangul syllables bypass canonical decomposition · case 01

Hangul syllables bypass canonical decomposition.

Unicode● Open access↗
FA-2842

Hangul syllables bypass canonical decomposition · case 02

Hangul syllables bypass canonical decomposition.

Unicode◈ Members↗
FA-2843

Hangul syllables bypass canonical decomposition · case 03

Hangul syllables bypass canonical decomposition.

Unicode◈ Members↗
FA-2844

Hangul syllables bypass canonical decomposition · case 04

Hangul syllables bypass canonical decomposition.

Unicode◈ Members↗
FA-2845

Hangul syllables bypass canonical decomposition · case 05

Hangul syllables bypass canonical decomposition.

Unicode◈ Members↗
FA-2846

A compatibility fraction remains opaque · case 01

A compatibility fraction remains opaque.

Unicode● Open access↗
FA-2847

A compatibility fraction remains opaque · case 02

A compatibility fraction remains opaque.

Unicode◈ Members↗
FA-2848

A compatibility fraction remains opaque · case 03

A compatibility fraction remains opaque.

Unicode◈ Members↗
FA-2849

A compatibility fraction remains opaque · case 04

A compatibility fraction remains opaque.

Unicode◈ Members↗
FA-2850

A compatibility fraction remains opaque · case 05

A compatibility fraction remains opaque.

Unicode◈ Members↗
FA-2851

Lowercasing misses multi-character caseless matches · case 01

Lowercasing misses multi-character caseless matches.

Unicode● Open access↗
FA-2852

Lowercasing misses multi-character caseless matches · case 02

Lowercasing misses multi-character caseless matches.

Unicode◈ Members↗
FA-2853

Lowercasing misses multi-character caseless matches · case 03

Lowercasing misses multi-character caseless matches.

Unicode◈ Members↗
FA-2854

Lowercasing misses multi-character caseless matches · case 04

Lowercasing misses multi-character caseless matches.

Unicode◈ Members↗
FA-2855

Lowercasing misses multi-character caseless matches · case 05

Lowercasing misses multi-character caseless matches.

Unicode◈ Members↗
FA-2856

Case folding leaves a decomposed identity · case 01

Case folding leaves a decomposed identity.

Unicode● Open access↗
FA-2857

Case folding leaves a decomposed identity · case 02

Case folding leaves a decomposed identity.

Unicode◈ Members↗
FA-2858

Case folding leaves a decomposed identity · case 03

Case folding leaves a decomposed identity.

Unicode◈ Members↗
FA-2859

Case folding leaves a decomposed identity · case 04

Case folding leaves a decomposed identity.

Unicode◈ Members↗
FA-2860

Case folding leaves a decomposed identity · case 05

Case folding leaves a decomposed identity.

Unicode◈ Members↗
FA-2861

Accent removal drops non-Latin letters · case 01

Accent removal drops non-Latin letters.

Unicode● Open access↗
FA-2862

Accent removal drops non-Latin letters · case 02

Accent removal drops non-Latin letters.

Unicode◈ Members↗
FA-2863

Accent removal drops non-Latin letters · case 03

Accent removal drops non-Latin letters.

Unicode◈ Members↗
FA-2864

Accent removal drops non-Latin letters · case 04

Accent removal drops non-Latin letters.

Unicode◈ Members↗
FA-2865

Accent removal drops non-Latin letters · case 05

Accent removal drops non-Latin letters.

Unicode◈ Members↗
FA-2866

A superscript is accepted as a decimal digit · case 01

A superscript is accepted as a decimal digit.

Unicode● Open access↗
FA-2867

A superscript is accepted as a decimal digit · case 02

A superscript is accepted as a decimal digit.

Unicode◈ Members↗
FA-2868

A superscript is accepted as a decimal digit · case 03

A superscript is accepted as a decimal digit.

Unicode◈ Members↗
FA-2869

A superscript is accepted as a decimal digit · case 04

A superscript is accepted as a decimal digit.

Unicode◈ Members↗
FA-2870

A superscript is accepted as a decimal digit · case 05

A superscript is accepted as a decimal digit.

Unicode◈ Members↗
FA-2871

Non-decimal numeric characters are rejected · case 01

Non-decimal numeric characters are rejected.

Unicode● Open access↗
FA-2872

Non-decimal numeric characters are rejected · case 02

Non-decimal numeric characters are rejected.

Unicode◈ Members↗
FA-2873

Non-decimal numeric characters are rejected · case 03

Non-decimal numeric characters are rejected.

Unicode◈ Members↗
FA-2874

Non-decimal numeric characters are rejected · case 04

Non-decimal numeric characters are rejected.

Unicode◈ Members↗
FA-2875

Non-decimal numeric characters are rejected · case 05

Non-decimal numeric characters are rejected.

Unicode◈ Members↗
FA-2876

Unicode digits leak into an ASCII decimal token · case 01

Unicode digits leak into an ASCII decimal token.

Lexical grammars● Open access↗
FA-2877

Unicode digits leak into an ASCII decimal token · case 02

Unicode digits leak into an ASCII decimal token.

Lexical grammars◈ Members↗
FA-2878

Unicode digits leak into an ASCII decimal token · case 03

Unicode digits leak into an ASCII decimal token.

Lexical grammars◈ Members↗
FA-2879

Unicode digits leak into an ASCII decimal token · case 04

Unicode digits leak into an ASCII decimal token.

Lexical grammars◈ Members↗
FA-2880

Unicode digits leak into an ASCII decimal token · case 05

Unicode digits leak into an ASCII decimal token.

Lexical grammars◈ Members↗
FA-2881

An identifier rejects underscores and admits leading digits · case 01

An identifier rejects underscores and admits leading digits.

Lexical grammars● Open access↗
FA-2882

An identifier rejects underscores and admits leading digits · case 02

An identifier rejects underscores and admits leading digits.

Lexical grammars◈ Members↗
FA-2883

An identifier rejects underscores and admits leading digits · case 03

An identifier rejects underscores and admits leading digits.

Lexical grammars◈ Members↗
FA-2884

An identifier rejects underscores and admits leading digits · case 04

An identifier rejects underscores and admits leading digits.

Lexical grammars◈ Members↗
FA-2885

An identifier rejects underscores and admits leading digits · case 05

An identifier rejects underscores and admits leading digits.

Lexical grammars◈ Members↗
FA-2886

A line separator is treated as printable text · case 01

A line separator is treated as printable text.

Unicode● Open access↗
FA-2887

A line separator is treated as printable text · case 02

A line separator is treated as printable text.

Unicode◈ Members↗
FA-2888

A line separator is treated as printable text · case 03

A line separator is treated as printable text.

Unicode◈ Members↗
FA-2889

A line separator is treated as printable text · case 04

A line separator is treated as printable text.

Unicode◈ Members↗
FA-2890

A line separator is treated as printable text · case 05

A line separator is treated as printable text.

Unicode◈ Members↗
FA-2891

A nonbreaking space is not recognized as whitespace · case 01

A nonbreaking space is not recognized as whitespace.

Unicode● Open access↗
FA-2892

A nonbreaking space is not recognized as whitespace · case 02

A nonbreaking space is not recognized as whitespace.

Unicode◈ Members↗
FA-2893

A nonbreaking space is not recognized as whitespace · case 03

A nonbreaking space is not recognized as whitespace.

Unicode◈ Members↗
FA-2894

A nonbreaking space is not recognized as whitespace · case 04

A nonbreaking space is not recognized as whitespace.

Unicode◈ Members↗
FA-2895

A nonbreaking space is not recognized as whitespace · case 05

A nonbreaking space is not recognized as whitespace.

Unicode◈ Members↗
FA-2896

Uncased punctuation invalidates uppercase text · case 01

Uncased punctuation invalidates uppercase text.

Unicode● Open access↗
FA-2897

Uncased punctuation invalidates uppercase text · case 02

Uncased punctuation invalidates uppercase text.

Unicode◈ Members↗
FA-2898

Uncased punctuation invalidates uppercase text · case 03

Uncased punctuation invalidates uppercase text.

Unicode◈ Members↗
FA-2899

Uncased punctuation invalidates uppercase text · case 04

Uncased punctuation invalidates uppercase text.

Unicode◈ Members↗
FA-2900

Uncased punctuation invalidates uppercase text · case 05

Uncased punctuation invalidates uppercase text.

Unicode◈ 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 ↗