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
Heterogeneous Channel Records: View channel mapping ignored or inverse permutation applied · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at physical_channel.
Heterogeneous Channel Records: View channel mapping ignored or inverse permutation applied · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at physical_channel.
Heterogeneous Channel Records: View channel mapping ignored or inverse permutation applied · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at physical_channel.
Heterogeneous Channel Records: View channel mapping ignored or inverse permutation applied · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at physical_channel.
Heterogeneous Channel Records: View channel mapping ignored or inverse permutation applied · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at physical_channel.
Heterogeneous Channel Records: Record-row guard omitted or inserted per pixel · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.
Heterogeneous Channel Records: Record-row guard omitted or inserted per pixel · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.
Heterogeneous Channel Records: Record-row guard omitted or inserted per pixel · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.
Heterogeneous Channel Records: Record-row guard omitted or inserted per pixel · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.
Heterogeneous Channel Records: Record-row guard omitted or inserted per pixel · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at row_pitch.
Heterogeneous Channel Records: Pixel record addressing excludes preceding footers or row guards · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at pixel_origin.
Heterogeneous Channel Records: Pixel record addressing excludes preceding footers or row guards · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at pixel_origin.
Heterogeneous Channel Records: Pixel record addressing excludes preceding footers or row guards · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at pixel_origin.
Heterogeneous Channel Records: Pixel record addressing excludes preceding footers or row guards · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at pixel_origin.
Heterogeneous Channel Records: Pixel record addressing excludes preceding footers or row guards · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at pixel_origin.
Heterogeneous Channel Records: Channel byte origin uses logical lane or channel number as byte offset · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_start.
Heterogeneous Channel Records: Channel byte origin uses logical lane or channel number as byte offset · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_start.
Heterogeneous Channel Records: Channel byte origin uses logical lane or channel number as byte offset · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_start.
Heterogeneous Channel Records: Channel byte origin uses logical lane or channel number as byte offset · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_start.
Heterogeneous Channel Records: Channel byte origin uses logical lane or channel number as byte offset · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_start.
Heterogeneous Channel Records: View channel byte size uses logical lane or widest channel · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_size.
Heterogeneous Channel Records: View channel byte size uses logical lane or widest channel · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_size.
Heterogeneous Channel Records: View channel byte size uses logical lane or widest channel · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_size.
Heterogeneous Channel Records: View channel byte size uses logical lane or widest channel · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_size.
Heterogeneous Channel Records: View channel byte size uses logical lane or widest channel · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_size.
Heterogeneous Channel Records: Channel view range includes other channels or uses inclusive endpoint · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_end.
Heterogeneous Channel Records: Channel view range includes other channels or uses inclusive endpoint · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_end.
Heterogeneous Channel Records: Channel view range includes other channels or uses inclusive endpoint · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_end.
Heterogeneous Channel Records: Channel view range includes other channels or uses inclusive endpoint · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_end.
Heterogeneous Channel Records: Channel view range includes other channels or uses inclusive endpoint · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at channel_end.
Heterogeneous Channel Records: Pixel footer update targets next pixel or selected channel endpoint · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at footer_start.
Heterogeneous Channel Records: Pixel footer update targets next pixel or selected channel endpoint · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at footer_start.
Heterogeneous Channel Records: Pixel footer update targets next pixel or selected channel endpoint · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at footer_start.
Heterogeneous Channel Records: Pixel footer update targets next pixel or selected channel endpoint · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at footer_start.
Heterogeneous Channel Records: Pixel footer update targets next pixel or selected channel endpoint · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at footer_start.
Heterogeneous Channel Records: Preservation ranges exclude logical instead of physical channel or omit aliases · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at other_channel_ranges.
Heterogeneous Channel Records: Preservation ranges exclude logical instead of physical channel or omit aliases · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at other_channel_ranges.
Heterogeneous Channel Records: Preservation ranges exclude logical instead of physical channel or omit aliases · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at other_channel_ranges.
Heterogeneous Channel Records: Preservation ranges exclude logical instead of physical channel or omit aliases · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at other_channel_ranges.
Heterogeneous Channel Records: Preservation ranges exclude logical instead of physical channel or omit aliases · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at other_channel_ranges.
Volume Transfer Skip Footprint: Upload source stride uses copied width or omits bytes per pixel · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at source_row_pitch.
Volume Transfer Skip Footprint: Upload source stride uses copied width or omits bytes per pixel · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at source_row_pitch.
Volume Transfer Skip Footprint: Upload source stride uses copied width or omits bytes per pixel · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at source_row_pitch.
Volume Transfer Skip Footprint: Upload source stride uses copied width or omits bytes per pixel · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at source_row_pitch.
Volume Transfer Skip Footprint: Upload source stride uses copied width or omits bytes per pixel · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at source_row_pitch.
Volume Transfer Skip Footprint: Upload slice stride uses copied height or one row · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at source_slice_pitch.
Volume Transfer Skip Footprint: Upload slice stride uses copied height or one row · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at source_slice_pitch.
Volume Transfer Skip Footprint: Upload slice stride uses copied height or one row · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at source_slice_pitch.
Volume Transfer Skip Footprint: Upload slice stride uses copied height or one row · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at source_slice_pitch.
Volume Transfer Skip Footprint: Upload slice stride uses copied height or one row · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at source_slice_pitch.
Volume Transfer Skip Footprint: Upload skips count pixels as bytes or images as rows · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at skip_bytes.
Volume Transfer Skip Footprint: Upload skips count pixels as bytes or images as rows · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at skip_bytes.
Volume Transfer Skip Footprint: Upload skips count pixels as bytes or images as rows · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at skip_bytes.
Volume Transfer Skip Footprint: Upload skips count pixels as bytes or images as rows · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at skip_bytes.
Volume Transfer Skip Footprint: Upload skips count pixels as bytes or images as rows · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at skip_bytes.
Volume Transfer Skip Footprint: Subvolume source origin discards skip footprint or source relocation · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at source_origin.
Volume Transfer Skip Footprint: Subvolume source origin discards skip footprint or source relocation · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at source_origin.
Volume Transfer Skip Footprint: Subvolume source origin discards skip footprint or source relocation · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at source_origin.
Volume Transfer Skip Footprint: Subvolume source origin discards skip footprint or source relocation · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at source_origin.
Volume Transfer Skip Footprint: Subvolume source origin discards skip footprint or source relocation · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at source_origin.
Volume Transfer Skip Footprint: Subvolume row copy includes skipped-row padding or counts pixels · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at row_bytes.
Volume Transfer Skip Footprint: Subvolume row copy includes skipped-row padding or counts pixels · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at row_bytes.
Volume Transfer Skip Footprint: Subvolume row copy includes skipped-row padding or counts pixels · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at row_bytes.
Volume Transfer Skip Footprint: Subvolume row copy includes skipped-row padding or counts pixels · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at row_bytes.
Volume Transfer Skip Footprint: Subvolume row copy includes skipped-row padding or counts pixels · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at row_bytes.
Volume Transfer Skip Footprint: Upload row list loses slice gaps or source row padding · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at source_rows.
Volume Transfer Skip Footprint: Upload row list loses slice gaps or source row padding · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at source_rows.
Volume Transfer Skip Footprint: Upload row list loses slice gaps or source row padding · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at source_rows.
Volume Transfer Skip Footprint: Upload row list loses slice gaps or source row padding · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at source_rows.
Volume Transfer Skip Footprint: Upload row list loses slice gaps or source row padding · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at source_rows.
Volume Transfer Skip Footprint: Destination volume inherits source footprint or omits slice pitch · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_rows.
Volume Transfer Skip Footprint: Destination volume inherits source footprint or omits slice pitch · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_rows.
Volume Transfer Skip Footprint: Destination volume inherits source footprint or omits slice pitch · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_rows.
Volume Transfer Skip Footprint: Destination volume inherits source footprint or omits slice pitch · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_rows.
Volume Transfer Skip Footprint: Destination volume inherits source footprint or omits slice pitch · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_rows.
Volume Transfer Skip Footprint: Volume transfer swaps source and destination or copies padding · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at transfers.
Volume Transfer Skip Footprint: Volume transfer swaps source and destination or copies padding · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at transfers.
Volume Transfer Skip Footprint: Volume transfer swaps source and destination or copies padding · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at transfers.
Volume Transfer Skip Footprint: Volume transfer swaps source and destination or copies padding · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at transfers.
Volume Transfer Skip Footprint: Volume transfer swaps source and destination or copies padding · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at transfers.
Volume Transfer Skip Footprint: Upload buffer requirement excludes skips/gaps or requires unused trailing row padding · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at source_required.
Volume Transfer Skip Footprint: Upload buffer requirement excludes skips/gaps or requires unused trailing row padding · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at source_required.
Volume Transfer Skip Footprint: Upload buffer requirement excludes skips/gaps or requires unused trailing row padding · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at source_required.
Volume Transfer Skip Footprint: Upload buffer requirement excludes skips/gaps or requires unused trailing row padding · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at source_required.
Volume Transfer Skip Footprint: Upload buffer requirement excludes skips/gaps or requires unused trailing row padding · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at source_required.
Volume Transfer Skip Footprint: Destination extent includes final unused slice padding or absolute base · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_required.
Volume Transfer Skip Footprint: Destination extent includes final unused slice padding or absolute base · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_required.
Volume Transfer Skip Footprint: Destination extent includes final unused slice padding or absolute base · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_required.
Volume Transfer Skip Footprint: Destination extent includes final unused slice padding or absolute base · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_required.
Volume Transfer Skip Footprint: Destination extent includes final unused slice padding or absolute base · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at destination_required.
Four Tap Sensor Storage: Tap quadrant width uses full sensor or vertical dimension · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at half_width.
Four Tap Sensor Storage: Tap quadrant width uses full sensor or vertical dimension · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at half_width.
Four Tap Sensor Storage: Tap quadrant width uses full sensor or vertical dimension · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at half_width.
Four Tap Sensor Storage: Tap quadrant width uses full sensor or vertical dimension · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at half_width.
Four Tap Sensor Storage: Tap quadrant width uses full sensor or vertical dimension · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at half_width.
Four Tap Sensor Storage: Tap quadrant height uses full sensor or horizontal dimension · case 01
The returned physical layout descriptor disagrees with the declared buffer mapping at half_height.
Four Tap Sensor Storage: Tap quadrant height uses full sensor or horizontal dimension · case 02
The returned physical layout descriptor disagrees with the declared buffer mapping at half_height.
Four Tap Sensor Storage: Tap quadrant height uses full sensor or horizontal dimension · case 03
The returned physical layout descriptor disagrees with the declared buffer mapping at half_height.
Four Tap Sensor Storage: Tap quadrant height uses full sensor or horizontal dimension · case 04
The returned physical layout descriptor disagrees with the declared buffer mapping at half_height.
Four Tap Sensor Storage: Tap quadrant height uses full sensor or horizontal dimension · case 05
The returned physical layout descriptor disagrees with the declared buffer mapping at half_height.
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 ↗