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

Unreachable predecessors erase definite assignments · case 01

Unreachable predecessors erase definite assignments.

Static analysis soundness● Open access↗
FA-11502

Unreachable predecessors erase definite assignments · case 02

Unreachable predecessors erase definite assignments.

Static analysis soundness◈ Members↗
FA-11503

Unreachable predecessors erase definite assignments · case 03

Unreachable predecessors erase definite assignments.

Static analysis soundness◈ Members↗
FA-11504

Unreachable predecessors erase definite assignments · case 04

Unreachable predecessors erase definite assignments.

Static analysis soundness◈ Members↗
FA-11505

Unreachable predecessors erase definite assignments · case 05

Unreachable predecessors erase definite assignments.

Static analysis soundness◈ Members↗
FA-11506

A context-specific sanitizer clears unrelated taint · case 01

A context-specific sanitizer clears unrelated taint.

Static analysis soundness● Open access↗
FA-11507

A context-specific sanitizer clears unrelated taint · case 02

A context-specific sanitizer clears unrelated taint.

Static analysis soundness◈ Members↗
FA-11508

A context-specific sanitizer clears unrelated taint · case 03

A context-specific sanitizer clears unrelated taint.

Static analysis soundness◈ Members↗
FA-11509

A context-specific sanitizer clears unrelated taint · case 04

A context-specific sanitizer clears unrelated taint.

Static analysis soundness◈ Members↗
FA-11510

A context-specific sanitizer clears unrelated taint · case 05

A context-specific sanitizer clears unrelated taint.

Static analysis soundness◈ Members↗
FA-11511

An ambiguous pointer store kills possible old values · case 01

An ambiguous pointer store kills possible old values.

Static analysis soundness● Open access↗
FA-11512

An ambiguous pointer store kills possible old values · case 02

An ambiguous pointer store kills possible old values.

Static analysis soundness◈ Members↗
FA-11513

An ambiguous pointer store kills possible old values · case 03

An ambiguous pointer store kills possible old values.

Static analysis soundness◈ Members↗
FA-11514

An ambiguous pointer store kills possible old values · case 04

An ambiguous pointer store kills possible old values.

Static analysis soundness◈ Members↗
FA-11515

An ambiguous pointer store kills possible old values · case 05

An ambiguous pointer store kills possible old values.

Static analysis soundness◈ Members↗
FA-11516

A definition kills its own incoming operand use · case 01

A definition kills its own incoming operand use.

Static analysis soundness● Open access↗
FA-11517

A definition kills its own incoming operand use · case 02

A definition kills its own incoming operand use.

Static analysis soundness◈ Members↗
FA-11518

A definition kills its own incoming operand use · case 03

A definition kills its own incoming operand use.

Static analysis soundness◈ Members↗
FA-11519

A definition kills its own incoming operand use · case 04

A definition kills its own incoming operand use.

Static analysis soundness◈ Members↗
FA-11520

A definition kills its own incoming operand use · case 05

A definition kills its own incoming operand use.

Static analysis soundness◈ Members↗
FA-11521

A call preserves a constant for a modified global · case 01

A call preserves a constant for a modified global.

Static analysis soundness● Open access↗
FA-11522

A call preserves a constant for a modified global · case 02

A call preserves a constant for a modified global.

Static analysis soundness◈ Members↗
FA-11523

A call preserves a constant for a modified global · case 03

A call preserves a constant for a modified global.

Static analysis soundness◈ Members↗
FA-11524

A call preserves a constant for a modified global · case 04

A call preserves a constant for a modified global.

Static analysis soundness◈ Members↗
FA-11525

A call preserves a constant for a modified global · case 05

A call preserves a constant for a modified global.

Static analysis soundness◈ Members↗
FA-11526

Unreachable input becomes an unknown constant at a join · case 01

Unreachable input becomes an unknown constant at a join.

Static analysis soundness● Open access↗
FA-11527

Unreachable input becomes an unknown constant at a join · case 02

Unreachable input becomes an unknown constant at a join.

Static analysis soundness◈ Members↗
FA-11528

Unreachable input becomes an unknown constant at a join · case 03

Unreachable input becomes an unknown constant at a join.

Static analysis soundness◈ Members↗
FA-11529

Unreachable input becomes an unknown constant at a join · case 04

Unreachable input becomes an unknown constant at a join.

Static analysis soundness◈ Members↗
FA-11530

Unreachable input becomes an unknown constant at a join · case 05

Unreachable input becomes an unknown constant at a join.

Static analysis soundness◈ Members↗
FA-11531

A single dataflow sweep misses facts across backward edges · case 01

A single dataflow sweep misses facts across backward edges.

Static analysis soundness● Open access↗
FA-11532

A single dataflow sweep misses facts across backward edges · case 02

A single dataflow sweep misses facts across backward edges.

Static analysis soundness◈ Members↗
FA-11533

A single dataflow sweep misses facts across backward edges · case 03

A single dataflow sweep misses facts across backward edges.

Static analysis soundness◈ Members↗
FA-11534

A single dataflow sweep misses facts across backward edges · case 04

A single dataflow sweep misses facts across backward edges.

Static analysis soundness◈ Members↗
FA-11535

A single dataflow sweep misses facts across backward edges · case 05

A single dataflow sweep misses facts across backward edges.

Static analysis soundness◈ Members↗
FA-11536

An inner lint suppression leaks into a sibling scope · case 01

An inner lint suppression leaks into a sibling scope.

Static analysis soundness● Open access↗
FA-11537

An inner lint suppression leaks into a sibling scope · case 02

An inner lint suppression leaks into a sibling scope.

Static analysis soundness◈ Members↗
FA-11538

An inner lint suppression leaks into a sibling scope · case 03

An inner lint suppression leaks into a sibling scope.

Static analysis soundness◈ Members↗
FA-11539

An inner lint suppression leaks into a sibling scope · case 04

An inner lint suppression leaks into a sibling scope.

Static analysis soundness◈ Members↗
FA-11540

An inner lint suppression leaks into a sibling scope · case 05

An inner lint suppression leaks into a sibling scope.

Static analysis soundness◈ Members↗
FA-11541

Unlinking the last name invalidates an open file · case 01

Unlinking the last name invalidates an open file.

Filesystem semantics● Open access↗
FA-11542

Unlinking the last name invalidates an open file · case 02

Unlinking the last name invalidates an open file.

Filesystem semantics◈ Members↗
FA-11543

Unlinking the last name invalidates an open file · case 03

Unlinking the last name invalidates an open file.

Filesystem semantics◈ Members↗
FA-11544

Unlinking the last name invalidates an open file · case 04

Unlinking the last name invalidates an open file.

Filesystem semantics◈ Members↗
FA-11545

Unlinking the last name invalidates an open file · case 05

Unlinking the last name invalidates an open file.

Filesystem semantics◈ Members↗
FA-11546

Duplicated descriptors advance independent read positions · case 01

Duplicated descriptors advance independent read positions.

Filesystem semantics● Open access↗
FA-11547

Duplicated descriptors advance independent read positions · case 02

Duplicated descriptors advance independent read positions.

Filesystem semantics◈ Members↗
FA-11548

Duplicated descriptors advance independent read positions · case 03

Duplicated descriptors advance independent read positions.

Filesystem semantics◈ Members↗
FA-11549

Duplicated descriptors advance independent read positions · case 04

Duplicated descriptors advance independent read positions.

Filesystem semantics◈ Members↗
FA-11550

Duplicated descriptors advance independent read positions · case 05

Duplicated descriptors advance independent read positions.

Filesystem semantics◈ Members↗
FA-11551

Replacing a pathname retargets an already open descriptor · case 01

Replacing a pathname retargets an already open descriptor.

Filesystem semantics● Open access↗
FA-11552

Replacing a pathname retargets an already open descriptor · case 02

Replacing a pathname retargets an already open descriptor.

Filesystem semantics◈ Members↗
FA-11553

Replacing a pathname retargets an already open descriptor · case 03

Replacing a pathname retargets an already open descriptor.

Filesystem semantics◈ Members↗
FA-11554

Replacing a pathname retargets an already open descriptor · case 04

Replacing a pathname retargets an already open descriptor.

Filesystem semantics◈ Members↗
FA-11555

Replacing a pathname retargets an already open descriptor · case 05

Replacing a pathname retargets an already open descriptor.

Filesystem semantics◈ Members↗
FA-11556

Creation mode subtraction borrows across permission bits · case 01

Creation mode subtraction borrows across permission bits.

Filesystem semantics● Open access↗
FA-11557

Creation mode subtraction borrows across permission bits · case 02

Creation mode subtraction borrows across permission bits.

Filesystem semantics◈ Members↗
FA-11558

Creation mode subtraction borrows across permission bits · case 03

Creation mode subtraction borrows across permission bits.

Filesystem semantics◈ Members↗
FA-11559

Creation mode subtraction borrows across permission bits · case 04

Creation mode subtraction borrows across permission bits.

Filesystem semantics◈ Members↗
FA-11560

Creation mode subtraction borrows across permission bits · case 05

Creation mode subtraction borrows across permission bits.

Filesystem semantics◈ Members↗
FA-11561

Permission evaluation falls through from owner to other · case 01

Permission evaluation falls through from owner to other.

Filesystem semantics● Open access↗
FA-11562

Permission evaluation falls through from owner to other · case 02

Permission evaluation falls through from owner to other.

Filesystem semantics◈ Members↗
FA-11563

Permission evaluation falls through from owner to other · case 03

Permission evaluation falls through from owner to other.

Filesystem semantics◈ Members↗
FA-11564

Permission evaluation falls through from owner to other · case 04

Permission evaluation falls through from owner to other.

Filesystem semantics◈ Members↗
FA-11565

Permission evaluation falls through from owner to other · case 05

Permission evaluation falls through from owner to other.

Filesystem semantics◈ Members↗
FA-11566

Readable directories are mistaken for searchable directories · case 01

Readable directories are mistaken for searchable directories.

Filesystem semantics● Open access↗
FA-11567

Readable directories are mistaken for searchable directories · case 02

Readable directories are mistaken for searchable directories.

Filesystem semantics◈ Members↗
FA-11568

Readable directories are mistaken for searchable directories · case 03

Readable directories are mistaken for searchable directories.

Filesystem semantics◈ Members↗
FA-11569

Readable directories are mistaken for searchable directories · case 04

Readable directories are mistaken for searchable directories.

Filesystem semantics◈ Members↗
FA-11570

Readable directories are mistaken for searchable directories · case 05

Readable directories are mistaken for searchable directories.

Filesystem semantics◈ Members↗
FA-11571

Sparse holes disappear when file bytes are reconstructed · case 01

Sparse holes disappear when file bytes are reconstructed.

Filesystem semantics● Open access↗
FA-11572

Sparse holes disappear when file bytes are reconstructed · case 02

Sparse holes disappear when file bytes are reconstructed.

Filesystem semantics◈ Members↗
FA-11573

Sparse holes disappear when file bytes are reconstructed · case 03

Sparse holes disappear when file bytes are reconstructed.

Filesystem semantics◈ Members↗
FA-11574

Sparse holes disappear when file bytes are reconstructed · case 04

Sparse holes disappear when file bytes are reconstructed.

Filesystem semantics◈ Members↗
FA-11575

Sparse holes disappear when file bytes are reconstructed · case 05

Sparse holes disappear when file bytes are reconstructed.

Filesystem semantics◈ Members↗
FA-11576

Seeking an append descriptor causes an overwrite · case 01

Seeking an append descriptor causes an overwrite.

Filesystem semantics● Open access↗
FA-11577

Seeking an append descriptor causes an overwrite · case 02

Seeking an append descriptor causes an overwrite.

Filesystem semantics◈ Members↗
FA-11578

Seeking an append descriptor causes an overwrite · case 03

Seeking an append descriptor causes an overwrite.

Filesystem semantics◈ Members↗
FA-11579

Seeking an append descriptor causes an overwrite · case 04

Seeking an append descriptor causes an overwrite.

Filesystem semantics◈ Members↗
FA-11580

Seeking an append descriptor causes an overwrite · case 05

Seeking an append descriptor causes an overwrite.

Filesystem semantics◈ Members↗
FA-11581

Truncation rewinds an open file position · case 01

Truncation rewinds an open file position.

Filesystem semantics● Open access↗
FA-11582

Truncation rewinds an open file position · case 02

Truncation rewinds an open file position.

Filesystem semantics◈ Members↗
FA-11583

Truncation rewinds an open file position · case 03

Truncation rewinds an open file position.

Filesystem semantics◈ Members↗
FA-11584

Truncation rewinds an open file position · case 04

Truncation rewinds an open file position.

Filesystem semantics◈ Members↗
FA-11585

Truncation rewinds an open file position · case 05

Truncation rewinds an open file position.

Filesystem semantics◈ Members↗
FA-11586

A dangling symbolic link disappears from metadata results · case 01

A dangling symbolic link disappears from metadata results.

Filesystem semantics● Open access↗
FA-11587

A dangling symbolic link disappears from metadata results · case 02

A dangling symbolic link disappears from metadata results.

Filesystem semantics◈ Members↗
FA-11588

A dangling symbolic link disappears from metadata results · case 03

A dangling symbolic link disappears from metadata results.

Filesystem semantics◈ Members↗
FA-11589

A dangling symbolic link disappears from metadata results · case 04

A dangling symbolic link disappears from metadata results.

Filesystem semantics◈ Members↗
FA-11590

A dangling symbolic link disappears from metadata results · case 05

A dangling symbolic link disappears from metadata results.

Filesystem semantics◈ Members↗
FA-11591

LZ match copying freezes the source before expansion · case 01

LZ match copying freezes the source before expansion.

Compression format semantics● Open access↗
FA-11592

LZ match copying freezes the source before expansion · case 02

LZ match copying freezes the source before expansion.

Compression format semantics◈ Members↗
FA-11593

LZ match copying freezes the source before expansion · case 03

LZ match copying freezes the source before expansion.

Compression format semantics◈ Members↗
FA-11594

LZ match copying freezes the source before expansion · case 04

LZ match copying freezes the source before expansion.

Compression format semantics◈ Members↗
FA-11595

LZ match copying freezes the source before expansion · case 05

LZ match copying freezes the source before expansion.

Compression format semantics◈ Members↗
FA-11596

LZ history keeps references beyond its window · case 01

LZ history keeps references beyond its window.

Compression format semantics● Open access↗
FA-11597

LZ history keeps references beyond its window · case 02

LZ history keeps references beyond its window.

Compression format semantics◈ Members↗
FA-11598

LZ history keeps references beyond its window · case 03

LZ history keeps references beyond its window.

Compression format semantics◈ Members↗
FA-11599

LZ history keeps references beyond its window · case 04

LZ history keeps references beyond its window.

Compression format semantics◈ Members↗
FA-11600

LZ history keeps references beyond its window · case 05

LZ history keeps references beyond its window.

Compression format semantics◈ 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 ↗