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

Fraction word loses its byte place value · case 01

The decoded time state disagrees with the explicit regression oracle for fraction.

Time representation● Open access↗
FA-17402

Fraction word loses its byte place value · case 02

The decoded time state disagrees with the explicit regression oracle for fraction.

Time representation◈ Members↗
FA-17403

Fraction word loses its byte place value · case 03

The decoded time state disagrees with the explicit regression oracle for fraction.

Time representation◈ Members↗
FA-17404

Fraction word loses its byte place value · case 04

The decoded time state disagrees with the explicit regression oracle for fraction.

Time representation◈ Members↗
FA-17405

Fraction word loses its byte place value · case 05

The decoded time state disagrees with the explicit regression oracle for fraction.

Time representation◈ Members↗
FA-17406

Fraction validator confuses the reserved endpoint · case 01

The decoded time state disagrees with the explicit regression oracle for valid.

Time representation● Open access↗
FA-17407

Fraction validator confuses the reserved endpoint · case 02

The decoded time state disagrees with the explicit regression oracle for valid.

Time representation◈ Members↗
FA-17408

Fraction validator confuses the reserved endpoint · case 03

The decoded time state disagrees with the explicit regression oracle for valid.

Time representation◈ Members↗
FA-17409

Fraction validator confuses the reserved endpoint · case 04

The decoded time state disagrees with the explicit regression oracle for valid.

Time representation◈ Members↗
FA-17410

Fraction validator confuses the reserved endpoint · case 05

The decoded time state disagrees with the explicit regression oracle for valid.

Time representation◈ Members↗
FA-17411

Fraction offset is subtracted from signed whole seconds · case 01

The decoded time state disagrees with the explicit regression oracle for total.

Time representation● Open access↗
FA-17412

Fraction offset is subtracted from signed whole seconds · case 02

The decoded time state disagrees with the explicit regression oracle for total.

Time representation◈ Members↗
FA-17413

Fraction offset is subtracted from signed whole seconds · case 03

The decoded time state disagrees with the explicit regression oracle for total.

Time representation◈ Members↗
FA-17414

Fraction offset is subtracted from signed whole seconds · case 04

The decoded time state disagrees with the explicit regression oracle for total.

Time representation◈ Members↗
FA-17415

Fraction offset is subtracted from signed whole seconds · case 05

The decoded time state disagrees with the explicit regression oracle for total.

Time representation◈ Members↗
FA-17416

Timestamp sign marker misses the minimum code or negative subsecond instants · case 01

The decoded time state disagrees with the explicit regression oracle for negative.

Time representation● Open access↗
FA-17417

Timestamp sign marker misses the minimum code or negative subsecond instants · case 02

The decoded time state disagrees with the explicit regression oracle for negative.

Time representation◈ Members↗
FA-17418

Timestamp sign marker misses the minimum code or negative subsecond instants · case 03

The decoded time state disagrees with the explicit regression oracle for negative.

Time representation◈ Members↗
FA-17419

Timestamp sign marker misses the minimum code or negative subsecond instants · case 04

The decoded time state disagrees with the explicit regression oracle for negative.

Time representation◈ Members↗
FA-17420

Timestamp sign marker misses the minimum code or negative subsecond instants · case 05

The decoded time state disagrees with the explicit regression oracle for negative.

Time representation◈ Members↗
FA-17421

Magnitude fails to complement a negative fractional instant · case 01

The decoded time state disagrees with the explicit regression oracle for magnitude.

Time representation● Open access↗
FA-17422

Magnitude fails to complement a negative fractional instant · case 02

The decoded time state disagrees with the explicit regression oracle for magnitude.

Time representation◈ Members↗
FA-17423

Magnitude fails to complement a negative fractional instant · case 03

The decoded time state disagrees with the explicit regression oracle for magnitude.

Time representation◈ Members↗
FA-17424

Magnitude fails to complement a negative fractional instant · case 04

The decoded time state disagrees with the explicit regression oracle for magnitude.

Time representation◈ Members↗
FA-17425

Magnitude fails to complement a negative fractional instant · case 05

The decoded time state disagrees with the explicit regression oracle for magnitude.

Time representation◈ Members↗
FA-17426

Whole display field uses residue or upward rounding · case 01

The decoded time state disagrees with the explicit regression oracle for whole.

Time representation● Open access↗
FA-17427

Whole display field uses residue or upward rounding · case 02

The decoded time state disagrees with the explicit regression oracle for whole.

Time representation◈ Members↗
FA-17428

Whole display field uses residue or upward rounding · case 03

The decoded time state disagrees with the explicit regression oracle for whole.

Time representation◈ Members↗
FA-17429

Whole display field uses residue or upward rounding · case 04

The decoded time state disagrees with the explicit regression oracle for whole.

Time representation◈ Members↗
FA-17430

Whole display field uses residue or upward rounding · case 05

The decoded time state disagrees with the explicit regression oracle for whole.

Time representation◈ Members↗
FA-17431

Negative instant fractional display is copied from wire fraction · case 01

The decoded time state disagrees with the explicit regression oracle for part.

Time representation● Open access↗
FA-17432

Negative instant fractional display is copied from wire fraction · case 02

The decoded time state disagrees with the explicit regression oracle for part.

Time representation◈ Members↗
FA-17433

Negative instant fractional display is copied from wire fraction · case 03

The decoded time state disagrees with the explicit regression oracle for part.

Time representation◈ Members↗
FA-17434

Negative instant fractional display is copied from wire fraction · case 04

The decoded time state disagrees with the explicit regression oracle for part.

Time representation◈ Members↗
FA-17435

Negative instant fractional display is copied from wire fraction · case 05

The decoded time state disagrees with the explicit regression oracle for part.

Time representation◈ Members↗
FA-17436

One-tick increment misses fractional carry · case 01

The decoded time state disagrees with the explicit regression oracle for next_second.

Time representation● Open access↗
FA-17437

One-tick increment misses fractional carry · case 02

The decoded time state disagrees with the explicit regression oracle for next_second.

Time representation◈ Members↗
FA-17438

One-tick increment misses fractional carry · case 03

The decoded time state disagrees with the explicit regression oracle for next_second.

Time representation◈ Members↗
FA-17439

One-tick increment misses fractional carry · case 04

The decoded time state disagrees with the explicit regression oracle for next_second.

Time representation◈ Members↗
FA-17440

One-tick increment misses fractional carry · case 05

The decoded time state disagrees with the explicit regression oracle for next_second.

Time representation◈ Members↗
FA-17441

Pending overflow is assigned to a pre-wrap capture · case 01

The decoded time state disagrees with the explicit regression oracle for epoch.

Time representation● Open access↗
FA-17442

Pending overflow is assigned to a pre-wrap capture · case 02

The decoded time state disagrees with the explicit regression oracle for epoch.

Time representation◈ Members↗
FA-17443

Pending overflow is assigned to a pre-wrap capture · case 03

The decoded time state disagrees with the explicit regression oracle for epoch.

Time representation◈ Members↗
FA-17444

Pending overflow is assigned to a pre-wrap capture · case 04

The decoded time state disagrees with the explicit regression oracle for epoch.

Time representation◈ Members↗
FA-17445

Pending overflow is assigned to a pre-wrap capture · case 05

The decoded time state disagrees with the explicit regression oracle for epoch.

Time representation◈ Members↗
FA-17446

Serviced overflow is not backed out for an earlier high capture · case 01

The decoded time state disagrees with the explicit regression oracle for previous_epoch.

Time representation● Open access↗
FA-17447

Serviced overflow is not backed out for an earlier high capture · case 02

The decoded time state disagrees with the explicit regression oracle for previous_epoch.

Time representation◈ Members↗
FA-17448

Serviced overflow is not backed out for an earlier high capture · case 03

The decoded time state disagrees with the explicit regression oracle for previous_epoch.

Time representation◈ Members↗
FA-17449

Serviced overflow is not backed out for an earlier high capture · case 04

The decoded time state disagrees with the explicit regression oracle for previous_epoch.

Time representation◈ Members↗
FA-17450

Serviced overflow is not backed out for an earlier high capture · case 05

The decoded time state disagrees with the explicit regression oracle for previous_epoch.

Time representation◈ Members↗
FA-17451

Expanded capture loses the high counter bit · case 01

The decoded time state disagrees with the explicit regression oracle for expanded.

Time representation● Open access↗
FA-17452

Expanded capture loses the high counter bit · case 02

The decoded time state disagrees with the explicit regression oracle for expanded.

Time representation◈ Members↗
FA-17453

Expanded capture loses the high counter bit · case 03

The decoded time state disagrees with the explicit regression oracle for expanded.

Time representation◈ Members↗
FA-17454

Expanded capture loses the high counter bit · case 04

The decoded time state disagrees with the explicit regression oracle for expanded.

Time representation◈ Members↗
FA-17455

Expanded capture loses the high counter bit · case 05

The decoded time state disagrees with the explicit regression oracle for expanded.

Time representation◈ Members↗
FA-17456

Interval silently discards complete hardware epochs · case 01

The decoded time state disagrees with the explicit regression oracle for delta.

Time representation● Open access↗
FA-17457

Interval silently discards complete hardware epochs · case 02

The decoded time state disagrees with the explicit regression oracle for delta.

Time representation◈ Members↗
FA-17458

Interval silently discards complete hardware epochs · case 03

The decoded time state disagrees with the explicit regression oracle for delta.

Time representation◈ Members↗
FA-17459

Interval silently discards complete hardware epochs · case 04

The decoded time state disagrees with the explicit regression oracle for delta.

Time representation◈ Members↗
FA-17460

Interval silently discards complete hardware epochs · case 05

The decoded time state disagrees with the explicit regression oracle for delta.

Time representation◈ Members↗
FA-17461

Coincident or reordered capture has incorrect forward classification · case 01

The decoded time state disagrees with the explicit regression oracle for forward.

Time representation● Open access↗
FA-17462

Coincident or reordered capture has incorrect forward classification · case 02

The decoded time state disagrees with the explicit regression oracle for forward.

Time representation◈ Members↗
FA-17463

Coincident or reordered capture has incorrect forward classification · case 03

The decoded time state disagrees with the explicit regression oracle for forward.

Time representation◈ Members↗
FA-17464

Coincident or reordered capture has incorrect forward classification · case 04

The decoded time state disagrees with the explicit regression oracle for forward.

Time representation◈ Members↗
FA-17465

Coincident or reordered capture has incorrect forward classification · case 05

The decoded time state disagrees with the explicit regression oracle for forward.

Time representation◈ Members↗
FA-17466

Bounded interval accepts reversed capture or rejects exact limit · case 01

The decoded time state disagrees with the explicit regression oracle for within.

Time representation● Open access↗
FA-17467

Bounded interval accepts reversed capture or rejects exact limit · case 02

The decoded time state disagrees with the explicit regression oracle for within.

Time representation◈ Members↗
FA-17468

Bounded interval accepts reversed capture or rejects exact limit · case 03

The decoded time state disagrees with the explicit regression oracle for within.

Time representation◈ Members↗
FA-17469

Bounded interval accepts reversed capture or rejects exact limit · case 04

The decoded time state disagrees with the explicit regression oracle for within.

Time representation◈ Members↗
FA-17470

Bounded interval accepts reversed capture or rejects exact limit · case 05

The decoded time state disagrees with the explicit regression oracle for within.

Time representation◈ Members↗
FA-17471

Epoch crossings are inferred from duration or a single wrap bit · case 01

The decoded time state disagrees with the explicit regression oracle for wraps.

Time representation● Open access↗
FA-17472

Epoch crossings are inferred from duration or a single wrap bit · case 02

The decoded time state disagrees with the explicit regression oracle for wraps.

Time representation◈ Members↗
FA-17473

Epoch crossings are inferred from duration or a single wrap bit · case 03

The decoded time state disagrees with the explicit regression oracle for wraps.

Time representation◈ Members↗
FA-17474

Epoch crossings are inferred from duration or a single wrap bit · case 04

The decoded time state disagrees with the explicit regression oracle for wraps.

Time representation◈ Members↗
FA-17475

Epoch crossings are inferred from duration or a single wrap bit · case 05

The decoded time state disagrees with the explicit regression oracle for wraps.

Time representation◈ Members↗
FA-17476

External phase grid is confused with hardware counter modulus · case 01

The decoded time state disagrees with the explicit regression oracle for phase.

Time representation● Open access↗
FA-17477

External phase grid is confused with hardware counter modulus · case 02

The decoded time state disagrees with the explicit regression oracle for phase.

Time representation◈ Members↗
FA-17478

External phase grid is confused with hardware counter modulus · case 03

The decoded time state disagrees with the explicit regression oracle for phase.

Time representation◈ Members↗
FA-17479

External phase grid is confused with hardware counter modulus · case 04

The decoded time state disagrees with the explicit regression oracle for phase.

Time representation◈ Members↗
FA-17480

External phase grid is confused with hardware counter modulus · case 05

The decoded time state disagrees with the explicit regression oracle for phase.

Time representation◈ Members↗
FA-17481

Grid-cycle index is rounded ahead of current capture · case 01

The decoded time state disagrees with the explicit regression oracle for cycles.

Time representation● Open access↗
FA-17482

Grid-cycle index is rounded ahead of current capture · case 02

The decoded time state disagrees with the explicit regression oracle for cycles.

Time representation◈ Members↗
FA-17483

Grid-cycle index is rounded ahead of current capture · case 03

The decoded time state disagrees with the explicit regression oracle for cycles.

Time representation◈ Members↗
FA-17484

Grid-cycle index is rounded ahead of current capture · case 04

The decoded time state disagrees with the explicit regression oracle for cycles.

Time representation◈ Members↗
FA-17485

Grid-cycle index is rounded ahead of current capture · case 05

The decoded time state disagrees with the explicit regression oracle for cycles.

Time representation◈ Members↗
FA-17486

Next grid edge is relative to capture rather than grid origin · case 01

The decoded time state disagrees with the explicit regression oracle for next_edge.

Time representation● Open access↗
FA-17487

Next grid edge is relative to capture rather than grid origin · case 02

The decoded time state disagrees with the explicit regression oracle for next_edge.

Time representation◈ Members↗
FA-17488

Next grid edge is relative to capture rather than grid origin · case 03

The decoded time state disagrees with the explicit regression oracle for next_edge.

Time representation◈ Members↗
FA-17489

Next grid edge is relative to capture rather than grid origin · case 04

The decoded time state disagrees with the explicit regression oracle for next_edge.

Time representation◈ Members↗
FA-17490

Next grid edge is relative to capture rather than grid origin · case 05

The decoded time state disagrees with the explicit regression oracle for next_edge.

Time representation◈ Members↗
FA-17491

Backward projection suppresses oscillator error growth · case 01

The decoded time state disagrees with the explicit regression oracle for age.

Time representation● Open access↗
FA-17492

Backward projection suppresses oscillator error growth · case 02

The decoded time state disagrees with the explicit regression oracle for age.

Time representation◈ Members↗
FA-17493

Backward projection suppresses oscillator error growth · case 03

The decoded time state disagrees with the explicit regression oracle for age.

Time representation◈ Members↗
FA-17494

Backward projection suppresses oscillator error growth · case 04

The decoded time state disagrees with the explicit regression oracle for age.

Time representation◈ Members↗
FA-17495

Backward projection suppresses oscillator error growth · case 05

The decoded time state disagrees with the explicit regression oracle for age.

Time representation◈ Members↗
FA-17496

Early uncertainty rounds inward or borrows late drift rate · case 01

The decoded time state disagrees with the explicit regression oracle for early_growth.

Time representation● Open access↗
FA-17497

Early uncertainty rounds inward or borrows late drift rate · case 02

The decoded time state disagrees with the explicit regression oracle for early_growth.

Time representation◈ Members↗
FA-17498

Early uncertainty rounds inward or borrows late drift rate · case 03

The decoded time state disagrees with the explicit regression oracle for early_growth.

Time representation◈ Members↗
FA-17499

Early uncertainty rounds inward or borrows late drift rate · case 04

The decoded time state disagrees with the explicit regression oracle for early_growth.

Time representation◈ Members↗
FA-17500

Early uncertainty rounds inward or borrows late drift rate · case 05

The decoded time state disagrees with the explicit regression oracle for early_growth.

Time representation◈ 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 ↗