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

Full outer join marks equal-key residual failures as matched · case 01

Full outer join marks equal-key residual failures as matched.

Data systems● Open access↗
FA-45002

Full outer join marks equal-key residual failures as matched · case 02

Full outer join marks equal-key residual failures as matched.

Data systems◈ Members↗
FA-45003

Full outer join marks equal-key residual failures as matched · case 03

Full outer join marks equal-key residual failures as matched.

Data systems◈ Members↗
FA-45004

Full outer join marks equal-key residual failures as matched · case 04

Full outer join marks equal-key residual failures as matched.

Data systems◈ Members↗
FA-45005

Full outer join marks equal-key residual failures as matched · case 05

Full outer join marks equal-key residual failures as matched.

Data systems◈ Members↗
FA-45006

Full outer join stores right IDs but tests physical positions · case 01

Full outer join stores right IDs but tests physical positions.

Data systems● Open access↗
FA-45007

Full outer join stores right IDs but tests physical positions · case 02

Full outer join stores right IDs but tests physical positions.

Data systems◈ Members↗
FA-45008

Full outer join stores right IDs but tests physical positions · case 03

Full outer join stores right IDs but tests physical positions.

Data systems◈ Members↗
FA-45009

Full outer join stores right IDs but tests physical positions · case 04

Full outer join stores right IDs but tests physical positions.

Data systems◈ Members↗
FA-45010

Full outer join stores right IDs but tests physical positions · case 05

Full outer join stores right IDs but tests physical positions.

Data systems◈ Members↗
FA-45011

Full outer join carries a successful match into the next left row · case 01

Full outer join carries a successful match into the next left row.

Data systems● Open access↗
FA-45012

Full outer join carries a successful match into the next left row · case 02

Full outer join carries a successful match into the next left row.

Data systems◈ Members↗
FA-45013

Full outer join carries a successful match into the next left row · case 03

Full outer join carries a successful match into the next left row.

Data systems◈ Members↗
FA-45014

Full outer join carries a successful match into the next left row · case 04

Full outer join carries a successful match into the next left row.

Data systems◈ Members↗
FA-45015

Full outer join carries a successful match into the next left row · case 05

Full outer join carries a successful match into the next left row.

Data systems◈ Members↗
FA-45016

Full outer join omits unmatched left placeholders · case 01

Full outer join omits unmatched left placeholders.

Data systems● Open access↗
FA-45017

Full outer join omits unmatched left placeholders · case 02

Full outer join omits unmatched left placeholders.

Data systems◈ Members↗
FA-45018

Full outer join omits unmatched left placeholders · case 03

Full outer join omits unmatched left placeholders.

Data systems◈ Members↗
FA-45019

Full outer join omits unmatched left placeholders · case 04

Full outer join omits unmatched left placeholders.

Data systems◈ Members↗
FA-45020

Full outer join omits unmatched left placeholders · case 05

Full outer join omits unmatched left placeholders.

Data systems◈ Members↗
FA-45021

Full outer join emits already matched right rows again · case 01

Full outer join emits already matched right rows again.

Data systems● Open access↗
FA-45022

Full outer join emits already matched right rows again · case 02

Full outer join emits already matched right rows again.

Data systems◈ Members↗
FA-45023

Full outer join emits already matched right rows again · case 03

Full outer join emits already matched right rows again.

Data systems◈ Members↗
FA-45024

Full outer join emits already matched right rows again · case 04

Full outer join emits already matched right rows again.

Data systems◈ Members↗
FA-45025

Full outer join emits already matched right rows again · case 05

Full outer join emits already matched right rows again.

Data systems◈ Members↗
FA-45026

Full outer join treats missing keys as equal matches · case 01

Full outer join treats missing keys as equal matches.

Data systems● Open access↗
FA-45027

Full outer join treats missing keys as equal matches · case 02

Full outer join treats missing keys as equal matches.

Data systems◈ Members↗
FA-45028

Full outer join treats missing keys as equal matches · case 03

Full outer join treats missing keys as equal matches.

Data systems◈ Members↗
FA-45029

Full outer join treats missing keys as equal matches · case 04

Full outer join treats missing keys as equal matches.

Data systems◈ Members↗
FA-45030

Full outer join treats missing keys as equal matches · case 05

Full outer join treats missing keys as equal matches.

Data systems◈ Members↗
FA-45031

A resume cursor stops at an empty batch instead of normalizing · case 01

A resume cursor stops at an empty batch instead of normalizing.

Data systems● Open access↗
FA-45032

A resume cursor stops at an empty batch instead of normalizing · case 02

A resume cursor stops at an empty batch instead of normalizing.

Data systems◈ Members↗
FA-45033

A resume cursor stops at an empty batch instead of normalizing · case 03

A resume cursor stops at an empty batch instead of normalizing.

Data systems◈ Members↗
FA-45034

A resume cursor stops at an empty batch instead of normalizing · case 04

A resume cursor stops at an empty batch instead of normalizing.

Data systems◈ Members↗
FA-45035

A resume cursor stops at an empty batch instead of normalizing · case 05

A resume cursor stops at an empty batch instead of normalizing.

Data systems◈ Members↗
FA-45036

Cross-batch resume carries the old row offset into the next batch · case 01

Cross-batch resume carries the old row offset into the next batch.

Data systems● Open access↗
FA-45037

Cross-batch resume carries the old row offset into the next batch · case 02

Cross-batch resume carries the old row offset into the next batch.

Data systems◈ Members↗
FA-45038

Cross-batch resume carries the old row offset into the next batch · case 03

Cross-batch resume carries the old row offset into the next batch.

Data systems◈ Members↗
FA-45039

Cross-batch resume carries the old row offset into the next batch · case 04

Cross-batch resume carries the old row offset into the next batch.

Data systems◈ Members↗
FA-45040

Cross-batch resume carries the old row offset into the next batch · case 05

Cross-batch resume carries the old row offset into the next batch.

Data systems◈ Members↗
FA-45041

Fetch decrements quota per batch rather than per emitted row · case 01

Fetch decrements quota per batch rather than per emitted row.

Data systems● Open access↗
FA-45042

Fetch decrements quota per batch rather than per emitted row · case 02

Fetch decrements quota per batch rather than per emitted row.

Data systems◈ Members↗
FA-45043

Fetch decrements quota per batch rather than per emitted row · case 03

Fetch decrements quota per batch rather than per emitted row.

Data systems◈ Members↗
FA-45044

Fetch decrements quota per batch rather than per emitted row · case 04

Fetch decrements quota per batch rather than per emitted row.

Data systems◈ Members↗
FA-45045

Fetch decrements quota per batch rather than per emitted row · case 05

Fetch decrements quota per batch rather than per emitted row.

Data systems◈ Members↗
FA-45046

Returned resume cursor points back at the last emitted row · case 01

Returned resume cursor points back at the last emitted row.

Data systems● Open access↗
FA-45047

Returned resume cursor points back at the last emitted row · case 02

Returned resume cursor points back at the last emitted row.

Data systems◈ Members↗
FA-45048

Returned resume cursor points back at the last emitted row · case 03

Returned resume cursor points back at the last emitted row.

Data systems◈ Members↗
FA-45049

Returned resume cursor points back at the last emitted row · case 04

Returned resume cursor points back at the last emitted row.

Data systems◈ Members↗
FA-45050

Returned resume cursor points back at the last emitted row · case 05

Returned resume cursor points back at the last emitted row.

Data systems◈ Members↗
FA-45051

Batch fetch reads the beginning of a partially consumed batch · case 01

Batch fetch reads the beginning of a partially consumed batch.

Data systems● Open access↗
FA-45052

Batch fetch reads the beginning of a partially consumed batch · case 02

Batch fetch reads the beginning of a partially consumed batch.

Data systems◈ Members↗
FA-45053

Batch fetch reads the beginning of a partially consumed batch · case 03

Batch fetch reads the beginning of a partially consumed batch.

Data systems◈ Members↗
FA-45054

Batch fetch reads the beginning of a partially consumed batch · case 04

Batch fetch reads the beginning of a partially consumed batch.

Data systems◈ Members↗
FA-45055

Batch fetch reads the beginning of a partially consumed batch · case 05

Batch fetch reads the beginning of a partially consumed batch.

Data systems◈ Members↗
FA-45056

Fetch drains all remaining rows despite its output quota · case 01

Fetch drains all remaining rows despite its output quota.

Data systems● Open access↗
FA-45057

Fetch drains all remaining rows despite its output quota · case 02

Fetch drains all remaining rows despite its output quota.

Data systems◈ Members↗
FA-45058

Fetch drains all remaining rows despite its output quota · case 03

Fetch drains all remaining rows despite its output quota.

Data systems◈ Members↗
FA-45059

Fetch drains all remaining rows despite its output quota · case 04

Fetch drains all remaining rows despite its output quota.

Data systems◈ Members↗
FA-45060

Fetch drains all remaining rows despite its output quota · case 05

Fetch drains all remaining rows despite its output quota.

Data systems◈ Members↗
FA-45061

Constant vector materialization ignores scalar validity · case 01

Constant vector materialization ignores scalar validity.

Data systems● Open access↗
FA-45062

Constant vector materialization ignores scalar validity · case 02

Constant vector materialization ignores scalar validity.

Data systems◈ Members↗
FA-45063

Constant vector materialization ignores scalar validity · case 03

Constant vector materialization ignores scalar validity.

Data systems◈ Members↗
FA-45064

Constant vector materialization ignores scalar validity · case 04

Constant vector materialization ignores scalar validity.

Data systems◈ Members↗
FA-45065

Constant vector materialization ignores scalar validity · case 05

Constant vector materialization ignores scalar validity.

Data systems◈ Members↗
FA-45066

Constant vector materialization ignores row validity · case 01

Constant vector materialization ignores row validity.

Data systems● Open access↗
FA-45067

Constant vector materialization ignores row validity · case 02

Constant vector materialization ignores row validity.

Data systems◈ Members↗
FA-45068

Constant vector materialization ignores row validity · case 03

Constant vector materialization ignores row validity.

Data systems◈ Members↗
FA-45069

Constant vector materialization ignores row validity · case 04

Constant vector materialization ignores row validity.

Data systems◈ Members↗
FA-45070

Constant vector materialization ignores row validity · case 05

Constant vector materialization ignores row validity.

Data systems◈ Members↗
FA-45071

Constant vector treats zero as a null scalar · case 01

Constant vector treats zero as a null scalar.

Data systems● Open access↗
FA-45072

Constant vector treats zero as a null scalar · case 02

Constant vector treats zero as a null scalar.

Data systems◈ Members↗
FA-45073

Constant vector treats zero as a null scalar · case 03

Constant vector treats zero as a null scalar.

Data systems◈ Members↗
FA-45074

Constant vector treats zero as a null scalar · case 04

Constant vector treats zero as a null scalar.

Data systems◈ Members↗
FA-45075

Constant vector treats zero as a null scalar · case 05

Constant vector treats zero as a null scalar.

Data systems◈ Members↗
FA-45076

Constant vector materializes the first selection-length rows · case 01

Constant vector materializes the first selection-length rows.

Data systems● Open access↗
FA-45077

Constant vector materializes the first selection-length rows · case 02

Constant vector materializes the first selection-length rows.

Data systems◈ Members↗
FA-45078

Constant vector materializes the first selection-length rows · case 03

Constant vector materializes the first selection-length rows.

Data systems◈ Members↗
FA-45079

Constant vector materializes the first selection-length rows · case 04

Constant vector materializes the first selection-length rows.

Data systems◈ Members↗
FA-45080

Constant vector materializes the first selection-length rows · case 05

Constant vector materializes the first selection-length rows.

Data systems◈ Members↗
FA-45081

Constant vector removes repeated gathered rows · case 01

Constant vector removes repeated gathered rows.

Data systems● Open access↗
FA-45082

Constant vector removes repeated gathered rows · case 02

Constant vector removes repeated gathered rows.

Data systems◈ Members↗
FA-45083

Constant vector removes repeated gathered rows · case 03

Constant vector removes repeated gathered rows.

Data systems◈ Members↗
FA-45084

Constant vector removes repeated gathered rows · case 04

Constant vector removes repeated gathered rows.

Data systems◈ Members↗
FA-45085

Constant vector removes repeated gathered rows · case 05

Constant vector removes repeated gathered rows.

Data systems◈ Members↗
FA-45086

Constant vector loses source row ordinals in output · case 01

Constant vector loses source row ordinals in output.

Data systems● Open access↗
FA-45087

Constant vector loses source row ordinals in output · case 02

Constant vector loses source row ordinals in output.

Data systems◈ Members↗
FA-45088

Constant vector loses source row ordinals in output · case 03

Constant vector loses source row ordinals in output.

Data systems◈ Members↗
FA-45089

Constant vector loses source row ordinals in output · case 04

Constant vector loses source row ordinals in output.

Data systems◈ Members↗
FA-45090

Constant vector loses source row ordinals in output · case 05

Constant vector loses source row ordinals in output.

Data systems◈ Members↗
FA-45091

Scatter writes lanes disabled by the update selection mask · case 01

Scatter writes lanes disabled by the update selection mask.

Data systems● Open access↗
FA-45092

Scatter writes lanes disabled by the update selection mask · case 02

Scatter writes lanes disabled by the update selection mask.

Data systems◈ Members↗
FA-45093

Scatter writes lanes disabled by the update selection mask · case 03

Scatter writes lanes disabled by the update selection mask.

Data systems◈ Members↗
FA-45094

Scatter writes lanes disabled by the update selection mask · case 04

Scatter writes lanes disabled by the update selection mask.

Data systems◈ Members↗
FA-45095

Scatter writes lanes disabled by the update selection mask · case 05

Scatter writes lanes disabled by the update selection mask.

Data systems◈ Members↗
FA-45096

Scatter uses update position instead of target address · case 01

Scatter uses update position instead of target address.

Data systems● Open access↗
FA-45097

Scatter uses update position instead of target address · case 02

Scatter uses update position instead of target address.

Data systems◈ Members↗
FA-45098

Scatter uses update position instead of target address · case 03

Scatter uses update position instead of target address.

Data systems◈ Members↗
FA-45099

Scatter uses update position instead of target address · case 04

Scatter uses update position instead of target address.

Data systems◈ Members↗
FA-45100

Scatter uses update position instead of target address · case 05

Scatter uses update position instead of target address.

Data systems◈ 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 ↗