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

Next value: Skips the immediate successor · case 01

The query violates its result contract: skips the immediate successor.

Analytical processing● Open access↗
FA-2502

Next value: Skips the immediate successor · case 02

The query violates its result contract: skips the immediate successor.

Analytical processing◈ Members↗
FA-2503

Next value: Skips the immediate successor · case 03

The query violates its result contract: skips the immediate successor.

Analytical processing◈ Members↗
FA-2504

Next value: Skips the immediate successor · case 04

The query violates its result contract: skips the immediate successor.

Analytical processing◈ Members↗
FA-2505

Next value: Skips the immediate successor · case 05

The query violates its result contract: skips the immediate successor.

Analytical processing◈ Members↗
FA-2506

Next value: Invents zero beyond the end of a partition · case 01

The query violates its result contract: invents zero beyond the end of a partition.

Analytical processing● Open access↗
FA-2507

Next value: Invents zero beyond the end of a partition · case 02

The query violates its result contract: invents zero beyond the end of a partition.

Analytical processing◈ Members↗
FA-2508

Next value: Invents zero beyond the end of a partition · case 03

The query violates its result contract: invents zero beyond the end of a partition.

Analytical processing◈ Members↗
FA-2509

Next value: Invents zero beyond the end of a partition · case 04

The query violates its result contract: invents zero beyond the end of a partition.

Analytical processing◈ Members↗
FA-2510

Next value: Invents zero beyond the end of a partition · case 05

The query violates its result contract: invents zero beyond the end of a partition.

Analytical processing◈ Members↗
FA-2511

Next value: Selects successor in value order instead of identity order · case 01

The query violates its result contract: selects successor in value order instead of identity order.

Analytical processing● Open access↗
FA-2512

Next value: Selects successor in value order instead of identity order · case 02

The query violates its result contract: selects successor in value order instead of identity order.

Analytical processing◈ Members↗
FA-2513

Next value: Selects successor in value order instead of identity order · case 03

The query violates its result contract: selects successor in value order instead of identity order.

Analytical processing◈ Members↗
FA-2514

Next value: Selects successor in value order instead of identity order · case 04

The query violates its result contract: selects successor in value order instead of identity order.

Analytical processing◈ Members↗
FA-2515

Next value: Selects successor in value order instead of identity order · case 05

The query violates its result contract: selects successor in value order instead of identity order.

Analytical processing◈ Members↗
FA-2516

Partition last value: Uses default frame ending at current row · case 01

The query violates its result contract: uses default frame ending at current row.

Analytical processing● Open access↗
FA-2517

Partition last value: Uses default frame ending at current row · case 02

The query violates its result contract: uses default frame ending at current row.

Analytical processing◈ Members↗
FA-2518

Partition last value: Uses default frame ending at current row · case 03

The query violates its result contract: uses default frame ending at current row.

Analytical processing◈ Members↗
FA-2519

Partition last value: Uses default frame ending at current row · case 04

The query violates its result contract: uses default frame ending at current row.

Analytical processing◈ Members↗
FA-2520

Partition last value: Uses default frame ending at current row · case 05

The query violates its result contract: uses default frame ending at current row.

Analytical processing◈ Members↗
FA-2521

Partition last value: Selects the first partition value · case 01

The query violates its result contract: selects the first partition value.

Analytical processing● Open access↗
FA-2522

Partition last value: Selects the first partition value · case 02

The query violates its result contract: selects the first partition value.

Analytical processing◈ Members↗
FA-2523

Partition last value: Selects the first partition value · case 03

The query violates its result contract: selects the first partition value.

Analytical processing◈ Members↗
FA-2524

Partition last value: Selects the first partition value · case 04

The query violates its result contract: selects the first partition value.

Analytical processing◈ Members↗
FA-2525

Partition last value: Selects the first partition value · case 05

The query violates its result contract: selects the first partition value.

Analytical processing◈ Members↗
FA-2526

Partition last value: Confuses last identity with largest measurement · case 01

The query violates its result contract: confuses last identity with largest measurement.

Analytical processing● Open access↗
FA-2527

Partition last value: Confuses last identity with largest measurement · case 02

The query violates its result contract: confuses last identity with largest measurement.

Analytical processing◈ Members↗
FA-2528

Partition last value: Confuses last identity with largest measurement · case 03

The query violates its result contract: confuses last identity with largest measurement.

Analytical processing◈ Members↗
FA-2529

Partition last value: Confuses last identity with largest measurement · case 04

The query violates its result contract: confuses last identity with largest measurement.

Analytical processing◈ Members↗
FA-2530

Partition last value: Confuses last identity with largest measurement · case 05

The query violates its result contract: confuses last identity with largest measurement.

Analytical processing◈ Members↗
FA-2531

Partition last value: Uses the last record in the entire relation · case 01

The query violates its result contract: uses the last record in the entire relation.

Analytical processing● Open access↗
FA-2532

Partition last value: Uses the last record in the entire relation · case 02

The query violates its result contract: uses the last record in the entire relation.

Analytical processing◈ Members↗
FA-2533

Partition last value: Uses the last record in the entire relation · case 03

The query violates its result contract: uses the last record in the entire relation.

Analytical processing◈ Members↗
FA-2534

Partition last value: Uses the last record in the entire relation · case 04

The query violates its result contract: uses the last record in the entire relation.

Analytical processing◈ Members↗
FA-2535

Partition last value: Uses the last record in the entire relation · case 05

The query violates its result contract: uses the last record in the entire relation.

Analytical processing◈ Members↗
FA-2536

Partition last value: Removes NULL values and output records before selecting last · case 01

The query violates its result contract: removes null values and output records before selecting last.

Analytical processing● Open access↗
FA-2537

Partition last value: Removes NULL values and output records before selecting last · case 02

The query violates its result contract: removes null values and output records before selecting last.

Analytical processing◈ Members↗
FA-2538

Partition last value: Removes NULL values and output records before selecting last · case 03

The query violates its result contract: removes null values and output records before selecting last.

Analytical processing◈ Members↗
FA-2539

Partition last value: Removes NULL values and output records before selecting last · case 04

The query violates its result contract: removes null values and output records before selecting last.

Analytical processing◈ Members↗
FA-2540

Partition last value: Removes NULL values and output records before selecting last · case 05

The query violates its result contract: removes null values and output records before selecting last.

Analytical processing◈ Members↗
FA-2541

Top two per key: Uses rank and returns more than two rows when tied · case 01

The query violates its result contract: uses rank and returns more than two rows when tied.

Analytical processing● Open access↗
FA-2542

Top two per key: Uses rank and returns more than two rows when tied · case 02

The query violates its result contract: uses rank and returns more than two rows when tied.

Analytical processing◈ Members↗
FA-2543

Top two per key: Uses rank and returns more than two rows when tied · case 03

The query violates its result contract: uses rank and returns more than two rows when tied.

Analytical processing◈ Members↗
FA-2544

Top two per key: Uses rank and returns more than two rows when tied · case 04

The query violates its result contract: uses rank and returns more than two rows when tied.

Analytical processing◈ Members↗
FA-2545

Top two per key: Uses rank and returns more than two rows when tied · case 05

The query violates its result contract: uses rank and returns more than two rows when tied.

Analytical processing◈ Members↗
FA-2546

Top two per key: Applies one shared quota to all keys · case 01

The query violates its result contract: applies one shared quota to all keys.

Analytical processing● Open access↗
FA-2547

Top two per key: Applies one shared quota to all keys · case 02

The query violates its result contract: applies one shared quota to all keys.

Analytical processing◈ Members↗
FA-2548

Top two per key: Applies one shared quota to all keys · case 03

The query violates its result contract: applies one shared quota to all keys.

Analytical processing◈ Members↗
FA-2549

Top two per key: Applies one shared quota to all keys · case 04

The query violates its result contract: applies one shared quota to all keys.

Analytical processing◈ Members↗
FA-2550

Top two per key: Applies one shared quota to all keys · case 05

The query violates its result contract: applies one shared quota to all keys.

Analytical processing◈ Members↗
FA-2551

Top two per key: Selects smallest measurements instead of greatest · case 01

The query violates its result contract: selects smallest measurements instead of greatest.

Analytical processing● Open access↗
FA-2552

Top two per key: Selects smallest measurements instead of greatest · case 02

The query violates its result contract: selects smallest measurements instead of greatest.

Analytical processing◈ Members↗
FA-2553

Top two per key: Selects smallest measurements instead of greatest · case 03

The query violates its result contract: selects smallest measurements instead of greatest.

Analytical processing◈ Members↗
FA-2554

Top two per key: Selects smallest measurements instead of greatest · case 04

The query violates its result contract: selects smallest measurements instead of greatest.

Analytical processing◈ Members↗
FA-2555

Top two per key: Selects smallest measurements instead of greatest · case 05

The query violates its result contract: selects smallest measurements instead of greatest.

Analytical processing◈ Members↗
FA-2556

Top two per key: Returns only one row due to a strict comparison · case 01

The query violates its result contract: returns only one row due to a strict comparison.

Analytical processing● Open access↗
FA-2557

Top two per key: Returns only one row due to a strict comparison · case 02

The query violates its result contract: returns only one row due to a strict comparison.

Analytical processing◈ Members↗
FA-2558

Top two per key: Returns only one row due to a strict comparison · case 03

The query violates its result contract: returns only one row due to a strict comparison.

Analytical processing◈ Members↗
FA-2559

Top two per key: Returns only one row due to a strict comparison · case 04

The query violates its result contract: returns only one row due to a strict comparison.

Analytical processing◈ Members↗
FA-2560

Top two per key: Returns only one row due to a strict comparison · case 05

The query violates its result contract: returns only one row due to a strict comparison.

Analytical processing◈ Members↗
FA-2561

Top two per key: Uses greatest ID when the quota cuts through a tie · case 01

The query violates its result contract: uses greatest id when the quota cuts through a tie.

Analytical processing● Open access↗
FA-2562

Top two per key: Uses greatest ID when the quota cuts through a tie · case 02

The query violates its result contract: uses greatest id when the quota cuts through a tie.

Analytical processing◈ Members↗
FA-2563

Top two per key: Uses greatest ID when the quota cuts through a tie · case 03

The query violates its result contract: uses greatest id when the quota cuts through a tie.

Analytical processing◈ Members↗
FA-2564

Top two per key: Uses greatest ID when the quota cuts through a tie · case 04

The query violates its result contract: uses greatest id when the quota cuts through a tie.

Analytical processing◈ Members↗
FA-2565

Top two per key: Uses greatest ID when the quota cuts through a tie · case 05

The query violates its result contract: uses greatest id when the quota cuts through a tie.

Analytical processing◈ Members↗
FA-2566

Rolling three: Retains only one predecessor · case 01

The query violates its result contract: retains only one predecessor.

Analytical processing● Open access↗
FA-2567

Rolling three: Retains only one predecessor · case 02

The query violates its result contract: retains only one predecessor.

Analytical processing◈ Members↗
FA-2568

Rolling three: Retains only one predecessor · case 03

The query violates its result contract: retains only one predecessor.

Analytical processing◈ Members↗
FA-2569

Rolling three: Retains only one predecessor · case 04

The query violates its result contract: retains only one predecessor.

Analytical processing◈ Members↗
FA-2570

Rolling three: Retains only one predecessor · case 05

The query violates its result contract: retains only one predecessor.

Analytical processing◈ Members↗
FA-2571

Rolling three: Includes one extra predecessor · case 01

The query violates its result contract: includes one extra predecessor.

Analytical processing● Open access↗
FA-2572

Rolling three: Includes one extra predecessor · case 02

The query violates its result contract: includes one extra predecessor.

Analytical processing◈ Members↗
FA-2573

Rolling three: Includes one extra predecessor · case 03

The query violates its result contract: includes one extra predecessor.

Analytical processing◈ Members↗
FA-2574

Rolling three: Includes one extra predecessor · case 04

The query violates its result contract: includes one extra predecessor.

Analytical processing◈ Members↗
FA-2575

Rolling three: Includes one extra predecessor · case 05

The query violates its result contract: includes one extra predecessor.

Analytical processing◈ Members↗
FA-2576

Rolling three: Uses one future row instead of two past rows · case 01

The query violates its result contract: uses one future row instead of two past rows.

Analytical processing● Open access↗
FA-2577

Rolling three: Uses one future row instead of two past rows · case 02

The query violates its result contract: uses one future row instead of two past rows.

Analytical processing◈ Members↗
FA-2578

Rolling three: Uses one future row instead of two past rows · case 03

The query violates its result contract: uses one future row instead of two past rows.

Analytical processing◈ Members↗
FA-2579

Rolling three: Uses one future row instead of two past rows · case 04

The query violates its result contract: uses one future row instead of two past rows.

Analytical processing◈ Members↗
FA-2580

Rolling three: Uses one future row instead of two past rows · case 05

The query violates its result contract: uses one future row instead of two past rows.

Analytical processing◈ Members↗
FA-2581

Rolling three: Uses identity distance rather than physical row count · case 01

The query violates its result contract: uses identity distance rather than physical row count.

Analytical processing● Open access↗
FA-2582

Rolling three: Uses identity distance rather than physical row count · case 02

The query violates its result contract: uses identity distance rather than physical row count.

Analytical processing◈ Members↗
FA-2583

Rolling three: Uses identity distance rather than physical row count · case 03

The query violates its result contract: uses identity distance rather than physical row count.

Analytical processing◈ Members↗
FA-2584

Rolling three: Uses identity distance rather than physical row count · case 04

The query violates its result contract: uses identity distance rather than physical row count.

Analytical processing◈ Members↗
FA-2585

Rolling three: Uses identity distance rather than physical row count · case 05

The query violates its result contract: uses identity distance rather than physical row count.

Analytical processing◈ Members↗
FA-2586

Rolling three: Mixes key partitions in a rolling aggregate · case 01

The query violates its result contract: mixes key partitions in a rolling aggregate.

Analytical processing● Open access↗
FA-2587

Rolling three: Mixes key partitions in a rolling aggregate · case 02

The query violates its result contract: mixes key partitions in a rolling aggregate.

Analytical processing◈ Members↗
FA-2588

Rolling three: Mixes key partitions in a rolling aggregate · case 03

The query violates its result contract: mixes key partitions in a rolling aggregate.

Analytical processing◈ Members↗
FA-2589

Rolling three: Mixes key partitions in a rolling aggregate · case 04

The query violates its result contract: mixes key partitions in a rolling aggregate.

Analytical processing◈ Members↗
FA-2590

Rolling three: Mixes key partitions in a rolling aggregate · case 05

The query violates its result contract: mixes key partitions in a rolling aggregate.

Analytical processing◈ Members↗
FA-2591

Unique index conflicts: Reports repeated NULLs as unique-index violations · case 01

The query violates its result contract: reports repeated nulls as unique-index violations.

Indexing● Open access↗
FA-2592

Unique index conflicts: Reports repeated NULLs as unique-index violations · case 02

The query violates its result contract: reports repeated nulls as unique-index violations.

Indexing◈ Members↗
FA-2593

Unique index conflicts: Reports repeated NULLs as unique-index violations · case 03

The query violates its result contract: reports repeated nulls as unique-index violations.

Indexing◈ Members↗
FA-2594

Unique index conflicts: Reports repeated NULLs as unique-index violations · case 04

The query violates its result contract: reports repeated nulls as unique-index violations.

Indexing◈ Members↗
FA-2595

Unique index conflicts: Reports repeated NULLs as unique-index violations · case 05

The query violates its result contract: reports repeated nulls as unique-index violations.

Indexing◈ Members↗
FA-2596

Unique index conflicts: Counts only rows with known payload while checking key uniqueness · case 01

The query violates its result contract: counts only rows with known payload while checking key uniqueness.

Indexing● Open access↗
FA-2597

Unique index conflicts: Counts only rows with known payload while checking key uniqueness · case 02

The query violates its result contract: counts only rows with known payload while checking key uniqueness.

Indexing◈ Members↗
FA-2598

Unique index conflicts: Counts only rows with known payload while checking key uniqueness · case 03

The query violates its result contract: counts only rows with known payload while checking key uniqueness.

Indexing◈ Members↗
FA-2599

Unique index conflicts: Counts only rows with known payload while checking key uniqueness · case 04

The query violates its result contract: counts only rows with known payload while checking key uniqueness.

Indexing◈ Members↗
FA-2600

Unique index conflicts: Counts only rows with known payload while checking key uniqueness · case 05

The query violates its result contract: counts only rows with known payload while checking key uniqueness.

Indexing◈ 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 ↗