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

Cosine restarts are misaligned with the end of warmup · case 01

Cosine restarts are misaligned with the end of warmup.

Learning rate schedules● Open access↗
FA-99102

Cosine restarts are misaligned with the end of warmup · case 02

Cosine restarts are misaligned with the end of warmup.

Learning rate schedules◈ Members↗
FA-99103

Cosine restarts are misaligned with the end of warmup · case 03

Cosine restarts are misaligned with the end of warmup.

Learning rate schedules◈ Members↗
FA-99104

Cosine restarts are misaligned with the end of warmup · case 04

Cosine restarts are misaligned with the end of warmup.

Learning rate schedules◈ Members↗
FA-99105

Cosine restarts are misaligned with the end of warmup · case 05

Cosine restarts are misaligned with the end of warmup.

Learning rate schedules◈ Members↗
FA-99106

Hold time consumes part of the decay ramp · case 01

Hold time consumes part of the decay ramp.

Learning rate schedules● Open access↗
FA-99107

Hold time consumes part of the decay ramp · case 02

Hold time consumes part of the decay ramp.

Learning rate schedules◈ Members↗
FA-99108

Hold time consumes part of the decay ramp · case 03

Hold time consumes part of the decay ramp.

Learning rate schedules◈ Members↗
FA-99109

Hold time consumes part of the decay ramp · case 04

Hold time consumes part of the decay ramp.

Learning rate schedules◈ Members↗
FA-99110

Hold time consumes part of the decay ramp · case 05

Hold time consumes part of the decay ramp.

Learning rate schedules◈ Members↗
FA-99111

Piecewise interpolation is anchored at the upper knot · case 01

Piecewise interpolation is anchored at the upper knot.

Learning rate schedules● Open access↗
FA-99112

Piecewise interpolation is anchored at the upper knot · case 02

Piecewise interpolation is anchored at the upper knot.

Learning rate schedules◈ Members↗
FA-99113

Piecewise interpolation is anchored at the upper knot · case 03

Piecewise interpolation is anchored at the upper knot.

Learning rate schedules◈ Members↗
FA-99114

Piecewise interpolation is anchored at the upper knot · case 04

Piecewise interpolation is anchored at the upper knot.

Learning rate schedules◈ Members↗
FA-99115

Piecewise interpolation is anchored at the upper knot · case 05

Piecewise interpolation is anchored at the upper knot.

Learning rate schedules◈ Members↗
FA-99116

Linear decay ignores the configured minimum rate · case 01

Linear decay ignores the configured minimum rate.

Learning rate schedules● Open access↗
FA-99117

Linear decay ignores the configured minimum rate · case 02

Linear decay ignores the configured minimum rate.

Learning rate schedules◈ Members↗
FA-99118

Linear decay ignores the configured minimum rate · case 03

Linear decay ignores the configured minimum rate.

Learning rate schedules◈ Members↗
FA-99119

Linear decay ignores the configured minimum rate · case 04

Linear decay ignores the configured minimum rate.

Learning rate schedules◈ Members↗
FA-99120

Linear decay ignores the configured minimum rate · case 05

Linear decay ignores the configured minimum rate.

Learning rate schedules◈ Members↗
FA-99121

Linear schedule exceeds its configured rate ceiling · case 01

Linear schedule exceeds its configured rate ceiling.

Learning rate schedules● Open access↗
FA-99122

Linear schedule exceeds its configured rate ceiling · case 02

Linear schedule exceeds its configured rate ceiling.

Learning rate schedules◈ Members↗
FA-99123

Linear schedule exceeds its configured rate ceiling · case 03

Linear schedule exceeds its configured rate ceiling.

Learning rate schedules◈ Members↗
FA-99124

Linear schedule exceeds its configured rate ceiling · case 04

Linear schedule exceeds its configured rate ceiling.

Learning rate schedules◈ Members↗
FA-99125

Linear schedule exceeds its configured rate ceiling · case 05

Linear schedule exceeds its configured rate ceiling.

Learning rate schedules◈ Members↗
FA-99126

Warmup decay drops below the terminal floor · case 01

Warmup decay drops below the terminal floor.

Learning rate schedules● Open access↗
FA-99127

Warmup decay drops below the terminal floor · case 02

Warmup decay drops below the terminal floor.

Learning rate schedules◈ Members↗
FA-99128

Warmup decay drops below the terminal floor · case 03

Warmup decay drops below the terminal floor.

Learning rate schedules◈ Members↗
FA-99129

Warmup decay drops below the terminal floor · case 04

Warmup decay drops below the terminal floor.

Learning rate schedules◈ Members↗
FA-99130

Warmup decay drops below the terminal floor · case 05

Warmup decay drops below the terminal floor.

Learning rate schedules◈ Members↗
FA-99131

One-cycle schedule extrapolates beyond its endpoints · case 01

One-cycle schedule extrapolates beyond its endpoints.

Learning rate schedules● Open access↗
FA-99132

One-cycle schedule extrapolates beyond its endpoints · case 02

One-cycle schedule extrapolates beyond its endpoints.

Learning rate schedules◈ Members↗
FA-99133

One-cycle schedule extrapolates beyond its endpoints · case 03

One-cycle schedule extrapolates beyond its endpoints.

Learning rate schedules◈ Members↗
FA-99134

One-cycle schedule extrapolates beyond its endpoints · case 04

One-cycle schedule extrapolates beyond its endpoints.

Learning rate schedules◈ Members↗
FA-99135

One-cycle schedule extrapolates beyond its endpoints · case 05

One-cycle schedule extrapolates beyond its endpoints.

Learning rate schedules◈ Members↗
FA-99136

Cosine decay ends at half the configured floor · case 01

Cosine decay ends at half the configured floor.

Learning rate schedules● Open access↗
FA-99137

Cosine decay ends at half the configured floor · case 02

Cosine decay ends at half the configured floor.

Learning rate schedules◈ Members↗
FA-99138

Cosine decay ends at half the configured floor · case 03

Cosine decay ends at half the configured floor.

Learning rate schedules◈ Members↗
FA-99139

Cosine decay ends at half the configured floor · case 04

Cosine decay ends at half the configured floor.

Learning rate schedules◈ Members↗
FA-99140

Cosine decay ends at half the configured floor · case 05

Cosine decay ends at half the configured floor.

Learning rate schedules◈ Members↗
FA-99141

Checkpoint mapping: module prefix is stripped from interior names · case 01

module prefix is stripped from interior names.

Checkpoint tensor mapping● Open access↗
FA-99142

Checkpoint mapping: module prefix is stripped from interior names · case 02

module prefix is stripped from interior names.

Checkpoint tensor mapping◈ Members↗
FA-99143

Checkpoint mapping: module prefix is stripped from interior names · case 03

module prefix is stripped from interior names.

Checkpoint tensor mapping◈ Members↗
FA-99144

Checkpoint mapping: module prefix is stripped from interior names · case 04

module prefix is stripped from interior names.

Checkpoint tensor mapping◈ Members↗
FA-99145

Checkpoint mapping: module prefix is stripped from interior names · case 05

module prefix is stripped from interior names.

Checkpoint tensor mapping◈ Members↗
FA-99146

Checkpoint mapping: permuted dimensions pass exact shape matching · case 01

permuted dimensions pass exact shape matching.

Checkpoint tensor mapping● Open access↗
FA-99147

Checkpoint mapping: permuted dimensions pass exact shape matching · case 02

permuted dimensions pass exact shape matching.

Checkpoint tensor mapping◈ Members↗
FA-99148

Checkpoint mapping: permuted dimensions pass exact shape matching · case 03

permuted dimensions pass exact shape matching.

Checkpoint tensor mapping◈ Members↗
FA-99149

Checkpoint mapping: permuted dimensions pass exact shape matching · case 04

permuted dimensions pass exact shape matching.

Checkpoint tensor mapping◈ Members↗
FA-99150

Checkpoint mapping: permuted dimensions pass exact shape matching · case 05

permuted dimensions pass exact shape matching.

Checkpoint tensor mapping◈ Members↗
FA-99151

Checkpoint mapping: a wildcard axis masks mismatches in fixed axes · case 01

a wildcard axis masks mismatches in fixed axes.

Checkpoint tensor mapping● Open access↗
FA-99152

Checkpoint mapping: a wildcard axis masks mismatches in fixed axes · case 02

a wildcard axis masks mismatches in fixed axes.

Checkpoint tensor mapping◈ Members↗
FA-99153

Checkpoint mapping: a wildcard axis masks mismatches in fixed axes · case 03

a wildcard axis masks mismatches in fixed axes.

Checkpoint tensor mapping◈ Members↗
FA-99154

Checkpoint mapping: a wildcard axis masks mismatches in fixed axes · case 04

a wildcard axis masks mismatches in fixed axes.

Checkpoint tensor mapping◈ Members↗
FA-99155

Checkpoint mapping: a wildcard axis masks mismatches in fixed axes · case 05

a wildcard axis masks mismatches in fixed axes.

Checkpoint tensor mapping◈ Members↗
FA-99156

Checkpoint mapping: arrival order changes reconstructed shard order · case 01

arrival order changes reconstructed shard order.

Checkpoint tensor mapping● Open access↗
FA-99157

Checkpoint mapping: arrival order changes reconstructed shard order · case 02

arrival order changes reconstructed shard order.

Checkpoint tensor mapping◈ Members↗
FA-99158

Checkpoint mapping: arrival order changes reconstructed shard order · case 03

arrival order changes reconstructed shard order.

Checkpoint tensor mapping◈ Members↗
FA-99159

Checkpoint mapping: arrival order changes reconstructed shard order · case 04

arrival order changes reconstructed shard order.

Checkpoint tensor mapping◈ Members↗
FA-99160

Checkpoint mapping: arrival order changes reconstructed shard order · case 05

arrival order changes reconstructed shard order.

Checkpoint tensor mapping◈ Members↗
FA-99161

Checkpoint mapping: missing shard indices are not detected · case 01

missing shard indices are not detected.

Checkpoint tensor mapping● Open access↗
FA-99162

Checkpoint mapping: missing shard indices are not detected · case 02

missing shard indices are not detected.

Checkpoint tensor mapping◈ Members↗
FA-99163

Checkpoint mapping: missing shard indices are not detected · case 03

missing shard indices are not detected.

Checkpoint tensor mapping◈ Members↗
FA-99164

Checkpoint mapping: missing shard indices are not detected · case 04

missing shard indices are not detected.

Checkpoint tensor mapping◈ Members↗
FA-99165

Checkpoint mapping: missing shard indices are not detected · case 05

missing shard indices are not detected.

Checkpoint tensor mapping◈ Members↗
FA-99166

Checkpoint mapping: renaming collisions are not rejected · case 01

renaming collisions are not rejected.

Checkpoint tensor mapping● Open access↗
FA-99167

Checkpoint mapping: renaming collisions are not rejected · case 02

renaming collisions are not rejected.

Checkpoint tensor mapping◈ Members↗
FA-99168

Checkpoint mapping: renaming collisions are not rejected · case 03

renaming collisions are not rejected.

Checkpoint tensor mapping◈ Members↗
FA-99169

Checkpoint mapping: renaming collisions are not rejected · case 04

renaming collisions are not rejected.

Checkpoint tensor mapping◈ Members↗
FA-99170

Checkpoint mapping: renaming collisions are not rejected · case 05

renaming collisions are not rejected.

Checkpoint tensor mapping◈ Members↗
FA-99171

Checkpoint mapping: unexpected checkpoint tensors are accepted · case 01

unexpected checkpoint tensors are accepted.

Checkpoint tensor mapping● Open access↗
FA-99172

Checkpoint mapping: unexpected checkpoint tensors are accepted · case 02

unexpected checkpoint tensors are accepted.

Checkpoint tensor mapping◈ Members↗
FA-99173

Checkpoint mapping: unexpected checkpoint tensors are accepted · case 03

unexpected checkpoint tensors are accepted.

Checkpoint tensor mapping◈ Members↗
FA-99174

Checkpoint mapping: unexpected checkpoint tensors are accepted · case 04

unexpected checkpoint tensors are accepted.

Checkpoint tensor mapping◈ Members↗
FA-99175

Checkpoint mapping: unexpected checkpoint tensors are accepted · case 05

unexpected checkpoint tensors are accepted.

Checkpoint tensor mapping◈ Members↗
FA-99176

Checkpoint mapping: optional buffers are treated as required parameters · case 01

optional buffers are treated as required parameters.

Checkpoint tensor mapping● Open access↗
FA-99177

Checkpoint mapping: optional buffers are treated as required parameters · case 02

optional buffers are treated as required parameters.

Checkpoint tensor mapping◈ Members↗
FA-99178

Checkpoint mapping: optional buffers are treated as required parameters · case 03

optional buffers are treated as required parameters.

Checkpoint tensor mapping◈ Members↗
FA-99179

Checkpoint mapping: optional buffers are treated as required parameters · case 04

optional buffers are treated as required parameters.

Checkpoint tensor mapping◈ Members↗
FA-99180

Checkpoint mapping: optional buffers are treated as required parameters · case 05

optional buffers are treated as required parameters.

Checkpoint tensor mapping◈ Members↗
FA-99181

Checkpoint mapping: different fixed dimensions pass shard compatibility · case 01

different fixed dimensions pass shard compatibility.

Checkpoint tensor mapping● Open access↗
FA-99182

Checkpoint mapping: different fixed dimensions pass shard compatibility · case 02

different fixed dimensions pass shard compatibility.

Checkpoint tensor mapping◈ Members↗
FA-99183

Checkpoint mapping: different fixed dimensions pass shard compatibility · case 03

different fixed dimensions pass shard compatibility.

Checkpoint tensor mapping◈ Members↗
FA-99184

Checkpoint mapping: different fixed dimensions pass shard compatibility · case 04

different fixed dimensions pass shard compatibility.

Checkpoint tensor mapping◈ Members↗
FA-99185

Checkpoint mapping: different fixed dimensions pass shard compatibility · case 05

different fixed dimensions pass shard compatibility.

Checkpoint tensor mapping◈ Members↗
FA-99186

Checkpoint mapping: shard sizes are added along the wrong axis · case 01

shard sizes are added along the wrong axis.

Checkpoint tensor mapping● Open access↗
FA-99187

Checkpoint mapping: shard sizes are added along the wrong axis · case 02

shard sizes are added along the wrong axis.

Checkpoint tensor mapping◈ Members↗
FA-99188

Checkpoint mapping: shard sizes are added along the wrong axis · case 03

shard sizes are added along the wrong axis.

Checkpoint tensor mapping◈ Members↗
FA-99189

Checkpoint mapping: shard sizes are added along the wrong axis · case 04

shard sizes are added along the wrong axis.

Checkpoint tensor mapping◈ Members↗
FA-99190

Checkpoint mapping: shard sizes are added along the wrong axis · case 05

shard sizes are added along the wrong axis.

Checkpoint tensor mapping◈ Members↗
FA-99191

Checkpoint mapping: row shard offset ignores preceding shard lengths · case 01

row shard offset ignores preceding shard lengths.

Checkpoint tensor mapping● Open access↗
FA-99192

Checkpoint mapping: row shard offset ignores preceding shard lengths · case 02

row shard offset ignores preceding shard lengths.

Checkpoint tensor mapping◈ Members↗
FA-99193

Checkpoint mapping: row shard offset ignores preceding shard lengths · case 03

row shard offset ignores preceding shard lengths.

Checkpoint tensor mapping◈ Members↗
FA-99194

Checkpoint mapping: row shard offset ignores preceding shard lengths · case 04

row shard offset ignores preceding shard lengths.

Checkpoint tensor mapping◈ Members↗
FA-99195

Checkpoint mapping: row shard offset ignores preceding shard lengths · case 05

row shard offset ignores preceding shard lengths.

Checkpoint tensor mapping◈ Members↗
FA-99196

Checkpoint mapping: two dimensional shard indices use the tile width as row stride · case 01

two dimensional shard indices use the tile width as row stride.

Checkpoint tensor mapping● Open access↗
FA-99197

Checkpoint mapping: two dimensional shard indices use the tile width as row stride · case 02

two dimensional shard indices use the tile width as row stride.

Checkpoint tensor mapping◈ Members↗
FA-99198

Checkpoint mapping: two dimensional shard indices use the tile width as row stride · case 03

two dimensional shard indices use the tile width as row stride.

Checkpoint tensor mapping◈ Members↗
FA-99199

Checkpoint mapping: two dimensional shard indices use the tile width as row stride · case 04

two dimensional shard indices use the tile width as row stride.

Checkpoint tensor mapping◈ Members↗
FA-99200

Checkpoint mapping: two dimensional shard indices use the tile width as row stride · case 05

two dimensional shard indices use the tile width as row stride.

Checkpoint tensor mapping◈ 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 ↗