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

Capture Ring Frame Slots: Ring write slot uses epoch or previous generation · case 01

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

Raster memory layout● Open access↗
FA-52902

Capture Ring Frame Slots: Ring write slot uses epoch or previous generation · case 02

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

Raster memory layout◈ Members↗
FA-52903

Capture Ring Frame Slots: Ring write slot uses epoch or previous generation · case 03

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

Raster memory layout◈ Members↗
FA-52904

Capture Ring Frame Slots: Ring write slot uses epoch or previous generation · case 04

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

Raster memory layout◈ Members↗
FA-52905

Capture Ring Frame Slots: Ring write slot uses epoch or previous generation · case 05

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

Raster memory layout◈ Members↗
FA-52906

Capture Ring Frame Slots: Readback selects current write slot or generation epoch · case 01

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

Raster memory layout● Open access↗
FA-52907

Capture Ring Frame Slots: Readback selects current write slot or generation epoch · case 02

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

Raster memory layout◈ Members↗
FA-52908

Capture Ring Frame Slots: Readback selects current write slot or generation epoch · case 03

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

Raster memory layout◈ Members↗
FA-52909

Capture Ring Frame Slots: Readback selects current write slot or generation epoch · case 04

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

Raster memory layout◈ Members↗
FA-52910

Capture Ring Frame Slots: Readback selects current write slot or generation epoch · case 05

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

Raster memory layout◈ Members↗
FA-52911

Capture Ring Frame Slots: Ring write origin omits slot framing or fence pitch · case 01

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

Raster memory layout● Open access↗
FA-52912

Capture Ring Frame Slots: Ring write origin omits slot framing or fence pitch · case 02

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

Raster memory layout◈ Members↗
FA-52913

Capture Ring Frame Slots: Ring write origin omits slot framing or fence pitch · case 03

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

Raster memory layout◈ Members↗
FA-52914

Capture Ring Frame Slots: Ring write origin omits slot framing or fence pitch · case 04

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

Raster memory layout◈ Members↗
FA-52915

Capture Ring Frame Slots: Ring write origin omits slot framing or fence pitch · case 05

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

Raster memory layout◈ Members↗
FA-52916

Capture Ring Frame Slots: Ring read origin aliases writer or excludes slot framing · case 01

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

Raster memory layout● Open access↗
FA-52917

Capture Ring Frame Slots: Ring read origin aliases writer or excludes slot framing · case 02

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

Raster memory layout◈ Members↗
FA-52918

Capture Ring Frame Slots: Ring read origin aliases writer or excludes slot framing · case 03

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

Raster memory layout◈ Members↗
FA-52919

Capture Ring Frame Slots: Ring read origin aliases writer or excludes slot framing · case 04

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

Raster memory layout◈ Members↗
FA-52920

Capture Ring Frame Slots: Ring read origin aliases writer or excludes slot framing · case 05

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

Raster memory layout◈ Members↗
FA-52921

Capture Ring Frame Slots: Ring reuse freshness compares slots instead of full generations · case 01

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

Raster memory layout● Open access↗
FA-52922

Capture Ring Frame Slots: Ring reuse freshness compares slots instead of full generations · case 02

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

Raster memory layout◈ Members↗
FA-52923

Capture Ring Frame Slots: Ring reuse freshness compares slots instead of full generations · case 03

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

Raster memory layout◈ Members↗
FA-52924

Capture Ring Frame Slots: Ring reuse freshness compares slots instead of full generations · case 04

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

Raster memory layout◈ Members↗
FA-52925

Capture Ring Frame Slots: Ring reuse freshness compares slots instead of full generations · case 05

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

Raster memory layout◈ Members↗
FA-52926

Capture Ring Frame Slots: Readback accesses header or current write frame · case 01

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

Raster memory layout● Open access↗
FA-52927

Capture Ring Frame Slots: Readback accesses header or current write frame · case 02

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

Raster memory layout◈ Members↗
FA-52928

Capture Ring Frame Slots: Readback accesses header or current write frame · case 03

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

Raster memory layout◈ Members↗
FA-52929

Capture Ring Frame Slots: Readback accesses header or current write frame · case 04

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

Raster memory layout◈ Members↗
FA-52930

Capture Ring Frame Slots: Readback accesses header or current write frame · case 05

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

Raster memory layout◈ Members↗
FA-52931

Capture Ring Frame Slots: Capture fence overwrites final pixels or next slot header · case 01

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

Raster memory layout● Open access↗
FA-52932

Capture Ring Frame Slots: Capture fence overwrites final pixels or next slot header · case 02

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

Raster memory layout◈ Members↗
FA-52933

Capture Ring Frame Slots: Capture fence overwrites final pixels or next slot header · case 03

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

Raster memory layout◈ Members↗
FA-52934

Capture Ring Frame Slots: Capture fence overwrites final pixels or next slot header · case 04

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

Raster memory layout◈ Members↗
FA-52935

Capture Ring Frame Slots: Capture fence overwrites final pixels or next slot header · case 05

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

Raster memory layout◈ Members↗
FA-52936

Capture Ring Frame Slots: Ring allocation omits framing or one slot · case 01

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

Raster memory layout● Open access↗
FA-52937

Capture Ring Frame Slots: Ring allocation omits framing or one slot · case 02

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

Raster memory layout◈ Members↗
FA-52938

Capture Ring Frame Slots: Ring allocation omits framing or one slot · case 03

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

Raster memory layout◈ Members↗
FA-52939

Capture Ring Frame Slots: Ring allocation omits framing or one slot · case 04

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

Raster memory layout◈ Members↗
FA-52940

Capture Ring Frame Slots: Ring allocation omits framing or one slot · case 05

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

Raster memory layout◈ Members↗
FA-52941

Scanline Scatter Gather: First segment length ignores request origin or request endpoint · case 01

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

Raster memory layout● Open access↗
FA-52942

Scanline Scatter Gather: First segment length ignores request origin or request endpoint · case 02

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

Raster memory layout◈ Members↗
FA-52943

Scanline Scatter Gather: First segment length ignores request origin or request endpoint · case 03

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

Raster memory layout◈ Members↗
FA-52944

Scanline Scatter Gather: First segment length ignores request origin or request endpoint · case 04

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

Raster memory layout◈ Members↗
FA-52945

Scanline Scatter Gather: First segment length ignores request origin or request endpoint · case 05

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

Raster memory layout◈ Members↗
FA-52946

Scanline Scatter Gather: Second segment length includes first segment or subtracts absolute split · case 01

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

Raster memory layout● Open access↗
FA-52947

Scanline Scatter Gather: Second segment length includes first segment or subtracts absolute split · case 02

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

Raster memory layout◈ Members↗
FA-52948

Scanline Scatter Gather: Second segment length includes first segment or subtracts absolute split · case 03

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

Raster memory layout◈ Members↗
FA-52949

Scanline Scatter Gather: Second segment length includes first segment or subtracts absolute split · case 04

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

Raster memory layout◈ Members↗
FA-52950

Scanline Scatter Gather: Second segment length includes first segment or subtracts absolute split · case 05

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

Raster memory layout◈ Members↗
FA-52951

Scanline Scatter Gather: First segment origin omits x offset or byte conversion · case 01

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

Raster memory layout● Open access↗
FA-52952

Scanline Scatter Gather: First segment origin omits x offset or byte conversion · case 02

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

Raster memory layout◈ Members↗
FA-52953

Scanline Scatter Gather: First segment origin omits x offset or byte conversion · case 03

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

Raster memory layout◈ Members↗
FA-52954

Scanline Scatter Gather: First segment origin omits x offset or byte conversion · case 04

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

Raster memory layout◈ Members↗
FA-52955

Scanline Scatter Gather: First segment origin omits x offset or byte conversion · case 05

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

Raster memory layout◈ Members↗
FA-52956

Scanline Scatter Gather: Second segment local origin retains global coordinate or becomes negative · case 01

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

Raster memory layout● Open access↗
FA-52957

Scanline Scatter Gather: Second segment local origin retains global coordinate or becomes negative · case 02

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

Raster memory layout◈ Members↗
FA-52958

Scanline Scatter Gather: Second segment local origin retains global coordinate or becomes negative · case 03

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

Raster memory layout◈ Members↗
FA-52959

Scanline Scatter Gather: Second segment local origin retains global coordinate or becomes negative · case 04

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

Raster memory layout◈ Members↗
FA-52960

Scanline Scatter Gather: Second segment local origin retains global coordinate or becomes negative · case 05

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

Raster memory layout◈ Members↗
FA-52961

Scanline Scatter Gather: Second segment assumes physical adjacency or loses pixel width · case 01

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

Raster memory layout● Open access↗
FA-52962

Scanline Scatter Gather: Second segment assumes physical adjacency or loses pixel width · case 02

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

Raster memory layout◈ Members↗
FA-52963

Scanline Scatter Gather: Second segment assumes physical adjacency or loses pixel width · case 03

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

Raster memory layout◈ Members↗
FA-52964

Scanline Scatter Gather: Second segment assumes physical adjacency or loses pixel width · case 04

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

Raster memory layout◈ Members↗
FA-52965

Scanline Scatter Gather: Second segment assumes physical adjacency or loses pixel width · case 05

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

Raster memory layout◈ Members↗
FA-52966

Scanline Scatter Gather: First span size is pixel count or entire segment extent · case 01

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

Raster memory layout● Open access↗
FA-52967

Scanline Scatter Gather: First span size is pixel count or entire segment extent · case 02

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

Raster memory layout◈ Members↗
FA-52968

Scanline Scatter Gather: First span size is pixel count or entire segment extent · case 03

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

Raster memory layout◈ Members↗
FA-52969

Scanline Scatter Gather: First span size is pixel count or entire segment extent · case 04

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

Raster memory layout◈ Members↗
FA-52970

Scanline Scatter Gather: First span size is pixel count or entire segment extent · case 05

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

Raster memory layout◈ Members↗
FA-52971

Scanline Scatter Gather: Second span size is pixels or full remaining scanline · case 01

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

Raster memory layout● Open access↗
FA-52972

Scanline Scatter Gather: Second span size is pixels or full remaining scanline · case 02

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

Raster memory layout◈ Members↗
FA-52973

Scanline Scatter Gather: Second span size is pixels or full remaining scanline · case 03

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

Raster memory layout◈ Members↗
FA-52974

Scanline Scatter Gather: Second span size is pixels or full remaining scanline · case 04

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

Raster memory layout◈ Members↗
FA-52975

Scanline Scatter Gather: Second span size is pixels or full remaining scanline · case 05

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

Raster memory layout◈ Members↗
FA-52976

Scanline Scatter Gather: Scatter-gather emits empty spans or reverses logical raster order · case 01

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

Raster memory layout● Open access↗
FA-52977

Scanline Scatter Gather: Scatter-gather emits empty spans or reverses logical raster order · case 02

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

Raster memory layout◈ Members↗
FA-52978

Scanline Scatter Gather: Scatter-gather emits empty spans or reverses logical raster order · case 03

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

Raster memory layout◈ Members↗
FA-52979

Scanline Scatter Gather: Scatter-gather emits empty spans or reverses logical raster order · case 04

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

Raster memory layout◈ Members↗
FA-52980

Scanline Scatter Gather: Scatter-gather emits empty spans or reverses logical raster order · case 05

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

Raster memory layout◈ Members↗
FA-52981

Scanline Scatter Gather: Gather destination overwrites first segment or uses pixel offset · case 01

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

Raster memory layout● Open access↗
FA-52982

Scanline Scatter Gather: Gather destination overwrites first segment or uses pixel offset · case 02

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

Raster memory layout◈ Members↗
FA-52983

Scanline Scatter Gather: Gather destination overwrites first segment or uses pixel offset · case 03

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

Raster memory layout◈ Members↗
FA-52984

Scanline Scatter Gather: Gather destination overwrites first segment or uses pixel offset · case 04

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

Raster memory layout◈ Members↗
FA-52985

Scanline Scatter Gather: Gather destination overwrites first segment or uses pixel offset · case 05

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

Raster memory layout◈ Members↗
FA-52986

Scanline Scatter Gather: Gather output extent uses full row or sums addresses · case 01

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

Raster memory layout● Open access↗
FA-52987

Scanline Scatter Gather: Gather output extent uses full row or sums addresses · case 02

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

Raster memory layout◈ Members↗
FA-52988

Scanline Scatter Gather: Gather output extent uses full row or sums addresses · case 03

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

Raster memory layout◈ Members↗
FA-52989

Scanline Scatter Gather: Gather output extent uses full row or sums addresses · case 04

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

Raster memory layout◈ Members↗
FA-52990

Scanline Scatter Gather: Gather output extent uses full row or sums addresses · case 05

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

Raster memory layout◈ Members↗
FA-52991

Virtual Texture Gutter Atlas: Atlas residency mapping bypassed or physical row discarded · case 01

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

Raster memory layout● Open access↗
FA-52992

Virtual Texture Gutter Atlas: Atlas residency mapping bypassed or physical row discarded · case 02

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

Raster memory layout◈ Members↗
FA-52993

Virtual Texture Gutter Atlas: Atlas residency mapping bypassed or physical row discarded · case 03

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

Raster memory layout◈ Members↗
FA-52994

Virtual Texture Gutter Atlas: Atlas residency mapping bypassed or physical row discarded · case 04

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

Raster memory layout◈ Members↗
FA-52995

Virtual Texture Gutter Atlas: Atlas residency mapping bypassed or physical row discarded · case 05

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

Raster memory layout◈ Members↗
FA-52996

Virtual Texture Gutter Atlas: Atlas cells transpose coordinates or use tile interior width as columns · case 01

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

Raster memory layout● Open access↗
FA-52997

Virtual Texture Gutter Atlas: Atlas cells transpose coordinates or use tile interior width as columns · case 02

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

Raster memory layout◈ Members↗
FA-52998

Virtual Texture Gutter Atlas: Atlas cells transpose coordinates or use tile interior width as columns · case 03

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

Raster memory layout◈ Members↗
FA-52999

Virtual Texture Gutter Atlas: Atlas cells transpose coordinates or use tile interior width as columns · case 04

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

Raster memory layout◈ Members↗
FA-53000

Virtual Texture Gutter Atlas: Atlas cells transpose coordinates or use tile interior width as columns · case 05

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

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 ↗