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 ↗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
Loads at undefined positions silently accepted · case 01
A manifest line for a position that does not exist in this aircraft passes validation.
Loads at undefined positions silently accepted · case 02
A manifest line for a position that does not exist in this aircraft passes validation.
Loads at undefined positions silently accepted · case 03
A manifest line for a position that does not exist in this aircraft passes validation.
Loads at undefined positions silently accepted · case 04
A manifest line for a position that does not exist in this aircraft passes validation.
Loads at undefined positions silently accepted · case 05
A manifest line for a position that does not exist in this aircraft passes validation.
Position findings follow manifest entry order · case 01
Two runs over the same load in different manifest order produce differently ordered findings.
Position findings follow manifest entry order · case 02
Two runs over the same load in different manifest order produce differently ordered findings.
Position findings follow manifest entry order · case 03
Two runs over the same load in different manifest order produce differently ordered findings.
Position findings follow manifest entry order · case 04
Two runs over the same load in different manifest order produce differently ordered findings.
Position findings follow manifest entry order · case 05
Two runs over the same load in different manifest order produce differently ordered findings.
Warm fuel treated as denser · case 01
Hot days produce short-fuelled aircraft because too few gallons are ordered.
Warm fuel treated as denser · case 02
Hot days produce short-fuelled aircraft because too few gallons are ordered.
Warm fuel treated as denser · case 03
Hot days produce short-fuelled aircraft because too few gallons are ordered.
Warm fuel treated as denser · case 04
Hot days produce short-fuelled aircraft because too few gallons are ordered.
Warm fuel treated as denser · case 05
Hot days produce short-fuelled aircraft because too few gallons are ordered.
Uplift truncated to whole gallons · case 01
The aircraft ends up a fraction of a gallon below the planned fuel weight.
Uplift truncated to whole gallons · case 02
The aircraft ends up a fraction of a gallon below the planned fuel weight.
Uplift truncated to whole gallons · case 03
The aircraft ends up a fraction of a gallon below the planned fuel weight.
Uplift truncated to whole gallons · case 04
The aircraft ends up a fraction of a gallon below the planned fuel weight.
Uplift truncated to whole gallons · case 05
The aircraft ends up a fraction of a gallon below the planned fuel weight.
Onboard gallons subtracted from a pound target · case 01
Uplift orders are far too large when fuel is already on board.
Onboard gallons subtracted from a pound target · case 02
Uplift orders are far too large when fuel is already on board.
Onboard gallons subtracted from a pound target · case 03
Uplift orders are far too large when fuel is already on board.
Onboard gallons subtracted from a pound target · case 04
Uplift orders are far too large when fuel is already on board.
Onboard gallons subtracted from a pound target · case 05
Uplift orders are far too large when fuel is already on board.
Tank capacity compared with the fuel weight target · case 01
Ordinary fuel orders are rejected because pounds exceed the gallon capacity number.
Tank capacity compared with the fuel weight target · case 02
Ordinary fuel orders are rejected because pounds exceed the gallon capacity number.
Tank capacity compared with the fuel weight target · case 03
Ordinary fuel orders are rejected because pounds exceed the gallon capacity number.
Tank capacity compared with the fuel weight target · case 04
Ordinary fuel orders are rejected because pounds exceed the gallon capacity number.
Tank capacity compared with the fuel weight target · case 05
Ordinary fuel orders are rejected because pounds exceed the gallon capacity number.
Sufficient onboard fuel reported as a capacity problem · case 01
A tanker-loaded aircraft that needs no fuel gets an ERR_CAPACITY result.
Sufficient onboard fuel reported as a capacity problem · case 02
A tanker-loaded aircraft that needs no fuel gets an ERR_CAPACITY result.
Sufficient onboard fuel reported as a capacity problem · case 03
A tanker-loaded aircraft that needs no fuel gets an ERR_CAPACITY result.
Sufficient onboard fuel reported as a capacity problem · case 04
A tanker-loaded aircraft that needs no fuel gets an ERR_CAPACITY result.
Sufficient onboard fuel reported as a capacity problem · case 05
A tanker-loaded aircraft that needs no fuel gets an ERR_CAPACITY result.
Unrounded density leaks float noise into the order · case 01
The density echoed on the fuel slip shows values like 6.6400000000000001 and gallon orders differ from the slip.
Unrounded density leaks float noise into the order · case 02
The density echoed on the fuel slip shows values like 6.6400000000000001 and gallon orders differ from the slip.
Unrounded density leaks float noise into the order · case 03
The density echoed on the fuel slip shows values like 6.6400000000000001 and gallon orders differ from the slip.
Unrounded density leaks float noise into the order · case 04
The density echoed on the fuel slip shows values like 6.6400000000000001 and gallon orders differ from the slip.
Unrounded density leaks float noise into the order · case 05
The density echoed on the fuel slip shows values like 6.6400000000000001 and gallon orders differ from the slip.
Advance purchase measured in elapsed 24-hour periods · case 01
A ticket bought at 22:30 for a 06:00 departure exactly 14 calendar days later fails a 14-day advance purchase.
Advance purchase measured in elapsed 24-hour periods · case 02
A ticket bought at 22:30 for a 06:00 departure exactly 14 calendar days later fails a 14-day advance purchase.
Advance purchase measured in elapsed 24-hour periods · case 03
A ticket bought at 22:30 for a 06:00 departure exactly 14 calendar days later fails a 14-day advance purchase.
Advance purchase measured in elapsed 24-hour periods · case 04
A ticket bought at 22:30 for a 06:00 departure exactly 14 calendar days later fails a 14-day advance purchase.
Advance purchase measured in elapsed 24-hour periods · case 05
A ticket bought at 22:30 for a 06:00 departure exactly 14 calendar days later fails a 14-day advance purchase.
Ticket bought exactly AP days ahead rejected · case 01
A 7-day advance purchase fare cannot be ticketed exactly seven days before departure.
Ticket bought exactly AP days ahead rejected · case 02
A 7-day advance purchase fare cannot be ticketed exactly seven days before departure.
Ticket bought exactly AP days ahead rejected · case 03
A 7-day advance purchase fare cannot be ticketed exactly seven days before departure.
Ticket bought exactly AP days ahead rejected · case 04
A 7-day advance purchase fare cannot be ticketed exactly seven days before departure.
Ticket bought exactly AP days ahead rejected · case 05
A 7-day advance purchase fare cannot be ticketed exactly seven days before departure.
Ticket issued at the exact time limit rejected · case 01
Tickets issued at exactly reservation plus 24 hours fail the ticketing time limit.
Ticket issued at the exact time limit rejected · case 02
Tickets issued at exactly reservation plus 24 hours fail the ticketing time limit.
Ticket issued at the exact time limit rejected · case 03
Tickets issued at exactly reservation plus 24 hours fail the ticketing time limit.
Ticket issued at the exact time limit rejected · case 04
Tickets issued at exactly reservation plus 24 hours fail the ticketing time limit.
Ticket issued at the exact time limit rejected · case 05
Tickets issued at exactly reservation plus 24 hours fail the ticketing time limit.
Ticketing time limit hours interpreted as days · case 01
A 24-hour ticketing limit allows tickets issued three weeks after booking.
Ticketing time limit hours interpreted as days · case 02
A 24-hour ticketing limit allows tickets issued three weeks after booking.
Ticketing time limit hours interpreted as days · case 03
A 24-hour ticketing limit allows tickets issued three weeks after booking.
Ticketing time limit hours interpreted as days · case 04
A 24-hour ticketing limit allows tickets issued three weeks after booking.
Ticketing time limit hours interpreted as days · case 05
A 24-hour ticketing limit allows tickets issued three weeks after booking.
Ticket timestamp earlier than the booking accepted · case 01
Records whose ticket predates the reservation silently pass.
Ticket timestamp earlier than the booking accepted · case 02
Records whose ticket predates the reservation silently pass.
Ticket timestamp earlier than the booking accepted · case 03
Records whose ticket predates the reservation silently pass.
Ticket timestamp earlier than the booking accepted · case 04
Records whose ticket predates the reservation silently pass.
Ticket timestamp earlier than the booking accepted · case 05
Records whose ticket predates the reservation silently pass.
Ticketing time limit reported ahead of an advance purchase failure · case 01
A late ticket that also misses advance purchase is reported only as a time-limit failure.
Ticketing time limit reported ahead of an advance purchase failure · case 02
A late ticket that also misses advance purchase is reported only as a time-limit failure.
Ticketing time limit reported ahead of an advance purchase failure · case 03
A late ticket that also misses advance purchase is reported only as a time-limit failure.
Ticketing time limit reported ahead of an advance purchase failure · case 04
A late ticket that also misses advance purchase is reported only as a time-limit failure.
Ticketing time limit reported ahead of an advance purchase failure · case 05
A late ticket that also misses advance purchase is reported only as a time-limit failure.
Sunday departures satisfy the Saturday-night rule immediately · case 01
A traveller leaving Sunday and returning Monday meets the Saturday-night stay.
Sunday departures satisfy the Saturday-night rule immediately · case 02
A traveller leaving Sunday and returning Monday meets the Saturday-night stay.
Sunday departures satisfy the Saturday-night rule immediately · case 03
A traveller leaving Sunday and returning Monday meets the Saturday-night stay.
Sunday departures satisfy the Saturday-night rule immediately · case 04
A traveller leaving Sunday and returning Monday meets the Saturday-night stay.
Sunday departures satisfy the Saturday-night rule immediately · case 05
A traveller leaving Sunday and returning Monday meets the Saturday-night stay.
Maximum stay months approximated as 30 days · case 01
A one-month maximum stay departing 1 January expires on 31 January instead of 1 February.
Maximum stay months approximated as 30 days · case 02
A one-month maximum stay departing 1 January expires on 31 January instead of 1 February.
Maximum stay months approximated as 30 days · case 03
A one-month maximum stay departing 1 January expires on 31 January instead of 1 February.
Maximum stay months approximated as 30 days · case 04
A one-month maximum stay departing 1 January expires on 31 January instead of 1 February.
Maximum stay months approximated as 30 days · case 05
A one-month maximum stay departing 1 January expires on 31 January instead of 1 February.
Return exactly on the minimum-stay day rejected · case 01
A 7-day minimum stay rejects a return exactly seven days after departure.
Return exactly on the minimum-stay day rejected · case 02
A 7-day minimum stay rejects a return exactly seven days after departure.
Return exactly on the minimum-stay day rejected · case 03
A 7-day minimum stay rejects a return exactly seven days after departure.
Return exactly on the minimum-stay day rejected · case 04
A 7-day minimum stay rejects a return exactly seven days after departure.
Return exactly on the minimum-stay day rejected · case 05
A 7-day minimum stay rejects a return exactly seven days after departure.
Saturday-night rule applied when disabled · case 01
Fares whose rule explicitly sets sat_night to false still report SAT failures.
Saturday-night rule applied when disabled · case 02
Fares whose rule explicitly sets sat_night to false still report SAT failures.
Saturday-night rule applied when disabled · case 03
Fares whose rule explicitly sets sat_night to false still report SAT failures.
Saturday-night rule applied when disabled · case 04
Fares whose rule explicitly sets sat_night to false still report SAT failures.
Saturday-night rule applied when disabled · case 05
Fares whose rule explicitly sets sat_night to false still report SAT failures.
Month-end departures lose the end-of-month extension · case 01
Departing 28 February with a one-month maximum expires 28 March instead of 31 March.
Month-end departures lose the end-of-month extension · case 02
Departing 28 February with a one-month maximum expires 28 March instead of 31 March.
Month-end departures lose the end-of-month extension · case 03
Departing 28 February with a one-month maximum expires 28 March instead of 31 March.
Month-end departures lose the end-of-month extension · case 04
Departing 28 February with a one-month maximum expires 28 March instead of 31 March.
Month-end departures lose the end-of-month extension · case 05
Departing 28 February with a one-month maximum expires 28 March instead of 31 March.
Year carry computed from one-based month · case 01
A November departure with a one-month maximum stay gets a December limit in the following year.
Year carry computed from one-based month · case 02
A November departure with a one-month maximum stay gets a December limit in the following year.
Year carry computed from one-based month · case 03
A November departure with a one-month maximum stay gets a December limit in the following year.
Year carry computed from one-based month · case 04
A November departure with a one-month maximum stay gets a December limit in the following year.
Year carry computed from one-based month · case 05
A November departure with a one-month maximum stay gets a December limit in the following year.
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 ↗