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

Package publication plan: Private packages are published publicly · case 01

Private packages are published publicly.

Packaging● Open access↗
FA-10002

Package publication plan: Private packages are published publicly · case 02

Private packages are published publicly.

Packaging◈ Members↗
FA-10003

Package publication plan: Private packages are published publicly · case 03

Private packages are published publicly.

Packaging◈ Members↗
FA-10004

Package publication plan: Private packages are published publicly · case 04

Private packages are published publicly.

Packaging◈ Members↗
FA-10005

Package publication plan: Private packages are published publicly · case 05

Private packages are published publicly.

Packaging◈ Members↗
FA-10006

Distribution budget enforcement: A bundle exactly at its count limit is rejected · case 01

A bundle exactly at its count limit is rejected.

Packaging● Open access↗
FA-10007

Distribution budget enforcement: A bundle exactly at its count limit is rejected · case 02

A bundle exactly at its count limit is rejected.

Packaging◈ Members↗
FA-10008

Distribution budget enforcement: A bundle exactly at its count limit is rejected · case 03

A bundle exactly at its count limit is rejected.

Packaging◈ Members↗
FA-10009

Distribution budget enforcement: A bundle exactly at its count limit is rejected · case 04

A bundle exactly at its count limit is rejected.

Packaging◈ Members↗
FA-10010

Distribution budget enforcement: A bundle exactly at its count limit is rejected · case 05

A bundle exactly at its count limit is rejected.

Packaging◈ Members↗
FA-10011

Distribution budget enforcement: Total distribution bytes are not checked · case 01

Total distribution bytes are not checked.

Packaging● Open access↗
FA-10012

Distribution budget enforcement: Total distribution bytes are not checked · case 02

Total distribution bytes are not checked.

Packaging◈ Members↗
FA-10013

Distribution budget enforcement: Total distribution bytes are not checked · case 03

Total distribution bytes are not checked.

Packaging◈ Members↗
FA-10014

Distribution budget enforcement: Total distribution bytes are not checked · case 04

Total distribution bytes are not checked.

Packaging◈ Members↗
FA-10015

Distribution budget enforcement: Total distribution bytes are not checked · case 05

Total distribution bytes are not checked.

Packaging◈ Members↗
FA-10016

Distribution budget enforcement: Oversized individual files pass an aggregate-only budget · case 01

Oversized individual files pass an aggregate-only budget.

Packaging● Open access↗
FA-10017

Distribution budget enforcement: Oversized individual files pass an aggregate-only budget · case 02

Oversized individual files pass an aggregate-only budget.

Packaging◈ Members↗
FA-10018

Distribution budget enforcement: Oversized individual files pass an aggregate-only budget · case 03

Oversized individual files pass an aggregate-only budget.

Packaging◈ Members↗
FA-10019

Distribution budget enforcement: Oversized individual files pass an aggregate-only budget · case 04

Oversized individual files pass an aggregate-only budget.

Packaging◈ Members↗
FA-10020

Distribution budget enforcement: Oversized individual files pass an aggregate-only budget · case 05

Oversized individual files pass an aggregate-only budget.

Packaging◈ Members↗
FA-10021

Distribution budget enforcement: Forbidden file types enter the distribution · case 01

Forbidden file types enter the distribution.

Packaging● Open access↗
FA-10022

Distribution budget enforcement: Forbidden file types enter the distribution · case 02

Forbidden file types enter the distribution.

Packaging◈ Members↗
FA-10023

Distribution budget enforcement: Forbidden file types enter the distribution · case 03

Forbidden file types enter the distribution.

Packaging◈ Members↗
FA-10024

Distribution budget enforcement: Forbidden file types enter the distribution · case 04

Forbidden file types enter the distribution.

Packaging◈ Members↗
FA-10025

Distribution budget enforcement: Forbidden file types enter the distribution · case 05

Forbidden file types enter the distribution.

Packaging◈ Members↗
FA-10026

Distribution budget enforcement: Mandatory package files may be absent · case 01

Mandatory package files may be absent.

Packaging● Open access↗
FA-10027

Distribution budget enforcement: Mandatory package files may be absent · case 02

Mandatory package files may be absent.

Packaging◈ Members↗
FA-10028

Distribution budget enforcement: Mandatory package files may be absent · case 03

Mandatory package files may be absent.

Packaging◈ Members↗
FA-10029

Distribution budget enforcement: Mandatory package files may be absent · case 04

Mandatory package files may be absent.

Packaging◈ Members↗
FA-10030

Distribution budget enforcement: Mandatory package files may be absent · case 05

Mandatory package files may be absent.

Packaging◈ Members↗
FA-10031

Editable installation mapping: Disabled module mappings are installed · case 01

Disabled module mappings are installed.

Packaging● Open access↗
FA-10032

Editable installation mapping: Disabled module mappings are installed · case 02

Disabled module mappings are installed.

Packaging◈ Members↗
FA-10033

Editable installation mapping: Disabled module mappings are installed · case 03

Disabled module mappings are installed.

Packaging◈ Members↗
FA-10034

Editable installation mapping: Disabled module mappings are installed · case 04

Disabled module mappings are installed.

Packaging◈ Members↗
FA-10035

Editable installation mapping: Disabled module mappings are installed · case 05

Disabled module mappings are installed.

Packaging◈ Members↗
FA-10036

Editable installation mapping: Editable mappings target nonexistent sources · case 01

Editable mappings target nonexistent sources.

Packaging● Open access↗
FA-10037

Editable installation mapping: Editable mappings target nonexistent sources · case 02

Editable mappings target nonexistent sources.

Packaging◈ Members↗
FA-10038

Editable installation mapping: Editable mappings target nonexistent sources · case 03

Editable mappings target nonexistent sources.

Packaging◈ Members↗
FA-10039

Editable installation mapping: Editable mappings target nonexistent sources · case 04

Editable mappings target nonexistent sources.

Packaging◈ Members↗
FA-10040

Editable installation mapping: Editable mappings target nonexistent sources · case 05

Editable mappings target nonexistent sources.

Packaging◈ Members↗
FA-10041

Editable installation mapping: Conflicting editable modules silently override · case 01

Conflicting editable modules silently override.

Packaging● Open access↗
FA-10042

Editable installation mapping: Conflicting editable modules silently override · case 02

Conflicting editable modules silently override.

Packaging◈ Members↗
FA-10043

Editable installation mapping: Conflicting editable modules silently override · case 03

Conflicting editable modules silently override.

Packaging◈ Members↗
FA-10044

Editable installation mapping: Conflicting editable modules silently override · case 04

Conflicting editable modules silently override.

Packaging◈ Members↗
FA-10045

Editable installation mapping: Conflicting editable modules silently override · case 05

Conflicting editable modules silently override.

Packaging◈ Members↗
FA-10046

Editable installation mapping: Module names replace source directory locations · case 01

Module names replace source directory locations.

Packaging● Open access↗
FA-10047

Editable installation mapping: Module names replace source directory locations · case 02

Module names replace source directory locations.

Packaging◈ Members↗
FA-10048

Editable installation mapping: Module names replace source directory locations · case 03

Module names replace source directory locations.

Packaging◈ Members↗
FA-10049

Editable installation mapping: Module names replace source directory locations · case 04

Module names replace source directory locations.

Packaging◈ Members↗
FA-10050

Editable installation mapping: Module names replace source directory locations · case 05

Module names replace source directory locations.

Packaging◈ Members↗
FA-10051

Editable installation mapping: Editable mapping output depends on declaration order · case 01

Editable mapping output depends on declaration order.

Packaging● Open access↗
FA-10052

Editable installation mapping: Editable mapping output depends on declaration order · case 02

Editable mapping output depends on declaration order.

Packaging◈ Members↗
FA-10053

Editable installation mapping: Editable mapping output depends on declaration order · case 03

Editable mapping output depends on declaration order.

Packaging◈ Members↗
FA-10054

Editable installation mapping: Editable mapping output depends on declaration order · case 04

Editable mapping output depends on declaration order.

Packaging◈ Members↗
FA-10055

Editable installation mapping: Editable mapping output depends on declaration order · case 05

Editable mapping output depends on declaration order.

Packaging◈ Members↗
FA-10056

Software bill of materials component assembly: Development-only components inflate production inventories · case 01

Development-only components inflate production inventories.

Packaging● Open access↗
FA-10057

Software bill of materials component assembly: Development-only components inflate production inventories · case 02

Development-only components inflate production inventories.

Packaging◈ Members↗
FA-10058

Software bill of materials component assembly: Development-only components inflate production inventories · case 03

Development-only components inflate production inventories.

Packaging◈ Members↗
FA-10059

Software bill of materials component assembly: Development-only components inflate production inventories · case 04

Development-only components inflate production inventories.

Packaging◈ Members↗
FA-10060

Software bill of materials component assembly: Development-only components inflate production inventories · case 05

Development-only components inflate production inventories.

Packaging◈ Members↗
FA-10061

Software bill of materials component assembly: Different component versions collapse in the inventory · case 01

Different component versions collapse in the inventory.

Packaging● Open access↗
FA-10062

Software bill of materials component assembly: Different component versions collapse in the inventory · case 02

Different component versions collapse in the inventory.

Packaging◈ Members↗
FA-10063

Software bill of materials component assembly: Different component versions collapse in the inventory · case 03

Different component versions collapse in the inventory.

Packaging◈ Members↗
FA-10064

Software bill of materials component assembly: Different component versions collapse in the inventory · case 04

Different component versions collapse in the inventory.

Packaging◈ Members↗
FA-10065

Software bill of materials component assembly: Different component versions collapse in the inventory · case 05

Different component versions collapse in the inventory.

Packaging◈ Members↗
FA-10066

Software bill of materials component assembly: Components from different origins collapse · case 01

Components from different origins collapse.

Packaging● Open access↗
FA-10067

Software bill of materials component assembly: Components from different origins collapse · case 02

Components from different origins collapse.

Packaging◈ Members↗
FA-10068

Software bill of materials component assembly: Components from different origins collapse · case 03

Components from different origins collapse.

Packaging◈ Members↗
FA-10069

Software bill of materials component assembly: Components from different origins collapse · case 04

Components from different origins collapse.

Packaging◈ Members↗
FA-10070

Software bill of materials component assembly: Components from different origins collapse · case 05

Components from different origins collapse.

Packaging◈ Members↗
FA-10071

Software bill of materials component assembly: Only the final digest is retained · case 01

Only the final digest is retained.

Packaging● Open access↗
FA-10072

Software bill of materials component assembly: Only the final digest is retained · case 02

Only the final digest is retained.

Packaging◈ Members↗
FA-10073

Software bill of materials component assembly: Only the final digest is retained · case 03

Only the final digest is retained.

Packaging◈ Members↗
FA-10074

Software bill of materials component assembly: Only the final digest is retained · case 04

Only the final digest is retained.

Packaging◈ Members↗
FA-10075

Software bill of materials component assembly: Only the final digest is retained · case 05

Only the final digest is retained.

Packaging◈ Members↗
FA-10076

Software bill of materials component assembly: Digest lists use reverse lexical order · case 01

Digest lists use reverse lexical order.

Packaging● Open access↗
FA-10077

Software bill of materials component assembly: Digest lists use reverse lexical order · case 02

Digest lists use reverse lexical order.

Packaging◈ Members↗
FA-10078

Software bill of materials component assembly: Digest lists use reverse lexical order · case 03

Digest lists use reverse lexical order.

Packaging◈ Members↗
FA-10079

Software bill of materials component assembly: Digest lists use reverse lexical order · case 04

Digest lists use reverse lexical order.

Packaging◈ Members↗
FA-10080

Software bill of materials component assembly: Digest lists use reverse lexical order · case 05

Digest lists use reverse lexical order.

Packaging◈ Members↗
FA-10081

Deployment promotion gate: A revision is promoted using another revision’s checks · case 01

A revision is promoted using another revision’s checks.

Deployment models● Open access↗
FA-10082

Deployment promotion gate: A revision is promoted using another revision’s checks · case 02

A revision is promoted using another revision’s checks.

Deployment models◈ Members↗
FA-10083

Deployment promotion gate: A revision is promoted using another revision’s checks · case 03

A revision is promoted using another revision’s checks.

Deployment models◈ Members↗
FA-10084

Deployment promotion gate: A revision is promoted using another revision’s checks · case 04

A revision is promoted using another revision’s checks.

Deployment models◈ Members↗
FA-10085

Deployment promotion gate: A revision is promoted using another revision’s checks · case 05

A revision is promoted using another revision’s checks.

Deployment models◈ Members↗
FA-10086

Deployment promotion gate: One passing check masks failing required checks · case 01

One passing check masks failing required checks.

Deployment models● Open access↗
FA-10087

Deployment promotion gate: One passing check masks failing required checks · case 02

One passing check masks failing required checks.

Deployment models◈ Members↗
FA-10088

Deployment promotion gate: One passing check masks failing required checks · case 03

One passing check masks failing required checks.

Deployment models◈ Members↗
FA-10089

Deployment promotion gate: One passing check masks failing required checks · case 04

One passing check masks failing required checks.

Deployment models◈ Members↗
FA-10090

Deployment promotion gate: One passing check masks failing required checks · case 05

One passing check masks failing required checks.

Deployment models◈ Members↗
FA-10091

Deployment promotion gate: Promotion occurs below the healthy replica floor · case 01

Promotion occurs below the healthy replica floor.

Deployment models● Open access↗
FA-10092

Deployment promotion gate: Promotion occurs below the healthy replica floor · case 02

Promotion occurs below the healthy replica floor.

Deployment models◈ Members↗
FA-10093

Deployment promotion gate: Promotion occurs below the healthy replica floor · case 03

Promotion occurs below the healthy replica floor.

Deployment models◈ Members↗
FA-10094

Deployment promotion gate: Promotion occurs below the healthy replica floor · case 04

Promotion occurs below the healthy replica floor.

Deployment models◈ Members↗
FA-10095

Deployment promotion gate: Promotion occurs below the healthy replica floor · case 05

Promotion occurs below the healthy replica floor.

Deployment models◈ Members↗
FA-10096

Deployment promotion gate: Mandatory deployment approval is ignored · case 01

Mandatory deployment approval is ignored.

Deployment models● Open access↗
FA-10097

Deployment promotion gate: Mandatory deployment approval is ignored · case 02

Mandatory deployment approval is ignored.

Deployment models◈ Members↗
FA-10098

Deployment promotion gate: Mandatory deployment approval is ignored · case 03

Mandatory deployment approval is ignored.

Deployment models◈ Members↗
FA-10099

Deployment promotion gate: Mandatory deployment approval is ignored · case 04

Mandatory deployment approval is ignored.

Deployment models◈ Members↗
FA-10100

Deployment promotion gate: Mandatory deployment approval is ignored · case 05

Mandatory deployment approval is ignored.

Deployment models◈ 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 ↗