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
Nested Macrotiles: Macrotile y uses microtile division or remainder · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_y.
Nested Macrotiles: Macrotile y uses microtile division or remainder · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_y.
Nested Macrotiles: Macrotile y uses microtile division or remainder · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_y.
Nested Macrotiles: Macrotile y uses microtile division or remainder · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_y.
Nested Macrotiles: Macrotile y uses microtile division or remainder · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_y.
Nested Macrotiles: Macrotile directory is traversed on the wrong axis · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_id.
Nested Macrotiles: Macrotile directory is traversed on the wrong axis · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_id.
Nested Macrotiles: Macrotile directory is traversed on the wrong axis · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_id.
Nested Macrotiles: Macrotile directory is traversed on the wrong axis · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_id.
Nested Macrotiles: Macrotile directory is traversed on the wrong axis · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_id.
Nested Macrotiles: Microtile x retains the macrotile component · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_x.
Nested Macrotiles: Microtile x retains the macrotile component · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_x.
Nested Macrotiles: Microtile x retains the macrotile component · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_x.
Nested Macrotiles: Microtile x retains the macrotile component · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_x.
Nested Macrotiles: Microtile x retains the macrotile component · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_x.
Nested Macrotiles: Microtile y retains the macrotile component · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_y.
Nested Macrotiles: Microtile y retains the macrotile component · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_y.
Nested Macrotiles: Microtile y retains the macrotile component · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_y.
Nested Macrotiles: Microtile y retains the macrotile component · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_y.
Nested Macrotiles: Microtile y retains the macrotile component · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_y.
Nested Macrotiles: Column-major microtile ordering is decoded row-major · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_id.
Nested Macrotiles: Column-major microtile ordering is decoded row-major · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_id.
Nested Macrotiles: Column-major microtile ordering is decoded row-major · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_id.
Nested Macrotiles: Column-major microtile ordering is decoded row-major · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_id.
Nested Macrotiles: Column-major microtile ordering is decoded row-major · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at micro_id.
Nested Macrotiles: Texel coordinate is transposed or reduced at wrong tile level · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Nested Macrotiles: Texel coordinate is transposed or reduced at wrong tile level · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Nested Macrotiles: Texel coordinate is transposed or reduced at wrong tile level · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Nested Macrotiles: Texel coordinate is transposed or reduced at wrong tile level · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Nested Macrotiles: Texel coordinate is transposed or reduced at wrong tile level · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Nested Macrotiles: Macrotile trailer is omitted or repeated per texel · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_pitch.
Nested Macrotiles: Macrotile trailer is omitted or repeated per texel · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_pitch.
Nested Macrotiles: Macrotile trailer is omitted or repeated per texel · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_pitch.
Nested Macrotiles: Macrotile trailer is omitted or repeated per texel · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_pitch.
Nested Macrotiles: Macrotile trailer is omitted or repeated per texel · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at macro_pitch.
Nested Macrotiles: Microtile origin uses pixels as bytes or edge length as area · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Nested Macrotiles: Microtile origin uses pixels as bytes or edge length as area · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Nested Macrotiles: Microtile origin uses pixels as bytes or edge length as area · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Nested Macrotiles: Microtile origin uses pixels as bytes or edge length as area · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Nested Macrotiles: Microtile origin uses pixels as bytes or edge length as area · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Bricked Volume: Volume brick column count drops partial bricks · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_columns.
Bricked Volume: Volume brick column count drops partial bricks · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_columns.
Bricked Volume: Volume brick column count drops partial bricks · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_columns.
Bricked Volume: Volume brick column count drops partial bricks · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_columns.
Bricked Volume: Volume brick column count drops partial bricks · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_columns.
Bricked Volume: Volume brick row count uses wrong footprint · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_rows.
Bricked Volume: Volume brick row count uses wrong footprint · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_rows.
Bricked Volume: Volume brick row count uses wrong footprint · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_rows.
Bricked Volume: Volume brick row count uses wrong footprint · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_rows.
Bricked Volume: Volume brick row count uses wrong footprint · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_rows.
Bricked Volume: Brick depth rounding drops final slab · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_layers.
Bricked Volume: Brick depth rounding drops final slab · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_layers.
Bricked Volume: Brick depth rounding drops final slab · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_layers.
Bricked Volume: Brick depth rounding drops final slab · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_layers.
Bricked Volume: Brick depth rounding drops final slab · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_layers.
Bricked Volume: Brick slice directory is transposed · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_xy.
Bricked Volume: Brick slice directory is transposed · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_xy.
Bricked Volume: Brick slice directory is transposed · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_xy.
Bricked Volume: Brick slice directory is transposed · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_xy.
Bricked Volume: Brick slice directory is transposed · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_xy.
Bricked Volume: Volume slab stride omits brick rows · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_id.
Bricked Volume: Volume slab stride omits brick rows · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_id.
Bricked Volume: Volume slab stride omits brick rows · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_id.
Bricked Volume: Volume slab stride omits brick rows · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_id.
Bricked Volume: Volume slab stride omits brick rows · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_id.
Bricked Volume: Brick-local depth is confused with slab number · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at local_slice.
Bricked Volume: Brick-local depth is confused with slab number · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at local_slice.
Bricked Volume: Brick-local depth is confused with slab number · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at local_slice.
Bricked Volume: Brick-local depth is confused with slab number · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at local_slice.
Bricked Volume: Brick-local depth is confused with slab number · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at local_slice.
Bricked Volume: Brick-local slice pitch uses edge length instead of slice area · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Bricked Volume: Brick-local slice pitch uses edge length instead of slice area · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Bricked Volume: Brick-local slice pitch uses edge length instead of slice area · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Bricked Volume: Brick-local slice pitch uses edge length instead of slice area · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Bricked Volume: Brick-local slice pitch uses edge length instead of slice area · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at local_texel.
Bricked Volume: Volume metadata is omitted or charged per voxel · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_pitch.
Bricked Volume: Volume metadata is omitted or charged per voxel · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_pitch.
Bricked Volume: Volume metadata is omitted or charged per voxel · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_pitch.
Bricked Volume: Volume metadata is omitted or charged per voxel · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_pitch.
Bricked Volume: Volume metadata is omitted or charged per voxel · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at brick_pitch.
Bricked Volume: Allocation ignores padded brick depth and metadata · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.
Bricked Volume: Allocation ignores padded brick depth and metadata · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.
Bricked Volume: Allocation ignores padded brick depth and metadata · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.
Bricked Volume: Allocation ignores padded brick depth and metadata · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.
Bricked Volume: Allocation ignores padded brick depth and metadata · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at allocation.
Bricked Volume: Voxel address omits brick prefix or voxel byte width · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Bricked Volume: Voxel address omits brick prefix or voxel byte width · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Bricked Volume: Voxel address omits brick prefix or voxel byte width · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Bricked Volume: Voxel address omits brick prefix or voxel byte width · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Bricked Volume: Voxel address omits brick prefix or voxel byte width · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at address.
Compressed Block Payload: Compression columns are counted as pixels or truncated · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at block_columns.
Compressed Block Payload: Compression columns are counted as pixels or truncated · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at block_columns.
Compressed Block Payload: Compression columns are counted as pixels or truncated · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at block_columns.
Compressed Block Payload: Compression columns are counted as pixels or truncated · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at block_columns.
Compressed Block Payload: Compression columns are counted as pixels or truncated · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at block_columns.
Compressed Block Payload: Compression row count assumes square block footprint · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at block_rows.
Compressed Block Payload: Compression row count assumes square block footprint · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at block_rows.
Compressed Block Payload: Compression row count assumes square block footprint · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at block_rows.
Compressed Block Payload: Compression row count assumes square block footprint · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at block_rows.
Compressed Block Payload: Compression row count assumes square block footprint · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at block_rows.
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 ↗