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

Recursive query joins frontier values to target rather than source · case 01

Recursive query joins frontier values to target rather than source.

Data systems● Open access↗
FA-45802

Recursive query joins frontier values to target rather than source · case 02

Recursive query joins frontier values to target rather than source.

Data systems◈ Members↗
FA-45803

Recursive query joins frontier values to target rather than source · case 03

Recursive query joins frontier values to target rather than source.

Data systems◈ Members↗
FA-45804

Recursive query joins frontier values to target rather than source · case 04

Recursive query joins frontier values to target rather than source.

Data systems◈ Members↗
FA-45805

Recursive query joins frontier values to target rather than source · case 05

Recursive query joins frontier values to target rather than source.

Data systems◈ Members↗
FA-45806

Recursive bag evaluation removes repeated values encountered at later depths · case 01

Recursive bag evaluation removes repeated values encountered at later depths.

Data systems● Open access↗
FA-45807

Recursive bag evaluation removes repeated values encountered at later depths · case 02

Recursive bag evaluation removes repeated values encountered at later depths.

Data systems◈ Members↗
FA-45808

Recursive bag evaluation removes repeated values encountered at later depths · case 03

Recursive bag evaluation removes repeated values encountered at later depths.

Data systems◈ Members↗
FA-45809

Recursive bag evaluation removes repeated values encountered at later depths · case 04

Recursive bag evaluation removes repeated values encountered at later depths.

Data systems◈ Members↗
FA-45810

Recursive bag evaluation removes repeated values encountered at later depths · case 05

Recursive bag evaluation removes repeated values encountered at later depths.

Data systems◈ Members↗
FA-45811

Interval join keeps intervals whose end equals the probe time · case 01

Interval join keeps intervals whose end equals the probe time.

Data systems● Open access↗
FA-45812

Interval join keeps intervals whose end equals the probe time · case 02

Interval join keeps intervals whose end equals the probe time.

Data systems◈ Members↗
FA-45813

Interval join keeps intervals whose end equals the probe time · case 03

Interval join keeps intervals whose end equals the probe time.

Data systems◈ Members↗
FA-45814

Interval join keeps intervals whose end equals the probe time · case 04

Interval join keeps intervals whose end equals the probe time.

Data systems◈ Members↗
FA-45815

Interval join keeps intervals whose end equals the probe time · case 05

Interval join keeps intervals whose end equals the probe time.

Data systems◈ Members↗
FA-45816

Interval join admits intervals before their start · case 01

Interval join admits intervals before their start.

Data systems● Open access↗
FA-45817

Interval join admits intervals before their start · case 02

Interval join admits intervals before their start.

Data systems◈ Members↗
FA-45818

Interval join admits intervals before their start · case 03

Interval join admits intervals before their start.

Data systems◈ Members↗
FA-45819

Interval join admits intervals before their start · case 04

Interval join admits intervals before their start.

Data systems◈ Members↗
FA-45820

Interval join admits intervals before their start · case 05

Interval join admits intervals before their start.

Data systems◈ Members↗
FA-45821

Interval join mixes active intervals from unrelated keys · case 01

Interval join mixes active intervals from unrelated keys.

Data systems● Open access↗
FA-45822

Interval join mixes active intervals from unrelated keys · case 02

Interval join mixes active intervals from unrelated keys.

Data systems◈ Members↗
FA-45823

Interval join mixes active intervals from unrelated keys · case 03

Interval join mixes active intervals from unrelated keys.

Data systems◈ Members↗
FA-45824

Interval join mixes active intervals from unrelated keys · case 04

Interval join mixes active intervals from unrelated keys.

Data systems◈ Members↗
FA-45825

Interval join mixes active intervals from unrelated keys · case 05

Interval join mixes active intervals from unrelated keys.

Data systems◈ Members↗
FA-45826

Interval join emits only the first active matching interval · case 01

Interval join emits only the first active matching interval.

Data systems● Open access↗
FA-45827

Interval join emits only the first active matching interval · case 02

Interval join emits only the first active matching interval.

Data systems◈ Members↗
FA-45828

Interval join emits only the first active matching interval · case 03

Interval join emits only the first active matching interval.

Data systems◈ Members↗
FA-45829

Interval join emits only the first active matching interval · case 04

Interval join emits only the first active matching interval.

Data systems◈ Members↗
FA-45830

Interval join emits only the first active matching interval · case 05

Interval join emits only the first active matching interval.

Data systems◈ Members↗
FA-45831

Interval join emits intervals by storage order rather than start order · case 01

Interval join emits intervals by storage order rather than start order.

Data systems● Open access↗
FA-45832

Interval join emits intervals by storage order rather than start order · case 02

Interval join emits intervals by storage order rather than start order.

Data systems◈ Members↗
FA-45833

Interval join emits intervals by storage order rather than start order · case 03

Interval join emits intervals by storage order rather than start order.

Data systems◈ Members↗
FA-45834

Interval join emits intervals by storage order rather than start order · case 04

Interval join emits intervals by storage order rather than start order.

Data systems◈ Members↗
FA-45835

Interval join emits intervals by storage order rather than start order · case 05

Interval join emits intervals by storage order rather than start order.

Data systems◈ Members↗
FA-45836

Interval join emits timestamp in place of probe identity · case 01

Interval join emits timestamp in place of probe identity.

Data systems● Open access↗
FA-45837

Interval join emits timestamp in place of probe identity · case 02

Interval join emits timestamp in place of probe identity.

Data systems◈ Members↗
FA-45838

Interval join emits timestamp in place of probe identity · case 03

Interval join emits timestamp in place of probe identity.

Data systems◈ Members↗
FA-45839

Interval join emits timestamp in place of probe identity · case 04

Interval join emits timestamp in place of probe identity.

Data systems◈ Members↗
FA-45840

Interval join emits timestamp in place of probe identity · case 05

Interval join emits timestamp in place of probe identity.

Data systems◈ Members↗
FA-45841

Reservation counts occupied slots as available · case 01

Reservation counts occupied slots as available.

Bounded deques● Open access↗
FA-45842

Reservation counts occupied slots as available · case 02

Reservation counts occupied slots as available.

Bounded deques◈ Members↗
FA-45843

Reservation counts occupied slots as available · case 03

Reservation counts occupied slots as available.

Bounded deques◈ Members↗
FA-45844

Reservation counts occupied slots as available · case 04

Reservation counts occupied slots as available.

Bounded deques◈ Members↗
FA-45845

Reservation counts occupied slots as available · case 05

Reservation counts occupied slots as available.

Bounded deques◈ Members↗
FA-45846

Reservation exceeds the available slot budget · case 01

Reservation exceeds the available slot budget.

Bounded deques● Open access↗
FA-45847

Reservation exceeds the available slot budget · case 02

Reservation exceeds the available slot budget.

Bounded deques◈ Members↗
FA-45848

Reservation exceeds the available slot budget · case 03

Reservation exceeds the available slot budget.

Bounded deques◈ Members↗
FA-45849

Reservation exceeds the available slot budget · case 04

Reservation exceeds the available slot budget.

Bounded deques◈ Members↗
FA-45850

Reservation exceeds the available slot budget · case 05

Reservation exceeds the available slot budget.

Bounded deques◈ Members↗
FA-45851

Reservation starts at the head instead of the write cursor · case 01

Reservation starts at the head instead of the write cursor.

Bounded deques● Open access↗
FA-45852

Reservation starts at the head instead of the write cursor · case 02

Reservation starts at the head instead of the write cursor.

Bounded deques◈ Members↗
FA-45853

Reservation starts at the head instead of the write cursor · case 03

Reservation starts at the head instead of the write cursor.

Bounded deques◈ Members↗
FA-45854

Reservation starts at the head instead of the write cursor · case 04

Reservation starts at the head instead of the write cursor.

Bounded deques◈ Members↗
FA-45855

Reservation starts at the head instead of the write cursor · case 05

Reservation starts at the head instead of the write cursor.

Bounded deques◈ Members↗
FA-45856

Reservation treats a wrapping region as contiguous · case 01

Reservation treats a wrapping region as contiguous.

Bounded deques● Open access↗
FA-45857

Reservation treats a wrapping region as contiguous · case 02

Reservation treats a wrapping region as contiguous.

Bounded deques◈ Members↗
FA-45858

Reservation treats a wrapping region as contiguous · case 03

Reservation treats a wrapping region as contiguous.

Bounded deques◈ Members↗
FA-45859

Reservation treats a wrapping region as contiguous · case 04

Reservation treats a wrapping region as contiguous.

Bounded deques◈ Members↗
FA-45860

Reservation treats a wrapping region as contiguous · case 05

Reservation treats a wrapping region as contiguous.

Bounded deques◈ Members↗
FA-45861

Reservation reuses the first span as the wrapped span · case 01

Reservation reuses the first span as the wrapped span.

Bounded deques● Open access↗
FA-45862

Reservation reuses the first span as the wrapped span · case 02

Reservation reuses the first span as the wrapped span.

Bounded deques◈ Members↗
FA-45863

Reservation reuses the first span as the wrapped span · case 03

Reservation reuses the first span as the wrapped span.

Bounded deques◈ Members↗
FA-45864

Reservation reuses the first span as the wrapped span · case 04

Reservation reuses the first span as the wrapped span.

Bounded deques◈ Members↗
FA-45865

Reservation reuses the first span as the wrapped span · case 05

Reservation reuses the first span as the wrapped span.

Bounded deques◈ Members↗
FA-45866

Bulk consume advances across unoccupied slots · case 01

Bulk consume advances across unoccupied slots.

Bounded deques● Open access↗
FA-45867

Bulk consume advances across unoccupied slots · case 02

Bulk consume advances across unoccupied slots.

Bounded deques◈ Members↗
FA-45868

Bulk consume advances across unoccupied slots · case 03

Bulk consume advances across unoccupied slots.

Bounded deques◈ Members↗
FA-45869

Bulk consume advances across unoccupied slots · case 04

Bulk consume advances across unoccupied slots.

Bounded deques◈ Members↗
FA-45870

Bulk consume advances across unoccupied slots · case 05

Bulk consume advances across unoccupied slots.

Bounded deques◈ Members↗
FA-45871

Bulk consume clears slots relative to array zero · case 01

Bulk consume clears slots relative to array zero.

Bounded deques● Open access↗
FA-45872

Bulk consume clears slots relative to array zero · case 02

Bulk consume clears slots relative to array zero.

Bounded deques◈ Members↗
FA-45873

Bulk consume clears slots relative to array zero · case 03

Bulk consume clears slots relative to array zero.

Bounded deques◈ Members↗
FA-45874

Bulk consume clears slots relative to array zero · case 04

Bulk consume clears slots relative to array zero.

Bounded deques◈ Members↗
FA-45875

Bulk consume clears slots relative to array zero · case 05

Bulk consume clears slots relative to array zero.

Bounded deques◈ Members↗
FA-45876

Read cursor escapes the backing allocation after consume · case 01

Read cursor escapes the backing allocation after consume.

Bounded deques● Open access↗
FA-45877

Read cursor escapes the backing allocation after consume · case 02

Read cursor escapes the backing allocation after consume.

Bounded deques◈ Members↗
FA-45878

Read cursor escapes the backing allocation after consume · case 03

Read cursor escapes the backing allocation after consume.

Bounded deques◈ Members↗
FA-45879

Read cursor escapes the backing allocation after consume · case 04

Read cursor escapes the backing allocation after consume.

Bounded deques◈ Members↗
FA-45880

Read cursor escapes the backing allocation after consume · case 05

Read cursor escapes the backing allocation after consume.

Bounded deques◈ Members↗
FA-45881

Consume overwrites occupancy with the consumed length · case 01

Consume overwrites occupancy with the consumed length.

Bounded deques● Open access↗
FA-45882

Consume overwrites occupancy with the consumed length · case 02

Consume overwrites occupancy with the consumed length.

Bounded deques◈ Members↗
FA-45883

Consume overwrites occupancy with the consumed length · case 03

Consume overwrites occupancy with the consumed length.

Bounded deques◈ Members↗
FA-45884

Consume overwrites occupancy with the consumed length · case 04

Consume overwrites occupancy with the consumed length.

Bounded deques◈ Members↗
FA-45885

Consume overwrites occupancy with the consumed length · case 05

Consume overwrites occupancy with the consumed length.

Bounded deques◈ Members↗
FA-45886

Consume flags a boundary-touch as a split memory region · case 01

Consume flags a boundary-touch as a split memory region.

Bounded deques● Open access↗
FA-45887

Consume flags a boundary-touch as a split memory region · case 02

Consume flags a boundary-touch as a split memory region.

Bounded deques◈ Members↗
FA-45888

Consume flags a boundary-touch as a split memory region · case 03

Consume flags a boundary-touch as a split memory region.

Bounded deques◈ Members↗
FA-45889

Consume flags a boundary-touch as a split memory region · case 04

Consume flags a boundary-touch as a split memory region.

Bounded deques◈ Members↗
FA-45890

Consume flags a boundary-touch as a split memory region · case 05

Consume flags a boundary-touch as a split memory region.

Bounded deques◈ Members↗
FA-45891

Growing a wrapped ring copies physical order · case 01

Growing a wrapped ring copies physical order.

Bounded deques● Open access↗
FA-45892

Growing a wrapped ring copies physical order · case 02

Growing a wrapped ring copies physical order.

Bounded deques◈ Members↗
FA-45893

Growing a wrapped ring copies physical order · case 03

Growing a wrapped ring copies physical order.

Bounded deques◈ Members↗
FA-45894

Growing a wrapped ring copies physical order · case 04

Growing a wrapped ring copies physical order.

Bounded deques◈ Members↗
FA-45895

Growing a wrapped ring copies physical order · case 05

Growing a wrapped ring copies physical order.

Bounded deques◈ Members↗
FA-45896

Growth leaves old-capacity slack instead of new-capacity slack · case 01

Growth leaves old-capacity slack instead of new-capacity slack.

Bounded deques● Open access↗
FA-45897

Growth leaves old-capacity slack instead of new-capacity slack · case 02

Growth leaves old-capacity slack instead of new-capacity slack.

Bounded deques◈ Members↗
FA-45898

Growth leaves old-capacity slack instead of new-capacity slack · case 03

Growth leaves old-capacity slack instead of new-capacity slack.

Bounded deques◈ Members↗
FA-45899

Growth leaves old-capacity slack instead of new-capacity slack · case 04

Growth leaves old-capacity slack instead of new-capacity slack.

Bounded deques◈ Members↗
FA-45900

Growth leaves old-capacity slack instead of new-capacity slack · case 05

Growth leaves old-capacity slack instead of new-capacity slack.

Bounded deques◈ 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 ↗