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

A titlecase digraph is reduced to an uppercase digraph · case 01

A titlecase digraph is reduced to an uppercase digraph.

Unicode● Open access↗
FA-2902

A titlecase digraph is reduced to an uppercase digraph · case 02

A titlecase digraph is reduced to an uppercase digraph.

Unicode◈ Members↗
FA-2903

A titlecase digraph is reduced to an uppercase digraph · case 03

A titlecase digraph is reduced to an uppercase digraph.

Unicode◈ Members↗
FA-2904

A titlecase digraph is reduced to an uppercase digraph · case 04

A titlecase digraph is reduced to an uppercase digraph.

Unicode◈ Members↗
FA-2905

A titlecase digraph is reduced to an uppercase digraph · case 05

A titlecase digraph is reduced to an uppercase digraph.

Unicode◈ Members↗
FA-2906

Capitalization leaves an uppercase tail · case 01

Capitalization leaves an uppercase tail.

Text processing● Open access↗
FA-2907

Capitalization leaves an uppercase tail · case 02

Capitalization leaves an uppercase tail.

Text processing◈ Members↗
FA-2908

Capitalization leaves an uppercase tail · case 03

Capitalization leaves an uppercase tail.

Text processing◈ Members↗
FA-2909

Capitalization leaves an uppercase tail · case 04

Capitalization leaves an uppercase tail.

Text processing◈ Members↗
FA-2910

Capitalization leaves an uppercase tail · case 05

Capitalization leaves an uppercase tail.

Text processing◈ Members↗
FA-2911

An uppercase expansion is truncated during case swap · case 01

An uppercase expansion is truncated during case swap.

Unicode● Open access↗
FA-2912

An uppercase expansion is truncated during case swap · case 02

An uppercase expansion is truncated during case swap.

Unicode◈ Members↗
FA-2913

An uppercase expansion is truncated during case swap · case 03

An uppercase expansion is truncated during case swap.

Unicode◈ Members↗
FA-2914

An uppercase expansion is truncated during case swap · case 04

An uppercase expansion is truncated during case swap.

Unicode◈ Members↗
FA-2915

An uppercase expansion is truncated during case swap · case 05

An uppercase expansion is truncated during case swap.

Unicode◈ Members↗
FA-2916

Alphabetic filtering admits combining letter numbers · case 01

Alphabetic filtering admits combining letter numbers.

Unicode● Open access↗
FA-2917

Alphabetic filtering admits combining letter numbers · case 02

Alphabetic filtering admits combining letter numbers.

Unicode◈ Members↗
FA-2918

Alphabetic filtering admits combining letter numbers · case 03

Alphabetic filtering admits combining letter numbers.

Unicode◈ Members↗
FA-2919

Alphabetic filtering admits combining letter numbers · case 04

Alphabetic filtering admits combining letter numbers.

Unicode◈ Members↗
FA-2920

Alphabetic filtering admits combining letter numbers · case 05

Alphabetic filtering admits combining letter numbers.

Unicode◈ Members↗
FA-2921

A zero-class mark survives mark stripping · case 01

A zero-class mark survives mark stripping.

Unicode● Open access↗
FA-2922

A zero-class mark survives mark stripping · case 02

A zero-class mark survives mark stripping.

Unicode◈ Members↗
FA-2923

A zero-class mark survives mark stripping · case 03

A zero-class mark survives mark stripping.

Unicode◈ Members↗
FA-2924

A zero-class mark survives mark stripping · case 04

A zero-class mark survives mark stripping.

Unicode◈ Members↗
FA-2925

A zero-class mark survives mark stripping · case 05

A zero-class mark survives mark stripping.

Unicode◈ Members↗
FA-2926

Invisible format controls survive control filtering · case 01

Invisible format controls survive control filtering.

Unicode● Open access↗
FA-2927

Invisible format controls survive control filtering · case 02

Invisible format controls survive control filtering.

Unicode◈ Members↗
FA-2928

Invisible format controls survive control filtering · case 03

Invisible format controls survive control filtering.

Unicode◈ Members↗
FA-2929

Invisible format controls survive control filtering · case 04

Invisible format controls survive control filtering.

Unicode◈ Members↗
FA-2930

Invisible format controls survive control filtering · case 05

Invisible format controls survive control filtering.

Unicode◈ Members↗
FA-2931

Fullwidth letters occupy one display column · case 01

Fullwidth letters occupy one display column.

Unicode● Open access↗
FA-2932

Fullwidth letters occupy one display column · case 02

Fullwidth letters occupy one display column.

Unicode◈ Members↗
FA-2933

Fullwidth letters occupy one display column · case 03

Fullwidth letters occupy one display column.

Unicode◈ Members↗
FA-2934

Fullwidth letters occupy one display column · case 04

Fullwidth letters occupy one display column.

Unicode◈ Members↗
FA-2935

Fullwidth letters occupy one display column · case 05

Fullwidth letters occupy one display column.

Unicode◈ Members↗
FA-2936

Character count underestimates an encoded field · case 01

Character count underestimates an encoded field.

Encodings● Open access↗
FA-2937

Character count underestimates an encoded field · case 02

Character count underestimates an encoded field.

Encodings◈ Members↗
FA-2938

Character count underestimates an encoded field · case 03

Character count underestimates an encoded field.

Encodings◈ Members↗
FA-2939

Character count underestimates an encoded field · case 04

Character count underestimates an encoded field.

Encodings◈ Members↗
FA-2940

Character count underestimates an encoded field · case 05

Character count underestimates an encoded field.

Encodings◈ Members↗
FA-2941

An astral character is counted as one UTF-16 unit · case 01

An astral character is counted as one UTF-16 unit.

Encodings● Open access↗
FA-2942

An astral character is counted as one UTF-16 unit · case 02

An astral character is counted as one UTF-16 unit.

Encodings◈ Members↗
FA-2943

An astral character is counted as one UTF-16 unit · case 03

An astral character is counted as one UTF-16 unit.

Encodings◈ Members↗
FA-2944

An astral character is counted as one UTF-16 unit · case 04

An astral character is counted as one UTF-16 unit.

Encodings◈ Members↗
FA-2945

An astral character is counted as one UTF-16 unit · case 05

An astral character is counted as one UTF-16 unit.

Encodings◈ Members↗
FA-2946

UTF-16 BOM is interpreted as ordinary text · case 01

UTF-16 BOM is interpreted as ordinary text.

Encodings● Open access↗
FA-2947

UTF-16 BOM is interpreted as ordinary text · case 02

UTF-16 BOM is interpreted as ordinary text.

Encodings◈ Members↗
FA-2948

UTF-16 BOM is interpreted as ordinary text · case 03

UTF-16 BOM is interpreted as ordinary text.

Encodings◈ Members↗
FA-2949

UTF-16 BOM is interpreted as ordinary text · case 04

UTF-16 BOM is interpreted as ordinary text.

Encodings◈ Members↗
FA-2950

UTF-16 BOM is interpreted as ordinary text · case 05

UTF-16 BOM is interpreted as ordinary text.

Encodings◈ Members↗
FA-2951

Latin-1 bytes are decoded through a typographic code page · case 01

Latin-1 bytes are decoded through a typographic code page.

Encodings● Open access↗
FA-2952

Latin-1 bytes are decoded through a typographic code page · case 02

Latin-1 bytes are decoded through a typographic code page.

Encodings◈ Members↗
FA-2953

Latin-1 bytes are decoded through a typographic code page · case 03

Latin-1 bytes are decoded through a typographic code page.

Encodings◈ Members↗
FA-2954

Latin-1 bytes are decoded through a typographic code page · case 04

Latin-1 bytes are decoded through a typographic code page.

Encodings◈ Members↗
FA-2955

Latin-1 bytes are decoded through a typographic code page · case 05

Latin-1 bytes are decoded through a typographic code page.

Encodings◈ Members↗
FA-2956

Windows punctuation decodes as controls · case 01

Windows punctuation decodes as controls.

Encodings● Open access↗
FA-2957

Windows punctuation decodes as controls · case 02

Windows punctuation decodes as controls.

Encodings◈ Members↗
FA-2958

Windows punctuation decodes as controls · case 03

Windows punctuation decodes as controls.

Encodings◈ Members↗
FA-2959

Windows punctuation decodes as controls · case 04

Windows punctuation decodes as controls.

Encodings◈ Members↗
FA-2960

Windows punctuation decodes as controls · case 05

Windows punctuation decodes as controls.

Encodings◈ Members↗
FA-2961

Invalid UTF-8 bytes silently disappear · case 01

Invalid UTF-8 bytes silently disappear.

Encodings● Open access↗
FA-2962

Invalid UTF-8 bytes silently disappear · case 02

Invalid UTF-8 bytes silently disappear.

Encodings◈ Members↗
FA-2963

Invalid UTF-8 bytes silently disappear · case 03

Invalid UTF-8 bytes silently disappear.

Encodings◈ Members↗
FA-2964

Invalid UTF-8 bytes silently disappear · case 04

Invalid UTF-8 bytes silently disappear.

Encodings◈ Members↗
FA-2965

Invalid UTF-8 bytes silently disappear · case 05

Invalid UTF-8 bytes silently disappear.

Encodings◈ Members↗
FA-2966

Undecodable bytes cannot be re-encoded losslessly · case 01

Undecodable bytes cannot be re-encoded losslessly.

Encodings● Open access↗
FA-2967

Undecodable bytes cannot be re-encoded losslessly · case 02

Undecodable bytes cannot be re-encoded losslessly.

Encodings◈ Members↗
FA-2968

Undecodable bytes cannot be re-encoded losslessly · case 03

Undecodable bytes cannot be re-encoded losslessly.

Encodings◈ Members↗
FA-2969

Undecodable bytes cannot be re-encoded losslessly · case 04

Undecodable bytes cannot be re-encoded losslessly.

Encodings◈ Members↗
FA-2970

Undecodable bytes cannot be re-encoded losslessly · case 05

Undecodable bytes cannot be re-encoded losslessly.

Encodings◈ Members↗
FA-2971

Odd hex nybbles become a complete byte · case 01

Odd hex nybbles become a complete byte.

Binary formats● Open access↗
FA-2972

Odd hex nybbles become a complete byte · case 02

Odd hex nybbles become a complete byte.

Binary formats◈ Members↗
FA-2973

Odd hex nybbles become a complete byte · case 03

Odd hex nybbles become a complete byte.

Binary formats◈ Members↗
FA-2974

Odd hex nybbles become a complete byte · case 04

Odd hex nybbles become a complete byte.

Binary formats◈ Members↗
FA-2975

Odd hex nybbles become a complete byte · case 05

Odd hex nybbles become a complete byte.

Binary formats◈ Members↗
FA-2976

Removing a prefix eats a set of leading characters · case 01

Removing a prefix eats a set of leading characters.

Text processing● Open access↗
FA-2977

Removing a prefix eats a set of leading characters · case 02

Removing a prefix eats a set of leading characters.

Text processing◈ Members↗
FA-2978

Removing a prefix eats a set of leading characters · case 03

Removing a prefix eats a set of leading characters.

Text processing◈ Members↗
FA-2979

Removing a prefix eats a set of leading characters · case 04

Removing a prefix eats a set of leading characters.

Text processing◈ Members↗
FA-2980

Removing a prefix eats a set of leading characters · case 05

Removing a prefix eats a set of leading characters.

Text processing◈ Members↗
FA-2981

Removing a suffix erases unrelated trailing characters · case 01

Removing a suffix erases unrelated trailing characters.

Text processing● Open access↗
FA-2982

Removing a suffix erases unrelated trailing characters · case 02

Removing a suffix erases unrelated trailing characters.

Text processing◈ Members↗
FA-2983

Removing a suffix erases unrelated trailing characters · case 03

Removing a suffix erases unrelated trailing characters.

Text processing◈ Members↗
FA-2984

Removing a suffix erases unrelated trailing characters · case 04

Removing a suffix erases unrelated trailing characters.

Text processing◈ Members↗
FA-2985

Removing a suffix erases unrelated trailing characters · case 05

Removing a suffix erases unrelated trailing characters.

Text processing◈ Members↗
FA-2986

An assignment value loses embedded equals signs · case 01

An assignment value loses embedded equals signs.

Text processing● Open access↗
FA-2987

An assignment value loses embedded equals signs · case 02

An assignment value loses embedded equals signs.

Text processing◈ Members↗
FA-2988

An assignment value loses embedded equals signs · case 03

An assignment value loses embedded equals signs.

Text processing◈ Members↗
FA-2989

An assignment value loses embedded equals signs · case 04

An assignment value loses embedded equals signs.

Text processing◈ Members↗
FA-2990

An assignment value loses embedded equals signs · case 05

An assignment value loses embedded equals signs.

Text processing◈ Members↗
FA-2991

A qualified label splits at its first colon · case 01

A qualified label splits at its first colon.

Text processing● Open access↗
FA-2992

A qualified label splits at its first colon · case 02

A qualified label splits at its first colon.

Text processing◈ Members↗
FA-2993

A qualified label splits at its first colon · case 03

A qualified label splits at its first colon.

Text processing◈ Members↗
FA-2994

A qualified label splits at its first colon · case 04

A qualified label splits at its first colon.

Text processing◈ Members↗
FA-2995

A qualified label splits at its first colon · case 05

A qualified label splits at its first colon.

Text processing◈ Members↗
FA-2996

Whitespace tokenization creates empty tokens · case 01

Whitespace tokenization creates empty tokens.

Text processing● Open access↗
FA-2997

Whitespace tokenization creates empty tokens · case 02

Whitespace tokenization creates empty tokens.

Text processing◈ Members↗
FA-2998

Whitespace tokenization creates empty tokens · case 03

Whitespace tokenization creates empty tokens.

Text processing◈ Members↗
FA-2999

Whitespace tokenization creates empty tokens · case 04

Whitespace tokenization creates empty tokens.

Text processing◈ Members↗
FA-3000

Whitespace tokenization creates empty tokens · case 05

Whitespace tokenization creates empty tokens.

Text processing◈ 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 ↗