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

Installed distribution record validation: Unexpected executable files pass validation · case 01

Unexpected executable files pass validation.

Packaging● Open access↗
FA-9902

Installed distribution record validation: Unexpected executable files pass validation · case 02

Unexpected executable files pass validation.

Packaging◈ Members↗
FA-9903

Installed distribution record validation: Unexpected executable files pass validation · case 03

Unexpected executable files pass validation.

Packaging◈ Members↗
FA-9904

Installed distribution record validation: Unexpected executable files pass validation · case 04

Unexpected executable files pass validation.

Packaging◈ Members↗
FA-9905

Installed distribution record validation: Unexpected executable files pass validation · case 05

Unexpected executable files pass validation.

Packaging◈ Members↗
FA-9906

Entry point registry assembly: Disabled entry points are published · case 01

Disabled entry points are published.

Packaging● Open access↗
FA-9907

Entry point registry assembly: Disabled entry points are published · case 02

Disabled entry points are published.

Packaging◈ Members↗
FA-9908

Entry point registry assembly: Disabled entry points are published · case 03

Disabled entry points are published.

Packaging◈ Members↗
FA-9909

Entry point registry assembly: Disabled entry points are published · case 04

Disabled entry points are published.

Packaging◈ Members↗
FA-9910

Entry point registry assembly: Disabled entry points are published · case 05

Disabled entry points are published.

Packaging◈ Members↗
FA-9911

Entry point registry assembly: Entry point groups share one namespace · case 01

Entry point groups share one namespace.

Packaging● Open access↗
FA-9912

Entry point registry assembly: Entry point groups share one namespace · case 02

Entry point groups share one namespace.

Packaging◈ Members↗
FA-9913

Entry point registry assembly: Entry point groups share one namespace · case 03

Entry point groups share one namespace.

Packaging◈ Members↗
FA-9914

Entry point registry assembly: Entry point groups share one namespace · case 04

Entry point groups share one namespace.

Packaging◈ Members↗
FA-9915

Entry point registry assembly: Entry point groups share one namespace · case 05

Entry point groups share one namespace.

Packaging◈ Members↗
FA-9916

Entry point registry assembly: Conflicting entry points silently replace earlier ones · case 01

Conflicting entry points silently replace earlier ones.

Packaging● Open access↗
FA-9917

Entry point registry assembly: Conflicting entry points silently replace earlier ones · case 02

Conflicting entry points silently replace earlier ones.

Packaging◈ Members↗
FA-9918

Entry point registry assembly: Conflicting entry points silently replace earlier ones · case 03

Conflicting entry points silently replace earlier ones.

Packaging◈ Members↗
FA-9919

Entry point registry assembly: Conflicting entry points silently replace earlier ones · case 04

Conflicting entry points silently replace earlier ones.

Packaging◈ Members↗
FA-9920

Entry point registry assembly: Conflicting entry points silently replace earlier ones · case 05

Conflicting entry points silently replace earlier ones.

Packaging◈ Members↗
FA-9921

Entry point registry assembly: Identical duplicate entry points are rejected · case 01

Identical duplicate entry points are rejected.

Packaging● Open access↗
FA-9922

Entry point registry assembly: Identical duplicate entry points are rejected · case 02

Identical duplicate entry points are rejected.

Packaging◈ Members↗
FA-9923

Entry point registry assembly: Identical duplicate entry points are rejected · case 03

Identical duplicate entry points are rejected.

Packaging◈ Members↗
FA-9924

Entry point registry assembly: Identical duplicate entry points are rejected · case 04

Identical duplicate entry points are rejected.

Packaging◈ Members↗
FA-9925

Entry point registry assembly: Identical duplicate entry points are rejected · case 05

Identical duplicate entry points are rejected.

Packaging◈ Members↗
FA-9926

Entry point registry assembly: Entry names replace import targets · case 01

Entry names replace import targets.

Packaging● Open access↗
FA-9927

Entry point registry assembly: Entry names replace import targets · case 02

Entry names replace import targets.

Packaging◈ Members↗
FA-9928

Entry point registry assembly: Entry names replace import targets · case 03

Entry names replace import targets.

Packaging◈ Members↗
FA-9929

Entry point registry assembly: Entry names replace import targets · case 04

Entry names replace import targets.

Packaging◈ Members↗
FA-9930

Entry point registry assembly: Entry names replace import targets · case 05

Entry names replace import targets.

Packaging◈ Members↗
FA-9931

Distribution license policy: Undeclared licenses pass admission · case 01

Undeclared licenses pass admission.

Packaging● Open access↗
FA-9932

Distribution license policy: Undeclared licenses pass admission · case 02

Undeclared licenses pass admission.

Packaging◈ Members↗
FA-9933

Distribution license policy: Undeclared licenses pass admission · case 03

Undeclared licenses pass admission.

Packaging◈ Members↗
FA-9934

Distribution license policy: Undeclared licenses pass admission · case 04

Undeclared licenses pass admission.

Packaging◈ Members↗
FA-9935

Distribution license policy: Undeclared licenses pass admission · case 05

Undeclared licenses pass admission.

Packaging◈ Members↗
FA-9936

Distribution license policy: One allowed license masks an unsupported requirement · case 01

One allowed license masks an unsupported requirement.

Packaging● Open access↗
FA-9937

Distribution license policy: One allowed license masks an unsupported requirement · case 02

One allowed license masks an unsupported requirement.

Packaging◈ Members↗
FA-9938

Distribution license policy: One allowed license masks an unsupported requirement · case 03

One allowed license masks an unsupported requirement.

Packaging◈ Members↗
FA-9939

Distribution license policy: One allowed license masks an unsupported requirement · case 04

One allowed license masks an unsupported requirement.

Packaging◈ Members↗
FA-9940

Distribution license policy: One allowed license masks an unsupported requirement · case 05

One allowed license masks an unsupported requirement.

Packaging◈ Members↗
FA-9941

Distribution license policy: Explicit prohibitions are ignored · case 01

Explicit prohibitions are ignored.

Packaging● Open access↗
FA-9942

Distribution license policy: Explicit prohibitions are ignored · case 02

Explicit prohibitions are ignored.

Packaging◈ Members↗
FA-9943

Distribution license policy: Explicit prohibitions are ignored · case 03

Explicit prohibitions are ignored.

Packaging◈ Members↗
FA-9944

Distribution license policy: Explicit prohibitions are ignored · case 04

Explicit prohibitions are ignored.

Packaging◈ Members↗
FA-9945

Distribution license policy: Explicit prohibitions are ignored · case 05

Explicit prohibitions are ignored.

Packaging◈ Members↗
FA-9946

Distribution license policy: Redistribution opt-out is ignored · case 01

Redistribution opt-out is ignored.

Packaging● Open access↗
FA-9947

Distribution license policy: Redistribution opt-out is ignored · case 02

Redistribution opt-out is ignored.

Packaging◈ Members↗
FA-9948

Distribution license policy: Redistribution opt-out is ignored · case 03

Redistribution opt-out is ignored.

Packaging◈ Members↗
FA-9949

Distribution license policy: Redistribution opt-out is ignored · case 04

Redistribution opt-out is ignored.

Packaging◈ Members↗
FA-9950

Distribution license policy: Redistribution opt-out is ignored · case 05

Redistribution opt-out is ignored.

Packaging◈ Members↗
FA-9951

Distribution license policy: Required source offers are missing · case 01

Required source offers are missing.

Packaging● Open access↗
FA-9952

Distribution license policy: Required source offers are missing · case 02

Required source offers are missing.

Packaging◈ Members↗
FA-9953

Distribution license policy: Required source offers are missing · case 03

Required source offers are missing.

Packaging◈ Members↗
FA-9954

Distribution license policy: Required source offers are missing · case 04

Required source offers are missing.

Packaging◈ Members↗
FA-9955

Distribution license policy: Required source offers are missing · case 05

Required source offers are missing.

Packaging◈ Members↗
FA-9956

Reproducible archive metadata: Archive owner IDs depend on the build host · case 01

Archive owner IDs depend on the build host.

Packaging● Open access↗
FA-9957

Reproducible archive metadata: Archive owner IDs depend on the build host · case 02

Archive owner IDs depend on the build host.

Packaging◈ Members↗
FA-9958

Reproducible archive metadata: Archive owner IDs depend on the build host · case 03

Archive owner IDs depend on the build host.

Packaging◈ Members↗
FA-9959

Reproducible archive metadata: Archive owner IDs depend on the build host · case 04

Archive owner IDs depend on the build host.

Packaging◈ Members↗
FA-9960

Reproducible archive metadata: Archive owner IDs depend on the build host · case 05

Archive owner IDs depend on the build host.

Packaging◈ Members↗
FA-9961

Reproducible archive metadata: Archive group IDs depend on the build host · case 01

Archive group IDs depend on the build host.

Packaging● Open access↗
FA-9962

Reproducible archive metadata: Archive group IDs depend on the build host · case 02

Archive group IDs depend on the build host.

Packaging◈ Members↗
FA-9963

Reproducible archive metadata: Archive group IDs depend on the build host · case 03

Archive group IDs depend on the build host.

Packaging◈ Members↗
FA-9964

Reproducible archive metadata: Archive group IDs depend on the build host · case 04

Archive group IDs depend on the build host.

Packaging◈ Members↗
FA-9965

Reproducible archive metadata: Archive group IDs depend on the build host · case 05

Archive group IDs depend on the build host.

Packaging◈ Members↗
FA-9966

Reproducible archive metadata: Archive timestamps depend on checkout time · case 01

Archive timestamps depend on checkout time.

Packaging● Open access↗
FA-9967

Reproducible archive metadata: Archive timestamps depend on checkout time · case 02

Archive timestamps depend on checkout time.

Packaging◈ Members↗
FA-9968

Reproducible archive metadata: Archive timestamps depend on checkout time · case 03

Archive timestamps depend on checkout time.

Packaging◈ Members↗
FA-9969

Reproducible archive metadata: Archive timestamps depend on checkout time · case 04

Archive timestamps depend on checkout time.

Packaging◈ Members↗
FA-9970

Reproducible archive metadata: Archive timestamps depend on checkout time · case 05

Archive timestamps depend on checkout time.

Packaging◈ Members↗
FA-9971

Reproducible archive metadata: Executable files lose their mode bit · case 01

Executable files lose their mode bit.

Packaging● Open access↗
FA-9972

Reproducible archive metadata: Executable files lose their mode bit · case 02

Executable files lose their mode bit.

Packaging◈ Members↗
FA-9973

Reproducible archive metadata: Executable files lose their mode bit · case 03

Executable files lose their mode bit.

Packaging◈ Members↗
FA-9974

Reproducible archive metadata: Executable files lose their mode bit · case 04

Executable files lose their mode bit.

Packaging◈ Members↗
FA-9975

Reproducible archive metadata: Executable files lose their mode bit · case 05

Executable files lose their mode bit.

Packaging◈ Members↗
FA-9976

Reproducible archive metadata: Archive entry order follows filesystem enumeration · case 01

Archive entry order follows filesystem enumeration.

Packaging● Open access↗
FA-9977

Reproducible archive metadata: Archive entry order follows filesystem enumeration · case 02

Archive entry order follows filesystem enumeration.

Packaging◈ Members↗
FA-9978

Reproducible archive metadata: Archive entry order follows filesystem enumeration · case 03

Archive entry order follows filesystem enumeration.

Packaging◈ Members↗
FA-9979

Reproducible archive metadata: Archive entry order follows filesystem enumeration · case 04

Archive entry order follows filesystem enumeration.

Packaging◈ Members↗
FA-9980

Reproducible archive metadata: Archive entry order follows filesystem enumeration · case 05

Archive entry order follows filesystem enumeration.

Packaging◈ Members↗
FA-9981

Package publication plan: An unrelated published version blocks a new release · case 01

An unrelated published version blocks a new release.

Packaging● Open access↗
FA-9982

Package publication plan: An unrelated published version blocks a new release · case 02

An unrelated published version blocks a new release.

Packaging◈ Members↗
FA-9983

Package publication plan: An unrelated published version blocks a new release · case 03

An unrelated published version blocks a new release.

Packaging◈ Members↗
FA-9984

Package publication plan: An unrelated published version blocks a new release · case 04

An unrelated published version blocks a new release.

Packaging◈ Members↗
FA-9985

Package publication plan: An unrelated published version blocks a new release · case 05

An unrelated published version blocks a new release.

Packaging◈ Members↗
FA-9986

Package publication plan: Different package bytes are treated as already published · case 01

Different package bytes are treated as already published.

Packaging● Open access↗
FA-9987

Package publication plan: Different package bytes are treated as already published · case 02

Different package bytes are treated as already published.

Packaging◈ Members↗
FA-9988

Package publication plan: Different package bytes are treated as already published · case 03

Different package bytes are treated as already published.

Packaging◈ Members↗
FA-9989

Package publication plan: Different package bytes are treated as already published · case 04

Different package bytes are treated as already published.

Packaging◈ Members↗
FA-9990

Package publication plan: Different package bytes are treated as already published · case 05

Different package bytes are treated as already published.

Packaging◈ Members↗
FA-9991

Package publication plan: Immutable versions are overwritten · case 01

Immutable versions are overwritten.

Packaging● Open access↗
FA-9992

Package publication plan: Immutable versions are overwritten · case 02

Immutable versions are overwritten.

Packaging◈ Members↗
FA-9993

Package publication plan: Immutable versions are overwritten · case 03

Immutable versions are overwritten.

Packaging◈ Members↗
FA-9994

Package publication plan: Immutable versions are overwritten · case 04

Immutable versions are overwritten.

Packaging◈ Members↗
FA-9995

Package publication plan: Immutable versions are overwritten · case 05

Immutable versions are overwritten.

Packaging◈ Members↗
FA-9996

Package publication plan: Unsigned provenance is ignored · case 01

Unsigned provenance is ignored.

Packaging● Open access↗
FA-9997

Package publication plan: Unsigned provenance is ignored · case 02

Unsigned provenance is ignored.

Packaging◈ Members↗
FA-9998

Package publication plan: Unsigned provenance is ignored · case 03

Unsigned provenance is ignored.

Packaging◈ Members↗
FA-9999

Package publication plan: Unsigned provenance is ignored · case 04

Unsigned provenance is ignored.

Packaging◈ Members↗
FA-10000

Package publication plan: Unsigned provenance is ignored · case 05

Unsigned provenance is ignored.

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