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

Retry budget reservation lifecycle: Reservation identity violates retry transition semantics · case 01

Reservation identity violates retry transition semantics

HTTP retries● Open access↗
FA-29902

Retry budget reservation lifecycle: Reservation identity violates retry transition semantics · case 02

Reservation identity violates retry transition semantics

HTTP retries◈ Members↗
FA-29903

Retry budget reservation lifecycle: Reservation identity violates retry transition semantics · case 03

Reservation identity violates retry transition semantics

HTTP retries◈ Members↗
FA-29904

Retry budget reservation lifecycle: Reservation identity violates retry transition semantics · case 04

Reservation identity violates retry transition semantics

HTTP retries◈ Members↗
FA-29905

Retry budget reservation lifecycle: Reservation identity violates retry transition semantics · case 05

Reservation identity violates retry transition semantics

HTTP retries◈ Members↗
FA-29906

Retry budget reservation lifecycle: Reserve result violates retry transition semantics · case 01

Reserve result violates retry transition semantics

HTTP retries● Open access↗
FA-29907

Retry budget reservation lifecycle: Reserve result violates retry transition semantics · case 02

Reserve result violates retry transition semantics

HTTP retries◈ Members↗
FA-29908

Retry budget reservation lifecycle: Reserve result violates retry transition semantics · case 03

Reserve result violates retry transition semantics

HTTP retries◈ Members↗
FA-29909

Retry budget reservation lifecycle: Reserve result violates retry transition semantics · case 04

Reserve result violates retry transition semantics

HTTP retries◈ Members↗
FA-29910

Retry budget reservation lifecycle: Reserve result violates retry transition semantics · case 05

Reserve result violates retry transition semantics

HTTP retries◈ Members↗
FA-29911

Retry budget reservation lifecycle: Commit remove violates retry transition semantics · case 01

Commit remove violates retry transition semantics

HTTP retries● Open access↗
FA-29912

Retry budget reservation lifecycle: Commit remove violates retry transition semantics · case 02

Commit remove violates retry transition semantics

HTTP retries◈ Members↗
FA-29913

Retry budget reservation lifecycle: Commit remove violates retry transition semantics · case 03

Commit remove violates retry transition semantics

HTTP retries◈ Members↗
FA-29914

Retry budget reservation lifecycle: Commit remove violates retry transition semantics · case 04

Commit remove violates retry transition semantics

HTTP retries◈ Members↗
FA-29915

Retry budget reservation lifecycle: Commit remove violates retry transition semantics · case 05

Commit remove violates retry transition semantics

HTTP retries◈ Members↗
FA-29916

Retry budget reservation lifecycle: Abort remove violates retry transition semantics · case 01

Abort remove violates retry transition semantics

HTTP retries● Open access↗
FA-29917

Retry budget reservation lifecycle: Abort remove violates retry transition semantics · case 02

Abort remove violates retry transition semantics

HTTP retries◈ Members↗
FA-29918

Retry budget reservation lifecycle: Abort remove violates retry transition semantics · case 03

Abort remove violates retry transition semantics

HTTP retries◈ Members↗
FA-29919

Retry budget reservation lifecycle: Abort remove violates retry transition semantics · case 04

Abort remove violates retry transition semantics

HTTP retries◈ Members↗
FA-29920

Retry budget reservation lifecycle: Abort remove violates retry transition semantics · case 05

Abort remove violates retry transition semantics

HTTP retries◈ Members↗
FA-29921

Retry budget reservation lifecycle: Refund violates retry transition semantics · case 01

Refund violates retry transition semantics

HTTP retries● Open access↗
FA-29922

Retry budget reservation lifecycle: Refund violates retry transition semantics · case 02

Refund violates retry transition semantics

HTTP retries◈ Members↗
FA-29923

Retry budget reservation lifecycle: Refund violates retry transition semantics · case 03

Refund violates retry transition semantics

HTTP retries◈ Members↗
FA-29924

Retry budget reservation lifecycle: Refund violates retry transition semantics · case 04

Refund violates retry transition semantics

HTTP retries◈ Members↗
FA-29925

Retry budget reservation lifecycle: Refund violates retry transition semantics · case 05

Refund violates retry transition semantics

HTTP retries◈ Members↗
FA-29926

Retry budget reservation lifecycle: Refill held violates retry transition semantics · case 01

Refill held violates retry transition semantics

HTTP retries● Open access↗
FA-29927

Retry budget reservation lifecycle: Refill held violates retry transition semantics · case 02

Refill held violates retry transition semantics

HTTP retries◈ Members↗
FA-29928

Retry budget reservation lifecycle: Refill held violates retry transition semantics · case 03

Refill held violates retry transition semantics

HTTP retries◈ Members↗
FA-29929

Retry budget reservation lifecycle: Refill held violates retry transition semantics · case 04

Refill held violates retry transition semantics

HTTP retries◈ Members↗
FA-29930

Retry budget reservation lifecycle: Refill held violates retry transition semantics · case 05

Refill held violates retry transition semantics

HTTP retries◈ Members↗
FA-29931

Retry budget reservation lifecycle: Refill amount violates retry transition semantics · case 01

Refill amount violates retry transition semantics

HTTP retries● Open access↗
FA-29932

Retry budget reservation lifecycle: Refill amount violates retry transition semantics · case 02

Refill amount violates retry transition semantics

HTTP retries◈ Members↗
FA-29933

Retry budget reservation lifecycle: Refill amount violates retry transition semantics · case 03

Refill amount violates retry transition semantics

HTTP retries◈ Members↗
FA-29934

Retry budget reservation lifecycle: Refill amount violates retry transition semantics · case 04

Refill amount violates retry transition semantics

HTTP retries◈ Members↗
FA-29935

Retry budget reservation lifecycle: Refill amount violates retry transition semantics · case 05

Refill amount violates retry transition semantics

HTTP retries◈ Members↗
FA-29936

Retry budget reservation lifecycle: Unknown abort violates retry transition semantics · case 01

Unknown abort violates retry transition semantics

HTTP retries● Open access↗
FA-29937

Retry budget reservation lifecycle: Unknown abort violates retry transition semantics · case 02

Unknown abort violates retry transition semantics

HTTP retries◈ Members↗
FA-29938

Retry budget reservation lifecycle: Unknown abort violates retry transition semantics · case 03

Unknown abort violates retry transition semantics

HTTP retries◈ Members↗
FA-29939

Retry budget reservation lifecycle: Unknown abort violates retry transition semantics · case 04

Unknown abort violates retry transition semantics

HTTP retries◈ Members↗
FA-29940

Retry budget reservation lifecycle: Unknown abort violates retry transition semantics · case 05

Unknown abort violates retry transition semantics

HTTP retries◈ Members↗
FA-29941

Retry budget reservation lifecycle: Refill cap violates retry transition semantics · case 01

Refill cap violates retry transition semantics

HTTP retries● Open access↗
FA-29942

Retry budget reservation lifecycle: Refill cap violates retry transition semantics · case 02

Refill cap violates retry transition semantics

HTTP retries◈ Members↗
FA-29943

Retry budget reservation lifecycle: Refill cap violates retry transition semantics · case 03

Refill cap violates retry transition semantics

HTTP retries◈ Members↗
FA-29944

Retry budget reservation lifecycle: Refill cap violates retry transition semantics · case 04

Refill cap violates retry transition semantics

HTTP retries◈ Members↗
FA-29945

Retry budget reservation lifecycle: Refill cap violates retry transition semantics · case 05

Refill cap violates retry transition semantics

HTTP retries◈ Members↗
FA-29946

Retry budget reservation lifecycle: Configure capacity violates retry transition semantics · case 01

Configure capacity violates retry transition semantics

HTTP retries● Open access↗
FA-29947

Retry budget reservation lifecycle: Configure capacity violates retry transition semantics · case 02

Configure capacity violates retry transition semantics

HTTP retries◈ Members↗
FA-29948

Retry budget reservation lifecycle: Configure capacity violates retry transition semantics · case 03

Configure capacity violates retry transition semantics

HTTP retries◈ Members↗
FA-29949

Retry budget reservation lifecycle: Configure capacity violates retry transition semantics · case 04

Configure capacity violates retry transition semantics

HTTP retries◈ Members↗
FA-29950

Retry budget reservation lifecycle: Configure capacity violates retry transition semantics · case 05

Configure capacity violates retry transition semantics

HTTP retries◈ Members↗
FA-29951

Cancellation of queued retries: Cancelled schedule violates retry transition semantics · case 01

Cancelled schedule violates retry transition semantics

HTTP retries● Open access↗
FA-29952

Cancellation of queued retries: Cancelled schedule violates retry transition semantics · case 02

Cancelled schedule violates retry transition semantics

HTTP retries◈ Members↗
FA-29953

Cancellation of queued retries: Cancelled schedule violates retry transition semantics · case 03

Cancelled schedule violates retry transition semantics

HTTP retries◈ Members↗
FA-29954

Cancellation of queued retries: Cancelled schedule violates retry transition semantics · case 04

Cancelled schedule violates retry transition semantics

HTTP retries◈ Members↗
FA-29955

Cancellation of queued retries: Cancelled schedule violates retry transition semantics · case 05

Cancelled schedule violates retry transition semantics

HTTP retries◈ Members↗
FA-29956

Cancellation of queued retries: Running schedule violates retry transition semantics · case 01

Running schedule violates retry transition semantics

HTTP retries● Open access↗
FA-29957

Cancellation of queued retries: Running schedule violates retry transition semantics · case 02

Running schedule violates retry transition semantics

HTTP retries◈ Members↗
FA-29958

Cancellation of queued retries: Running schedule violates retry transition semantics · case 03

Running schedule violates retry transition semantics

HTTP retries◈ Members↗
FA-29959

Cancellation of queued retries: Running schedule violates retry transition semantics · case 04

Running schedule violates retry transition semantics

HTTP retries◈ Members↗
FA-29960

Cancellation of queued retries: Running schedule violates retry transition semantics · case 05

Running schedule violates retry transition semantics

HTTP retries◈ Members↗
FA-29961

Cancellation of queued retries: Reschedule time violates retry transition semantics · case 01

Reschedule time violates retry transition semantics

HTTP retries● Open access↗
FA-29962

Cancellation of queued retries: Reschedule time violates retry transition semantics · case 02

Reschedule time violates retry transition semantics

HTTP retries◈ Members↗
FA-29963

Cancellation of queued retries: Reschedule time violates retry transition semantics · case 03

Reschedule time violates retry transition semantics

HTTP retries◈ Members↗
FA-29964

Cancellation of queued retries: Reschedule time violates retry transition semantics · case 04

Reschedule time violates retry transition semantics

HTTP retries◈ Members↗
FA-29965

Cancellation of queued retries: Reschedule time violates retry transition semantics · case 05

Reschedule time violates retry transition semantics

HTTP retries◈ Members↗
FA-29966

Cancellation of queued retries: Cancel sticky violates retry transition semantics · case 01

Cancel sticky violates retry transition semantics

HTTP retries● Open access↗
FA-29967

Cancellation of queued retries: Cancel sticky violates retry transition semantics · case 02

Cancel sticky violates retry transition semantics

HTTP retries◈ Members↗
FA-29968

Cancellation of queued retries: Cancel sticky violates retry transition semantics · case 03

Cancel sticky violates retry transition semantics

HTTP retries◈ Members↗
FA-29969

Cancellation of queued retries: Cancel sticky violates retry transition semantics · case 04

Cancel sticky violates retry transition semantics

HTTP retries◈ Members↗
FA-29970

Cancellation of queued retries: Cancel sticky violates retry transition semantics · case 05

Cancel sticky violates retry transition semantics

HTTP retries◈ Members↗
FA-29971

Cancellation of queued retries: Cancel queued violates retry transition semantics · case 01

Cancel queued violates retry transition semantics

HTTP retries● Open access↗
FA-29972

Cancellation of queued retries: Cancel queued violates retry transition semantics · case 02

Cancel queued violates retry transition semantics

HTTP retries◈ Members↗
FA-29973

Cancellation of queued retries: Cancel queued violates retry transition semantics · case 03

Cancel queued violates retry transition semantics

HTTP retries◈ Members↗
FA-29974

Cancellation of queued retries: Cancel queued violates retry transition semantics · case 04

Cancel queued violates retry transition semantics

HTTP retries◈ Members↗
FA-29975

Cancellation of queued retries: Cancel queued violates retry transition semantics · case 05

Cancel queued violates retry transition semantics

HTTP retries◈ Members↗
FA-29976

Cancellation of queued retries: Cancel running violates retry transition semantics · case 01

Cancel running violates retry transition semantics

HTTP retries● Open access↗
FA-29977

Cancellation of queued retries: Cancel running violates retry transition semantics · case 02

Cancel running violates retry transition semantics

HTTP retries◈ Members↗
FA-29978

Cancellation of queued retries: Cancel running violates retry transition semantics · case 03

Cancel running violates retry transition semantics

HTTP retries◈ Members↗
FA-29979

Cancellation of queued retries: Cancel running violates retry transition semantics · case 04

Cancel running violates retry transition semantics

HTTP retries◈ Members↗
FA-29980

Cancellation of queued retries: Cancel running violates retry transition semantics · case 05

Cancel running violates retry transition semantics

HTTP retries◈ Members↗
FA-29981

Cancellation of queued retries: Due inclusive violates retry transition semantics · case 01

Due inclusive violates retry transition semantics

HTTP retries● Open access↗
FA-29982

Cancellation of queued retries: Due inclusive violates retry transition semantics · case 02

Due inclusive violates retry transition semantics

HTTP retries◈ Members↗
FA-29983

Cancellation of queued retries: Due inclusive violates retry transition semantics · case 03

Due inclusive violates retry transition semantics

HTTP retries◈ Members↗
FA-29984

Cancellation of queued retries: Due inclusive violates retry transition semantics · case 04

Due inclusive violates retry transition semantics

HTTP retries◈ Members↗
FA-29985

Cancellation of queued retries: Due inclusive violates retry transition semantics · case 05

Due inclusive violates retry transition semantics

HTTP retries◈ Members↗
FA-29986

Cancellation of queued retries: Due order violates retry transition semantics · case 01

Due order violates retry transition semantics

HTTP retries● Open access↗
FA-29987

Cancellation of queued retries: Due order violates retry transition semantics · case 02

Due order violates retry transition semantics

HTTP retries◈ Members↗
FA-29988

Cancellation of queued retries: Due order violates retry transition semantics · case 03

Due order violates retry transition semantics

HTTP retries◈ Members↗
FA-29989

Cancellation of queued retries: Due order violates retry transition semantics · case 04

Due order violates retry transition semantics

HTTP retries◈ Members↗
FA-29990

Cancellation of queued retries: Due order violates retry transition semantics · case 05

Due order violates retry transition semantics

HTTP retries◈ Members↗
FA-29991

Cancellation of queued retries: Dequeue on start violates retry transition semantics · case 01

Dequeue on start violates retry transition semantics

HTTP retries● Open access↗
FA-29992

Cancellation of queued retries: Dequeue on start violates retry transition semantics · case 02

Dequeue on start violates retry transition semantics

HTTP retries◈ Members↗
FA-29993

Cancellation of queued retries: Dequeue on start violates retry transition semantics · case 03

Dequeue on start violates retry transition semantics

HTTP retries◈ Members↗
FA-29994

Cancellation of queued retries: Dequeue on start violates retry transition semantics · case 04

Dequeue on start violates retry transition semantics

HTTP retries◈ Members↗
FA-29995

Cancellation of queued retries: Dequeue on start violates retry transition semantics · case 05

Dequeue on start violates retry transition semantics

HTTP retries◈ Members↗
FA-29996

Cancellation of queued retries: Running mark violates retry transition semantics · case 01

Running mark violates retry transition semantics

HTTP retries● Open access↗
FA-29997

Cancellation of queued retries: Running mark violates retry transition semantics · case 02

Running mark violates retry transition semantics

HTTP retries◈ Members↗
FA-29998

Cancellation of queued retries: Running mark violates retry transition semantics · case 03

Running mark violates retry transition semantics

HTTP retries◈ Members↗
FA-29999

Cancellation of queued retries: Running mark violates retry transition semantics · case 04

Running mark violates retry transition semantics

HTTP retries◈ Members↗
FA-30000

Cancellation of queued retries: Running mark violates retry transition semantics · case 05

Running mark violates retry transition semantics

HTTP retries◈ 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 ↗