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

Rejected semantic patches consume revision numbers · case 01

Rejected semantic patches consume revision numbers.

Accessibility interaction semantics● Open access↗
FA-54002

Rejected semantic patches consume revision numbers · case 02

Rejected semantic patches consume revision numbers.

Accessibility interaction semantics◈ Members↗
FA-54003

Rejected semantic patches consume revision numbers · case 03

Rejected semantic patches consume revision numbers.

Accessibility interaction semantics◈ Members↗
FA-54004

Rejected semantic patches consume revision numbers · case 04

Rejected semantic patches consume revision numbers.

Accessibility interaction semantics◈ Members↗
FA-54005

Rejected semantic patches consume revision numbers · case 05

Rejected semantic patches consume revision numbers.

Accessibility interaction semantics◈ Members↗
FA-54006

Child pages mix snapshots after a document revision · case 01

Child pages mix snapshots after a document revision.

Accessibility interaction semantics● Open access↗
FA-54007

Child pages mix snapshots after a document revision · case 02

Child pages mix snapshots after a document revision.

Accessibility interaction semantics◈ Members↗
FA-54008

Child pages mix snapshots after a document revision · case 03

Child pages mix snapshots after a document revision.

Accessibility interaction semantics◈ Members↗
FA-54009

Child pages mix snapshots after a document revision · case 04

Child pages mix snapshots after a document revision.

Accessibility interaction semantics◈ Members↗
FA-54010

Child pages mix snapshots after a document revision · case 05

Child pages mix snapshots after a document revision.

Accessibility interaction semantics◈ Members↗
FA-54011

Boolean child offsets become integer indices · case 01

Boolean child offsets become integer indices.

Accessibility interaction semantics● Open access↗
FA-54012

Boolean child offsets become integer indices · case 02

Boolean child offsets become integer indices.

Accessibility interaction semantics◈ Members↗
FA-54013

Boolean child offsets become integer indices · case 03

Boolean child offsets become integer indices.

Accessibility interaction semantics◈ Members↗
FA-54014

Boolean child offsets become integer indices · case 04

Boolean child offsets become integer indices.

Accessibility interaction semantics◈ Members↗
FA-54015

Boolean child offsets become integer indices · case 05

Boolean child offsets become integer indices.

Accessibility interaction semantics◈ Members↗
FA-54016

Boolean page capacities are treated as a one-child request · case 01

Boolean page capacities are treated as a one-child request.

Accessibility interaction semantics● Open access↗
FA-54017

Boolean page capacities are treated as a one-child request · case 02

Boolean page capacities are treated as a one-child request.

Accessibility interaction semantics◈ Members↗
FA-54018

Boolean page capacities are treated as a one-child request · case 03

Boolean page capacities are treated as a one-child request.

Accessibility interaction semantics◈ Members↗
FA-54019

Boolean page capacities are treated as a one-child request · case 04

Boolean page capacities are treated as a one-child request.

Accessibility interaction semantics◈ Members↗
FA-54020

Boolean page capacities are treated as a one-child request · case 05

Boolean page capacities are treated as a one-child request.

Accessibility interaction semantics◈ Members↗
FA-54021

Negative child offsets address the final page · case 01

Negative child offsets address the final page.

Accessibility interaction semantics● Open access↗
FA-54022

Negative child offsets address the final page · case 02

Negative child offsets address the final page.

Accessibility interaction semantics◈ Members↗
FA-54023

Negative child offsets address the final page · case 03

Negative child offsets address the final page.

Accessibility interaction semantics◈ Members↗
FA-54024

Negative child offsets address the final page · case 04

Negative child offsets address the final page.

Accessibility interaction semantics◈ Members↗
FA-54025

Negative child offsets address the final page · case 05

Negative child offsets address the final page.

Accessibility interaction semantics◈ Members↗
FA-54026

Negative child capacities silently truncate results · case 01

Negative child capacities silently truncate results.

Accessibility interaction semantics● Open access↗
FA-54027

Negative child capacities silently truncate results · case 02

Negative child capacities silently truncate results.

Accessibility interaction semantics◈ Members↗
FA-54028

Negative child capacities silently truncate results · case 03

Negative child capacities silently truncate results.

Accessibility interaction semantics◈ Members↗
FA-54029

Negative child capacities silently truncate results · case 04

Negative child capacities silently truncate results.

Accessibility interaction semantics◈ Members↗
FA-54030

Negative child capacities silently truncate results · case 05

Negative child capacities silently truncate results.

Accessibility interaction semantics◈ Members↗
FA-54031

Unexposed child placeholders consume page capacity · case 01

Unexposed child placeholders consume page capacity.

Accessibility interaction semantics● Open access↗
FA-54032

Unexposed child placeholders consume page capacity · case 02

Unexposed child placeholders consume page capacity.

Accessibility interaction semantics◈ Members↗
FA-54033

Unexposed child placeholders consume page capacity · case 03

Unexposed child placeholders consume page capacity.

Accessibility interaction semantics◈ Members↗
FA-54034

Unexposed child placeholders consume page capacity · case 04

Unexposed child placeholders consume page capacity.

Accessibility interaction semantics◈ Members↗
FA-54035

Unexposed child placeholders consume page capacity · case 05

Unexposed child placeholders consume page capacity.

Accessibility interaction semantics◈ Members↗
FA-54036

Repeated semantic children occupy multiple page slots · case 01

Repeated semantic children occupy multiple page slots.

Accessibility interaction semantics● Open access↗
FA-54037

Repeated semantic children occupy multiple page slots · case 02

Repeated semantic children occupy multiple page slots.

Accessibility interaction semantics◈ Members↗
FA-54038

Repeated semantic children occupy multiple page slots · case 03

Repeated semantic children occupy multiple page slots.

Accessibility interaction semantics◈ Members↗
FA-54039

Repeated semantic children occupy multiple page slots · case 04

Repeated semantic children occupy multiple page slots.

Accessibility interaction semantics◈ Members↗
FA-54040

Repeated semantic children occupy multiple page slots · case 05

Repeated semantic children occupy multiple page slots.

Accessibility interaction semantics◈ Members↗
FA-54041

Child pagination treats capacity as an absolute end offset · case 01

Child pagination treats capacity as an absolute end offset.

Accessibility interaction semantics● Open access↗
FA-54042

Child pagination treats capacity as an absolute end offset · case 02

Child pagination treats capacity as an absolute end offset.

Accessibility interaction semantics◈ Members↗
FA-54043

Child pagination treats capacity as an absolute end offset · case 03

Child pagination treats capacity as an absolute end offset.

Accessibility interaction semantics◈ Members↗
FA-54044

Child pagination treats capacity as an absolute end offset · case 04

Child pagination treats capacity as an absolute end offset.

Accessibility interaction semantics◈ Members↗
FA-54045

Child pagination treats capacity as an absolute end offset · case 05

Child pagination treats capacity as an absolute end offset.

Accessibility interaction semantics◈ Members↗
FA-54046

An empty child page advertises a continuation to itself · case 01

An empty child page advertises a continuation to itself.

Accessibility interaction semantics● Open access↗
FA-54047

An empty child page advertises a continuation to itself · case 02

An empty child page advertises a continuation to itself.

Accessibility interaction semantics◈ Members↗
FA-54048

An empty child page advertises a continuation to itself · case 03

An empty child page advertises a continuation to itself.

Accessibility interaction semantics◈ Members↗
FA-54049

An empty child page advertises a continuation to itself · case 04

An empty child page advertises a continuation to itself.

Accessibility interaction semantics◈ Members↗
FA-54050

An empty child page advertises a continuation to itself · case 05

An empty child page advertises a continuation to itself.

Accessibility interaction semantics◈ Members↗
FA-54051

A terminal child page advertises an extra empty page · case 01

A terminal child page advertises an extra empty page.

Accessibility interaction semantics● Open access↗
FA-54052

A terminal child page advertises an extra empty page · case 02

A terminal child page advertises an extra empty page.

Accessibility interaction semantics◈ Members↗
FA-54053

A terminal child page advertises an extra empty page · case 03

A terminal child page advertises an extra empty page.

Accessibility interaction semantics◈ Members↗
FA-54054

A terminal child page advertises an extra empty page · case 04

A terminal child page advertises an extra empty page.

Accessibility interaction semantics◈ Members↗
FA-54055

A terminal child page advertises an extra empty page · case 05

A terminal child page advertises an extra empty page.

Accessibility interaction semantics◈ Members↗
FA-54056

Read-only text exposes a mutating accessibility edit path · case 01

Read-only text exposes a mutating accessibility edit path.

Accessibility interaction semantics● Open access↗
FA-54057

Read-only text exposes a mutating accessibility edit path · case 02

Read-only text exposes a mutating accessibility edit path.

Accessibility interaction semantics◈ Members↗
FA-54058

Read-only text exposes a mutating accessibility edit path · case 03

Read-only text exposes a mutating accessibility edit path.

Accessibility interaction semantics◈ Members↗
FA-54059

Read-only text exposes a mutating accessibility edit path · case 04

Read-only text exposes a mutating accessibility edit path.

Accessibility interaction semantics◈ Members↗
FA-54060

Read-only text exposes a mutating accessibility edit path · case 05

Read-only text exposes a mutating accessibility edit path.

Accessibility interaction semantics◈ Members↗
FA-54061

Accessible edits accept negative source offsets · case 01

Accessible edits accept negative source offsets.

Accessibility interaction semantics● Open access↗
FA-54062

Accessible edits accept negative source offsets · case 02

Accessible edits accept negative source offsets.

Accessibility interaction semantics◈ Members↗
FA-54063

Accessible edits accept negative source offsets · case 03

Accessible edits accept negative source offsets.

Accessibility interaction semantics◈ Members↗
FA-54064

Accessible edits accept negative source offsets · case 04

Accessible edits accept negative source offsets.

Accessibility interaction semantics◈ Members↗
FA-54065

Accessible edits accept negative source offsets · case 05

Accessible edits accept negative source offsets.

Accessibility interaction semantics◈ Members↗
FA-54066

Reversed edit ranges duplicate accessible text · case 01

Reversed edit ranges duplicate accessible text.

Accessibility interaction semantics● Open access↗
FA-54067

Reversed edit ranges duplicate accessible text · case 02

Reversed edit ranges duplicate accessible text.

Accessibility interaction semantics◈ Members↗
FA-54068

Reversed edit ranges duplicate accessible text · case 03

Reversed edit ranges duplicate accessible text.

Accessibility interaction semantics◈ Members↗
FA-54069

Reversed edit ranges duplicate accessible text · case 04

Reversed edit ranges duplicate accessible text.

Accessibility interaction semantics◈ Members↗
FA-54070

Reversed edit ranges duplicate accessible text · case 05

Reversed edit ranges duplicate accessible text.

Accessibility interaction semantics◈ Members↗
FA-54071

Edit end beyond current text is silently accepted · case 01

Edit end beyond current text is silently accepted.

Accessibility interaction semantics● Open access↗
FA-54072

Edit end beyond current text is silently accepted · case 02

Edit end beyond current text is silently accepted.

Accessibility interaction semantics◈ Members↗
FA-54073

Edit end beyond current text is silently accepted · case 03

Edit end beyond current text is silently accepted.

Accessibility interaction semantics◈ Members↗
FA-54074

Edit end beyond current text is silently accepted · case 04

Edit end beyond current text is silently accepted.

Accessibility interaction semantics◈ Members↗
FA-54075

Edit end beyond current text is silently accepted · case 05

Edit end beyond current text is silently accepted.

Accessibility interaction semantics◈ Members↗
FA-54076

Text replacement deletes one extra codepoint · case 01

Text replacement deletes one extra codepoint.

Accessibility interaction semantics● Open access↗
FA-54077

Text replacement deletes one extra codepoint · case 02

Text replacement deletes one extra codepoint.

Accessibility interaction semantics◈ Members↗
FA-54078

Text replacement deletes one extra codepoint · case 03

Text replacement deletes one extra codepoint.

Accessibility interaction semantics◈ Members↗
FA-54079

Text replacement deletes one extra codepoint · case 04

Text replacement deletes one extra codepoint.

Accessibility interaction semantics◈ Members↗
FA-54080

Text replacement deletes one extra codepoint · case 05

Text replacement deletes one extra codepoint.

Accessibility interaction semantics◈ Members↗
FA-54081

Replacement text is appended at the end of the control · case 01

Replacement text is appended at the end of the control.

Accessibility interaction semantics● Open access↗
FA-54082

Replacement text is appended at the end of the control · case 02

Replacement text is appended at the end of the control.

Accessibility interaction semantics◈ Members↗
FA-54083

Replacement text is appended at the end of the control · case 03

Replacement text is appended at the end of the control.

Accessibility interaction semantics◈ Members↗
FA-54084

Replacement text is appended at the end of the control · case 04

Replacement text is appended at the end of the control.

Accessibility interaction semantics◈ Members↗
FA-54085

Replacement text is appended at the end of the control · case 05

Replacement text is appended at the end of the control.

Accessibility interaction semantics◈ Members↗
FA-54086

Text exactly at the declared maximum is rejected · case 01

Text exactly at the declared maximum is rejected.

Accessibility interaction semantics● Open access↗
FA-54087

Text exactly at the declared maximum is rejected · case 02

Text exactly at the declared maximum is rejected.

Accessibility interaction semantics◈ Members↗
FA-54088

Text exactly at the declared maximum is rejected · case 03

Text exactly at the declared maximum is rejected.

Accessibility interaction semantics◈ Members↗
FA-54089

Text exactly at the declared maximum is rejected · case 04

Text exactly at the declared maximum is rejected.

Accessibility interaction semantics◈ Members↗
FA-54090

Text exactly at the declared maximum is rejected · case 05

Text exactly at the declared maximum is rejected.

Accessibility interaction semantics◈ Members↗
FA-54091

Zero-capacity accessible editors accept inserted text · case 01

Zero-capacity accessible editors accept inserted text.

Accessibility interaction semantics● Open access↗
FA-54092

Zero-capacity accessible editors accept inserted text · case 02

Zero-capacity accessible editors accept inserted text.

Accessibility interaction semantics◈ Members↗
FA-54093

Zero-capacity accessible editors accept inserted text · case 03

Zero-capacity accessible editors accept inserted text.

Accessibility interaction semantics◈ Members↗
FA-54094

Zero-capacity accessible editors accept inserted text · case 04

Zero-capacity accessible editors accept inserted text.

Accessibility interaction semantics◈ Members↗
FA-54095

Zero-capacity accessible editors accept inserted text · case 05

Zero-capacity accessible editors accept inserted text.

Accessibility interaction semantics◈ Members↗
FA-54096

Successful replacement reports the removed range end · case 01

Successful replacement reports the removed range end.

Accessibility interaction semantics● Open access↗
FA-54097

Successful replacement reports the removed range end · case 02

Successful replacement reports the removed range end.

Accessibility interaction semantics◈ Members↗
FA-54098

Successful replacement reports the removed range end · case 03

Successful replacement reports the removed range end.

Accessibility interaction semantics◈ Members↗
FA-54099

Successful replacement reports the removed range end · case 04

Successful replacement reports the removed range end.

Accessibility interaction semantics◈ Members↗
FA-54100

Successful replacement reports the removed range end · case 05

Successful replacement reports the removed range end.

Accessibility interaction 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 ↗