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

Notification visual impression qualification: leaves-viewport from qualifying · case 01

The leaves-viewport event leaves a notification in reporting instead of offscreen.

Notification interfaces● Open access↗
FA-34902

Notification visual impression qualification: leaves-viewport from qualifying · case 02

The leaves-viewport event leaves a notification in reporting instead of offscreen.

Notification interfaces◈ Members↗
FA-34903

Notification visual impression qualification: leaves-viewport from qualifying · case 03

The leaves-viewport event leaves a notification in reporting instead of offscreen.

Notification interfaces◈ Members↗
FA-34904

Notification visual impression qualification: leaves-viewport from qualifying · case 04

The leaves-viewport event leaves a notification in reporting instead of offscreen.

Notification interfaces◈ Members↗
FA-34905

Notification visual impression qualification: leaves-viewport from qualifying · case 05

The leaves-viewport event leaves a notification in reporting instead of offscreen.

Notification interfaces◈ Members↗
FA-34906

Notification visual impression qualification: report-success from reporting · case 01

The report-success event leaves a notification in qualifying instead of counted.

Notification interfaces● Open access↗
FA-34907

Notification visual impression qualification: report-success from reporting · case 02

The report-success event leaves a notification in qualifying instead of counted.

Notification interfaces◈ Members↗
FA-34908

Notification visual impression qualification: report-success from reporting · case 03

The report-success event leaves a notification in qualifying instead of counted.

Notification interfaces◈ Members↗
FA-34909

Notification visual impression qualification: report-success from reporting · case 04

The report-success event leaves a notification in qualifying instead of counted.

Notification interfaces◈ Members↗
FA-34910

Notification visual impression qualification: report-success from reporting · case 05

The report-success event leaves a notification in qualifying instead of counted.

Notification interfaces◈ Members↗
FA-34911

Notification visual impression qualification: report-failure from reporting · case 01

The report-failure event leaves a notification in counted instead of report-error.

Notification interfaces● Open access↗
FA-34912

Notification visual impression qualification: report-failure from reporting · case 02

The report-failure event leaves a notification in counted instead of report-error.

Notification interfaces◈ Members↗
FA-34913

Notification visual impression qualification: report-failure from reporting · case 03

The report-failure event leaves a notification in counted instead of report-error.

Notification interfaces◈ Members↗
FA-34914

Notification visual impression qualification: report-failure from reporting · case 04

The report-failure event leaves a notification in counted instead of report-error.

Notification interfaces◈ Members↗
FA-34915

Notification visual impression qualification: report-failure from reporting · case 05

The report-failure event leaves a notification in counted instead of report-error.

Notification interfaces◈ Members↗
FA-34916

Notification visual impression qualification: retry-report from report-error · case 01

The retry-report event leaves a notification in counted instead of reporting.

Notification interfaces● Open access↗
FA-34917

Notification visual impression qualification: retry-report from report-error · case 02

The retry-report event leaves a notification in counted instead of reporting.

Notification interfaces◈ Members↗
FA-34918

Notification visual impression qualification: retry-report from report-error · case 03

The retry-report event leaves a notification in counted instead of reporting.

Notification interfaces◈ Members↗
FA-34919

Notification visual impression qualification: retry-report from report-error · case 04

The retry-report event leaves a notification in counted instead of reporting.

Notification interfaces◈ Members↗
FA-34920

Notification visual impression qualification: retry-report from report-error · case 05

The retry-report event leaves a notification in counted instead of reporting.

Notification interfaces◈ Members↗
FA-34921

Notification visual impression qualification: covered-by-overlay from qualifying · case 01

The covered-by-overlay event leaves a notification in reporting instead of occluded.

Notification interfaces● Open access↗
FA-34922

Notification visual impression qualification: covered-by-overlay from qualifying · case 02

The covered-by-overlay event leaves a notification in reporting instead of occluded.

Notification interfaces◈ Members↗
FA-34923

Notification visual impression qualification: covered-by-overlay from qualifying · case 03

The covered-by-overlay event leaves a notification in reporting instead of occluded.

Notification interfaces◈ Members↗
FA-34924

Notification visual impression qualification: covered-by-overlay from qualifying · case 04

The covered-by-overlay event leaves a notification in reporting instead of occluded.

Notification interfaces◈ Members↗
FA-34925

Notification visual impression qualification: covered-by-overlay from qualifying · case 05

The covered-by-overlay event leaves a notification in reporting instead of occluded.

Notification interfaces◈ Members↗
FA-34926

Notification visual impression qualification: overlay-removed from occluded · case 01

The overlay-removed event leaves a notification in counted instead of qualifying.

Notification interfaces● Open access↗
FA-34927

Notification visual impression qualification: overlay-removed from occluded · case 02

The overlay-removed event leaves a notification in counted instead of qualifying.

Notification interfaces◈ Members↗
FA-34928

Notification visual impression qualification: overlay-removed from occluded · case 03

The overlay-removed event leaves a notification in counted instead of qualifying.

Notification interfaces◈ Members↗
FA-34929

Notification visual impression qualification: overlay-removed from occluded · case 04

The overlay-removed event leaves a notification in counted instead of qualifying.

Notification interfaces◈ Members↗
FA-34930

Notification visual impression qualification: overlay-removed from occluded · case 05

The overlay-removed event leaves a notification in counted instead of qualifying.

Notification interfaces◈ Members↗
FA-34931

Notification visual impression qualification: reenter-viewport from counted · case 01

The reenter-viewport event leaves a notification in qualifying instead of counted.

Notification interfaces● Open access↗
FA-34932

Notification visual impression qualification: reenter-viewport from counted · case 02

The reenter-viewport event leaves a notification in qualifying instead of counted.

Notification interfaces◈ Members↗
FA-34933

Notification visual impression qualification: reenter-viewport from counted · case 03

The reenter-viewport event leaves a notification in qualifying instead of counted.

Notification interfaces◈ Members↗
FA-34934

Notification visual impression qualification: reenter-viewport from counted · case 04

The reenter-viewport event leaves a notification in qualifying instead of counted.

Notification interfaces◈ Members↗
FA-34935

Notification visual impression qualification: reenter-viewport from counted · case 05

The reenter-viewport event leaves a notification in qualifying instead of counted.

Notification interfaces◈ Members↗
FA-34936

Notification visual impression qualification: leaves-viewport from reporting · case 01

The leaves-viewport event leaves a notification in offscreen instead of reporting.

Notification interfaces● Open access↗
FA-34937

Notification visual impression qualification: leaves-viewport from reporting · case 02

The leaves-viewport event leaves a notification in offscreen instead of reporting.

Notification interfaces◈ Members↗
FA-34938

Notification visual impression qualification: leaves-viewport from reporting · case 03

The leaves-viewport event leaves a notification in offscreen instead of reporting.

Notification interfaces◈ Members↗
FA-34939

Notification visual impression qualification: leaves-viewport from reporting · case 04

The leaves-viewport event leaves a notification in offscreen instead of reporting.

Notification interfaces◈ Members↗
FA-34940

Notification visual impression qualification: leaves-viewport from reporting · case 05

The leaves-viewport event leaves a notification in offscreen instead of reporting.

Notification interfaces◈ Members↗
FA-34941

Notification content revision review: revision-two-arrives from revision-one-read · case 01

The revision-two-arrives event leaves a notification in revision-one-read instead of revision-two-unread.

Notification interfaces● Open access↗
FA-34942

Notification content revision review: revision-two-arrives from revision-one-read · case 02

The revision-two-arrives event leaves a notification in revision-one-read instead of revision-two-unread.

Notification interfaces◈ Members↗
FA-34943

Notification content revision review: revision-two-arrives from revision-one-read · case 03

The revision-two-arrives event leaves a notification in revision-one-read instead of revision-two-unread.

Notification interfaces◈ Members↗
FA-34944

Notification content revision review: revision-two-arrives from revision-one-read · case 04

The revision-two-arrives event leaves a notification in revision-one-read instead of revision-two-unread.

Notification interfaces◈ Members↗
FA-34945

Notification content revision review: revision-two-arrives from revision-one-read · case 05

The revision-two-arrives event leaves a notification in revision-one-read instead of revision-two-unread.

Notification interfaces◈ Members↗
FA-34946

Notification content revision review: open-revision from revision-two-unread · case 01

The open-revision event leaves a notification in revision-two-read instead of revision-two-preview.

Notification interfaces● Open access↗
FA-34947

Notification content revision review: open-revision from revision-two-unread · case 02

The open-revision event leaves a notification in revision-two-read instead of revision-two-preview.

Notification interfaces◈ Members↗
FA-34948

Notification content revision review: open-revision from revision-two-unread · case 03

The open-revision event leaves a notification in revision-two-read instead of revision-two-preview.

Notification interfaces◈ Members↗
FA-34949

Notification content revision review: open-revision from revision-two-unread · case 04

The open-revision event leaves a notification in revision-two-read instead of revision-two-preview.

Notification interfaces◈ Members↗
FA-34950

Notification content revision review: open-revision from revision-two-unread · case 05

The open-revision event leaves a notification in revision-two-read instead of revision-two-preview.

Notification interfaces◈ Members↗
FA-34951

Notification content revision review: ack-revision from revision-two-preview · case 01

The ack-revision event leaves a notification in revision-one-read instead of revision-two-read.

Notification interfaces● Open access↗
FA-34952

Notification content revision review: ack-revision from revision-two-preview · case 02

The ack-revision event leaves a notification in revision-one-read instead of revision-two-read.

Notification interfaces◈ Members↗
FA-34953

Notification content revision review: ack-revision from revision-two-preview · case 03

The ack-revision event leaves a notification in revision-one-read instead of revision-two-read.

Notification interfaces◈ Members↗
FA-34954

Notification content revision review: ack-revision from revision-two-preview · case 04

The ack-revision event leaves a notification in revision-one-read instead of revision-two-read.

Notification interfaces◈ Members↗
FA-34955

Notification content revision review: ack-revision from revision-two-preview · case 05

The ack-revision event leaves a notification in revision-one-read instead of revision-two-read.

Notification interfaces◈ Members↗
FA-34956

Notification content revision review: revision-three-arrives from revision-two-preview · case 01

The revision-three-arrives event leaves a notification in revision-two-read instead of revision-three-pending-review.

Notification interfaces● Open access↗
FA-34957

Notification content revision review: revision-three-arrives from revision-two-preview · case 02

The revision-three-arrives event leaves a notification in revision-two-read instead of revision-three-pending-review.

Notification interfaces◈ Members↗
FA-34958

Notification content revision review: revision-three-arrives from revision-two-preview · case 03

The revision-three-arrives event leaves a notification in revision-two-read instead of revision-three-pending-review.

Notification interfaces◈ Members↗
FA-34959

Notification content revision review: revision-three-arrives from revision-two-preview · case 04

The revision-three-arrives event leaves a notification in revision-two-read instead of revision-three-pending-review.

Notification interfaces◈ Members↗
FA-34960

Notification content revision review: revision-three-arrives from revision-two-preview · case 05

The revision-three-arrives event leaves a notification in revision-two-read instead of revision-three-pending-review.

Notification interfaces◈ Members↗
FA-34961

Notification content revision review: accept-update from revision-three-pending-review · case 01

The accept-update event leaves a notification in revision-three-read instead of revision-three-preview.

Notification interfaces● Open access↗
FA-34962

Notification content revision review: accept-update from revision-three-pending-review · case 02

The accept-update event leaves a notification in revision-three-read instead of revision-three-preview.

Notification interfaces◈ Members↗
FA-34963

Notification content revision review: accept-update from revision-three-pending-review · case 03

The accept-update event leaves a notification in revision-three-read instead of revision-three-preview.

Notification interfaces◈ Members↗
FA-34964

Notification content revision review: accept-update from revision-three-pending-review · case 04

The accept-update event leaves a notification in revision-three-read instead of revision-three-preview.

Notification interfaces◈ Members↗
FA-34965

Notification content revision review: accept-update from revision-three-pending-review · case 05

The accept-update event leaves a notification in revision-three-read instead of revision-three-preview.

Notification interfaces◈ Members↗
FA-34966

Notification content revision review: ack-revision from revision-three-preview · case 01

The ack-revision event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces● Open access↗
FA-34967

Notification content revision review: ack-revision from revision-three-preview · case 02

The ack-revision event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces◈ Members↗
FA-34968

Notification content revision review: ack-revision from revision-three-preview · case 03

The ack-revision event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces◈ Members↗
FA-34969

Notification content revision review: ack-revision from revision-three-preview · case 04

The ack-revision event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces◈ Members↗
FA-34970

Notification content revision review: ack-revision from revision-three-preview · case 05

The ack-revision event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces◈ Members↗
FA-34971

Notification content revision review: late-revision-two from revision-three-read · case 01

The late-revision-two event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces● Open access↗
FA-34972

Notification content revision review: late-revision-two from revision-three-read · case 02

The late-revision-two event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces◈ Members↗
FA-34973

Notification content revision review: late-revision-two from revision-three-read · case 03

The late-revision-two event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces◈ Members↗
FA-34974

Notification content revision review: late-revision-two from revision-three-read · case 04

The late-revision-two event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces◈ Members↗
FA-34975

Notification content revision review: late-revision-two from revision-three-read · case 05

The late-revision-two event leaves a notification in revision-two-read instead of revision-three-read.

Notification interfaces◈ Members↗
FA-34976

Notification content revision review: close-preview from revision-three-pending-review · case 01

The close-preview event leaves a notification in revision-three-read instead of revision-three-unread.

Notification interfaces● Open access↗
FA-34977

Notification content revision review: close-preview from revision-three-pending-review · case 02

The close-preview event leaves a notification in revision-three-read instead of revision-three-unread.

Notification interfaces◈ Members↗
FA-34978

Notification content revision review: close-preview from revision-three-pending-review · case 03

The close-preview event leaves a notification in revision-three-read instead of revision-three-unread.

Notification interfaces◈ Members↗
FA-34979

Notification content revision review: close-preview from revision-three-pending-review · case 04

The close-preview event leaves a notification in revision-three-read instead of revision-three-unread.

Notification interfaces◈ Members↗
FA-34980

Notification content revision review: close-preview from revision-three-pending-review · case 05

The close-preview event leaves a notification in revision-three-read instead of revision-three-unread.

Notification interfaces◈ Members↗
FA-34981

Notification content revision review: open-revision from revision-three-unread · case 01

The open-revision event leaves a notification in revision-two-preview instead of revision-three-preview.

Notification interfaces● Open access↗
FA-34982

Notification content revision review: open-revision from revision-three-unread · case 02

The open-revision event leaves a notification in revision-two-preview instead of revision-three-preview.

Notification interfaces◈ Members↗
FA-34983

Notification content revision review: open-revision from revision-three-unread · case 03

The open-revision event leaves a notification in revision-two-preview instead of revision-three-preview.

Notification interfaces◈ Members↗
FA-34984

Notification content revision review: open-revision from revision-three-unread · case 04

The open-revision event leaves a notification in revision-two-preview instead of revision-three-preview.

Notification interfaces◈ Members↗
FA-34985

Notification content revision review: open-revision from revision-three-unread · case 05

The open-revision event leaves a notification in revision-two-preview instead of revision-three-preview.

Notification interfaces◈ Members↗
FA-34986

Notification content revision review: revision-withdrawn from revision-two-unread · case 01

The revision-withdrawn event leaves a notification in revision-two-read instead of withdrawn.

Notification interfaces● Open access↗
FA-34987

Notification content revision review: revision-withdrawn from revision-two-unread · case 02

The revision-withdrawn event leaves a notification in revision-two-read instead of withdrawn.

Notification interfaces◈ Members↗
FA-34988

Notification content revision review: revision-withdrawn from revision-two-unread · case 03

The revision-withdrawn event leaves a notification in revision-two-read instead of withdrawn.

Notification interfaces◈ Members↗
FA-34989

Notification content revision review: revision-withdrawn from revision-two-unread · case 04

The revision-withdrawn event leaves a notification in revision-two-read instead of withdrawn.

Notification interfaces◈ Members↗
FA-34990

Notification content revision review: revision-withdrawn from revision-two-unread · case 05

The revision-withdrawn event leaves a notification in revision-two-read instead of withdrawn.

Notification interfaces◈ Members↗
FA-34991

Notification target opening feedback: open-target from actionable · case 01

The open-target event leaves a notification in opened instead of resolving.

Notification interfaces● Open access↗
FA-34992

Notification target opening feedback: open-target from actionable · case 02

The open-target event leaves a notification in opened instead of resolving.

Notification interfaces◈ Members↗
FA-34993

Notification target opening feedback: open-target from actionable · case 03

The open-target event leaves a notification in opened instead of resolving.

Notification interfaces◈ Members↗
FA-34994

Notification target opening feedback: open-target from actionable · case 04

The open-target event leaves a notification in opened instead of resolving.

Notification interfaces◈ Members↗
FA-34995

Notification target opening feedback: open-target from actionable · case 05

The open-target event leaves a notification in opened instead of resolving.

Notification interfaces◈ Members↗
FA-34996

Notification target opening feedback: target-found from resolving · case 01

The target-found event leaves a notification in opened instead of navigating.

Notification interfaces● Open access↗
FA-34997

Notification target opening feedback: target-found from resolving · case 02

The target-found event leaves a notification in opened instead of navigating.

Notification interfaces◈ Members↗
FA-34998

Notification target opening feedback: target-found from resolving · case 03

The target-found event leaves a notification in opened instead of navigating.

Notification interfaces◈ Members↗
FA-34999

Notification target opening feedback: target-found from resolving · case 04

The target-found event leaves a notification in opened instead of navigating.

Notification interfaces◈ Members↗
FA-35000

Notification target opening feedback: target-found from resolving · case 05

The target-found event leaves a notification in opened instead of navigating.

Notification interfaces◈ 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 ↗