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

An ISBN-13-shaped token admits an unrelated prefix · case 01

An ISBN-13-shaped token admits an unrelated prefix.

Lexical grammars● Open access↗
FA-3602

An ISBN-13-shaped token admits an unrelated prefix · case 02

An ISBN-13-shaped token admits an unrelated prefix.

Lexical grammars◈ Members↗
FA-3603

An ISBN-13-shaped token admits an unrelated prefix · case 03

An ISBN-13-shaped token admits an unrelated prefix.

Lexical grammars◈ Members↗
FA-3604

An ISBN-13-shaped token admits an unrelated prefix · case 04

An ISBN-13-shaped token admits an unrelated prefix.

Lexical grammars◈ Members↗
FA-3605

An ISBN-13-shaped token admits an unrelated prefix · case 05

An ISBN-13-shaped token admits an unrelated prefix.

Lexical grammars◈ Members↗
FA-3606

A network-order word uses host-style little endian · case 01

A network-order word uses host-style little endian.

Binary formats● Open access↗
FA-3607

A network-order word uses host-style little endian · case 02

A network-order word uses host-style little endian.

Binary formats◈ Members↗
FA-3608

A network-order word uses host-style little endian · case 03

A network-order word uses host-style little endian.

Binary formats◈ Members↗
FA-3609

A network-order word uses host-style little endian · case 04

A network-order word uses host-style little endian.

Binary formats◈ Members↗
FA-3610

A network-order word uses host-style little endian · case 05

A network-order word uses host-style little endian.

Binary formats◈ Members↗
FA-3611

A signed octet is interpreted as an unsigned magnitude · case 01

A signed octet is interpreted as an unsigned magnitude.

Binary formats● Open access↗
FA-3612

A signed octet is interpreted as an unsigned magnitude · case 02

A signed octet is interpreted as an unsigned magnitude.

Binary formats◈ Members↗
FA-3613

A signed octet is interpreted as an unsigned magnitude · case 03

A signed octet is interpreted as an unsigned magnitude.

Binary formats◈ Members↗
FA-3614

A signed octet is interpreted as an unsigned magnitude · case 04

A signed octet is interpreted as an unsigned magnitude.

Binary formats◈ Members↗
FA-3615

A signed octet is interpreted as an unsigned magnitude · case 05

A signed octet is interpreted as an unsigned magnitude.

Binary formats◈ Members↗
FA-3616

A sign-magnitude octet is decoded as two-complement · case 01

A sign-magnitude octet is decoded as two-complement.

Binary formats● Open access↗
FA-3617

A sign-magnitude octet is decoded as two-complement · case 02

A sign-magnitude octet is decoded as two-complement.

Binary formats◈ Members↗
FA-3618

A sign-magnitude octet is decoded as two-complement · case 03

A sign-magnitude octet is decoded as two-complement.

Binary formats◈ Members↗
FA-3619

A sign-magnitude octet is decoded as two-complement · case 04

A sign-magnitude octet is decoded as two-complement.

Binary formats◈ Members↗
FA-3620

A sign-magnitude octet is decoded as two-complement · case 05

A sign-magnitude octet is decoded as two-complement.

Binary formats◈ Members↗
FA-3621

Zigzag decoding loses odd-value signs · case 01

Zigzag decoding loses odd-value signs.

Binary formats● Open access↗
FA-3622

Zigzag decoding loses odd-value signs · case 02

Zigzag decoding loses odd-value signs.

Binary formats◈ Members↗
FA-3623

Zigzag decoding loses odd-value signs · case 03

Zigzag decoding loses odd-value signs.

Binary formats◈ Members↗
FA-3624

Zigzag decoding loses odd-value signs · case 04

Zigzag decoding loses odd-value signs.

Binary formats◈ Members↗
FA-3625

Zigzag decoding loses odd-value signs · case 05

Zigzag decoding loses odd-value signs.

Binary formats◈ Members↗
FA-3626

Packed decimal decodes as a binary integer · case 01

Packed decimal decodes as a binary integer.

Binary formats● Open access↗
FA-3627

Packed decimal decodes as a binary integer · case 02

Packed decimal decodes as a binary integer.

Binary formats◈ Members↗
FA-3628

Packed decimal decodes as a binary integer · case 03

Packed decimal decodes as a binary integer.

Binary formats◈ Members↗
FA-3629

Packed decimal decodes as a binary integer · case 04

Packed decimal decodes as a binary integer.

Binary formats◈ Members↗
FA-3630

Packed decimal decodes as a binary integer · case 05

Packed decimal decodes as a binary integer.

Binary formats◈ Members↗
FA-3631

A packed-decimal sign nybble becomes a digit · case 01

A packed-decimal sign nybble becomes a digit.

Binary formats● Open access↗
FA-3632

A packed-decimal sign nybble becomes a digit · case 02

A packed-decimal sign nybble becomes a digit.

Binary formats◈ Members↗
FA-3633

A packed-decimal sign nybble becomes a digit · case 03

A packed-decimal sign nybble becomes a digit.

Binary formats◈ Members↗
FA-3634

A packed-decimal sign nybble becomes a digit · case 04

A packed-decimal sign nybble becomes a digit.

Binary formats◈ Members↗
FA-3635

A packed-decimal sign nybble becomes a digit · case 05

A packed-decimal sign nybble becomes a digit.

Binary formats◈ Members↗
FA-3636

Testing a flag requires every bit to equal the mask · case 01

Testing a flag requires every bit to equal the mask.

Binary formats● Open access↗
FA-3637

Testing a flag requires every bit to equal the mask · case 02

Testing a flag requires every bit to equal the mask.

Binary formats◈ Members↗
FA-3638

Testing a flag requires every bit to equal the mask · case 03

Testing a flag requires every bit to equal the mask.

Binary formats◈ Members↗
FA-3639

Testing a flag requires every bit to equal the mask · case 04

Testing a flag requires every bit to equal the mask.

Binary formats◈ Members↗
FA-3640

Testing a flag requires every bit to equal the mask · case 05

Testing a flag requires every bit to equal the mask.

Binary formats◈ Members↗
FA-3641

A packed field includes adjacent flag bits · case 01

A packed field includes adjacent flag bits.

Binary formats● Open access↗
FA-3642

A packed field includes adjacent flag bits · case 02

A packed field includes adjacent flag bits.

Binary formats◈ Members↗
FA-3643

A packed field includes adjacent flag bits · case 03

A packed field includes adjacent flag bits.

Binary formats◈ Members↗
FA-3644

A packed field includes adjacent flag bits · case 04

A packed field includes adjacent flag bits.

Binary formats◈ Members↗
FA-3645

A packed field includes adjacent flag bits · case 05

A packed field includes adjacent flag bits.

Binary formats◈ Members↗
FA-3646

Unknown reserved flag bits are silently retained · case 01

Unknown reserved flag bits are silently retained.

Binary formats● Open access↗
FA-3647

Unknown reserved flag bits are silently retained · case 02

Unknown reserved flag bits are silently retained.

Binary formats◈ Members↗
FA-3648

Unknown reserved flag bits are silently retained · case 03

Unknown reserved flag bits are silently retained.

Binary formats◈ Members↗
FA-3649

Unknown reserved flag bits are silently retained · case 04

Unknown reserved flag bits are silently retained.

Binary formats◈ Members↗
FA-3650

Unknown reserved flag bits are silently retained · case 05

Unknown reserved flag bits are silently retained.

Binary formats◈ Members↗
FA-3651

Bit expansion emits least-significant bits first · case 01

Bit expansion emits least-significant bits first.

Binary formats● Open access↗
FA-3652

Bit expansion emits least-significant bits first · case 02

Bit expansion emits least-significant bits first.

Binary formats◈ Members↗
FA-3653

Bit expansion emits least-significant bits first · case 03

Bit expansion emits least-significant bits first.

Binary formats◈ Members↗
FA-3654

Bit expansion emits least-significant bits first · case 04

Bit expansion emits least-significant bits first.

Binary formats◈ Members↗
FA-3655

Bit expansion emits least-significant bits first · case 05

Bit expansion emits least-significant bits first.

Binary formats◈ Members↗
FA-3656

Varint continuation bits contribute to the value · case 01

Varint continuation bits contribute to the value.

Binary formats● Open access↗
FA-3657

Varint continuation bits contribute to the value · case 02

Varint continuation bits contribute to the value.

Binary formats◈ Members↗
FA-3658

Varint continuation bits contribute to the value · case 03

Varint continuation bits contribute to the value.

Binary formats◈ Members↗
FA-3659

Varint continuation bits contribute to the value · case 04

Varint continuation bits contribute to the value.

Binary formats◈ Members↗
FA-3660

Varint continuation bits contribute to the value · case 05

Varint continuation bits contribute to the value.

Binary formats◈ Members↗
FA-3661

A byte-count prefix is trusted without checking body size · case 01

A byte-count prefix is trusted without checking body size.

Binary formats● Open access↗
FA-3662

A byte-count prefix is trusted without checking body size · case 02

A byte-count prefix is trusted without checking body size.

Binary formats◈ Members↗
FA-3663

A byte-count prefix is trusted without checking body size · case 03

A byte-count prefix is trusted without checking body size.

Binary formats◈ Members↗
FA-3664

A byte-count prefix is trusted without checking body size · case 04

A byte-count prefix is trusted without checking body size.

Binary formats◈ Members↗
FA-3665

A byte-count prefix is trusted without checking body size · case 05

A byte-count prefix is trusted without checking body size.

Binary formats◈ Members↗
FA-3666

A terminated field consumes padding after the first zero · case 01

A terminated field consumes padding after the first zero.

Binary formats● Open access↗
FA-3667

A terminated field consumes padding after the first zero · case 02

A terminated field consumes padding after the first zero.

Binary formats◈ Members↗
FA-3668

A terminated field consumes padding after the first zero · case 03

A terminated field consumes padding after the first zero.

Binary formats◈ Members↗
FA-3669

A terminated field consumes padding after the first zero · case 04

A terminated field consumes padding after the first zero.

Binary formats◈ Members↗
FA-3670

A terminated field consumes padding after the first zero · case 05

A terminated field consumes padding after the first zero.

Binary formats◈ Members↗
FA-3671

Fixed text padding removal destroys embedded zero bytes · case 01

Fixed text padding removal destroys embedded zero bytes.

Binary formats● Open access↗
FA-3672

Fixed text padding removal destroys embedded zero bytes · case 02

Fixed text padding removal destroys embedded zero bytes.

Binary formats◈ Members↗
FA-3673

Fixed text padding removal destroys embedded zero bytes · case 03

Fixed text padding removal destroys embedded zero bytes.

Binary formats◈ Members↗
FA-3674

Fixed text padding removal destroys embedded zero bytes · case 04

Fixed text padding removal destroys embedded zero bytes.

Binary formats◈ Members↗
FA-3675

Fixed text padding removal destroys embedded zero bytes · case 05

Fixed text padding removal destroys embedded zero bytes.

Binary formats◈ Members↗
FA-3676

A Pascal string length exceeds its physical slot · case 01

A Pascal string length exceeds its physical slot.

Binary formats● Open access↗
FA-3677

A Pascal string length exceeds its physical slot · case 02

A Pascal string length exceeds its physical slot.

Binary formats◈ Members↗
FA-3678

A Pascal string length exceeds its physical slot · case 03

A Pascal string length exceeds its physical slot.

Binary formats◈ Members↗
FA-3679

A Pascal string length exceeds its physical slot · case 04

A Pascal string length exceeds its physical slot.

Binary formats◈ Members↗
FA-3680

A Pascal string length exceeds its physical slot · case 05

A Pascal string length exceeds its physical slot.

Binary formats◈ Members↗
FA-3681

A three-byte field is padded on the wrong side · case 01

A three-byte field is padded on the wrong side.

Binary formats● Open access↗
FA-3682

A three-byte field is padded on the wrong side · case 02

A three-byte field is padded on the wrong side.

Binary formats◈ Members↗
FA-3683

A three-byte field is padded on the wrong side · case 03

A three-byte field is padded on the wrong side.

Binary formats◈ Members↗
FA-3684

A three-byte field is padded on the wrong side · case 04

A three-byte field is padded on the wrong side.

Binary formats◈ Members↗
FA-3685

A three-byte field is padded on the wrong side · case 05

A three-byte field is padded on the wrong side.

Binary formats◈ Members↗
FA-3686

An odd trailing byte is silently dropped from a word array · case 01

An odd trailing byte is silently dropped from a word array.

Binary formats● Open access↗
FA-3687

An odd trailing byte is silently dropped from a word array · case 02

An odd trailing byte is silently dropped from a word array.

Binary formats◈ Members↗
FA-3688

An odd trailing byte is silently dropped from a word array · case 03

An odd trailing byte is silently dropped from a word array.

Binary formats◈ Members↗
FA-3689

An odd trailing byte is silently dropped from a word array · case 04

An odd trailing byte is silently dropped from a word array.

Binary formats◈ Members↗
FA-3690

An odd trailing byte is silently dropped from a word array · case 05

An odd trailing byte is silently dropped from a word array.

Binary formats◈ Members↗
FA-3691

Hex nybbles are swapped within each byte · case 01

Hex nybbles are swapped within each byte.

Binary formats● Open access↗
FA-3692

Hex nybbles are swapped within each byte · case 02

Hex nybbles are swapped within each byte.

Binary formats◈ Members↗
FA-3693

Hex nybbles are swapped within each byte · case 03

Hex nybbles are swapped within each byte.

Binary formats◈ Members↗
FA-3694

Hex nybbles are swapped within each byte · case 04

Hex nybbles are swapped within each byte.

Binary formats◈ Members↗
FA-3695

Hex nybbles are swapped within each byte · case 05

Hex nybbles are swapped within each byte.

Binary formats◈ Members↗
FA-3696

Bit packing puts padding before the data · case 01

Bit packing puts padding before the data.

Binary formats● Open access↗
FA-3697

Bit packing puts padding before the data · case 02

Bit packing puts padding before the data.

Binary formats◈ Members↗
FA-3698

Bit packing puts padding before the data · case 03

Bit packing puts padding before the data.

Binary formats◈ Members↗
FA-3699

Bit packing puts padding before the data · case 04

Bit packing puts padding before the data.

Binary formats◈ Members↗
FA-3700

Bit packing puts padding before the data · case 05

Bit packing puts padding before the data.

Binary formats◈ 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 ↗