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

Long-running notification progress: pause-accepted from pause-pending · case 01

The pause-accepted event leaves a notification in running instead of paused.

Notification interfaces● Open access↗
FA-34402

Long-running notification progress: pause-accepted from pause-pending · case 02

The pause-accepted event leaves a notification in running instead of paused.

Notification interfaces◈ Members↗
FA-34403

Long-running notification progress: pause-accepted from pause-pending · case 03

The pause-accepted event leaves a notification in running instead of paused.

Notification interfaces◈ Members↗
FA-34404

Long-running notification progress: pause-accepted from pause-pending · case 04

The pause-accepted event leaves a notification in running instead of paused.

Notification interfaces◈ Members↗
FA-34405

Long-running notification progress: pause-accepted from pause-pending · case 05

The pause-accepted event leaves a notification in running instead of paused.

Notification interfaces◈ Members↗
FA-34406

Long-running notification progress: pause-rejected from pause-pending · case 01

The pause-rejected event leaves a notification in paused instead of running.

Notification interfaces● Open access↗
FA-34407

Long-running notification progress: pause-rejected from pause-pending · case 02

The pause-rejected event leaves a notification in paused instead of running.

Notification interfaces◈ Members↗
FA-34408

Long-running notification progress: pause-rejected from pause-pending · case 03

The pause-rejected event leaves a notification in paused instead of running.

Notification interfaces◈ Members↗
FA-34409

Long-running notification progress: pause-rejected from pause-pending · case 04

The pause-rejected event leaves a notification in paused instead of running.

Notification interfaces◈ Members↗
FA-34410

Long-running notification progress: pause-rejected from pause-pending · case 05

The pause-rejected event leaves a notification in paused instead of running.

Notification interfaces◈ Members↗
FA-34411

Long-running notification progress: resume-click from paused · case 01

The resume-click event leaves a notification in running instead of resume-pending.

Notification interfaces● Open access↗
FA-34412

Long-running notification progress: resume-click from paused · case 02

The resume-click event leaves a notification in running instead of resume-pending.

Notification interfaces◈ Members↗
FA-34413

Long-running notification progress: resume-click from paused · case 03

The resume-click event leaves a notification in running instead of resume-pending.

Notification interfaces◈ Members↗
FA-34414

Long-running notification progress: resume-click from paused · case 04

The resume-click event leaves a notification in running instead of resume-pending.

Notification interfaces◈ Members↗
FA-34415

Long-running notification progress: resume-click from paused · case 05

The resume-click event leaves a notification in running instead of resume-pending.

Notification interfaces◈ Members↗
FA-34416

Long-running notification progress: resume-accepted from resume-pending · case 01

The resume-accepted event leaves a notification in paused instead of running.

Notification interfaces● Open access↗
FA-34417

Long-running notification progress: resume-accepted from resume-pending · case 02

The resume-accepted event leaves a notification in paused instead of running.

Notification interfaces◈ Members↗
FA-34418

Long-running notification progress: resume-accepted from resume-pending · case 03

The resume-accepted event leaves a notification in paused instead of running.

Notification interfaces◈ Members↗
FA-34419

Long-running notification progress: resume-accepted from resume-pending · case 04

The resume-accepted event leaves a notification in paused instead of running.

Notification interfaces◈ Members↗
FA-34420

Long-running notification progress: resume-accepted from resume-pending · case 05

The resume-accepted event leaves a notification in paused instead of running.

Notification interfaces◈ Members↗
FA-34421

Long-running notification progress: work-complete from running · case 01

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces● Open access↗
FA-34422

Long-running notification progress: work-complete from running · case 02

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces◈ Members↗
FA-34423

Long-running notification progress: work-complete from running · case 03

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces◈ Members↗
FA-34424

Long-running notification progress: work-complete from running · case 04

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces◈ Members↗
FA-34425

Long-running notification progress: work-complete from running · case 05

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces◈ Members↗
FA-34426

Long-running notification progress: work-failed from running · case 01

The work-failed event leaves a notification in complete instead of failed.

Notification interfaces● Open access↗
FA-34427

Long-running notification progress: work-failed from running · case 02

The work-failed event leaves a notification in complete instead of failed.

Notification interfaces◈ Members↗
FA-34428

Long-running notification progress: work-failed from running · case 03

The work-failed event leaves a notification in complete instead of failed.

Notification interfaces◈ Members↗
FA-34429

Long-running notification progress: work-failed from running · case 04

The work-failed event leaves a notification in complete instead of failed.

Notification interfaces◈ Members↗
FA-34430

Long-running notification progress: work-failed from running · case 05

The work-failed event leaves a notification in complete instead of failed.

Notification interfaces◈ Members↗
FA-34431

Long-running notification progress: late-progress from complete · case 01

The late-progress event leaves a notification in running instead of complete.

Notification interfaces● Open access↗
FA-34432

Long-running notification progress: late-progress from complete · case 02

The late-progress event leaves a notification in running instead of complete.

Notification interfaces◈ Members↗
FA-34433

Long-running notification progress: late-progress from complete · case 03

The late-progress event leaves a notification in running instead of complete.

Notification interfaces◈ Members↗
FA-34434

Long-running notification progress: late-progress from complete · case 04

The late-progress event leaves a notification in running instead of complete.

Notification interfaces◈ Members↗
FA-34435

Long-running notification progress: late-progress from complete · case 05

The late-progress event leaves a notification in running instead of complete.

Notification interfaces◈ Members↗
FA-34436

Long-running notification progress: work-complete from paused · case 01

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces● Open access↗
FA-34437

Long-running notification progress: work-complete from paused · case 02

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces◈ Members↗
FA-34438

Long-running notification progress: work-complete from paused · case 03

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces◈ Members↗
FA-34439

Long-running notification progress: work-complete from paused · case 04

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces◈ Members↗
FA-34440

Long-running notification progress: work-complete from paused · case 05

The work-complete event leaves a notification in paused instead of complete.

Notification interfaces◈ Members↗
FA-34441

Banner to inbox promotion: retain-in-inbox from banner · case 01

The retain-in-inbox event leaves a notification in inbox-only instead of saving.

Notification interfaces● Open access↗
FA-34442

Banner to inbox promotion: retain-in-inbox from banner · case 02

The retain-in-inbox event leaves a notification in inbox-only instead of saving.

Notification interfaces◈ Members↗
FA-34443

Banner to inbox promotion: retain-in-inbox from banner · case 03

The retain-in-inbox event leaves a notification in inbox-only instead of saving.

Notification interfaces◈ Members↗
FA-34444

Banner to inbox promotion: retain-in-inbox from banner · case 04

The retain-in-inbox event leaves a notification in inbox-only instead of saving.

Notification interfaces◈ Members↗
FA-34445

Banner to inbox promotion: retain-in-inbox from banner · case 05

The retain-in-inbox event leaves a notification in inbox-only instead of saving.

Notification interfaces◈ Members↗
FA-34446

Banner to inbox promotion: save-success from saving · case 01

The save-success event leaves a notification in banner instead of both.

Notification interfaces● Open access↗
FA-34447

Banner to inbox promotion: save-success from saving · case 02

The save-success event leaves a notification in banner instead of both.

Notification interfaces◈ Members↗
FA-34448

Banner to inbox promotion: save-success from saving · case 03

The save-success event leaves a notification in banner instead of both.

Notification interfaces◈ Members↗
FA-34449

Banner to inbox promotion: save-success from saving · case 04

The save-success event leaves a notification in banner instead of both.

Notification interfaces◈ Members↗
FA-34450

Banner to inbox promotion: save-success from saving · case 05

The save-success event leaves a notification in banner instead of both.

Notification interfaces◈ Members↗
FA-34451

Banner to inbox promotion: save-failure from saving · case 01

The save-failure event leaves a notification in inbox-only instead of save-error.

Notification interfaces● Open access↗
FA-34452

Banner to inbox promotion: save-failure from saving · case 02

The save-failure event leaves a notification in inbox-only instead of save-error.

Notification interfaces◈ Members↗
FA-34453

Banner to inbox promotion: save-failure from saving · case 03

The save-failure event leaves a notification in inbox-only instead of save-error.

Notification interfaces◈ Members↗
FA-34454

Banner to inbox promotion: save-failure from saving · case 04

The save-failure event leaves a notification in inbox-only instead of save-error.

Notification interfaces◈ Members↗
FA-34455

Banner to inbox promotion: save-failure from saving · case 05

The save-failure event leaves a notification in inbox-only instead of save-error.

Notification interfaces◈ Members↗
FA-34456

Banner to inbox promotion: banner-exposure-end from both · case 01

The banner-exposure-end event leaves a notification in gone instead of inbox-only.

Notification interfaces● Open access↗
FA-34457

Banner to inbox promotion: banner-exposure-end from both · case 02

The banner-exposure-end event leaves a notification in gone instead of inbox-only.

Notification interfaces◈ Members↗
FA-34458

Banner to inbox promotion: banner-exposure-end from both · case 03

The banner-exposure-end event leaves a notification in gone instead of inbox-only.

Notification interfaces◈ Members↗
FA-34459

Banner to inbox promotion: banner-exposure-end from both · case 04

The banner-exposure-end event leaves a notification in gone instead of inbox-only.

Notification interfaces◈ Members↗
FA-34460

Banner to inbox promotion: banner-exposure-end from both · case 05

The banner-exposure-end event leaves a notification in gone instead of inbox-only.

Notification interfaces◈ Members↗
FA-34461

Banner to inbox promotion: retry-retention from save-error · case 01

The retry-retention event leaves a notification in both instead of saving.

Notification interfaces● Open access↗
FA-34462

Banner to inbox promotion: retry-retention from save-error · case 02

The retry-retention event leaves a notification in both instead of saving.

Notification interfaces◈ Members↗
FA-34463

Banner to inbox promotion: retry-retention from save-error · case 03

The retry-retention event leaves a notification in both instead of saving.

Notification interfaces◈ Members↗
FA-34464

Banner to inbox promotion: retry-retention from save-error · case 04

The retry-retention event leaves a notification in both instead of saving.

Notification interfaces◈ Members↗
FA-34465

Banner to inbox promotion: retry-retention from save-error · case 05

The retry-retention event leaves a notification in both instead of saving.

Notification interfaces◈ Members↗
FA-34466

Banner to inbox promotion: banner-exposure-end from saving · case 01

The banner-exposure-end event leaves a notification in gone instead of saving-without-banner.

Notification interfaces● Open access↗
FA-34467

Banner to inbox promotion: banner-exposure-end from saving · case 02

The banner-exposure-end event leaves a notification in gone instead of saving-without-banner.

Notification interfaces◈ Members↗
FA-34468

Banner to inbox promotion: banner-exposure-end from saving · case 03

The banner-exposure-end event leaves a notification in gone instead of saving-without-banner.

Notification interfaces◈ Members↗
FA-34469

Banner to inbox promotion: banner-exposure-end from saving · case 04

The banner-exposure-end event leaves a notification in gone instead of saving-without-banner.

Notification interfaces◈ Members↗
FA-34470

Banner to inbox promotion: banner-exposure-end from saving · case 05

The banner-exposure-end event leaves a notification in gone instead of saving-without-banner.

Notification interfaces◈ Members↗
FA-34471

Banner to inbox promotion: save-success from saving-without-banner · case 01

The save-success event leaves a notification in both instead of inbox-only.

Notification interfaces● Open access↗
FA-34472

Banner to inbox promotion: save-success from saving-without-banner · case 02

The save-success event leaves a notification in both instead of inbox-only.

Notification interfaces◈ Members↗
FA-34473

Banner to inbox promotion: save-success from saving-without-banner · case 03

The save-success event leaves a notification in both instead of inbox-only.

Notification interfaces◈ Members↗
FA-34474

Banner to inbox promotion: save-success from saving-without-banner · case 04

The save-success event leaves a notification in both instead of inbox-only.

Notification interfaces◈ Members↗
FA-34475

Banner to inbox promotion: save-success from saving-without-banner · case 05

The save-success event leaves a notification in both instead of inbox-only.

Notification interfaces◈ Members↗
FA-34476

Banner to inbox promotion: save-failure from saving-without-banner · case 01

The save-failure event leaves a notification in gone instead of recovery-banner.

Notification interfaces● Open access↗
FA-34477

Banner to inbox promotion: save-failure from saving-without-banner · case 02

The save-failure event leaves a notification in gone instead of recovery-banner.

Notification interfaces◈ Members↗
FA-34478

Banner to inbox promotion: save-failure from saving-without-banner · case 03

The save-failure event leaves a notification in gone instead of recovery-banner.

Notification interfaces◈ Members↗
FA-34479

Banner to inbox promotion: save-failure from saving-without-banner · case 04

The save-failure event leaves a notification in gone instead of recovery-banner.

Notification interfaces◈ Members↗
FA-34480

Banner to inbox promotion: save-failure from saving-without-banner · case 05

The save-failure event leaves a notification in gone instead of recovery-banner.

Notification interfaces◈ Members↗
FA-34481

Banner to inbox promotion: show-banner-again from inbox-only · case 01

The show-banner-again event leaves a notification in both instead of repromoting.

Notification interfaces● Open access↗
FA-34482

Banner to inbox promotion: show-banner-again from inbox-only · case 02

The show-banner-again event leaves a notification in both instead of repromoting.

Notification interfaces◈ Members↗
FA-34483

Banner to inbox promotion: show-banner-again from inbox-only · case 03

The show-banner-again event leaves a notification in both instead of repromoting.

Notification interfaces◈ Members↗
FA-34484

Banner to inbox promotion: show-banner-again from inbox-only · case 04

The show-banner-again event leaves a notification in both instead of repromoting.

Notification interfaces◈ Members↗
FA-34485

Banner to inbox promotion: show-banner-again from inbox-only · case 05

The show-banner-again event leaves a notification in both instead of repromoting.

Notification interfaces◈ Members↗
FA-34486

Banner to inbox promotion: banner-mounted from repromoting · case 01

The banner-mounted event leaves a notification in inbox-only instead of both.

Notification interfaces● Open access↗
FA-34487

Banner to inbox promotion: banner-mounted from repromoting · case 02

The banner-mounted event leaves a notification in inbox-only instead of both.

Notification interfaces◈ Members↗
FA-34488

Banner to inbox promotion: banner-mounted from repromoting · case 03

The banner-mounted event leaves a notification in inbox-only instead of both.

Notification interfaces◈ Members↗
FA-34489

Banner to inbox promotion: banner-mounted from repromoting · case 04

The banner-mounted event leaves a notification in inbox-only instead of both.

Notification interfaces◈ Members↗
FA-34490

Banner to inbox promotion: banner-mounted from repromoting · case 05

The banner-mounted event leaves a notification in inbox-only instead of both.

Notification interfaces◈ Members↗
FA-34491

Swipe-to-dismiss notification feedback: drag-start from resting · case 01

The drag-start event leaves a notification in dismissed instead of dragging.

Notification interfaces● Open access↗
FA-34492

Swipe-to-dismiss notification feedback: drag-start from resting · case 02

The drag-start event leaves a notification in dismissed instead of dragging.

Notification interfaces◈ Members↗
FA-34493

Swipe-to-dismiss notification feedback: drag-start from resting · case 03

The drag-start event leaves a notification in dismissed instead of dragging.

Notification interfaces◈ Members↗
FA-34494

Swipe-to-dismiss notification feedback: drag-start from resting · case 04

The drag-start event leaves a notification in dismissed instead of dragging.

Notification interfaces◈ Members↗
FA-34495

Swipe-to-dismiss notification feedback: drag-start from resting · case 05

The drag-start event leaves a notification in dismissed instead of dragging.

Notification interfaces◈ Members↗
FA-34496

Swipe-to-dismiss notification feedback: below-threshold-release from dragging · case 01

The below-threshold-release event leaves a notification in dismissed instead of returning.

Notification interfaces● Open access↗
FA-34497

Swipe-to-dismiss notification feedback: below-threshold-release from dragging · case 02

The below-threshold-release event leaves a notification in dismissed instead of returning.

Notification interfaces◈ Members↗
FA-34498

Swipe-to-dismiss notification feedback: below-threshold-release from dragging · case 03

The below-threshold-release event leaves a notification in dismissed instead of returning.

Notification interfaces◈ Members↗
FA-34499

Swipe-to-dismiss notification feedback: below-threshold-release from dragging · case 04

The below-threshold-release event leaves a notification in dismissed instead of returning.

Notification interfaces◈ Members↗
FA-34500

Swipe-to-dismiss notification feedback: below-threshold-release from dragging · case 05

The below-threshold-release event leaves a notification in dismissed instead of returning.

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 ↗