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 ↗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
Frequency left quantile: An exact cumulative rank boundary advances to the next support value. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: An exact cumulative rank boundary advances to the next support value. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: An exact cumulative rank boundary advances to the next support value. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: An exact cumulative rank boundary advances to the next support value. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: An exact cumulative rank boundary advances to the next support value. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rank target uses the number of compressed rows. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rank target uses the number of compressed rows. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rank target uses the number of compressed rows. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rank target uses the number of compressed rows. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rank target uses the number of compressed rows. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Cumulative mass increments by one per row. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Cumulative mass increments by one per row. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Cumulative mass increments by one per row. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Cumulative mass increments by one per row. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Cumulative mass increments by one per row. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Zero-frequency rows can satisfy the zero-percentile query. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Zero-frequency rows can satisfy the zero-percentile query. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Zero-frequency rows can satisfy the zero-percentile query. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Zero-frequency rows can satisfy the zero-percentile query. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Zero-frequency rows can satisfy the zero-percentile query. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Support values are sorted descending for a lower-tail quantile. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Support values are sorted descending for a lower-tail quantile. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Support values are sorted descending for a lower-tail quantile. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Support values are sorted descending for a lower-tail quantile. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: Support values are sorted descending for a lower-tail quantile. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rational target is rounded down before cumulative comparison. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rational target is rounded down before cumulative comparison. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rational target is rounded down before cumulative comparison. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rational target is rounded down before cumulative comparison. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The rational target is rounded down before cumulative comparison. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The current row is checked before adding its own frequency. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The current row is checked before adding its own frequency. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The current row is checked before adding its own frequency. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The current row is checked before adding its own frequency. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency left quantile: The current row is checked before adding its own frequency. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Frequency affects the center but not the squared deviations. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Frequency affects the center but not the squared deviations. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Frequency affects the center but not the squared deviations. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Frequency affects the center but not the squared deviations. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Frequency affects the center but not the squared deviations. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Uncentered second moments replace centered scatter. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Uncentered second moments replace centered scatter. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Uncentered second moments replace centered scatter. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Uncentered second moments replace centered scatter. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Uncentered second moments replace centered scatter. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Squared deviations are normalized even though the summary stores total scatter. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Squared deviations are normalized even though the summary stores total scatter. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Squared deviations are normalized even though the summary stores total scatter. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Squared deviations are normalized even though the summary stores total scatter. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Squared deviations are normalized even though the summary stores total scatter. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: The rational center is truncated before residual reduction. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: The rational center is truncated before residual reduction. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: The rational center is truncated before residual reduction. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: The rational center is truncated before residual reduction. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: The rational center is truncated before residual reduction. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Absolute deviations are substituted for squared deviations. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Absolute deviations are substituted for squared deviations. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Absolute deviations are substituted for squared deviations. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Absolute deviations are substituted for squared deviations. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Absolute deviations are substituted for squared deviations. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Equal-frequency observations are collapsed by their weight. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Equal-frequency observations are collapsed by their weight. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Equal-frequency observations are collapsed by their weight. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Equal-frequency observations are collapsed by their weight. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Equal-frequency observations are collapsed by their weight. · case 05
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Only the most deviant support point contributes to scatter. · case 01
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Only the most deviant support point contributes to scatter. · case 02
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Only the most deviant support point contributes to scatter. · case 03
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Only the most deviant support point contributes to scatter. · case 04
The reduction disagrees with its explicit aggregation oracle.
Frequency central scatter: Only the most deviant support point contributes to scatter. · case 05
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The best interval spanning a block boundary is never considered. · case 01
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The best interval spanning a block boundary is never considered. · case 02
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The best interval spanning a block boundary is never considered. · case 03
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The best interval spanning a block boundary is never considered. · case 04
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The best interval spanning a block boundary is never considered. · case 05
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The crossing candidate combines the old prefix with incoming suffix. · case 01
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The crossing candidate combines the old prefix with incoming suffix. · case 02
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The crossing candidate combines the old prefix with incoming suffix. · case 03
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The crossing candidate combines the old prefix with incoming suffix. · case 04
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The crossing candidate combines the old prefix with incoming suffix. · case 05
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a prefix uses the old suffix instead of the whole old total. · case 01
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a prefix uses the old suffix instead of the whole old total. · case 02
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a prefix uses the old suffix instead of the whole old total. · case 03
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a prefix uses the old suffix instead of the whole old total. · case 04
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a prefix uses the old suffix instead of the whole old total. · case 05
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a suffix adds incoming prefix instead of its entire total. · case 01
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a suffix adds incoming prefix instead of its entire total. · case 02
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a suffix adds incoming prefix instead of its entire total. · case 03
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a suffix adds incoming prefix instead of its entire total. · case 04
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: Extending a suffix adds incoming prefix instead of its entire total. · case 05
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The incoming local prefix is treated as a global prefix. · case 01
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The incoming local prefix is treated as a global prefix. · case 02
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The incoming local prefix is treated as a global prefix. · case 03
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The incoming local prefix is treated as a global prefix. · case 04
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The incoming local prefix is treated as a global prefix. · case 05
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The accumulated local suffix is retained without crossing the incoming block. · case 01
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The accumulated local suffix is retained without crossing the incoming block. · case 02
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The accumulated local suffix is retained without crossing the incoming block. · case 03
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The accumulated local suffix is retained without crossing the incoming block. · case 04
The reduction disagrees with its explicit aggregation oracle.
Maximum subarray block summary: The accumulated local suffix is retained without crossing the incoming block. · case 05
The reduction disagrees with its explicit aggregation oracle.
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 ↗