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

Reverse bookmark mapping includes the exclusive stop · case 01

Reverse bookmark mapping includes the exclusive stop.

Bounded deques● Open access↗
FA-46302

Reverse bookmark mapping includes the exclusive stop · case 02

Reverse bookmark mapping includes the exclusive stop.

Bounded deques◈ Members↗
FA-46303

Reverse bookmark mapping includes the exclusive stop · case 03

Reverse bookmark mapping includes the exclusive stop.

Bounded deques◈ Members↗
FA-46304

Reverse bookmark mapping includes the exclusive stop · case 04

Reverse bookmark mapping includes the exclusive stop.

Bounded deques◈ Members↗
FA-46305

Reverse bookmark mapping includes the exclusive stop · case 05

Reverse bookmark mapping includes the exclusive stop.

Bounded deques◈ Members↗
FA-46306

Reverse returns bookmark mappings in new traversal order · case 01

Reverse returns bookmark mappings in new traversal order.

Bounded deques● Open access↗
FA-46307

Reverse returns bookmark mappings in new traversal order · case 02

Reverse returns bookmark mappings in new traversal order.

Bounded deques◈ Members↗
FA-46308

Reverse returns bookmark mappings in new traversal order · case 03

Reverse returns bookmark mappings in new traversal order.

Bounded deques◈ Members↗
FA-46309

Reverse returns bookmark mappings in new traversal order · case 04

Reverse returns bookmark mappings in new traversal order.

Bounded deques◈ Members↗
FA-46310

Reverse returns bookmark mappings in new traversal order · case 05

Reverse returns bookmark mappings in new traversal order.

Bounded deques◈ Members↗
FA-46311

Deque reorder accepts duplicated indices as a permutation · case 01

Deque reorder accepts duplicated indices as a permutation.

Bounded deques● Open access↗
FA-46312

Deque reorder accepts duplicated indices as a permutation · case 02

Deque reorder accepts duplicated indices as a permutation.

Bounded deques◈ Members↗
FA-46313

Deque reorder accepts duplicated indices as a permutation · case 03

Deque reorder accepts duplicated indices as a permutation.

Bounded deques◈ Members↗
FA-46314

Deque reorder accepts duplicated indices as a permutation · case 04

Deque reorder accepts duplicated indices as a permutation.

Bounded deques◈ Members↗
FA-46315

Deque reorder accepts duplicated indices as a permutation · case 05

Deque reorder accepts duplicated indices as a permutation.

Bounded deques◈ Members↗
FA-46316

Deque reorder sorts its supplied permutation before applying it · case 01

Deque reorder sorts its supplied permutation before applying it.

Bounded deques● Open access↗
FA-46317

Deque reorder sorts its supplied permutation before applying it · case 02

Deque reorder sorts its supplied permutation before applying it.

Bounded deques◈ Members↗
FA-46318

Deque reorder sorts its supplied permutation before applying it · case 03

Deque reorder sorts its supplied permutation before applying it.

Bounded deques◈ Members↗
FA-46319

Deque reorder sorts its supplied permutation before applying it · case 04

Deque reorder sorts its supplied permutation before applying it.

Bounded deques◈ Members↗
FA-46320

Deque reorder sorts its supplied permutation before applying it · case 05

Deque reorder sorts its supplied permutation before applying it.

Bounded deques◈ Members↗
FA-46321

Bookmark reorder writes the forward permutation as its inverse · case 01

Bookmark reorder writes the forward permutation as its inverse.

Bounded deques● Open access↗
FA-46322

Bookmark reorder writes the forward permutation as its inverse · case 02

Bookmark reorder writes the forward permutation as its inverse.

Bounded deques◈ Members↗
FA-46323

Bookmark reorder writes the forward permutation as its inverse · case 03

Bookmark reorder writes the forward permutation as its inverse.

Bounded deques◈ Members↗
FA-46324

Bookmark reorder writes the forward permutation as its inverse · case 04

Bookmark reorder writes the forward permutation as its inverse.

Bounded deques◈ Members↗
FA-46325

Bookmark reorder writes the forward permutation as its inverse · case 05

Bookmark reorder writes the forward permutation as its inverse.

Bounded deques◈ Members↗
FA-46326

Bookmark reorder allocates one extra inverse entry · case 01

Bookmark reorder allocates one extra inverse entry.

Bounded deques● Open access↗
FA-46327

Bookmark reorder allocates one extra inverse entry · case 02

Bookmark reorder allocates one extra inverse entry.

Bounded deques◈ Members↗
FA-46328

Bookmark reorder allocates one extra inverse entry · case 03

Bookmark reorder allocates one extra inverse entry.

Bounded deques◈ Members↗
FA-46329

Bookmark reorder allocates one extra inverse entry · case 04

Bookmark reorder allocates one extra inverse entry.

Bounded deques◈ Members↗
FA-46330

Bookmark reorder allocates one extra inverse entry · case 05

Bookmark reorder allocates one extra inverse entry.

Bounded deques◈ Members↗
FA-46331

Rejected deque reorder clears the original data · case 01

Rejected deque reorder clears the original data.

Bounded deques● Open access↗
FA-46332

Rejected deque reorder clears the original data · case 02

Rejected deque reorder clears the original data.

Bounded deques◈ Members↗
FA-46333

Rejected deque reorder clears the original data · case 03

Rejected deque reorder clears the original data.

Bounded deques◈ Members↗
FA-46334

Rejected deque reorder clears the original data · case 04

Rejected deque reorder clears the original data.

Bounded deques◈ Members↗
FA-46335

Rejected deque reorder clears the original data · case 05

Rejected deque reorder clears the original data.

Bounded deques◈ Members↗
FA-46336

Deque uniqueness clears seen identities after each item · case 01

Deque uniqueness clears seen identities after each item.

Bounded deques● Open access↗
FA-46337

Deque uniqueness clears seen identities after each item · case 02

Deque uniqueness clears seen identities after each item.

Bounded deques◈ Members↗
FA-46338

Deque uniqueness clears seen identities after each item · case 03

Deque uniqueness clears seen identities after each item.

Bounded deques◈ Members↗
FA-46339

Deque uniqueness clears seen identities after each item · case 04

Deque uniqueness clears seen identities after each item.

Bounded deques◈ Members↗
FA-46340

Deque uniqueness clears seen identities after each item · case 05

Deque uniqueness clears seen identities after each item.

Bounded deques◈ Members↗
FA-46341

Deque uniqueness reports duplicate values instead of removed positions · case 01

Deque uniqueness reports duplicate values instead of removed positions.

Bounded deques● Open access↗
FA-46342

Deque uniqueness reports duplicate values instead of removed positions · case 02

Deque uniqueness reports duplicate values instead of removed positions.

Bounded deques◈ Members↗
FA-46343

Deque uniqueness reports duplicate values instead of removed positions · case 03

Deque uniqueness reports duplicate values instead of removed positions.

Bounded deques◈ Members↗
FA-46344

Deque uniqueness reports duplicate values instead of removed positions · case 04

Deque uniqueness reports duplicate values instead of removed positions.

Bounded deques◈ Members↗
FA-46345

Deque uniqueness reports duplicate values instead of removed positions · case 05

Deque uniqueness reports duplicate values instead of removed positions.

Bounded deques◈ Members↗
FA-46346

Deque uniqueness prepends each first occurrence · case 01

Deque uniqueness prepends each first occurrence.

Bounded deques● Open access↗
FA-46347

Deque uniqueness prepends each first occurrence · case 02

Deque uniqueness prepends each first occurrence.

Bounded deques◈ Members↗
FA-46348

Deque uniqueness prepends each first occurrence · case 03

Deque uniqueness prepends each first occurrence.

Bounded deques◈ Members↗
FA-46349

Deque uniqueness prepends each first occurrence · case 04

Deque uniqueness prepends each first occurrence.

Bounded deques◈ Members↗
FA-46350

Deque uniqueness prepends each first occurrence · case 05

Deque uniqueness prepends each first occurrence.

Bounded deques◈ Members↗
FA-46351

Deque uniqueness treats zero as never seen · case 01

Deque uniqueness treats zero as never seen.

Bounded deques● Open access↗
FA-46352

Deque uniqueness treats zero as never seen · case 02

Deque uniqueness treats zero as never seen.

Bounded deques◈ Members↗
FA-46353

Deque uniqueness treats zero as never seen · case 03

Deque uniqueness treats zero as never seen.

Bounded deques◈ Members↗
FA-46354

Deque uniqueness treats zero as never seen · case 04

Deque uniqueness treats zero as never seen.

Bounded deques◈ Members↗
FA-46355

Deque uniqueness treats zero as never seen · case 05

Deque uniqueness treats zero as never seen.

Bounded deques◈ Members↗
FA-46356

Deque uniqueness accidentally returns duplicate positions as survivors · case 01

Deque uniqueness accidentally returns duplicate positions as survivors.

Bounded deques● Open access↗
FA-46357

Deque uniqueness accidentally returns duplicate positions as survivors · case 02

Deque uniqueness accidentally returns duplicate positions as survivors.

Bounded deques◈ Members↗
FA-46358

Deque uniqueness accidentally returns duplicate positions as survivors · case 03

Deque uniqueness accidentally returns duplicate positions as survivors.

Bounded deques◈ Members↗
FA-46359

Deque uniqueness accidentally returns duplicate positions as survivors · case 04

Deque uniqueness accidentally returns duplicate positions as survivors.

Bounded deques◈ Members↗
FA-46360

Deque uniqueness accidentally returns duplicate positions as survivors · case 05

Deque uniqueness accidentally returns duplicate positions as survivors.

Bounded deques◈ Members↗
FA-46361

Block split leaves the boundary value in both blocks · case 01

Block split leaves the boundary value in both blocks.

Bounded deques● Open access↗
FA-46362

Block split leaves the boundary value in both blocks · case 02

Block split leaves the boundary value in both blocks.

Bounded deques◈ Members↗
FA-46363

Block split leaves the boundary value in both blocks · case 03

Block split leaves the boundary value in both blocks.

Bounded deques◈ Members↗
FA-46364

Block split leaves the boundary value in both blocks · case 04

Block split leaves the boundary value in both blocks.

Bounded deques◈ Members↗
FA-46365

Block split leaves the boundary value in both blocks · case 05

Block split leaves the boundary value in both blocks.

Bounded deques◈ Members↗
FA-46366

Block split omits its first right-side value · case 01

Block split omits its first right-side value.

Bounded deques● Open access↗
FA-46367

Block split omits its first right-side value · case 02

Block split omits its first right-side value.

Bounded deques◈ Members↗
FA-46368

Block split omits its first right-side value · case 03

Block split omits its first right-side value.

Bounded deques◈ Members↗
FA-46369

Block split omits its first right-side value · case 04

Block split omits its first right-side value.

Bounded deques◈ Members↗
FA-46370

Block split omits its first right-side value · case 05

Block split omits its first right-side value.

Bounded deques◈ Members↗
FA-46371

Block split renames the block still held by existing handles · case 01

Block split renames the block still held by existing handles.

Bounded deques● Open access↗
FA-46372

Block split renames the block still held by existing handles · case 02

Block split renames the block still held by existing handles.

Bounded deques◈ Members↗
FA-46373

Block split renames the block still held by existing handles · case 03

Block split renames the block still held by existing handles.

Bounded deques◈ Members↗
FA-46374

Block split renames the block still held by existing handles · case 04

Block split renames the block still held by existing handles.

Bounded deques◈ Members↗
FA-46375

Block split renames the block still held by existing handles · case 05

Block split renames the block still held by existing handles.

Bounded deques◈ Members↗
FA-46376

Block split aliases both halves to the same block identity · case 01

Block split aliases both halves to the same block identity.

Bounded deques● Open access↗
FA-46377

Block split aliases both halves to the same block identity · case 02

Block split aliases both halves to the same block identity.

Bounded deques◈ Members↗
FA-46378

Block split aliases both halves to the same block identity · case 03

Block split aliases both halves to the same block identity.

Bounded deques◈ Members↗
FA-46379

Block split aliases both halves to the same block identity · case 04

Block split aliases both halves to the same block identity.

Bounded deques◈ Members↗
FA-46380

Block split aliases both halves to the same block identity · case 05

Block split aliases both halves to the same block identity.

Bounded deques◈ Members↗
FA-46381

Block split leaves directory cache generation unchanged · case 01

Block split leaves directory cache generation unchanged.

Bounded deques● Open access↗
FA-46382

Block split leaves directory cache generation unchanged · case 02

Block split leaves directory cache generation unchanged.

Bounded deques◈ Members↗
FA-46383

Block split leaves directory cache generation unchanged · case 03

Block split leaves directory cache generation unchanged.

Bounded deques◈ Members↗
FA-46384

Block split leaves directory cache generation unchanged · case 04

Block split leaves directory cache generation unchanged.

Bounded deques◈ Members↗
FA-46385

Block split leaves directory cache generation unchanged · case 05

Block split leaves directory cache generation unchanged.

Bounded deques◈ Members↗
FA-46386

Block split counts block descriptors as logical entries · case 01

Block split counts block descriptors as logical entries.

Bounded deques● Open access↗
FA-46387

Block split counts block descriptors as logical entries · case 02

Block split counts block descriptors as logical entries.

Bounded deques◈ Members↗
FA-46388

Block split counts block descriptors as logical entries · case 03

Block split counts block descriptors as logical entries.

Bounded deques◈ Members↗
FA-46389

Block split counts block descriptors as logical entries · case 04

Block split counts block descriptors as logical entries.

Bounded deques◈ Members↗
FA-46390

Block split counts block descriptors as logical entries · case 05

Block split counts block descriptors as logical entries.

Bounded deques◈ Members↗
FA-46391

Block split publishes its right block before its left block · case 01

Block split publishes its right block before its left block.

Bounded deques● Open access↗
FA-46392

Block split publishes its right block before its left block · case 02

Block split publishes its right block before its left block.

Bounded deques◈ Members↗
FA-46393

Block split publishes its right block before its left block · case 03

Block split publishes its right block before its left block.

Bounded deques◈ Members↗
FA-46394

Block split publishes its right block before its left block · case 04

Block split publishes its right block before its left block.

Bounded deques◈ Members↗
FA-46395

Block split publishes its right block before its left block · case 05

Block split publishes its right block before its left block.

Bounded deques◈ Members↗
FA-46396

Adjacent block merge ignores left block occupancy · case 01

Adjacent block merge ignores left block occupancy.

Bounded deques● Open access↗
FA-46397

Adjacent block merge ignores left block occupancy · case 02

Adjacent block merge ignores left block occupancy.

Bounded deques◈ Members↗
FA-46398

Adjacent block merge ignores left block occupancy · case 03

Adjacent block merge ignores left block occupancy.

Bounded deques◈ Members↗
FA-46399

Adjacent block merge ignores left block occupancy · case 04

Adjacent block merge ignores left block occupancy.

Bounded deques◈ Members↗
FA-46400

Adjacent block merge ignores left block occupancy · case 05

Adjacent block merge ignores left block occupancy.

Bounded deques◈ 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 ↗