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

Sack reports out of order blocks without changing cumulative ack · case 01

Sack reports out of order blocks without changing cumulative ack.

Transport flow control● Open access↗
FA-7302

Sack reports out of order blocks without changing cumulative ack · case 02

Sack reports out of order blocks without changing cumulative ack.

Transport flow control◈ Members↗
FA-7303

Sack reports out of order blocks without changing cumulative ack · case 03

Sack reports out of order blocks without changing cumulative ack.

Transport flow control◈ Members↗
FA-7304

Sack reports out of order blocks without changing cumulative ack · case 04

Sack reports out of order blocks without changing cumulative ack.

Transport flow control◈ Members↗
FA-7305

Sack reports out of order blocks without changing cumulative ack · case 05

Sack reports out of order blocks without changing cumulative ack.

Transport flow control◈ Members↗
FA-7306

Udp zero length datagram is data not stream eof · case 01

Udp zero length datagram is data not stream eof.

Transport flow control● Open access↗
FA-7307

Udp zero length datagram is data not stream eof · case 02

Udp zero length datagram is data not stream eof.

Transport flow control◈ Members↗
FA-7308

Udp zero length datagram is data not stream eof · case 03

Udp zero length datagram is data not stream eof.

Transport flow control◈ Members↗
FA-7309

Udp zero length datagram is data not stream eof · case 04

Udp zero length datagram is data not stream eof.

Transport flow control◈ Members↗
FA-7310

Udp zero length datagram is data not stream eof · case 05

Udp zero length datagram is data not stream eof.

Transport flow control◈ Members↗
FA-7311

Datagram truncation is reported separately from copied length · case 01

Datagram truncation is reported separately from copied length.

Transport flow control● Open access↗
FA-7312

Datagram truncation is reported separately from copied length · case 02

Datagram truncation is reported separately from copied length.

Transport flow control◈ Members↗
FA-7313

Datagram truncation is reported separately from copied length · case 03

Datagram truncation is reported separately from copied length.

Transport flow control◈ Members↗
FA-7314

Datagram truncation is reported separately from copied length · case 04

Datagram truncation is reported separately from copied length.

Transport flow control◈ Members↗
FA-7315

Datagram truncation is reported separately from copied length · case 05

Datagram truncation is reported separately from copied length.

Transport flow control◈ Members↗
FA-7316

Path mtu payload budget subtracts all protocol overheads · case 01

Path mtu payload budget subtracts all protocol overheads.

Transport flow control● Open access↗
FA-7317

Path mtu payload budget subtracts all protocol overheads · case 02

Path mtu payload budget subtracts all protocol overheads.

Transport flow control◈ Members↗
FA-7318

Path mtu payload budget subtracts all protocol overheads · case 03

Path mtu payload budget subtracts all protocol overheads.

Transport flow control◈ Members↗
FA-7319

Path mtu payload budget subtracts all protocol overheads · case 04

Path mtu payload budget subtracts all protocol overheads.

Transport flow control◈ Members↗
FA-7320

Path mtu payload budget subtracts all protocol overheads · case 05

Path mtu payload budget subtracts all protocol overheads.

Transport flow control◈ Members↗
FA-7321

Dont fragment policy rejects packets exceeding path mtu · case 01

Dont fragment policy rejects packets exceeding path mtu.

Transport flow control● Open access↗
FA-7322

Dont fragment policy rejects packets exceeding path mtu · case 02

Dont fragment policy rejects packets exceeding path mtu.

Transport flow control◈ Members↗
FA-7323

Dont fragment policy rejects packets exceeding path mtu · case 03

Dont fragment policy rejects packets exceeding path mtu.

Transport flow control◈ Members↗
FA-7324

Dont fragment policy rejects packets exceeding path mtu · case 04

Dont fragment policy rejects packets exceeding path mtu.

Transport flow control◈ Members↗
FA-7325

Dont fragment policy rejects packets exceeding path mtu · case 05

Dont fragment policy rejects packets exceeding path mtu.

Transport flow control◈ Members↗
FA-7326

Ip forwarding expires a packet before hop limit underflows · case 01

Ip forwarding expires a packet before hop limit underflows.

Transport flow control● Open access↗
FA-7327

Ip forwarding expires a packet before hop limit underflows · case 02

Ip forwarding expires a packet before hop limit underflows.

Transport flow control◈ Members↗
FA-7328

Ip forwarding expires a packet before hop limit underflows · case 03

Ip forwarding expires a packet before hop limit underflows.

Transport flow control◈ Members↗
FA-7329

Ip forwarding expires a packet before hop limit underflows · case 04

Ip forwarding expires a packet before hop limit underflows.

Transport flow control◈ Members↗
FA-7330

Ip forwarding expires a packet before hop limit underflows · case 05

Ip forwarding expires a packet before hop limit underflows.

Transport flow control◈ Members↗
FA-7331

Dns name equality ignores case and final root dot · case 01

Dns name equality ignores case and final root dot.

DNS resolution● Open access↗
FA-7332

Dns name equality ignores case and final root dot · case 02

Dns name equality ignores case and final root dot.

DNS resolution◈ Members↗
FA-7333

Dns name equality ignores case and final root dot · case 03

Dns name equality ignores case and final root dot.

DNS resolution◈ Members↗
FA-7334

Dns name equality ignores case and final root dot · case 04

Dns name equality ignores case and final root dot.

DNS resolution◈ Members↗
FA-7335

Dns name equality ignores case and final root dot · case 05

Dns name equality ignores case and final root dot.

DNS resolution◈ Members↗
FA-7336

Dns response correlates identifier and question · case 01

Dns response correlates identifier and question.

DNS resolution● Open access↗
FA-7337

Dns response correlates identifier and question · case 02

Dns response correlates identifier and question.

DNS resolution◈ Members↗
FA-7338

Dns response correlates identifier and question · case 03

Dns response correlates identifier and question.

DNS resolution◈ Members↗
FA-7339

Dns response correlates identifier and question · case 04

Dns response correlates identifier and question.

DNS resolution◈ Members↗
FA-7340

Dns response correlates identifier and question · case 05

Dns response correlates identifier and question.

DNS resolution◈ Members↗
FA-7341

Dns truncation triggers stream retry even with partial answers · case 01

Dns truncation triggers stream retry even with partial answers.

DNS resolution● Open access↗
FA-7342

Dns truncation triggers stream retry even with partial answers · case 02

Dns truncation triggers stream retry even with partial answers.

DNS resolution◈ Members↗
FA-7343

Dns truncation triggers stream retry even with partial answers · case 03

Dns truncation triggers stream retry even with partial answers.

DNS resolution◈ Members↗
FA-7344

Dns truncation triggers stream retry even with partial answers · case 04

Dns truncation triggers stream retry even with partial answers.

DNS resolution◈ Members↗
FA-7345

Dns truncation triggers stream retry even with partial answers · case 05

Dns truncation triggers stream retry even with partial answers.

DNS resolution◈ Members↗
FA-7346

Dns nxdomain is distinct from empty noerror answer · case 01

Dns nxdomain is distinct from empty noerror answer.

DNS resolution● Open access↗
FA-7347

Dns nxdomain is distinct from empty noerror answer · case 02

Dns nxdomain is distinct from empty noerror answer.

DNS resolution◈ Members↗
FA-7348

Dns nxdomain is distinct from empty noerror answer · case 03

Dns nxdomain is distinct from empty noerror answer.

DNS resolution◈ Members↗
FA-7349

Dns nxdomain is distinct from empty noerror answer · case 04

Dns nxdomain is distinct from empty noerror answer.

DNS resolution◈ Members↗
FA-7350

Dns nxdomain is distinct from empty noerror answer · case 05

Dns nxdomain is distinct from empty noerror answer.

DNS resolution◈ Members↗
FA-7351

Dns negative ttl is minimum of soa ttl and minimum field · case 01

Dns negative ttl is minimum of soa ttl and minimum field.

DNS resolution● Open access↗
FA-7352

Dns negative ttl is minimum of soa ttl and minimum field · case 02

Dns negative ttl is minimum of soa ttl and minimum field.

DNS resolution◈ Members↗
FA-7353

Dns negative ttl is minimum of soa ttl and minimum field · case 03

Dns negative ttl is minimum of soa ttl and minimum field.

DNS resolution◈ Members↗
FA-7354

Dns negative ttl is minimum of soa ttl and minimum field · case 04

Dns negative ttl is minimum of soa ttl and minimum field.

DNS resolution◈ Members↗
FA-7355

Dns negative ttl is minimum of soa ttl and minimum field · case 05

Dns negative ttl is minimum of soa ttl and minimum field.

DNS resolution◈ Members↗
FA-7356

Dns rrset ttl uses lowest member ttl · case 01

Dns rrset ttl uses lowest member ttl.

DNS resolution● Open access↗
FA-7357

Dns rrset ttl uses lowest member ttl · case 02

Dns rrset ttl uses lowest member ttl.

DNS resolution◈ Members↗
FA-7358

Dns rrset ttl uses lowest member ttl · case 03

Dns rrset ttl uses lowest member ttl.

DNS resolution◈ Members↗
FA-7359

Dns rrset ttl uses lowest member ttl · case 04

Dns rrset ttl uses lowest member ttl.

DNS resolution◈ Members↗
FA-7360

Dns rrset ttl uses lowest member ttl · case 05

Dns rrset ttl uses lowest member ttl.

DNS resolution◈ Members↗
FA-7361

Dns ttl is reduced by resident seconds and clamped · case 01

Dns ttl is reduced by resident seconds and clamped.

DNS resolution● Open access↗
FA-7362

Dns ttl is reduced by resident seconds and clamped · case 02

Dns ttl is reduced by resident seconds and clamped.

DNS resolution◈ Members↗
FA-7363

Dns ttl is reduced by resident seconds and clamped · case 03

Dns ttl is reduced by resident seconds and clamped.

DNS resolution◈ Members↗
FA-7364

Dns ttl is reduced by resident seconds and clamped · case 04

Dns ttl is reduced by resident seconds and clamped.

DNS resolution◈ Members↗
FA-7365

Dns ttl is reduced by resident seconds and clamped · case 05

Dns ttl is reduced by resident seconds and clamped.

DNS resolution◈ Members↗
FA-7366

Dns zero ttl answer can serve current query without caching · case 01

Dns zero ttl answer can serve current query without caching.

DNS resolution● Open access↗
FA-7367

Dns zero ttl answer can serve current query without caching · case 02

Dns zero ttl answer can serve current query without caching.

DNS resolution◈ Members↗
FA-7368

Dns zero ttl answer can serve current query without caching · case 03

Dns zero ttl answer can serve current query without caching.

DNS resolution◈ Members↗
FA-7369

Dns zero ttl answer can serve current query without caching · case 04

Dns zero ttl answer can serve current query without caching.

DNS resolution◈ Members↗
FA-7370

Dns zero ttl answer can serve current query without caching · case 05

Dns zero ttl answer can serve current query without caching.

DNS resolution◈ Members↗
FA-7371

Dns cache key includes query type · case 01

Dns cache key includes query type.

DNS resolution● Open access↗
FA-7372

Dns cache key includes query type · case 02

Dns cache key includes query type.

DNS resolution◈ Members↗
FA-7373

Dns cache key includes query type · case 03

Dns cache key includes query type.

DNS resolution◈ Members↗
FA-7374

Dns cache key includes query type · case 04

Dns cache key includes query type.

DNS resolution◈ Members↗
FA-7375

Dns cache key includes query type · case 05

Dns cache key includes query type.

DNS resolution◈ Members↗
FA-7376

Dns cname target is followed until requested type is reached · case 01

Dns cname target is followed until requested type is reached.

DNS resolution● Open access↗
FA-7377

Dns cname target is followed until requested type is reached · case 02

Dns cname target is followed until requested type is reached.

DNS resolution◈ Members↗
FA-7378

Dns cname target is followed until requested type is reached · case 03

Dns cname target is followed until requested type is reached.

DNS resolution◈ Members↗
FA-7379

Dns cname target is followed until requested type is reached · case 04

Dns cname target is followed until requested type is reached.

DNS resolution◈ Members↗
FA-7380

Dns cname target is followed until requested type is reached · case 05

Dns cname target is followed until requested type is reached.

DNS resolution◈ Members↗
FA-7381

Dns cname loop detection normalizes target identities · case 01

Dns cname loop detection normalizes target identities.

DNS resolution● Open access↗
FA-7382

Dns cname loop detection normalizes target identities · case 02

Dns cname loop detection normalizes target identities.

DNS resolution◈ Members↗
FA-7383

Dns cname loop detection normalizes target identities · case 03

Dns cname loop detection normalizes target identities.

DNS resolution◈ Members↗
FA-7384

Dns cname loop detection normalizes target identities · case 04

Dns cname loop detection normalizes target identities.

DNS resolution◈ Members↗
FA-7385

Dns cname loop detection normalizes target identities · case 05

Dns cname loop detection normalizes target identities.

DNS resolution◈ Members↗
FA-7386

Dns alias answer lifetime cannot exceed any chain link · case 01

Dns alias answer lifetime cannot exceed any chain link.

DNS resolution● Open access↗
FA-7387

Dns alias answer lifetime cannot exceed any chain link · case 02

Dns alias answer lifetime cannot exceed any chain link.

DNS resolution◈ Members↗
FA-7388

Dns alias answer lifetime cannot exceed any chain link · case 03

Dns alias answer lifetime cannot exceed any chain link.

DNS resolution◈ Members↗
FA-7389

Dns alias answer lifetime cannot exceed any chain link · case 04

Dns alias answer lifetime cannot exceed any chain link.

DNS resolution◈ Members↗
FA-7390

Dns alias answer lifetime cannot exceed any chain link · case 05

Dns alias answer lifetime cannot exceed any chain link.

DNS resolution◈ Members↗
FA-7391

Dns glue is accepted only within delegated zone · case 01

Dns glue is accepted only within delegated zone.

DNS resolution● Open access↗
FA-7392

Dns glue is accepted only within delegated zone · case 02

Dns glue is accepted only within delegated zone.

DNS resolution◈ Members↗
FA-7393

Dns glue is accepted only within delegated zone · case 03

Dns glue is accepted only within delegated zone.

DNS resolution◈ Members↗
FA-7394

Dns glue is accepted only within delegated zone · case 04

Dns glue is accepted only within delegated zone.

DNS resolution◈ Members↗
FA-7395

Dns glue is accepted only within delegated zone · case 05

Dns glue is accepted only within delegated zone.

DNS resolution◈ Members↗
FA-7396

Dns additional records do not override authoritative answers · case 01

Dns additional records do not override authoritative answers.

DNS resolution● Open access↗
FA-7397

Dns additional records do not override authoritative answers · case 02

Dns additional records do not override authoritative answers.

DNS resolution◈ Members↗
FA-7398

Dns additional records do not override authoritative answers · case 03

Dns additional records do not override authoritative answers.

DNS resolution◈ Members↗
FA-7399

Dns additional records do not override authoritative answers · case 04

Dns additional records do not override authoritative answers.

DNS resolution◈ Members↗
FA-7400

Dns additional records do not override authoritative answers · case 05

Dns additional records do not override authoritative answers.

DNS resolution◈ 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 ↗