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

Compressed Block Payload: Block-row padding misses partial groups or overpads exact groups · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at padded_columns.

Raster memory layout● Open access↗
FA-52002

Compressed Block Payload: Block-row padding misses partial groups or overpads exact groups · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at padded_columns.

Raster memory layout◈ Members↗
FA-52003

Compressed Block Payload: Block-row padding misses partial groups or overpads exact groups · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at padded_columns.

Raster memory layout◈ Members↗
FA-52004

Compressed Block Payload: Block-row padding misses partial groups or overpads exact groups · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at padded_columns.

Raster memory layout◈ Members↗
FA-52005

Compressed Block Payload: Block-row padding misses partial groups or overpads exact groups · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at padded_columns.

Raster memory layout◈ Members↗
FA-52006

Compressed Block Payload: Endpoint and selector segments are multiplied or prefix dropped · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at block_size.

Raster memory layout● Open access↗
FA-52007

Compressed Block Payload: Endpoint and selector segments are multiplied or prefix dropped · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at block_size.

Raster memory layout◈ Members↗
FA-52008

Compressed Block Payload: Endpoint and selector segments are multiplied or prefix dropped · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at block_size.

Raster memory layout◈ Members↗
FA-52009

Compressed Block Payload: Endpoint and selector segments are multiplied or prefix dropped · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at block_size.

Raster memory layout◈ Members↗
FA-52010

Compressed Block Payload: Endpoint and selector segments are multiplied or prefix dropped · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at block_size.

Raster memory layout◈ Members↗
FA-52011

Compressed Block Payload: Compressed row pitch ignores padding or endpoint bytes · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.

Raster memory layout● Open access↗
FA-52012

Compressed Block Payload: Compressed row pitch ignores padding or endpoint bytes · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.

Raster memory layout◈ Members↗
FA-52013

Compressed Block Payload: Compressed row pitch ignores padding or endpoint bytes · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.

Raster memory layout◈ Members↗
FA-52014

Compressed Block Payload: Compressed row pitch ignores padding or endpoint bytes · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.

Raster memory layout◈ Members↗
FA-52015

Compressed Block Payload: Compressed row pitch ignores padding or endpoint bytes · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.

Raster memory layout◈ Members↗
FA-52016

Compressed Block Payload: Compressed texel coordinates are not converted to block coordinates · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at block_start.

Raster memory layout● Open access↗
FA-52017

Compressed Block Payload: Compressed texel coordinates are not converted to block coordinates · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at block_start.

Raster memory layout◈ Members↗
FA-52018

Compressed Block Payload: Compressed texel coordinates are not converted to block coordinates · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at block_start.

Raster memory layout◈ Members↗
FA-52019

Compressed Block Payload: Compressed texel coordinates are not converted to block coordinates · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at block_start.

Raster memory layout◈ Members↗
FA-52020

Compressed Block Payload: Compressed texel coordinates are not converted to block coordinates · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at block_start.

Raster memory layout◈ Members↗
FA-52021

Compressed Block Payload: Selector ordering is transposed or assumes square blocks · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_id.

Raster memory layout● Open access↗
FA-52022

Compressed Block Payload: Selector ordering is transposed or assumes square blocks · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_id.

Raster memory layout◈ Members↗
FA-52023

Compressed Block Payload: Selector ordering is transposed or assumes square blocks · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_id.

Raster memory layout◈ Members↗
FA-52024

Compressed Block Payload: Selector ordering is transposed or assumes square blocks · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_id.

Raster memory layout◈ Members↗
FA-52025

Compressed Block Payload: Selector ordering is transposed or assumes square blocks · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_id.

Raster memory layout◈ Members↗
FA-52026

Compressed Block Payload: Selector starts in endpoint prefix or uses endpoint count as stride · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_address.

Raster memory layout● Open access↗
FA-52027

Compressed Block Payload: Selector starts in endpoint prefix or uses endpoint count as stride · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_address.

Raster memory layout◈ Members↗
FA-52028

Compressed Block Payload: Selector starts in endpoint prefix or uses endpoint count as stride · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_address.

Raster memory layout◈ Members↗
FA-52029

Compressed Block Payload: Selector starts in endpoint prefix or uses endpoint count as stride · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_address.

Raster memory layout◈ Members↗
FA-52030

Compressed Block Payload: Selector starts in endpoint prefix or uses endpoint count as stride · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at selector_address.

Raster memory layout◈ Members↗
FA-52031

Compressed Block Payload: Compressed allocation uses texel rows or omits block-row padding · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.

Raster memory layout● Open access↗
FA-52032

Compressed Block Payload: Compressed allocation uses texel rows or omits block-row padding · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.

Raster memory layout◈ Members↗
FA-52033

Compressed Block Payload: Compressed allocation uses texel rows or omits block-row padding · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.

Raster memory layout◈ Members↗
FA-52034

Compressed Block Payload: Compressed allocation uses texel rows or omits block-row padding · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.

Raster memory layout◈ Members↗
FA-52035

Compressed Block Payload: Compressed allocation uses texel rows or omits block-row padding · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.

Raster memory layout◈ Members↗
FA-52036

Compressed Block Payload: Edge-block valid extent is replaced by full or image-wide footprint · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at block_valid_texels.

Raster memory layout● Open access↗
FA-52037

Compressed Block Payload: Edge-block valid extent is replaced by full or image-wide footprint · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at block_valid_texels.

Raster memory layout◈ Members↗
FA-52038

Compressed Block Payload: Edge-block valid extent is replaced by full or image-wide footprint · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at block_valid_texels.

Raster memory layout◈ Members↗
FA-52039

Compressed Block Payload: Edge-block valid extent is replaced by full or image-wide footprint · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at block_valid_texels.

Raster memory layout◈ Members↗
FA-52040

Compressed Block Payload: Edge-block valid extent is replaced by full or image-wide footprint · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at block_valid_texels.

Raster memory layout◈ Members↗
FA-52041

Mip Chain Directory: Mip widths truncate odd edges or use linear divisors · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at widths.

Raster memory layout● Open access↗
FA-52042

Mip Chain Directory: Mip widths truncate odd edges or use linear divisors · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at widths.

Raster memory layout◈ Members↗
FA-52043

Mip Chain Directory: Mip widths truncate odd edges or use linear divisors · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at widths.

Raster memory layout◈ Members↗
FA-52044

Mip Chain Directory: Mip widths truncate odd edges or use linear divisors · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at widths.

Raster memory layout◈ Members↗
FA-52045

Mip Chain Directory: Mip widths truncate odd edges or use linear divisors · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at widths.

Raster memory layout◈ Members↗
FA-52046

Mip Chain Directory: Mip heights drop odd rows or never shrink · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at heights.

Raster memory layout● Open access↗
FA-52047

Mip Chain Directory: Mip heights drop odd rows or never shrink · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at heights.

Raster memory layout◈ Members↗
FA-52048

Mip Chain Directory: Mip heights drop odd rows or never shrink · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at heights.

Raster memory layout◈ Members↗
FA-52049

Mip Chain Directory: Mip heights drop odd rows or never shrink · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at heights.

Raster memory layout◈ Members↗
FA-52050

Mip Chain Directory: Mip heights drop odd rows or never shrink · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at heights.

Raster memory layout◈ Members↗
FA-52051

Mip Chain Directory: Mip row guards are missing or level-zero stride reused · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitches.

Raster memory layout● Open access↗
FA-52052

Mip Chain Directory: Mip row guards are missing or level-zero stride reused · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitches.

Raster memory layout◈ Members↗
FA-52053

Mip Chain Directory: Mip row guards are missing or level-zero stride reused · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitches.

Raster memory layout◈ Members↗
FA-52054

Mip Chain Directory: Mip row guards are missing or level-zero stride reused · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitches.

Raster memory layout◈ Members↗
FA-52055

Mip Chain Directory: Mip row guards are missing or level-zero stride reused · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitches.

Raster memory layout◈ Members↗
FA-52056

Mip Chain Directory: Level header omitted or inserted before every row · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at level_sizes.

Raster memory layout● Open access↗
FA-52057

Mip Chain Directory: Level header omitted or inserted before every row · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at level_sizes.

Raster memory layout◈ Members↗
FA-52058

Mip Chain Directory: Level header omitted or inserted before every row · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at level_sizes.

Raster memory layout◈ Members↗
FA-52059

Mip Chain Directory: Level header omitted or inserted before every row · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at level_sizes.

Raster memory layout◈ Members↗
FA-52060

Mip Chain Directory: Level header omitted or inserted before every row · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at level_sizes.

Raster memory layout◈ Members↗
FA-52061

Mip Chain Directory: Mip directory size uses entry count or texel width · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at directory_size.

Raster memory layout● Open access↗
FA-52062

Mip Chain Directory: Mip directory size uses entry count or texel width · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at directory_size.

Raster memory layout◈ Members↗
FA-52063

Mip Chain Directory: Mip directory size uses entry count or texel width · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at directory_size.

Raster memory layout◈ Members↗
FA-52064

Mip Chain Directory: Mip directory size uses entry count or texel width · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at directory_size.

Raster memory layout◈ Members↗
FA-52065

Mip Chain Directory: Mip directory size uses entry count or texel width · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at directory_size.

Raster memory layout◈ Members↗
FA-52066

Mip Chain Directory: Mip starts include current size or use constant largest-level pitch · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at level_offsets.

Raster memory layout● Open access↗
FA-52067

Mip Chain Directory: Mip starts include current size or use constant largest-level pitch · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at level_offsets.

Raster memory layout◈ Members↗
FA-52068

Mip Chain Directory: Mip starts include current size or use constant largest-level pitch · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at level_offsets.

Raster memory layout◈ Members↗
FA-52069

Mip Chain Directory: Mip starts include current size or use constant largest-level pitch · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at level_offsets.

Raster memory layout◈ Members↗
FA-52070

Mip Chain Directory: Mip starts include current size or use constant largest-level pitch · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at level_offsets.

Raster memory layout◈ Members↗
FA-52071

Mip Chain Directory: Selected mip extent is read from base or terminal level · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at selected_size.

Raster memory layout● Open access↗
FA-52072

Mip Chain Directory: Selected mip extent is read from base or terminal level · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at selected_size.

Raster memory layout◈ Members↗
FA-52073

Mip Chain Directory: Selected mip extent is read from base or terminal level · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at selected_size.

Raster memory layout◈ Members↗
FA-52074

Mip Chain Directory: Selected mip extent is read from base or terminal level · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at selected_size.

Raster memory layout◈ Members↗
FA-52075

Mip Chain Directory: Selected mip extent is read from base or terminal level · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at selected_size.

Raster memory layout◈ Members↗
FA-52076

Mip Chain Directory: Selected mip origin loses level index or allocation relocation · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at level_origin.

Raster memory layout● Open access↗
FA-52077

Mip Chain Directory: Selected mip origin loses level index or allocation relocation · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at level_origin.

Raster memory layout◈ Members↗
FA-52078

Mip Chain Directory: Selected mip origin loses level index or allocation relocation · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at level_origin.

Raster memory layout◈ Members↗
FA-52079

Mip Chain Directory: Selected mip origin loses level index or allocation relocation · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at level_origin.

Raster memory layout◈ Members↗
FA-52080

Mip Chain Directory: Selected mip origin loses level index or allocation relocation · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at level_origin.

Raster memory layout◈ Members↗
FA-52081

Mip Chain Directory: Mip payload origin ignores header or counts it per scanline · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at payload_origin.

Raster memory layout● Open access↗
FA-52082

Mip Chain Directory: Mip payload origin ignores header or counts it per scanline · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at payload_origin.

Raster memory layout◈ Members↗
FA-52083

Mip Chain Directory: Mip payload origin ignores header or counts it per scanline · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at payload_origin.

Raster memory layout◈ Members↗
FA-52084

Mip Chain Directory: Mip payload origin ignores header or counts it per scanline · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at payload_origin.

Raster memory layout◈ Members↗
FA-52085

Mip Chain Directory: Mip payload origin ignores header or counts it per scanline · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at payload_origin.

Raster memory layout◈ Members↗
FA-52086

Mip Chain Directory: Mip chain extent excludes directory or later levels · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.

Raster memory layout● Open access↗
FA-52087

Mip Chain Directory: Mip chain extent excludes directory or later levels · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.

Raster memory layout◈ Members↗
FA-52088

Mip Chain Directory: Mip chain extent excludes directory or later levels · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.

Raster memory layout◈ Members↗
FA-52089

Mip Chain Directory: Mip chain extent excludes directory or later levels · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.

Raster memory layout◈ Members↗
FA-52090

Mip Chain Directory: Mip chain extent excludes directory or later levels · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at allocation_end.

Raster memory layout◈ Members↗
FA-52091

Mip Major Array: Array mip dimensions are truncated or held constant · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at dims.

Raster memory layout● Open access↗
FA-52092

Mip Major Array: Array mip dimensions are truncated or held constant · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at dims.

Raster memory layout◈ Members↗
FA-52093

Mip Major Array: Array mip dimensions are truncated or held constant · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at dims.

Raster memory layout◈ Members↗
FA-52094

Mip Major Array: Array mip dimensions are truncated or held constant · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at dims.

Raster memory layout◈ Members↗
FA-52095

Mip Major Array: Array mip dimensions are truncated or held constant · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at dims.

Raster memory layout◈ Members↗
FA-52096

Mip Major Array: Rectangular array mip area uses sum or square · case 01

The returned physical layout descriptor disagrees with the declared buffer mapping at texel_counts.

Raster memory layout● Open access↗
FA-52097

Mip Major Array: Rectangular array mip area uses sum or square · case 02

The returned physical layout descriptor disagrees with the declared buffer mapping at texel_counts.

Raster memory layout◈ Members↗
FA-52098

Mip Major Array: Rectangular array mip area uses sum or square · case 03

The returned physical layout descriptor disagrees with the declared buffer mapping at texel_counts.

Raster memory layout◈ Members↗
FA-52099

Mip Major Array: Rectangular array mip area uses sum or square · case 04

The returned physical layout descriptor disagrees with the declared buffer mapping at texel_counts.

Raster memory layout◈ Members↗
FA-52100

Mip Major Array: Rectangular array mip area uses sum or square · case 05

The returned physical layout descriptor disagrees with the declared buffer mapping at texel_counts.

Raster memory layout◈ 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 ↗