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

Group total filter: Tests for one positive member instead of positive total · case 01

The query violates its result contract: tests for one positive member instead of positive total.

Analytical processing● Open access↗
FA-2202

Group total filter: Tests for one positive member instead of positive total · case 02

The query violates its result contract: tests for one positive member instead of positive total.

Analytical processing◈ Members↗
FA-2203

Group total filter: Tests for one positive member instead of positive total · case 03

The query violates its result contract: tests for one positive member instead of positive total.

Analytical processing◈ Members↗
FA-2204

Group total filter: Tests for one positive member instead of positive total · case 04

The query violates its result contract: tests for one positive member instead of positive total.

Analytical processing◈ Members↗
FA-2205

Group total filter: Tests for one positive member instead of positive total · case 05

The query violates its result contract: tests for one positive member instead of positive total.

Analytical processing◈ Members↗
FA-2206

Group total filter: Requires every known measurement to be positive · case 01

The query violates its result contract: requires every known measurement to be positive.

Analytical processing● Open access↗
FA-2207

Group total filter: Requires every known measurement to be positive · case 02

The query violates its result contract: requires every known measurement to be positive.

Analytical processing◈ Members↗
FA-2208

Group total filter: Requires every known measurement to be positive · case 03

The query violates its result contract: requires every known measurement to be positive.

Analytical processing◈ Members↗
FA-2209

Group total filter: Requires every known measurement to be positive · case 04

The query violates its result contract: requires every known measurement to be positive.

Analytical processing◈ Members↗
FA-2210

Group total filter: Requires every known measurement to be positive · case 05

The query violates its result contract: requires every known measurement to be positive.

Analytical processing◈ Members↗
FA-2211

Group total filter: Filters using the sum of unique amounts · case 01

The query violates its result contract: filters using the sum of unique amounts.

Analytical processing● Open access↗
FA-2212

Group total filter: Filters using the sum of unique amounts · case 02

The query violates its result contract: filters using the sum of unique amounts.

Analytical processing◈ Members↗
FA-2213

Group total filter: Filters using the sum of unique amounts · case 03

The query violates its result contract: filters using the sum of unique amounts.

Analytical processing◈ Members↗
FA-2214

Group total filter: Filters using the sum of unique amounts · case 04

The query violates its result contract: filters using the sum of unique amounts.

Analytical processing◈ Members↗
FA-2215

Group total filter: Filters using the sum of unique amounts · case 05

The query violates its result contract: filters using the sum of unique amounts.

Analytical processing◈ Members↗
FA-2216

Distinct known count: Counts occurrences instead of distinct observations · case 01

The query violates its result contract: counts occurrences instead of distinct observations.

Analytical processing● Open access↗
FA-2217

Distinct known count: Counts occurrences instead of distinct observations · case 02

The query violates its result contract: counts occurrences instead of distinct observations.

Analytical processing◈ Members↗
FA-2218

Distinct known count: Counts occurrences instead of distinct observations · case 03

The query violates its result contract: counts occurrences instead of distinct observations.

Analytical processing◈ Members↗
FA-2219

Distinct known count: Counts occurrences instead of distinct observations · case 04

The query violates its result contract: counts occurrences instead of distinct observations.

Analytical processing◈ Members↗
FA-2220

Distinct known count: Counts occurrences instead of distinct observations · case 05

The query violates its result contract: counts occurrences instead of distinct observations.

Analytical processing◈ Members↗
FA-2221

Distinct known count: Includes NULL as one distinct measured value · case 01

The query violates its result contract: includes null as one distinct measured value.

Analytical processing● Open access↗
FA-2222

Distinct known count: Includes NULL as one distinct measured value · case 02

The query violates its result contract: includes null as one distinct measured value.

Analytical processing◈ Members↗
FA-2223

Distinct known count: Includes NULL as one distinct measured value · case 03

The query violates its result contract: includes null as one distinct measured value.

Analytical processing◈ Members↗
FA-2224

Distinct known count: Includes NULL as one distinct measured value · case 04

The query violates its result contract: includes null as one distinct measured value.

Analytical processing◈ Members↗
FA-2225

Distinct known count: Includes NULL as one distinct measured value · case 05

The query violates its result contract: includes null as one distinct measured value.

Analytical processing◈ Members↗
FA-2226

Distinct known count: Counts distinct keys instead of measurements · case 01

The query violates its result contract: counts distinct keys instead of measurements.

Analytical processing● Open access↗
FA-2227

Distinct known count: Counts distinct keys instead of measurements · case 02

The query violates its result contract: counts distinct keys instead of measurements.

Analytical processing◈ Members↗
FA-2228

Distinct known count: Counts distinct keys instead of measurements · case 03

The query violates its result contract: counts distinct keys instead of measurements.

Analytical processing◈ Members↗
FA-2229

Distinct known count: Counts distinct keys instead of measurements · case 04

The query violates its result contract: counts distinct keys instead of measurements.

Analytical processing◈ Members↗
FA-2230

Distinct known count: Counts distinct keys instead of measurements · case 05

The query violates its result contract: counts distinct keys instead of measurements.

Analytical processing◈ Members↗
FA-2231

Distinct known count: Introduces zero when only NULL is present · case 01

The query violates its result contract: introduces zero when only null is present.

Analytical processing● Open access↗
FA-2232

Distinct known count: Introduces zero when only NULL is present · case 02

The query violates its result contract: introduces zero when only null is present.

Analytical processing◈ Members↗
FA-2233

Distinct known count: Introduces zero when only NULL is present · case 03

The query violates its result contract: introduces zero when only null is present.

Analytical processing◈ Members↗
FA-2234

Distinct known count: Introduces zero when only NULL is present · case 04

The query violates its result contract: introduces zero when only null is present.

Analytical processing◈ Members↗
FA-2235

Distinct known count: Introduces zero when only NULL is present · case 05

The query violates its result contract: introduces zero when only null is present.

Analytical processing◈ Members↗
FA-2236

Distinct known count: Drops nonpositive known values · case 01

The query violates its result contract: drops nonpositive known values.

Analytical processing● Open access↗
FA-2237

Distinct known count: Drops nonpositive known values · case 02

The query violates its result contract: drops nonpositive known values.

Analytical processing◈ Members↗
FA-2238

Distinct known count: Drops nonpositive known values · case 03

The query violates its result contract: drops nonpositive known values.

Analytical processing◈ Members↗
FA-2239

Distinct known count: Drops nonpositive known values · case 04

The query violates its result contract: drops nonpositive known values.

Analytical processing◈ Members↗
FA-2240

Distinct known count: Drops nonpositive known values · case 05

The query violates its result contract: drops nonpositive known values.

Analytical processing◈ Members↗
FA-2241

Left join count: Counts the NULL-padded outer row as a match · case 01

The query violates its result contract: counts the null-padded outer row as a match.

Storage and queries● Open access↗
FA-2242

Left join count: Counts the NULL-padded outer row as a match · case 02

The query violates its result contract: counts the null-padded outer row as a match.

Storage and queries◈ Members↗
FA-2243

Left join count: Counts the NULL-padded outer row as a match · case 03

The query violates its result contract: counts the null-padded outer row as a match.

Storage and queries◈ Members↗
FA-2244

Left join count: Counts the NULL-padded outer row as a match · case 04

The query violates its result contract: counts the null-padded outer row as a match.

Storage and queries◈ Members↗
FA-2245

Left join count: Counts the NULL-padded outer row as a match · case 05

The query violates its result contract: counts the null-padded outer row as a match.

Storage and queries◈ Members↗
FA-2246

Left join count: Does not count matches with NULL payloads · case 01

The query violates its result contract: does not count matches with null payloads.

Storage and queries● Open access↗
FA-2247

Left join count: Does not count matches with NULL payloads · case 02

The query violates its result contract: does not count matches with null payloads.

Storage and queries◈ Members↗
FA-2248

Left join count: Does not count matches with NULL payloads · case 03

The query violates its result contract: does not count matches with null payloads.

Storage and queries◈ Members↗
FA-2249

Left join count: Does not count matches with NULL payloads · case 04

The query violates its result contract: does not count matches with null payloads.

Storage and queries◈ Members↗
FA-2250

Left join count: Does not count matches with NULL payloads · case 05

The query violates its result contract: does not count matches with null payloads.

Storage and queries◈ Members↗
FA-2251

Left join count: Collapses separate matches with equal values · case 01

The query violates its result contract: collapses separate matches with equal values.

Storage and queries● Open access↗
FA-2252

Left join count: Collapses separate matches with equal values · case 02

The query violates its result contract: collapses separate matches with equal values.

Storage and queries◈ Members↗
FA-2253

Left join count: Collapses separate matches with equal values · case 03

The query violates its result contract: collapses separate matches with equal values.

Storage and queries◈ Members↗
FA-2254

Left join count: Collapses separate matches with equal values · case 04

The query violates its result contract: collapses separate matches with equal values.

Storage and queries◈ Members↗
FA-2255

Left join count: Collapses separate matches with equal values · case 05

The query violates its result contract: collapses separate matches with equal values.

Storage and queries◈ Members↗
FA-2256

Left join count: Drops left rows with zero matches · case 01

The query violates its result contract: drops left rows with zero matches.

Storage and queries● Open access↗
FA-2257

Left join count: Drops left rows with zero matches · case 02

The query violates its result contract: drops left rows with zero matches.

Storage and queries◈ Members↗
FA-2258

Left join count: Drops left rows with zero matches · case 03

The query violates its result contract: drops left rows with zero matches.

Storage and queries◈ Members↗
FA-2259

Left join count: Drops left rows with zero matches · case 04

The query violates its result contract: drops left rows with zero matches.

Storage and queries◈ Members↗
FA-2260

Left join count: Drops left rows with zero matches · case 05

The query violates its result contract: drops left rows with zero matches.

Storage and queries◈ Members↗
FA-2261

Left join count: Combines separate left identities sharing a key · case 01

The query violates its result contract: combines separate left identities sharing a key.

Storage and queries● Open access↗
FA-2262

Left join count: Combines separate left identities sharing a key · case 02

The query violates its result contract: combines separate left identities sharing a key.

Storage and queries◈ Members↗
FA-2263

Left join count: Combines separate left identities sharing a key · case 03

The query violates its result contract: combines separate left identities sharing a key.

Storage and queries◈ Members↗
FA-2264

Left join count: Combines separate left identities sharing a key · case 04

The query violates its result contract: combines separate left identities sharing a key.

Storage and queries◈ Members↗
FA-2265

Left join count: Combines separate left identities sharing a key · case 05

The query violates its result contract: combines separate left identities sharing a key.

Storage and queries◈ Members↗
FA-2266

Correlated maximum: Omits the correlation predicate · case 01

The query violates its result contract: omits the correlation predicate.

Storage and queries● Open access↗
FA-2267

Correlated maximum: Omits the correlation predicate · case 02

The query violates its result contract: omits the correlation predicate.

Storage and queries◈ Members↗
FA-2268

Correlated maximum: Omits the correlation predicate · case 03

The query violates its result contract: omits the correlation predicate.

Storage and queries◈ Members↗
FA-2269

Correlated maximum: Omits the correlation predicate · case 04

The query violates its result contract: omits the correlation predicate.

Storage and queries◈ Members↗
FA-2270

Correlated maximum: Omits the correlation predicate · case 05

The query violates its result contract: omits the correlation predicate.

Storage and queries◈ Members↗
FA-2271

Correlated maximum: Searches the source table instead of the reference table · case 01

The query violates its result contract: searches the source table instead of the reference table.

Storage and queries● Open access↗
FA-2272

Correlated maximum: Searches the source table instead of the reference table · case 02

The query violates its result contract: searches the source table instead of the reference table.

Storage and queries◈ Members↗
FA-2273

Correlated maximum: Searches the source table instead of the reference table · case 03

The query violates its result contract: searches the source table instead of the reference table.

Storage and queries◈ Members↗
FA-2274

Correlated maximum: Searches the source table instead of the reference table · case 04

The query violates its result contract: searches the source table instead of the reference table.

Storage and queries◈ Members↗
FA-2275

Correlated maximum: Searches the source table instead of the reference table · case 05

The query violates its result contract: searches the source table instead of the reference table.

Storage and queries◈ Members↗
FA-2276

Correlated maximum: Selects the minimum reference value · case 01

The query violates its result contract: selects the minimum reference value.

Storage and queries● Open access↗
FA-2277

Correlated maximum: Selects the minimum reference value · case 02

The query violates its result contract: selects the minimum reference value.

Storage and queries◈ Members↗
FA-2278

Correlated maximum: Selects the minimum reference value · case 03

The query violates its result contract: selects the minimum reference value.

Storage and queries◈ Members↗
FA-2279

Correlated maximum: Selects the minimum reference value · case 04

The query violates its result contract: selects the minimum reference value.

Storage and queries◈ Members↗
FA-2280

Correlated maximum: Selects the minimum reference value · case 05

The query violates its result contract: selects the minimum reference value.

Storage and queries◈ Members↗
FA-2281

Correlated maximum: Matches any reference value rather than the maximum · case 01

The query violates its result contract: matches any reference value rather than the maximum.

Storage and queries● Open access↗
FA-2282

Correlated maximum: Matches any reference value rather than the maximum · case 02

The query violates its result contract: matches any reference value rather than the maximum.

Storage and queries◈ Members↗
FA-2283

Correlated maximum: Matches any reference value rather than the maximum · case 03

The query violates its result contract: matches any reference value rather than the maximum.

Storage and queries◈ Members↗
FA-2284

Correlated maximum: Matches any reference value rather than the maximum · case 04

The query violates its result contract: matches any reference value rather than the maximum.

Storage and queries◈ Members↗
FA-2285

Correlated maximum: Matches any reference value rather than the maximum · case 05

The query violates its result contract: matches any reference value rather than the maximum.

Storage and queries◈ Members↗
FA-2286

Correlated maximum: Treats missing maximum and missing measurement as equal · case 01

The query violates its result contract: treats missing maximum and missing measurement as equal.

Storage and queries● Open access↗
FA-2287

Correlated maximum: Treats missing maximum and missing measurement as equal · case 02

The query violates its result contract: treats missing maximum and missing measurement as equal.

Storage and queries◈ Members↗
FA-2288

Correlated maximum: Treats missing maximum and missing measurement as equal · case 03

The query violates its result contract: treats missing maximum and missing measurement as equal.

Storage and queries◈ Members↗
FA-2289

Correlated maximum: Treats missing maximum and missing measurement as equal · case 04

The query violates its result contract: treats missing maximum and missing measurement as equal.

Storage and queries◈ Members↗
FA-2290

Correlated maximum: Treats missing maximum and missing measurement as equal · case 05

The query violates its result contract: treats missing maximum and missing measurement as equal.

Storage and queries◈ Members↗
FA-2291

All reference values: Accepts one smaller reference despite a larger blocker · case 01

The query violates its result contract: accepts one smaller reference despite a larger blocker.

Relational algebra● Open access↗
FA-2292

All reference values: Accepts one smaller reference despite a larger blocker · case 02

The query violates its result contract: accepts one smaller reference despite a larger blocker.

Relational algebra◈ Members↗
FA-2293

All reference values: Accepts one smaller reference despite a larger blocker · case 03

The query violates its result contract: accepts one smaller reference despite a larger blocker.

Relational algebra◈ Members↗
FA-2294

All reference values: Accepts one smaller reference despite a larger blocker · case 04

The query violates its result contract: accepts one smaller reference despite a larger blocker.

Relational algebra◈ Members↗
FA-2295

All reference values: Accepts one smaller reference despite a larger blocker · case 05

The query violates its result contract: accepts one smaller reference despite a larger blocker.

Relational algebra◈ Members↗
FA-2296

All reference values: A scalar MAX comparison loses vacuous truth on empty reference sets · case 01

The query violates its result contract: a scalar max comparison loses vacuous truth on empty reference sets.

Relational algebra● Open access↗
FA-2297

All reference values: A scalar MAX comparison loses vacuous truth on empty reference sets · case 02

The query violates its result contract: a scalar max comparison loses vacuous truth on empty reference sets.

Relational algebra◈ Members↗
FA-2298

All reference values: A scalar MAX comparison loses vacuous truth on empty reference sets · case 03

The query violates its result contract: a scalar max comparison loses vacuous truth on empty reference sets.

Relational algebra◈ Members↗
FA-2299

All reference values: A scalar MAX comparison loses vacuous truth on empty reference sets · case 04

The query violates its result contract: a scalar max comparison loses vacuous truth on empty reference sets.

Relational algebra◈ Members↗
FA-2300

All reference values: A scalar MAX comparison loses vacuous truth on empty reference sets · case 05

The query violates its result contract: a scalar max comparison loses vacuous truth on empty reference sets.

Relational algebra◈ 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 ↗