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
RTC seconds low nibble is lost or read from adjacent register · case 01
The decoded time state disagrees with the explicit regression oracle for second.
RTC seconds low nibble is lost or read from adjacent register · case 02
The decoded time state disagrees with the explicit regression oracle for second.
RTC seconds low nibble is lost or read from adjacent register · case 03
The decoded time state disagrees with the explicit regression oracle for second.
RTC seconds low nibble is lost or read from adjacent register · case 04
The decoded time state disagrees with the explicit regression oracle for second.
RTC seconds low nibble is lost or read from adjacent register · case 05
The decoded time state disagrees with the explicit regression oracle for second.
RTC snapshot validation accepts a generation change during register reads · case 01
The decoded time state disagrees with the explicit regression oracle for bcd.
RTC snapshot validation accepts a generation change during register reads · case 02
The decoded time state disagrees with the explicit regression oracle for bcd.
RTC snapshot validation accepts a generation change during register reads · case 03
The decoded time state disagrees with the explicit regression oracle for bcd.
RTC snapshot validation accepts a generation change during register reads · case 04
The decoded time state disagrees with the explicit regression oracle for bcd.
RTC snapshot validation accepts a generation change during register reads · case 05
The decoded time state disagrees with the explicit regression oracle for bcd.
RTC hour range is validated against the wrong mode · case 01
The decoded time state disagrees with the explicit regression oracle for hour_valid.
RTC hour range is validated against the wrong mode · case 02
The decoded time state disagrees with the explicit regression oracle for hour_valid.
RTC hour range is validated against the wrong mode · case 03
The decoded time state disagrees with the explicit regression oracle for hour_valid.
RTC hour range is validated against the wrong mode · case 04
The decoded time state disagrees with the explicit regression oracle for hour_valid.
RTC hour range is validated against the wrong mode · case 05
The decoded time state disagrees with the explicit regression oracle for hour_valid.
RTC minute endpoint admits sixty or excludes fifty-nine · case 01
The decoded time state disagrees with the explicit regression oracle for minute_valid.
RTC minute endpoint admits sixty or excludes fifty-nine · case 02
The decoded time state disagrees with the explicit regression oracle for minute_valid.
RTC minute endpoint admits sixty or excludes fifty-nine · case 03
The decoded time state disagrees with the explicit regression oracle for minute_valid.
RTC minute endpoint admits sixty or excludes fifty-nine · case 04
The decoded time state disagrees with the explicit regression oracle for minute_valid.
RTC minute endpoint admits sixty or excludes fifty-nine · case 05
The decoded time state disagrees with the explicit regression oracle for minute_valid.
RTC seconds register uses leap-second policy despite no leap support · case 01
The decoded time state disagrees with the explicit regression oracle for second_valid.
RTC seconds register uses leap-second policy despite no leap support · case 02
The decoded time state disagrees with the explicit regression oracle for second_valid.
RTC seconds register uses leap-second policy despite no leap support · case 03
The decoded time state disagrees with the explicit regression oracle for second_valid.
RTC seconds register uses leap-second policy despite no leap support · case 04
The decoded time state disagrees with the explicit regression oracle for second_valid.
RTC seconds register uses leap-second policy despite no leap support · case 05
The decoded time state disagrees with the explicit regression oracle for second_valid.
RTC mode validation ignores forbidden PM bit or rejects valid PM · case 01
The decoded time state disagrees with the explicit regression oracle for mode_valid.
RTC mode validation ignores forbidden PM bit or rejects valid PM · case 02
The decoded time state disagrees with the explicit regression oracle for mode_valid.
RTC mode validation ignores forbidden PM bit or rejects valid PM · case 03
The decoded time state disagrees with the explicit regression oracle for mode_valid.
RTC mode validation ignores forbidden PM bit or rejects valid PM · case 04
The decoded time state disagrees with the explicit regression oracle for mode_valid.
RTC mode validation ignores forbidden PM bit or rejects valid PM · case 05
The decoded time state disagrees with the explicit regression oracle for mode_valid.
Twelve-hour RTC maps noon or midnight incorrectly · case 01
The decoded time state disagrees with the explicit regression oracle for converted_hour.
Twelve-hour RTC maps noon or midnight incorrectly · case 02
The decoded time state disagrees with the explicit regression oracle for converted_hour.
Twelve-hour RTC maps noon or midnight incorrectly · case 03
The decoded time state disagrees with the explicit regression oracle for converted_hour.
Twelve-hour RTC maps noon or midnight incorrectly · case 04
The decoded time state disagrees with the explicit regression oracle for converted_hour.
Twelve-hour RTC maps noon or midnight incorrectly · case 05
The decoded time state disagrees with the explicit regression oracle for converted_hour.
RTC snapshot admits stopped oscillator or contradictory mode bit · case 01
The decoded time state disagrees with the explicit regression oracle for valid.
RTC snapshot admits stopped oscillator or contradictory mode bit · case 02
The decoded time state disagrees with the explicit regression oracle for valid.
RTC snapshot admits stopped oscillator or contradictory mode bit · case 03
The decoded time state disagrees with the explicit regression oracle for valid.
RTC snapshot admits stopped oscillator or contradictory mode bit · case 04
The decoded time state disagrees with the explicit regression oracle for valid.
RTC snapshot admits stopped oscillator or contradictory mode bit · case 05
The decoded time state disagrees with the explicit regression oracle for valid.
Timestamp bucket endpoint uses inclusive-label convention or loses origin · case 01
The decoded time state disagrees with the explicit regression oracle for a_end.
Timestamp bucket endpoint uses inclusive-label convention or loses origin · case 02
The decoded time state disagrees with the explicit regression oracle for a_end.
Timestamp bucket endpoint uses inclusive-label convention or loses origin · case 03
The decoded time state disagrees with the explicit regression oracle for a_end.
Timestamp bucket endpoint uses inclusive-label convention or loses origin · case 04
The decoded time state disagrees with the explicit regression oracle for a_end.
Timestamp bucket endpoint uses inclusive-label convention or loses origin · case 05
The decoded time state disagrees with the explicit regression oracle for a_end.
Second timestamp bucket inherits first timestamp precision · case 01
The decoded time state disagrees with the explicit regression oracle for b_end.
Second timestamp bucket inherits first timestamp precision · case 02
The decoded time state disagrees with the explicit regression oracle for b_end.
Second timestamp bucket inherits first timestamp precision · case 03
The decoded time state disagrees with the explicit regression oracle for b_end.
Second timestamp bucket inherits first timestamp precision · case 04
The decoded time state disagrees with the explicit regression oracle for b_end.
Second timestamp bucket inherits first timestamp precision · case 05
The decoded time state disagrees with the explicit regression oracle for b_end.
Precision comparison ignores clock domain or hardcodes UTC · case 01
The decoded time state disagrees with the explicit regression oracle for compatible.
Precision comparison ignores clock domain or hardcodes UTC · case 02
The decoded time state disagrees with the explicit regression oracle for compatible.
Precision comparison ignores clock domain or hardcodes UTC · case 03
The decoded time state disagrees with the explicit regression oracle for compatible.
Precision comparison ignores clock domain or hardcodes UTC · case 04
The decoded time state disagrees with the explicit regression oracle for compatible.
Precision comparison ignores clock domain or hardcodes UTC · case 05
The decoded time state disagrees with the explicit regression oracle for compatible.
Timestamp intersection starts before the later bucket · case 01
The decoded time state disagrees with the explicit regression oracle for low.
Timestamp intersection starts before the later bucket · case 02
The decoded time state disagrees with the explicit regression oracle for low.
Timestamp intersection starts before the later bucket · case 03
The decoded time state disagrees with the explicit regression oracle for low.
Timestamp intersection starts before the later bucket · case 04
The decoded time state disagrees with the explicit regression oracle for low.
Timestamp intersection starts before the later bucket · case 05
The decoded time state disagrees with the explicit regression oracle for low.
Timestamp intersection keeps the later endpoint · case 01
The decoded time state disagrees with the explicit regression oracle for high.
Timestamp intersection keeps the later endpoint · case 02
The decoded time state disagrees with the explicit regression oracle for high.
Timestamp intersection keeps the later endpoint · case 03
The decoded time state disagrees with the explicit regression oracle for high.
Timestamp intersection keeps the later endpoint · case 04
The decoded time state disagrees with the explicit regression oracle for high.
Timestamp intersection keeps the later endpoint · case 05
The decoded time state disagrees with the explicit regression oracle for high.
Touching precision buckets are treated as overlapping · case 01
The decoded time state disagrees with the explicit regression oracle for overlap.
Touching precision buckets are treated as overlapping · case 02
The decoded time state disagrees with the explicit regression oracle for overlap.
Touching precision buckets are treated as overlapping · case 03
The decoded time state disagrees with the explicit regression oracle for overlap.
Touching precision buckets are treated as overlapping · case 04
The decoded time state disagrees with the explicit regression oracle for overlap.
Touching precision buckets are treated as overlapping · case 05
The decoded time state disagrees with the explicit regression oracle for overlap.
Definite timestamp ordering ignores measurement width · case 01
The decoded time state disagrees with the explicit regression oracle for definite_before.
Definite timestamp ordering ignores measurement width · case 02
The decoded time state disagrees with the explicit regression oracle for definite_before.
Definite timestamp ordering ignores measurement width · case 03
The decoded time state disagrees with the explicit regression oracle for definite_before.
Definite timestamp ordering ignores measurement width · case 04
The decoded time state disagrees with the explicit regression oracle for definite_before.
Definite timestamp ordering ignores measurement width · case 05
The decoded time state disagrees with the explicit regression oracle for definite_before.
Possible timestamp ordering is confused with definite ordering · case 01
The decoded time state disagrees with the explicit regression oracle for possible_before.
Possible timestamp ordering is confused with definite ordering · case 02
The decoded time state disagrees with the explicit regression oracle for possible_before.
Possible timestamp ordering is confused with definite ordering · case 03
The decoded time state disagrees with the explicit regression oracle for possible_before.
Possible timestamp ordering is confused with definite ordering · case 04
The decoded time state disagrees with the explicit regression oracle for possible_before.
Possible timestamp ordering is confused with definite ordering · case 05
The decoded time state disagrees with the explicit regression oracle for possible_before.
Equal point labels conceal different represented precision intervals · case 01
The decoded time state disagrees with the explicit regression oracle for equal.
Equal point labels conceal different represented precision intervals · case 02
The decoded time state disagrees with the explicit regression oracle for equal.
Equal point labels conceal different represented precision intervals · case 03
The decoded time state disagrees with the explicit regression oracle for equal.
Equal point labels conceal different represented precision intervals · case 04
The decoded time state disagrees with the explicit regression oracle for equal.
Equal point labels conceal different represented precision intervals · case 05
The decoded time state disagrees with the explicit regression oracle for equal.
Timestamp-bucket membership applies closed or open endpoint policy · case 01
The decoded time state disagrees with the explicit regression oracle for contains.
Timestamp-bucket membership applies closed or open endpoint policy · case 02
The decoded time state disagrees with the explicit regression oracle for contains.
Timestamp-bucket membership applies closed or open endpoint policy · case 03
The decoded time state disagrees with the explicit regression oracle for contains.
Timestamp-bucket membership applies closed or open endpoint policy · case 04
The decoded time state disagrees with the explicit regression oracle for contains.
Timestamp-bucket membership applies closed or open endpoint policy · case 05
The decoded time state disagrees with the explicit regression oracle for contains.
Client elapsed interval crosses clock domains or conceals clock regression · case 01
The decoded time state disagrees with the explicit regression oracle for client_span.
Client elapsed interval crosses clock domains or conceals clock regression · case 02
The decoded time state disagrees with the explicit regression oracle for client_span.
Client elapsed interval crosses clock domains or conceals clock regression · case 03
The decoded time state disagrees with the explicit regression oracle for client_span.
Client elapsed interval crosses clock domains or conceals clock regression · case 04
The decoded time state disagrees with the explicit regression oracle for client_span.
Client elapsed interval crosses clock domains or conceals clock regression · case 05
The decoded time state disagrees with the explicit regression oracle for client_span.
Server processing delay is omitted or measured from client send · case 01
The decoded time state disagrees with the explicit regression oracle for server_span.
Server processing delay is omitted or measured from client send · case 02
The decoded time state disagrees with the explicit regression oracle for server_span.
Server processing delay is omitted or measured from client send · case 03
The decoded time state disagrees with the explicit regression oracle for server_span.
Server processing delay is omitted or measured from client send · case 04
The decoded time state disagrees with the explicit regression oracle for server_span.
Server processing delay is omitted or measured from client send · case 05
The decoded time state disagrees with the explicit regression oracle for server_span.
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 ↗