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

Release retention selection: A zero retention count keeps historical releases · case 01

A zero retention count keeps historical releases.

Deployment models● Open access↗
FA-10202

Release retention selection: A zero retention count keeps historical releases · case 02

A zero retention count keeps historical releases.

Deployment models◈ Members↗
FA-10203

Release retention selection: A zero retention count keeps historical releases · case 03

A zero retention count keeps historical releases.

Deployment models◈ Members↗
FA-10204

Release retention selection: A zero retention count keeps historical releases · case 04

A zero retention count keeps historical releases.

Deployment models◈ Members↗
FA-10205

Release retention selection: A zero retention count keeps historical releases · case 05

A zero retention count keeps historical releases.

Deployment models◈ Members↗
FA-10206

Environment promotion plan: Unknown environments are silently created · case 01

Unknown environments are silently created.

Deployment models● Open access↗
FA-10207

Environment promotion plan: Unknown environments are silently created · case 02

Unknown environments are silently created.

Deployment models◈ Members↗
FA-10208

Environment promotion plan: Unknown environments are silently created · case 03

Unknown environments are silently created.

Deployment models◈ Members↗
FA-10209

Environment promotion plan: Unknown environments are silently created · case 04

Unknown environments are silently created.

Deployment models◈ Members↗
FA-10210

Environment promotion plan: Unknown environments are silently created · case 05

Unknown environments are silently created.

Deployment models◈ Members↗
FA-10211

Environment promotion plan: Downgrades ignore the explicit policy · case 01

Downgrades ignore the explicit policy.

Deployment models● Open access↗
FA-10212

Environment promotion plan: Downgrades ignore the explicit policy · case 02

Downgrades ignore the explicit policy.

Deployment models◈ Members↗
FA-10213

Environment promotion plan: Downgrades ignore the explicit policy · case 03

Downgrades ignore the explicit policy.

Deployment models◈ Members↗
FA-10214

Environment promotion plan: Downgrades ignore the explicit policy · case 04

Downgrades ignore the explicit policy.

Deployment models◈ Members↗
FA-10215

Environment promotion plan: Downgrades ignore the explicit policy · case 05

Downgrades ignore the explicit policy.

Deployment models◈ Members↗
FA-10216

Environment promotion plan: Identical artifacts require redundant promotion · case 01

Identical artifacts require redundant promotion.

Deployment models● Open access↗
FA-10217

Environment promotion plan: Identical artifacts require redundant promotion · case 02

Identical artifacts require redundant promotion.

Deployment models◈ Members↗
FA-10218

Environment promotion plan: Identical artifacts require redundant promotion · case 03

Identical artifacts require redundant promotion.

Deployment models◈ Members↗
FA-10219

Environment promotion plan: Identical artifacts require redundant promotion · case 04

Identical artifacts require redundant promotion.

Deployment models◈ Members↗
FA-10220

Environment promotion plan: Identical artifacts require redundant promotion · case 05

Identical artifacts require redundant promotion.

Deployment models◈ Members↗
FA-10221

Environment promotion plan: Untested artifacts reach the target · case 01

Untested artifacts reach the target.

Deployment models● Open access↗
FA-10222

Environment promotion plan: Untested artifacts reach the target · case 02

Untested artifacts reach the target.

Deployment models◈ Members↗
FA-10223

Environment promotion plan: Untested artifacts reach the target · case 03

Untested artifacts reach the target.

Deployment models◈ Members↗
FA-10224

Environment promotion plan: Untested artifacts reach the target · case 04

Untested artifacts reach the target.

Deployment models◈ Members↗
FA-10225

Environment promotion plan: Untested artifacts reach the target · case 05

Untested artifacts reach the target.

Deployment models◈ Members↗
FA-10226

Environment promotion plan: Promotion erases unrelated environments · case 01

Promotion erases unrelated environments.

Deployment models● Open access↗
FA-10227

Environment promotion plan: Promotion erases unrelated environments · case 02

Promotion erases unrelated environments.

Deployment models◈ Members↗
FA-10228

Environment promotion plan: Promotion erases unrelated environments · case 03

Promotion erases unrelated environments.

Deployment models◈ Members↗
FA-10229

Environment promotion plan: Promotion erases unrelated environments · case 04

Promotion erases unrelated environments.

Deployment models◈ Members↗
FA-10230

Environment promotion plan: Promotion erases unrelated environments · case 05

Promotion erases unrelated environments.

Deployment models◈ Members↗
FA-10231

Deployment resource cleanup eligibility: Desired resources are selected for deletion · case 01

Desired resources are selected for deletion.

Deployment models● Open access↗
FA-10232

Deployment resource cleanup eligibility: Desired resources are selected for deletion · case 02

Desired resources are selected for deletion.

Deployment models◈ Members↗
FA-10233

Deployment resource cleanup eligibility: Desired resources are selected for deletion · case 03

Desired resources are selected for deletion.

Deployment models◈ Members↗
FA-10234

Deployment resource cleanup eligibility: Desired resources are selected for deletion · case 04

Desired resources are selected for deletion.

Deployment models◈ Members↗
FA-10235

Deployment resource cleanup eligibility: Desired resources are selected for deletion · case 05

Desired resources are selected for deletion.

Deployment models◈ Members↗
FA-10236

Deployment resource cleanup eligibility: Another deployment’s resources are deleted · case 01

Another deployment’s resources are deleted.

Deployment models● Open access↗
FA-10237

Deployment resource cleanup eligibility: Another deployment’s resources are deleted · case 02

Another deployment’s resources are deleted.

Deployment models◈ Members↗
FA-10238

Deployment resource cleanup eligibility: Another deployment’s resources are deleted · case 03

Another deployment’s resources are deleted.

Deployment models◈ Members↗
FA-10239

Deployment resource cleanup eligibility: Another deployment’s resources are deleted · case 04

Another deployment’s resources are deleted.

Deployment models◈ Members↗
FA-10240

Deployment resource cleanup eligibility: Another deployment’s resources are deleted · case 05

Another deployment’s resources are deleted.

Deployment models◈ Members↗
FA-10241

Deployment resource cleanup eligibility: Protected resources are deleted · case 01

Protected resources are deleted.

Deployment models● Open access↗
FA-10242

Deployment resource cleanup eligibility: Protected resources are deleted · case 02

Protected resources are deleted.

Deployment models◈ Members↗
FA-10243

Deployment resource cleanup eligibility: Protected resources are deleted · case 03

Protected resources are deleted.

Deployment models◈ Members↗
FA-10244

Deployment resource cleanup eligibility: Protected resources are deleted · case 04

Protected resources are deleted.

Deployment models◈ Members↗
FA-10245

Deployment resource cleanup eligibility: Protected resources are deleted · case 05

Protected resources are deleted.

Deployment models◈ Members↗
FA-10246

Deployment resource cleanup eligibility: Resources with active consumers are deleted · case 01

Resources with active consumers are deleted.

Deployment models● Open access↗
FA-10247

Deployment resource cleanup eligibility: Resources with active consumers are deleted · case 02

Resources with active consumers are deleted.

Deployment models◈ Members↗
FA-10248

Deployment resource cleanup eligibility: Resources with active consumers are deleted · case 03

Resources with active consumers are deleted.

Deployment models◈ Members↗
FA-10249

Deployment resource cleanup eligibility: Resources with active consumers are deleted · case 04

Resources with active consumers are deleted.

Deployment models◈ Members↗
FA-10250

Deployment resource cleanup eligibility: Resources with active consumers are deleted · case 05

Resources with active consumers are deleted.

Deployment models◈ Members↗
FA-10251

Deployment resource cleanup eligibility: Resources are deleted before their grace deadline · case 01

Resources are deleted before their grace deadline.

Deployment models● Open access↗
FA-10252

Deployment resource cleanup eligibility: Resources are deleted before their grace deadline · case 02

Resources are deleted before their grace deadline.

Deployment models◈ Members↗
FA-10253

Deployment resource cleanup eligibility: Resources are deleted before their grace deadline · case 03

Resources are deleted before their grace deadline.

Deployment models◈ Members↗
FA-10254

Deployment resource cleanup eligibility: Resources are deleted before their grace deadline · case 04

Resources are deleted before their grace deadline.

Deployment models◈ Members↗
FA-10255

Deployment resource cleanup eligibility: Resources are deleted before their grace deadline · case 05

Resources are deleted before their grace deadline.

Deployment models◈ Members↗
FA-10256

Metric series identity: Different instruments collide by omitting the metric name · case 01

Different instruments collide by omitting the metric name.

Observability● Open access↗
FA-10257

Metric series identity: Different instruments collide by omitting the metric name · case 02

Different instruments collide by omitting the metric name.

Observability◈ Members↗
FA-10258

Metric series identity: Different instruments collide by omitting the metric name · case 03

Different instruments collide by omitting the metric name.

Observability◈ Members↗
FA-10259

Metric series identity: Different instruments collide by omitting the metric name · case 04

Different instruments collide by omitting the metric name.

Observability◈ Members↗
FA-10260

Metric series identity: Different instruments collide by omitting the metric name · case 05

Different instruments collide by omitting the metric name.

Observability◈ Members↗
FA-10261

Metric series identity: Label insertion order fragments one series · case 01

Label insertion order fragments one series.

Observability● Open access↗
FA-10262

Metric series identity: Label insertion order fragments one series · case 02

Label insertion order fragments one series.

Observability◈ Members↗
FA-10263

Metric series identity: Label insertion order fragments one series · case 03

Label insertion order fragments one series.

Observability◈ Members↗
FA-10264

Metric series identity: Label insertion order fragments one series · case 04

Label insertion order fragments one series.

Observability◈ Members↗
FA-10265

Metric series identity: Label insertion order fragments one series · case 05

Label insertion order fragments one series.

Observability◈ Members↗
FA-10266

Metric series identity: Dropped high-cardinality labels remain in identity · case 01

Dropped high-cardinality labels remain in identity.

Observability● Open access↗
FA-10267

Metric series identity: Dropped high-cardinality labels remain in identity · case 02

Dropped high-cardinality labels remain in identity.

Observability◈ Members↗
FA-10268

Metric series identity: Dropped high-cardinality labels remain in identity · case 03

Dropped high-cardinality labels remain in identity.

Observability◈ Members↗
FA-10269

Metric series identity: Dropped high-cardinality labels remain in identity · case 04

Dropped high-cardinality labels remain in identity.

Observability◈ Members↗
FA-10270

Metric series identity: Dropped high-cardinality labels remain in identity · case 05

Dropped high-cardinality labels remain in identity.

Observability◈ Members↗
FA-10271

Metric series identity: Metrics using different units collide · case 01

Metrics using different units collide.

Observability● Open access↗
FA-10272

Metric series identity: Metrics using different units collide · case 02

Metrics using different units collide.

Observability◈ Members↗
FA-10273

Metric series identity: Metrics using different units collide · case 03

Metrics using different units collide.

Observability◈ Members↗
FA-10274

Metric series identity: Metrics using different units collide · case 04

Metrics using different units collide.

Observability◈ Members↗
FA-10275

Metric series identity: Metrics using different units collide · case 05

Metrics using different units collide.

Observability◈ Members↗
FA-10276

Metric series identity: Counter and gauge identities collide · case 01

Counter and gauge identities collide.

Observability● Open access↗
FA-10277

Metric series identity: Counter and gauge identities collide · case 02

Counter and gauge identities collide.

Observability◈ Members↗
FA-10278

Metric series identity: Counter and gauge identities collide · case 03

Counter and gauge identities collide.

Observability◈ Members↗
FA-10279

Metric series identity: Counter and gauge identities collide · case 04

Counter and gauge identities collide.

Observability◈ Members↗
FA-10280

Metric series identity: Counter and gauge identities collide · case 05

Counter and gauge identities collide.

Observability◈ Members↗
FA-10281

Structured log emission policy: Logs exactly at threshold disappear · case 01

Logs exactly at threshold disappear.

Observability● Open access↗
FA-10282

Structured log emission policy: Logs exactly at threshold disappear · case 02

Logs exactly at threshold disappear.

Observability◈ Members↗
FA-10283

Structured log emission policy: Logs exactly at threshold disappear · case 03

Logs exactly at threshold disappear.

Observability◈ Members↗
FA-10284

Structured log emission policy: Logs exactly at threshold disappear · case 04

Logs exactly at threshold disappear.

Observability◈ Members↗
FA-10285

Structured log emission policy: Logs exactly at threshold disappear · case 05

Logs exactly at threshold disappear.

Observability◈ Members↗
FA-10286

Structured log emission policy: Disabled loggers still emit events · case 01

Disabled loggers still emit events.

Observability● Open access↗
FA-10287

Structured log emission policy: Disabled loggers still emit events · case 02

Disabled loggers still emit events.

Observability◈ Members↗
FA-10288

Structured log emission policy: Disabled loggers still emit events · case 03

Disabled loggers still emit events.

Observability◈ Members↗
FA-10289

Structured log emission policy: Disabled loggers still emit events · case 04

Disabled loggers still emit events.

Observability◈ Members↗
FA-10290

Structured log emission policy: Disabled loggers still emit events · case 05

Disabled loggers still emit events.

Observability◈ Members↗
FA-10291

Structured log emission policy: Rejected samples still produce log records · case 01

Rejected samples still produce log records.

Observability● Open access↗
FA-10292

Structured log emission policy: Rejected samples still produce log records · case 02

Rejected samples still produce log records.

Observability◈ Members↗
FA-10293

Structured log emission policy: Rejected samples still produce log records · case 03

Rejected samples still produce log records.

Observability◈ Members↗
FA-10294

Structured log emission policy: Rejected samples still produce log records · case 04

Rejected samples still produce log records.

Observability◈ Members↗
FA-10295

Structured log emission policy: Rejected samples still produce log records · case 05

Rejected samples still produce log records.

Observability◈ Members↗
FA-10296

Structured log emission policy: Suppressed log records are exported · case 01

Suppressed log records are exported.

Observability● Open access↗
FA-10297

Structured log emission policy: Suppressed log records are exported · case 02

Suppressed log records are exported.

Observability◈ Members↗
FA-10298

Structured log emission policy: Suppressed log records are exported · case 03

Suppressed log records are exported.

Observability◈ Members↗
FA-10299

Structured log emission policy: Suppressed log records are exported · case 04

Suppressed log records are exported.

Observability◈ Members↗
FA-10300

Structured log emission policy: Suppressed log records are exported · case 05

Suppressed log records are exported.

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