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

An unknown TLV tag shifts the next record boundary · case 01

An unknown TLV tag shifts the next record boundary.

Binary formats● Open access↗
FA-3702

An unknown TLV tag shifts the next record boundary · case 02

An unknown TLV tag shifts the next record boundary.

Binary formats◈ Members↗
FA-3703

An unknown TLV tag shifts the next record boundary · case 03

An unknown TLV tag shifts the next record boundary.

Binary formats◈ Members↗
FA-3704

An unknown TLV tag shifts the next record boundary · case 04

An unknown TLV tag shifts the next record boundary.

Binary formats◈ Members↗
FA-3705

An unknown TLV tag shifts the next record boundary · case 05

An unknown TLV tag shifts the next record boundary.

Binary formats◈ Members↗
FA-3706

Run-length decoding treats zero count as one · case 01

Run-length decoding treats zero count as one.

Binary formats● Open access↗
FA-3707

Run-length decoding treats zero count as one · case 02

Run-length decoding treats zero count as one.

Binary formats◈ Members↗
FA-3708

Run-length decoding treats zero count as one · case 03

Run-length decoding treats zero count as one.

Binary formats◈ Members↗
FA-3709

Run-length decoding treats zero count as one · case 04

Run-length decoding treats zero count as one.

Binary formats◈ Members↗
FA-3710

Run-length decoding treats zero count as one · case 05

Run-length decoding treats zero count as one.

Binary formats◈ Members↗
FA-3711

Run-length encoding forgets the final run · case 01

Run-length encoding forgets the final run.

Binary formats● Open access↗
FA-3712

Run-length encoding forgets the final run · case 02

Run-length encoding forgets the final run.

Binary formats◈ Members↗
FA-3713

Run-length encoding forgets the final run · case 03

Run-length encoding forgets the final run.

Binary formats◈ Members↗
FA-3714

Run-length encoding forgets the final run · case 04

Run-length encoding forgets the final run.

Binary formats◈ Members↗
FA-3715

Run-length encoding forgets the final run · case 05

Run-length encoding forgets the final run.

Binary formats◈ Members↗
FA-3716

Escaped frame markers are decoded as delimiters · case 01

Escaped frame markers are decoded as delimiters.

Binary formats● Open access↗
FA-3717

Escaped frame markers are decoded as delimiters · case 02

Escaped frame markers are decoded as delimiters.

Binary formats◈ Members↗
FA-3718

Escaped frame markers are decoded as delimiters · case 03

Escaped frame markers are decoded as delimiters.

Binary formats◈ Members↗
FA-3719

Escaped frame markers are decoded as delimiters · case 04

Escaped frame markers are decoded as delimiters.

Binary formats◈ Members↗
FA-3720

Escaped frame markers are decoded as delimiters · case 05

Escaped frame markers are decoded as delimiters.

Binary formats◈ Members↗
FA-3721

A complemented byte mask includes unbounded high bits · case 01

A complemented byte mask includes unbounded high bits.

Binary formats● Open access↗
FA-3722

A complemented byte mask includes unbounded high bits · case 02

A complemented byte mask includes unbounded high bits.

Binary formats◈ Members↗
FA-3723

A complemented byte mask includes unbounded high bits · case 03

A complemented byte mask includes unbounded high bits.

Binary formats◈ Members↗
FA-3724

A complemented byte mask includes unbounded high bits · case 04

A complemented byte mask includes unbounded high bits.

Binary formats◈ Members↗
FA-3725

A complemented byte mask includes unbounded high bits · case 05

A complemented byte mask includes unbounded high bits.

Binary formats◈ Members↗
FA-3726

Delta decoding omits the first absolute sample · case 01

Delta decoding omits the first absolute sample.

Binary formats● Open access↗
FA-3727

Delta decoding omits the first absolute sample · case 02

Delta decoding omits the first absolute sample.

Binary formats◈ Members↗
FA-3728

Delta decoding omits the first absolute sample · case 03

Delta decoding omits the first absolute sample.

Binary formats◈ Members↗
FA-3729

Delta decoding omits the first absolute sample · case 04

Delta decoding omits the first absolute sample.

Binary formats◈ Members↗
FA-3730

Delta decoding omits the first absolute sample · case 05

Delta decoding omits the first absolute sample.

Binary formats◈ Members↗
FA-3731

Delta encoding subtracts the initial sample every time · case 01

Delta encoding subtracts the initial sample every time.

Binary formats● Open access↗
FA-3732

Delta encoding subtracts the initial sample every time · case 02

Delta encoding subtracts the initial sample every time.

Binary formats◈ Members↗
FA-3733

Delta encoding subtracts the initial sample every time · case 03

Delta encoding subtracts the initial sample every time.

Binary formats◈ Members↗
FA-3734

Delta encoding subtracts the initial sample every time · case 04

Delta encoding subtracts the initial sample every time.

Binary formats◈ Members↗
FA-3735

Delta encoding subtracts the initial sample every time · case 05

Delta encoding subtracts the initial sample every time.

Binary formats◈ Members↗
FA-3736

A binary boolean treats all nonzero octets as true · case 01

A binary boolean treats all nonzero octets as true.

Binary formats● Open access↗
FA-3737

A binary boolean treats all nonzero octets as true · case 02

A binary boolean treats all nonzero octets as true.

Binary formats◈ Members↗
FA-3738

A binary boolean treats all nonzero octets as true · case 03

A binary boolean treats all nonzero octets as true.

Binary formats◈ Members↗
FA-3739

A binary boolean treats all nonzero octets as true · case 04

A binary boolean treats all nonzero octets as true.

Binary formats◈ Members↗
FA-3740

A binary boolean treats all nonzero octets as true · case 05

A binary boolean treats all nonzero octets as true.

Binary formats◈ Members↗
FA-3741

A mixed-endian identifier reverses every field · case 01

A mixed-endian identifier reverses every field.

Binary formats● Open access↗
FA-3742

A mixed-endian identifier reverses every field · case 02

A mixed-endian identifier reverses every field.

Binary formats◈ Members↗
FA-3743

A mixed-endian identifier reverses every field · case 03

A mixed-endian identifier reverses every field.

Binary formats◈ Members↗
FA-3744

A mixed-endian identifier reverses every field · case 04

A mixed-endian identifier reverses every field.

Binary formats◈ Members↗
FA-3745

A mixed-endian identifier reverses every field · case 05

A mixed-endian identifier reverses every field.

Binary formats◈ Members↗
FA-3746

An all-ones unsigned sentinel becomes a valid length · case 01

An all-ones unsigned sentinel becomes a valid length.

Binary formats● Open access↗
FA-3747

An all-ones unsigned sentinel becomes a valid length · case 02

An all-ones unsigned sentinel becomes a valid length.

Binary formats◈ Members↗
FA-3748

An all-ones unsigned sentinel becomes a valid length · case 03

An all-ones unsigned sentinel becomes a valid length.

Binary formats◈ Members↗
FA-3749

An all-ones unsigned sentinel becomes a valid length · case 04

An all-ones unsigned sentinel becomes a valid length.

Binary formats◈ Members↗
FA-3750

An all-ones unsigned sentinel becomes a valid length · case 05

An all-ones unsigned sentinel becomes a valid length.

Binary formats◈ Members↗
FA-3751

A closing parenthesis appears before its matching opener · case 01

A closing parenthesis appears before its matching opener.

Parsing● Open access↗
FA-3752

A closing parenthesis appears before its matching opener · case 02

A closing parenthesis appears before its matching opener.

Parsing◈ Members↗
FA-3753

A closing parenthesis appears before its matching opener · case 03

A closing parenthesis appears before its matching opener.

Parsing◈ Members↗
FA-3754

A closing parenthesis appears before its matching opener · case 04

A closing parenthesis appears before its matching opener.

Parsing◈ Members↗
FA-3755

A closing parenthesis appears before its matching opener · case 05

A closing parenthesis appears before its matching opener.

Parsing◈ Members↗
FA-3756

Balanced delimiters close in the wrong nesting order · case 01

Balanced delimiters close in the wrong nesting order.

Parsing● Open access↗
FA-3757

Balanced delimiters close in the wrong nesting order · case 02

Balanced delimiters close in the wrong nesting order.

Parsing◈ Members↗
FA-3758

Balanced delimiters close in the wrong nesting order · case 03

Balanced delimiters close in the wrong nesting order.

Parsing◈ Members↗
FA-3759

Balanced delimiters close in the wrong nesting order · case 04

Balanced delimiters close in the wrong nesting order.

Parsing◈ Members↗
FA-3760

Balanced delimiters close in the wrong nesting order · case 05

Balanced delimiters close in the wrong nesting order.

Parsing◈ Members↗
FA-3761

A two-character operator is split into single tokens · case 01

A two-character operator is split into single tokens.

Tokenization● Open access↗
FA-3762

A two-character operator is split into single tokens · case 02

A two-character operator is split into single tokens.

Tokenization◈ Members↗
FA-3763

A two-character operator is split into single tokens · case 03

A two-character operator is split into single tokens.

Tokenization◈ Members↗
FA-3764

A two-character operator is split into single tokens · case 04

A two-character operator is split into single tokens.

Tokenization◈ Members↗
FA-3765

A two-character operator is split into single tokens · case 05

A two-character operator is split into single tokens.

Tokenization◈ Members↗
FA-3766

Keyword prefix matching splits an identifier · case 01

Keyword prefix matching splits an identifier.

Tokenization● Open access↗
FA-3767

Keyword prefix matching splits an identifier · case 02

Keyword prefix matching splits an identifier.

Tokenization◈ Members↗
FA-3768

Keyword prefix matching splits an identifier · case 03

Keyword prefix matching splits an identifier.

Tokenization◈ Members↗
FA-3769

Keyword prefix matching splits an identifier · case 04

Keyword prefix matching splits an identifier.

Tokenization◈ Members↗
FA-3770

Keyword prefix matching splits an identifier · case 05

Keyword prefix matching splits an identifier.

Tokenization◈ Members↗
FA-3771

Whitespace removal shifts token source offsets · case 01

Whitespace removal shifts token source offsets.

Tokenization● Open access↗
FA-3772

Whitespace removal shifts token source offsets · case 02

Whitespace removal shifts token source offsets.

Tokenization◈ Members↗
FA-3773

Whitespace removal shifts token source offsets · case 03

Whitespace removal shifts token source offsets.

Tokenization◈ Members↗
FA-3774

Whitespace removal shifts token source offsets · case 04

Whitespace removal shifts token source offsets.

Tokenization◈ Members↗
FA-3775

Whitespace removal shifts token source offsets · case 05

Whitespace removal shifts token source offsets.

Tokenization◈ Members↗
FA-3776

Character offsets are reported as UTF-8 byte offsets · case 01

Character offsets are reported as UTF-8 byte offsets.

Tokenization● Open access↗
FA-3777

Character offsets are reported as UTF-8 byte offsets · case 02

Character offsets are reported as UTF-8 byte offsets.

Tokenization◈ Members↗
FA-3778

Character offsets are reported as UTF-8 byte offsets · case 03

Character offsets are reported as UTF-8 byte offsets.

Tokenization◈ Members↗
FA-3779

Character offsets are reported as UTF-8 byte offsets · case 04

Character offsets are reported as UTF-8 byte offsets.

Tokenization◈ Members↗
FA-3780

Character offsets are reported as UTF-8 byte offsets · case 05

Character offsets are reported as UTF-8 byte offsets.

Tokenization◈ Members↗
FA-3781

Column tracking does not reset after a newline · case 01

Column tracking does not reset after a newline.

Parsing● Open access↗
FA-3782

Column tracking does not reset after a newline · case 02

Column tracking does not reset after a newline.

Parsing◈ Members↗
FA-3783

Column tracking does not reset after a newline · case 03

Column tracking does not reset after a newline.

Parsing◈ Members↗
FA-3784

Column tracking does not reset after a newline · case 04

Column tracking does not reset after a newline.

Parsing◈ Members↗
FA-3785

Column tracking does not reset after a newline · case 05

Column tracking does not reset after a newline.

Parsing◈ Members↗
FA-3786

CRLF normalization creates duplicate newlines · case 01

CRLF normalization creates duplicate newlines.

Text processing● Open access↗
FA-3787

CRLF normalization creates duplicate newlines · case 02

CRLF normalization creates duplicate newlines.

Text processing◈ Members↗
FA-3788

CRLF normalization creates duplicate newlines · case 03

CRLF normalization creates duplicate newlines.

Text processing◈ Members↗
FA-3789

CRLF normalization creates duplicate newlines · case 04

CRLF normalization creates duplicate newlines.

Text processing◈ Members↗
FA-3790

CRLF normalization creates duplicate newlines · case 05

CRLF normalization creates duplicate newlines.

Text processing◈ Members↗
FA-3791

A physical continuation inserts a semantic space · case 01

A physical continuation inserts a semantic space.

Parsing● Open access↗
FA-3792

A physical continuation inserts a semantic space · case 02

A physical continuation inserts a semantic space.

Parsing◈ Members↗
FA-3793

A physical continuation inserts a semantic space · case 03

A physical continuation inserts a semantic space.

Parsing◈ Members↗
FA-3794

A physical continuation inserts a semantic space · case 04

A physical continuation inserts a semantic space.

Parsing◈ Members↗
FA-3795

A physical continuation inserts a semantic space · case 05

A physical continuation inserts a semantic space.

Parsing◈ Members↗
FA-3796

Paragraph splitting counts each blank line separately · case 01

Paragraph splitting counts each blank line separately.

Text processing● Open access↗
FA-3797

Paragraph splitting counts each blank line separately · case 02

Paragraph splitting counts each blank line separately.

Text processing◈ Members↗
FA-3798

Paragraph splitting counts each blank line separately · case 03

Paragraph splitting counts each blank line separately.

Text processing◈ Members↗
FA-3799

Paragraph splitting counts each blank line separately · case 04

Paragraph splitting counts each blank line separately.

Text processing◈ Members↗
FA-3800

Paragraph splitting counts each blank line separately · case 05

Paragraph splitting counts each blank line separately.

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 ↗