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

Dependency group activation: Dependencies repeated across groups install repeatedly · case 01

Dependencies repeated across groups install repeatedly.

Dependency resolution● Open access↗
FA-9402

Dependency group activation: Dependencies repeated across groups install repeatedly · case 02

Dependencies repeated across groups install repeatedly.

Dependency resolution◈ Members↗
FA-9403

Dependency group activation: Dependencies repeated across groups install repeatedly · case 03

Dependencies repeated across groups install repeatedly.

Dependency resolution◈ Members↗
FA-9404

Dependency group activation: Dependencies repeated across groups install repeatedly · case 04

Dependencies repeated across groups install repeatedly.

Dependency resolution◈ Members↗
FA-9405

Dependency group activation: Dependencies repeated across groups install repeatedly · case 05

Dependencies repeated across groups install repeatedly.

Dependency resolution◈ Members↗
FA-9406

Layered dependency override resolution: Global overrides win over package-local overrides · case 01

Global overrides win over package-local overrides.

Configuration● Open access↗
FA-9407

Layered dependency override resolution: Global overrides win over package-local overrides · case 02

Global overrides win over package-local overrides.

Configuration◈ Members↗
FA-9408

Layered dependency override resolution: Global overrides win over package-local overrides · case 03

Global overrides win over package-local overrides.

Configuration◈ Members↗
FA-9409

Layered dependency override resolution: Global overrides win over package-local overrides · case 04

Global overrides win over package-local overrides.

Configuration◈ Members↗
FA-9410

Layered dependency override resolution: Global overrides win over package-local overrides · case 05

Global overrides win over package-local overrides.

Configuration◈ Members↗
FA-9411

Layered dependency override resolution: An unrelated override changes the selected package · case 01

An unrelated override changes the selected package.

Configuration● Open access↗
FA-9412

Layered dependency override resolution: An unrelated override changes the selected package · case 02

An unrelated override changes the selected package.

Configuration◈ Members↗
FA-9413

Layered dependency override resolution: An unrelated override changes the selected package · case 03

An unrelated override changes the selected package.

Configuration◈ Members↗
FA-9414

Layered dependency override resolution: An unrelated override changes the selected package · case 04

An unrelated override changes the selected package.

Configuration◈ Members↗
FA-9415

Layered dependency override resolution: An unrelated override changes the selected package · case 05

An unrelated override changes the selected package.

Configuration◈ Members↗
FA-9416

Layered dependency override resolution: Deletion replaces the requirement with null · case 01

Deletion replaces the requirement with null.

Configuration● Open access↗
FA-9417

Layered dependency override resolution: Deletion replaces the requirement with null · case 02

Deletion replaces the requirement with null.

Configuration◈ Members↗
FA-9418

Layered dependency override resolution: Deletion replaces the requirement with null · case 03

Deletion replaces the requirement with null.

Configuration◈ Members↗
FA-9419

Layered dependency override resolution: Deletion replaces the requirement with null · case 04

Deletion replaces the requirement with null.

Configuration◈ Members↗
FA-9420

Layered dependency override resolution: Deletion replaces the requirement with null · case 05

Deletion replaces the requirement with null.

Configuration◈ Members↗
FA-9421

Layered dependency override resolution: Explicit empty overrides are silently ignored · case 01

Explicit empty overrides are silently ignored.

Configuration● Open access↗
FA-9422

Layered dependency override resolution: Explicit empty overrides are silently ignored · case 02

Explicit empty overrides are silently ignored.

Configuration◈ Members↗
FA-9423

Layered dependency override resolution: Explicit empty overrides are silently ignored · case 03

Explicit empty overrides are silently ignored.

Configuration◈ Members↗
FA-9424

Layered dependency override resolution: Explicit empty overrides are silently ignored · case 04

Explicit empty overrides are silently ignored.

Configuration◈ Members↗
FA-9425

Layered dependency override resolution: Explicit empty overrides are silently ignored · case 05

Explicit empty overrides are silently ignored.

Configuration◈ Members↗
FA-9426

Layered dependency override resolution: Present override values never replace the base · case 01

Present override values never replace the base.

Configuration● Open access↗
FA-9427

Layered dependency override resolution: Present override values never replace the base · case 02

Present override values never replace the base.

Configuration◈ Members↗
FA-9428

Layered dependency override resolution: Present override values never replace the base · case 03

Present override values never replace the base.

Configuration◈ Members↗
FA-9429

Layered dependency override resolution: Present override values never replace the base · case 04

Present override values never replace the base.

Configuration◈ Members↗
FA-9430

Layered dependency override resolution: Present override values never replace the base · case 05

Present override values never replace the base.

Configuration◈ Members↗
FA-9431

Lockfile consistency report: Unlocked requirements disappear from diagnostics · case 01

Unlocked requirements disappear from diagnostics.

Dependency resolution● Open access↗
FA-9432

Lockfile consistency report: Unlocked requirements disappear from diagnostics · case 02

Unlocked requirements disappear from diagnostics.

Dependency resolution◈ Members↗
FA-9433

Lockfile consistency report: Unlocked requirements disappear from diagnostics · case 03

Unlocked requirements disappear from diagnostics.

Dependency resolution◈ Members↗
FA-9434

Lockfile consistency report: Unlocked requirements disappear from diagnostics · case 04

Unlocked requirements disappear from diagnostics.

Dependency resolution◈ Members↗
FA-9435

Lockfile consistency report: Unlocked requirements disappear from diagnostics · case 05

Unlocked requirements disappear from diagnostics.

Dependency resolution◈ Members↗
FA-9436

Lockfile consistency report: Unrequested lock entries disappear from diagnostics · case 01

Unrequested lock entries disappear from diagnostics.

Dependency resolution● Open access↗
FA-9437

Lockfile consistency report: Unrequested lock entries disappear from diagnostics · case 02

Unrequested lock entries disappear from diagnostics.

Dependency resolution◈ Members↗
FA-9438

Lockfile consistency report: Unrequested lock entries disappear from diagnostics · case 03

Unrequested lock entries disappear from diagnostics.

Dependency resolution◈ Members↗
FA-9439

Lockfile consistency report: Unrequested lock entries disappear from diagnostics · case 04

Unrequested lock entries disappear from diagnostics.

Dependency resolution◈ Members↗
FA-9440

Lockfile consistency report: Unrequested lock entries disappear from diagnostics · case 05

Unrequested lock entries disappear from diagnostics.

Dependency resolution◈ Members↗
FA-9441

Lockfile consistency report: Locked version drift is ignored · case 01

Locked version drift is ignored.

Dependency resolution● Open access↗
FA-9442

Lockfile consistency report: Locked version drift is ignored · case 02

Locked version drift is ignored.

Dependency resolution◈ Members↗
FA-9443

Lockfile consistency report: Locked version drift is ignored · case 03

Locked version drift is ignored.

Dependency resolution◈ Members↗
FA-9444

Lockfile consistency report: Locked version drift is ignored · case 04

Locked version drift is ignored.

Dependency resolution◈ Members↗
FA-9445

Lockfile consistency report: Locked version drift is ignored · case 05

Locked version drift is ignored.

Dependency resolution◈ Members↗
FA-9446

Lockfile consistency report: Changed content at the same version is ignored · case 01

Changed content at the same version is ignored.

Dependency resolution● Open access↗
FA-9447

Lockfile consistency report: Changed content at the same version is ignored · case 02

Changed content at the same version is ignored.

Dependency resolution◈ Members↗
FA-9448

Lockfile consistency report: Changed content at the same version is ignored · case 03

Changed content at the same version is ignored.

Dependency resolution◈ Members↗
FA-9449

Lockfile consistency report: Changed content at the same version is ignored · case 04

Changed content at the same version is ignored.

Dependency resolution◈ Members↗
FA-9450

Lockfile consistency report: Changed content at the same version is ignored · case 05

Changed content at the same version is ignored.

Dependency resolution◈ Members↗
FA-9451

Lockfile consistency report: A package can silently change origin · case 01

A package can silently change origin.

Dependency resolution● Open access↗
FA-9452

Lockfile consistency report: A package can silently change origin · case 02

A package can silently change origin.

Dependency resolution◈ Members↗
FA-9453

Lockfile consistency report: A package can silently change origin · case 03

A package can silently change origin.

Dependency resolution◈ Members↗
FA-9454

Lockfile consistency report: A package can silently change origin · case 04

A package can silently change origin.

Dependency resolution◈ Members↗
FA-9455

Lockfile consistency report: A package can silently change origin · case 05

A package can silently change origin.

Dependency resolution◈ Members↗
FA-9456

Peer dependency diagnostics: Missing optional peers become errors · case 01

Missing optional peers become errors.

Dependency resolution● Open access↗
FA-9457

Peer dependency diagnostics: Missing optional peers become errors · case 02

Missing optional peers become errors.

Dependency resolution◈ Members↗
FA-9458

Peer dependency diagnostics: Missing optional peers become errors · case 03

Missing optional peers become errors.

Dependency resolution◈ Members↗
FA-9459

Peer dependency diagnostics: Missing optional peers become errors · case 04

Missing optional peers become errors.

Dependency resolution◈ Members↗
FA-9460

Peer dependency diagnostics: Missing optional peers become errors · case 05

Missing optional peers become errors.

Dependency resolution◈ Members↗
FA-9461

Peer dependency diagnostics: Missing peers are classified as version failures · case 01

Missing peers are classified as version failures.

Dependency resolution● Open access↗
FA-9462

Peer dependency diagnostics: Missing peers are classified as version failures · case 02

Missing peers are classified as version failures.

Dependency resolution◈ Members↗
FA-9463

Peer dependency diagnostics: Missing peers are classified as version failures · case 03

Missing peers are classified as version failures.

Dependency resolution◈ Members↗
FA-9464

Peer dependency diagnostics: Missing peers are classified as version failures · case 04

Missing peers are classified as version failures.

Dependency resolution◈ Members↗
FA-9465

Peer dependency diagnostics: Missing peers are classified as version failures · case 05

Missing peers are classified as version failures.

Dependency resolution◈ Members↗
FA-9466

Peer dependency diagnostics: The minimum supported peer version is rejected · case 01

The minimum supported peer version is rejected.

Dependency resolution● Open access↗
FA-9467

Peer dependency diagnostics: The minimum supported peer version is rejected · case 02

The minimum supported peer version is rejected.

Dependency resolution◈ Members↗
FA-9468

Peer dependency diagnostics: The minimum supported peer version is rejected · case 03

The minimum supported peer version is rejected.

Dependency resolution◈ Members↗
FA-9469

Peer dependency diagnostics: The minimum supported peer version is rejected · case 04

The minimum supported peer version is rejected.

Dependency resolution◈ Members↗
FA-9470

Peer dependency diagnostics: The minimum supported peer version is rejected · case 05

The minimum supported peer version is rejected.

Dependency resolution◈ Members↗
FA-9471

Peer dependency diagnostics: The excluded upper peer version is accepted · case 01

The excluded upper peer version is accepted.

Dependency resolution● Open access↗
FA-9472

Peer dependency diagnostics: The excluded upper peer version is accepted · case 02

The excluded upper peer version is accepted.

Dependency resolution◈ Members↗
FA-9473

Peer dependency diagnostics: The excluded upper peer version is accepted · case 03

The excluded upper peer version is accepted.

Dependency resolution◈ Members↗
FA-9474

Peer dependency diagnostics: The excluded upper peer version is accepted · case 04

The excluded upper peer version is accepted.

Dependency resolution◈ Members↗
FA-9475

Peer dependency diagnostics: The excluded upper peer version is accepted · case 05

The excluded upper peer version is accepted.

Dependency resolution◈ Members↗
FA-9476

Peer dependency diagnostics: Diagnostics lose the failing package identity · case 01

Diagnostics lose the failing package identity.

Dependency resolution● Open access↗
FA-9477

Peer dependency diagnostics: Diagnostics lose the failing package identity · case 02

Diagnostics lose the failing package identity.

Dependency resolution◈ Members↗
FA-9478

Peer dependency diagnostics: Diagnostics lose the failing package identity · case 03

Diagnostics lose the failing package identity.

Dependency resolution◈ Members↗
FA-9479

Peer dependency diagnostics: Diagnostics lose the failing package identity · case 04

Diagnostics lose the failing package identity.

Dependency resolution◈ Members↗
FA-9480

Peer dependency diagnostics: Diagnostics lose the failing package identity · case 05

Diagnostics lose the failing package identity.

Dependency resolution◈ Members↗
FA-9481

Package source selection: Disabled indexes can supply packages · case 01

Disabled indexes can supply packages.

Dependency resolution● Open access↗
FA-9482

Package source selection: Disabled indexes can supply packages · case 02

Disabled indexes can supply packages.

Dependency resolution◈ Members↗
FA-9483

Package source selection: Disabled indexes can supply packages · case 03

Disabled indexes can supply packages.

Dependency resolution◈ Members↗
FA-9484

Package source selection: Disabled indexes can supply packages · case 04

Disabled indexes can supply packages.

Dependency resolution◈ Members↗
FA-9485

Package source selection: Disabled indexes can supply packages · case 05

Disabled indexes can supply packages.

Dependency resolution◈ Members↗
FA-9486

Package source selection: Untrusted indexes can supply packages · case 01

Untrusted indexes can supply packages.

Dependency resolution● Open access↗
FA-9487

Package source selection: Untrusted indexes can supply packages · case 02

Untrusted indexes can supply packages.

Dependency resolution◈ Members↗
FA-9488

Package source selection: Untrusted indexes can supply packages · case 03

Untrusted indexes can supply packages.

Dependency resolution◈ Members↗
FA-9489

Package source selection: Untrusted indexes can supply packages · case 04

Untrusted indexes can supply packages.

Dependency resolution◈ Members↗
FA-9490

Package source selection: Untrusted indexes can supply packages · case 05

Untrusted indexes can supply packages.

Dependency resolution◈ Members↗
FA-9491

Package source selection: An index missing the package is selected · case 01

An index missing the package is selected.

Dependency resolution● Open access↗
FA-9492

Package source selection: An index missing the package is selected · case 02

An index missing the package is selected.

Dependency resolution◈ Members↗
FA-9493

Package source selection: An index missing the package is selected · case 03

An index missing the package is selected.

Dependency resolution◈ Members↗
FA-9494

Package source selection: An index missing the package is selected · case 04

An index missing the package is selected.

Dependency resolution◈ Members↗
FA-9495

Package source selection: An index missing the package is selected · case 05

An index missing the package is selected.

Dependency resolution◈ Members↗
FA-9496

Package source selection: A mirror outranks an available primary · case 01

A mirror outranks an available primary.

Dependency resolution● Open access↗
FA-9497

Package source selection: A mirror outranks an available primary · case 02

A mirror outranks an available primary.

Dependency resolution◈ Members↗
FA-9498

Package source selection: A mirror outranks an available primary · case 03

A mirror outranks an available primary.

Dependency resolution◈ Members↗
FA-9499

Package source selection: A mirror outranks an available primary · case 04

A mirror outranks an available primary.

Dependency resolution◈ Members↗
FA-9500

Package source selection: A mirror outranks an available primary · case 05

A mirror outranks an available primary.

Dependency resolution◈ 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 ↗