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
Dns referral needs authority ns records without terminal answer · case 01
Dns referral needs authority ns records without terminal answer.
Dns referral needs authority ns records without terminal answer · case 02
Dns referral needs authority ns records without terminal answer.
Dns referral needs authority ns records without terminal answer · case 03
Dns referral needs authority ns records without terminal answer.
Dns referral needs authority ns records without terminal answer · case 04
Dns referral needs authority ns records without terminal answer.
Dns referral needs authority ns records without terminal answer · case 05
Dns referral needs authority ns records without terminal answer.
Dns search list is skipped for absolute query name · case 01
Dns search list is skipped for absolute query name.
Dns search list is skipped for absolute query name · case 02
Dns search list is skipped for absolute query name.
Dns search list is skipped for absolute query name · case 03
Dns search list is skipped for absolute query name.
Dns search list is skipped for absolute query name · case 04
Dns search list is skipped for absolute query name.
Dns search list is skipped for absolute query name · case 05
Dns search list is skipped for absolute query name.
Dns ndots threshold selects absolute query first · case 01
Dns ndots threshold selects absolute query first.
Dns ndots threshold selects absolute query first · case 02
Dns ndots threshold selects absolute query first.
Dns ndots threshold selects absolute query first · case 03
Dns ndots threshold selects absolute query first.
Dns ndots threshold selects absolute query first · case 04
Dns ndots threshold selects absolute query first.
Dns ndots threshold selects absolute query first · case 05
Dns ndots threshold selects absolute query first.
Dns servfail is retryable while nxdomain is terminal · case 01
Dns servfail is retryable while nxdomain is terminal.
Dns servfail is retryable while nxdomain is terminal · case 02
Dns servfail is retryable while nxdomain is terminal.
Dns servfail is retryable while nxdomain is terminal · case 03
Dns servfail is retryable while nxdomain is terminal.
Dns servfail is retryable while nxdomain is terminal · case 04
Dns servfail is retryable while nxdomain is terminal.
Dns servfail is retryable while nxdomain is terminal · case 05
Dns servfail is retryable while nxdomain is terminal.
Dns server retry excludes already failed servers · case 01
Dns server retry excludes already failed servers.
Dns server retry excludes already failed servers · case 02
Dns server retry excludes already failed servers.
Dns server retry excludes already failed servers · case 03
Dns server retry excludes already failed servers.
Dns server retry excludes already failed servers · case 04
Dns server retry excludes already failed servers.
Dns server retry excludes already failed servers · case 05
Dns server retry excludes already failed servers.
Dns edns payload negotiation respects both peer and local cap · case 01
Dns edns payload negotiation respects both peer and local cap.
Dns edns payload negotiation respects both peer and local cap · case 02
Dns edns payload negotiation respects both peer and local cap.
Dns edns payload negotiation respects both peer and local cap · case 03
Dns edns payload negotiation respects both peer and local cap.
Dns edns payload negotiation respects both peer and local cap · case 04
Dns edns payload negotiation respects both peer and local cap.
Dns edns payload negotiation respects both peer and local cap · case 05
Dns edns payload negotiation respects both peer and local cap.
Dns edns fallback removes extension after format error only · case 01
Dns edns fallback removes extension after format error only.
Dns edns fallback removes extension after format error only · case 02
Dns edns fallback removes extension after format error only.
Dns edns fallback removes extension after format error only · case 03
Dns edns fallback removes extension after format error only.
Dns edns fallback removes extension after format error only · case 04
Dns edns fallback removes extension after format error only.
Dns edns fallback removes extension after format error only · case 05
Dns edns fallback removes extension after format error only.
Dns response qr bit must mark response · case 01
Dns response qr bit must mark response.
Dns response qr bit must mark response · case 02
Dns response qr bit must mark response.
Dns response qr bit must mark response · case 03
Dns response qr bit must mark response.
Dns response qr bit must mark response · case 04
Dns response qr bit must mark response.
Dns response qr bit must mark response · case 05
Dns response qr bit must mark response.
Dns answer class must match question class · case 01
Dns answer class must match question class.
Dns answer class must match question class · case 02
Dns answer class must match question class.
Dns answer class must match question class · case 03
Dns answer class must match question class.
Dns answer class must match question class · case 04
Dns answer class must match question class.
Dns answer class must match question class · case 05
Dns answer class must match question class.
Dns srv priority is selected before weight · case 01
Dns srv priority is selected before weight.
Dns srv priority is selected before weight · case 02
Dns srv priority is selected before weight.
Dns srv priority is selected before weight · case 03
Dns srv priority is selected before weight.
Dns srv priority is selected before weight · case 04
Dns srv priority is selected before weight.
Dns srv priority is selected before weight · case 05
Dns srv priority is selected before weight.
Dns mx null target denotes no mail service · case 01
Dns mx null target denotes no mail service.
Dns mx null target denotes no mail service · case 02
Dns mx null target denotes no mail service.
Dns mx null target denotes no mail service · case 03
Dns mx null target denotes no mail service.
Dns mx null target denotes no mail service · case 04
Dns mx null target denotes no mail service.
Dns mx null target denotes no mail service · case 05
Dns mx null target denotes no mail service.
Http2 client initiated stream identifiers are positive odd · case 01
Http2 client initiated stream identifiers are positive odd.
Http2 client initiated stream identifiers are positive odd · case 02
Http2 client initiated stream identifiers are positive odd.
Http2 client initiated stream identifiers are positive odd · case 03
Http2 client initiated stream identifiers are positive odd.
Http2 client initiated stream identifiers are positive odd · case 04
Http2 client initiated stream identifiers are positive odd.
Http2 client initiated stream identifiers are positive odd · case 05
Http2 client initiated stream identifiers are positive odd.
Http2 server push identifiers are positive even · case 01
Http2 server push identifiers are positive even.
Http2 server push identifiers are positive even · case 02
Http2 server push identifiers are positive even.
Http2 server push identifiers are positive even · case 03
Http2 server push identifiers are positive even.
Http2 server push identifiers are positive even · case 04
Http2 server push identifiers are positive even.
Http2 server push identifiers are positive even · case 05
Http2 server push identifiers are positive even.
Http2 new stream id must increase without reuse · case 01
Http2 new stream id must increase without reuse.
Http2 new stream id must increase without reuse · case 02
Http2 new stream id must increase without reuse.
Http2 new stream id must increase without reuse · case 03
Http2 new stream id must increase without reuse.
Http2 new stream id must increase without reuse · case 04
Http2 new stream id must increase without reuse.
Http2 new stream id must increase without reuse · case 05
Http2 new stream id must increase without reuse.
Http2 end stream closes only sending half · case 01
Http2 end stream closes only sending half.
Http2 end stream closes only sending half · case 02
Http2 end stream closes only sending half.
Http2 end stream closes only sending half · case 03
Http2 end stream closes only sending half.
Http2 end stream closes only sending half · case 04
Http2 end stream closes only sending half.
Http2 end stream closes only sending half · case 05
Http2 end stream closes only sending half.
Http2 data credit is constrained by stream and connection · case 01
Http2 data credit is constrained by stream and connection.
Http2 data credit is constrained by stream and connection · case 02
Http2 data credit is constrained by stream and connection.
Http2 data credit is constrained by stream and connection · case 03
Http2 data credit is constrained by stream and connection.
Http2 data credit is constrained by stream and connection · case 04
Http2 data credit is constrained by stream and connection.
Http2 data credit is constrained by stream and connection · case 05
Http2 data credit is constrained by stream and connection.
Http2 padding consumes flow control credit · case 01
Http2 padding consumes flow control credit.
Http2 padding consumes flow control credit · case 02
Http2 padding consumes flow control credit.
Http2 padding consumes flow control credit · case 03
Http2 padding consumes flow control credit.
Http2 padding consumes flow control credit · case 04
Http2 padding consumes flow control credit.
Http2 padding consumes flow control credit · case 05
Http2 padding consumes flow control credit.
Http2 window update rejects zero and overflow · case 01
Http2 window update rejects zero and overflow.
Http2 window update rejects zero and overflow · case 02
Http2 window update rejects zero and overflow.
Http2 window update rejects zero and overflow · case 03
Http2 window update rejects zero and overflow.
Http2 window update rejects zero and overflow · case 04
Http2 window update rejects zero and overflow.
Http2 window update rejects zero and overflow · case 05
Http2 window update rejects zero and overflow.
Http2 initial window change applies delta to existing streams · case 01
Http2 initial window change applies delta to existing streams.
Http2 initial window change applies delta to existing streams · case 02
Http2 initial window change applies delta to existing streams.
Http2 initial window change applies delta to existing streams · case 03
Http2 initial window change applies delta to existing streams.
Http2 initial window change applies delta to existing streams · case 04
Http2 initial window change applies delta to existing streams.
Http2 initial window change applies delta to existing streams · case 05
Http2 initial window change applies delta to existing streams.
Http2 settings ack must have empty payload · case 01
Http2 settings ack must have empty payload.
Http2 settings ack must have empty payload · case 02
Http2 settings ack must have empty payload.
Http2 settings ack must have empty payload · case 03
Http2 settings ack must have empty payload.
Http2 settings ack must have empty payload · case 04
Http2 settings ack must have empty payload.
Http2 settings ack must have empty payload · case 05
Http2 settings ack must have empty payload.
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 ↗