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

Transit signal priority decision: the lockout window lets the boundary cycle through · case 01

Transit signal priority decision returns a wrong result when the lockout window lets the boundary cycle through.

Traffic signal timing plans● Open access↗
FA-68202

Transit signal priority decision: the lockout window lets the boundary cycle through · case 02

Transit signal priority decision returns a wrong result when the lockout window lets the boundary cycle through.

Traffic signal timing plans◈ Members↗
FA-68203

Transit signal priority decision: the lockout window lets the boundary cycle through · case 03

Transit signal priority decision returns a wrong result when the lockout window lets the boundary cycle through.

Traffic signal timing plans◈ Members↗
FA-68204

Transit signal priority decision: the lockout window lets the boundary cycle through · case 04

Transit signal priority decision returns a wrong result when the lockout window lets the boundary cycle through.

Traffic signal timing plans◈ Members↗
FA-68205

Transit signal priority decision: the lockout window lets the boundary cycle through · case 05

Transit signal priority decision returns a wrong result when the lockout window lets the boundary cycle through.

Traffic signal timing plans◈ Members↗
FA-68206

Transit signal priority decision: a bus arriving at green end is treated as in green · case 01

Transit signal priority decision returns a wrong result when a bus arriving at green end is treated as in green.

Traffic signal timing plans● Open access↗
FA-68207

Transit signal priority decision: a bus arriving at green end is treated as in green · case 02

Transit signal priority decision returns a wrong result when a bus arriving at green end is treated as in green.

Traffic signal timing plans◈ Members↗
FA-68208

Transit signal priority decision: a bus arriving at green end is treated as in green · case 03

Transit signal priority decision returns a wrong result when a bus arriving at green end is treated as in green.

Traffic signal timing plans◈ Members↗
FA-68209

Transit signal priority decision: a bus arriving at green end is treated as in green · case 04

Transit signal priority decision returns a wrong result when a bus arriving at green end is treated as in green.

Traffic signal timing plans◈ Members↗
FA-68210

Transit signal priority decision: a bus arriving at green end is treated as in green · case 05

Transit signal priority decision returns a wrong result when a bus arriving at green end is treated as in green.

Traffic signal timing plans◈ Members↗
FA-68211

Transit signal priority decision: the extension distance is not wrapped around the cycle · case 01

Transit signal priority decision returns a wrong result when the extension distance is not wrapped around the cycle.

Traffic signal timing plans● Open access↗
FA-68212

Transit signal priority decision: the extension distance is not wrapped around the cycle · case 02

Transit signal priority decision returns a wrong result when the extension distance is not wrapped around the cycle.

Traffic signal timing plans◈ Members↗
FA-68213

Transit signal priority decision: the extension distance is not wrapped around the cycle · case 03

Transit signal priority decision returns a wrong result when the extension distance is not wrapped around the cycle.

Traffic signal timing plans◈ Members↗
FA-68214

Transit signal priority decision: the extension distance is not wrapped around the cycle · case 04

Transit signal priority decision returns a wrong result when the extension distance is not wrapped around the cycle.

Traffic signal timing plans◈ Members↗
FA-68215

Transit signal priority decision: the extension distance is not wrapped around the cycle · case 05

Transit signal priority decision returns a wrong result when the extension distance is not wrapped around the cycle.

Traffic signal timing plans◈ Members↗
FA-68216

Transit signal priority decision: green is extended only up to the arrival second · case 01

Transit signal priority decision returns a wrong result when green is extended only up to the arrival second.

Traffic signal timing plans● Open access↗
FA-68217

Transit signal priority decision: green is extended only up to the arrival second · case 02

Transit signal priority decision returns a wrong result when green is extended only up to the arrival second.

Traffic signal timing plans◈ Members↗
FA-68218

Transit signal priority decision: green is extended only up to the arrival second · case 03

Transit signal priority decision returns a wrong result when green is extended only up to the arrival second.

Traffic signal timing plans◈ Members↗
FA-68219

Transit signal priority decision: green is extended only up to the arrival second · case 04

Transit signal priority decision returns a wrong result when green is extended only up to the arrival second.

Traffic signal timing plans◈ Members↗
FA-68220

Transit signal priority decision: green is extended only up to the arrival second · case 05

Transit signal priority decision returns a wrong result when green is extended only up to the arrival second.

Traffic signal timing plans◈ Members↗
FA-68221

Transit signal priority decision: early green always uses the maximum advance · case 01

Transit signal priority decision returns a wrong result when early green always uses the maximum advance.

Traffic signal timing plans● Open access↗
FA-68222

Transit signal priority decision: early green always uses the maximum advance · case 02

Transit signal priority decision returns a wrong result when early green always uses the maximum advance.

Traffic signal timing plans◈ Members↗
FA-68223

Transit signal priority decision: early green always uses the maximum advance · case 03

Transit signal priority decision returns a wrong result when early green always uses the maximum advance.

Traffic signal timing plans◈ Members↗
FA-68224

Transit signal priority decision: early green always uses the maximum advance · case 04

Transit signal priority decision returns a wrong result when early green always uses the maximum advance.

Traffic signal timing plans◈ Members↗
FA-68225

Transit signal priority decision: early green always uses the maximum advance · case 05

Transit signal priority decision returns a wrong result when early green always uses the maximum advance.

Traffic signal timing plans◈ Members↗
FA-68226

Transit signal priority decision: time to next green is measured backwards · case 01

Transit signal priority decision returns a wrong result when time to next green is measured backwards.

Traffic signal timing plans● Open access↗
FA-68227

Transit signal priority decision: time to next green is measured backwards · case 02

Transit signal priority decision returns a wrong result when time to next green is measured backwards.

Traffic signal timing plans◈ Members↗
FA-68228

Transit signal priority decision: time to next green is measured backwards · case 03

Transit signal priority decision returns a wrong result when time to next green is measured backwards.

Traffic signal timing plans◈ Members↗
FA-68229

Transit signal priority decision: time to next green is measured backwards · case 04

Transit signal priority decision returns a wrong result when time to next green is measured backwards.

Traffic signal timing plans◈ Members↗
FA-68230

Transit signal priority decision: time to next green is measured backwards · case 05

Transit signal priority decision returns a wrong result when time to next green is measured backwards.

Traffic signal timing plans◈ Members↗
FA-68231

Loop detector count and occupancy binning: vehicles are counted in the bin where they leave · case 01

Loop detector count and occupancy binning returns a wrong result when vehicles are counted in the bin where they leave.

Traffic signal timing plans● Open access↗
FA-68232

Loop detector count and occupancy binning: vehicles are counted in the bin where they leave · case 02

Loop detector count and occupancy binning returns a wrong result when vehicles are counted in the bin where they leave.

Traffic signal timing plans◈ Members↗
FA-68233

Loop detector count and occupancy binning: vehicles are counted in the bin where they leave · case 03

Loop detector count and occupancy binning returns a wrong result when vehicles are counted in the bin where they leave.

Traffic signal timing plans◈ Members↗
FA-68234

Loop detector count and occupancy binning: vehicles are counted in the bin where they leave · case 04

Loop detector count and occupancy binning returns a wrong result when vehicles are counted in the bin where they leave.

Traffic signal timing plans◈ Members↗
FA-68235

Loop detector count and occupancy binning: vehicles are counted in the bin where they leave · case 05

Loop detector count and occupancy binning returns a wrong result when vehicles are counted in the bin where they leave.

Traffic signal timing plans◈ Members↗
FA-68236

Loop detector count and occupancy binning: occupied time is measured from vehicle arrival rather than bin start · case 01

Loop detector count and occupancy binning returns a wrong result when occupied time is measured from vehicle arrival rather than bin start.

Traffic signal timing plans● Open access↗
FA-68237

Loop detector count and occupancy binning: occupied time is measured from vehicle arrival rather than bin start · case 02

Loop detector count and occupancy binning returns a wrong result when occupied time is measured from vehicle arrival rather than bin start.

Traffic signal timing plans◈ Members↗
FA-68238

Loop detector count and occupancy binning: occupied time is measured from vehicle arrival rather than bin start · case 03

Loop detector count and occupancy binning returns a wrong result when occupied time is measured from vehicle arrival rather than bin start.

Traffic signal timing plans◈ Members↗
FA-68239

Loop detector count and occupancy binning: occupied time is measured from vehicle arrival rather than bin start · case 04

Loop detector count and occupancy binning returns a wrong result when occupied time is measured from vehicle arrival rather than bin start.

Traffic signal timing plans◈ Members↗
FA-68240

Loop detector count and occupancy binning: occupied time is measured from vehicle arrival rather than bin start · case 05

Loop detector count and occupancy binning returns a wrong result when occupied time is measured from vehicle arrival rather than bin start.

Traffic signal timing plans◈ Members↗
FA-68241

Loop detector count and occupancy binning: a presence exactly at the threshold is not stuck · case 01

Loop detector count and occupancy binning returns a wrong result when a presence exactly at the threshold is not stuck.

Traffic signal timing plans● Open access↗
FA-68242

Loop detector count and occupancy binning: a presence exactly at the threshold is not stuck · case 02

Loop detector count and occupancy binning returns a wrong result when a presence exactly at the threshold is not stuck.

Traffic signal timing plans◈ Members↗
FA-68243

Loop detector count and occupancy binning: a presence exactly at the threshold is not stuck · case 03

Loop detector count and occupancy binning returns a wrong result when a presence exactly at the threshold is not stuck.

Traffic signal timing plans◈ Members↗
FA-68244

Loop detector count and occupancy binning: a presence exactly at the threshold is not stuck · case 04

Loop detector count and occupancy binning returns a wrong result when a presence exactly at the threshold is not stuck.

Traffic signal timing plans◈ Members↗
FA-68245

Loop detector count and occupancy binning: a presence exactly at the threshold is not stuck · case 05

Loop detector count and occupancy binning returns a wrong result when a presence exactly at the threshold is not stuck.

Traffic signal timing plans◈ Members↗
FA-68246

Loop detector count and occupancy binning: occupancy percent is scaled after integer division · case 01

Loop detector count and occupancy binning returns a wrong result when occupancy percent is scaled after integer division.

Traffic signal timing plans● Open access↗
FA-68247

Loop detector count and occupancy binning: occupancy percent is scaled after integer division · case 02

Loop detector count and occupancy binning returns a wrong result when occupancy percent is scaled after integer division.

Traffic signal timing plans◈ Members↗
FA-68248

Loop detector count and occupancy binning: occupancy percent is scaled after integer division · case 03

Loop detector count and occupancy binning returns a wrong result when occupancy percent is scaled after integer division.

Traffic signal timing plans◈ Members↗
FA-68249

Loop detector count and occupancy binning: occupancy percent is scaled after integer division · case 04

Loop detector count and occupancy binning returns a wrong result when occupancy percent is scaled after integer division.

Traffic signal timing plans◈ Members↗
FA-68250

Loop detector count and occupancy binning: occupancy percent is scaled after integer division · case 05

Loop detector count and occupancy binning returns a wrong result when occupancy percent is scaled after integer division.

Traffic signal timing plans◈ Members↗
FA-68251

Loop detector count and occupancy binning: the no-activity limit is compared with the bin count · case 01

Loop detector count and occupancy binning returns a wrong result when the no-activity limit is compared with the bin count.

Traffic signal timing plans● Open access↗
FA-68252

Loop detector count and occupancy binning: the no-activity limit is compared with the bin count · case 02

Loop detector count and occupancy binning returns a wrong result when the no-activity limit is compared with the bin count.

Traffic signal timing plans◈ Members↗
FA-68253

Loop detector count and occupancy binning: the no-activity limit is compared with the bin count · case 03

Loop detector count and occupancy binning returns a wrong result when the no-activity limit is compared with the bin count.

Traffic signal timing plans◈ Members↗
FA-68254

Loop detector count and occupancy binning: the no-activity limit is compared with the bin count · case 04

Loop detector count and occupancy binning returns a wrong result when the no-activity limit is compared with the bin count.

Traffic signal timing plans◈ Members↗
FA-68255

Loop detector count and occupancy binning: the no-activity limit is compared with the bin count · case 05

Loop detector count and occupancy binning returns a wrong result when the no-activity limit is compared with the bin count.

Traffic signal timing plans◈ Members↗
FA-68256

Loop detector count and occupancy binning: vehicles present before period start are counted in the last bin · case 01

Loop detector count and occupancy binning returns a wrong result when vehicles present before period start are counted in the last bin.

Traffic signal timing plans● Open access↗
FA-68257

Loop detector count and occupancy binning: vehicles present before period start are counted in the last bin · case 02

Loop detector count and occupancy binning returns a wrong result when vehicles present before period start are counted in the last bin.

Traffic signal timing plans◈ Members↗
FA-68258

Loop detector count and occupancy binning: vehicles present before period start are counted in the last bin · case 03

Loop detector count and occupancy binning returns a wrong result when vehicles present before period start are counted in the last bin.

Traffic signal timing plans◈ Members↗
FA-68259

Loop detector count and occupancy binning: vehicles present before period start are counted in the last bin · case 04

Loop detector count and occupancy binning returns a wrong result when vehicles present before period start are counted in the last bin.

Traffic signal timing plans◈ Members↗
FA-68260

Loop detector count and occupancy binning: vehicles present before period start are counted in the last bin · case 05

Loop detector count and occupancy binning returns a wrong result when vehicles present before period start are counted in the last bin.

Traffic signal timing plans◈ Members↗
FA-68261

Split failure detection: the red occupancy window starts at yellow onset · case 01

Split failure detection returns a wrong result when the red occupancy window starts at yellow onset.

Traffic signal timing plans● Open access↗
FA-68262

Split failure detection: the red occupancy window starts at yellow onset · case 02

Split failure detection returns a wrong result when the red occupancy window starts at yellow onset.

Traffic signal timing plans◈ Members↗
FA-68263

Split failure detection: the red occupancy window starts at yellow onset · case 03

Split failure detection returns a wrong result when the red occupancy window starts at yellow onset.

Traffic signal timing plans◈ Members↗
FA-68264

Split failure detection: the red occupancy window starts at yellow onset · case 04

Split failure detection returns a wrong result when the red occupancy window starts at yellow onset.

Traffic signal timing plans◈ Members↗
FA-68265

Split failure detection: the red occupancy window starts at yellow onset · case 05

Split failure detection returns a wrong result when the red occupancy window starts at yellow onset.

Traffic signal timing plans◈ Members↗
FA-68266

Split failure detection: split failure requires strictly more than 80 percent · case 01

Split failure detection returns a wrong result when split failure requires strictly more than 80 percent.

Traffic signal timing plans● Open access↗
FA-68267

Split failure detection: split failure requires strictly more than 80 percent · case 02

Split failure detection returns a wrong result when split failure requires strictly more than 80 percent.

Traffic signal timing plans◈ Members↗
FA-68268

Split failure detection: split failure requires strictly more than 80 percent · case 03

Split failure detection returns a wrong result when split failure requires strictly more than 80 percent.

Traffic signal timing plans◈ Members↗
FA-68269

Split failure detection: split failure requires strictly more than 80 percent · case 04

Split failure detection returns a wrong result when split failure requires strictly more than 80 percent.

Traffic signal timing plans◈ Members↗
FA-68270

Split failure detection: split failure requires strictly more than 80 percent · case 05

Split failure detection returns a wrong result when split failure requires strictly more than 80 percent.

Traffic signal timing plans◈ Members↗
FA-68271

Split failure detection: occupancy before the window start is credited · case 01

Split failure detection returns a wrong result when occupancy before the window start is credited.

Traffic signal timing plans● Open access↗
FA-68272

Split failure detection: occupancy before the window start is credited · case 02

Split failure detection returns a wrong result when occupancy before the window start is credited.

Traffic signal timing plans◈ Members↗
FA-68273

Split failure detection: occupancy before the window start is credited · case 03

Split failure detection returns a wrong result when occupancy before the window start is credited.

Traffic signal timing plans◈ Members↗
FA-68274

Split failure detection: occupancy before the window start is credited · case 04

Split failure detection returns a wrong result when occupancy before the window start is credited.

Traffic signal timing plans◈ Members↗
FA-68275

Split failure detection: occupancy before the window start is credited · case 05

Split failure detection returns a wrong result when occupancy before the window start is credited.

Traffic signal timing plans◈ Members↗
FA-68276

Split failure detection: green occupancy includes the yellow interval · case 01

Split failure detection returns a wrong result when green occupancy includes the yellow interval.

Traffic signal timing plans● Open access↗
FA-68277

Split failure detection: green occupancy includes the yellow interval · case 02

Split failure detection returns a wrong result when green occupancy includes the yellow interval.

Traffic signal timing plans◈ Members↗
FA-68278

Split failure detection: green occupancy includes the yellow interval · case 03

Split failure detection returns a wrong result when green occupancy includes the yellow interval.

Traffic signal timing plans◈ Members↗
FA-68279

Split failure detection: green occupancy includes the yellow interval · case 04

Split failure detection returns a wrong result when green occupancy includes the yellow interval.

Traffic signal timing plans◈ Members↗
FA-68280

Split failure detection: green occupancy includes the yellow interval · case 05

Split failure detection returns a wrong result when green occupancy includes the yellow interval.

Traffic signal timing plans◈ Members↗
FA-68281

Split failure detection: the failure percentage divides before scaling · case 01

Split failure detection returns a wrong result when the failure percentage divides before scaling.

Traffic signal timing plans● Open access↗
FA-68282

Split failure detection: the failure percentage divides before scaling · case 02

Split failure detection returns a wrong result when the failure percentage divides before scaling.

Traffic signal timing plans◈ Members↗
FA-68283

Split failure detection: the failure percentage divides before scaling · case 03

Split failure detection returns a wrong result when the failure percentage divides before scaling.

Traffic signal timing plans◈ Members↗
FA-68284

Split failure detection: the failure percentage divides before scaling · case 04

Split failure detection returns a wrong result when the failure percentage divides before scaling.

Traffic signal timing plans◈ Members↗
FA-68285

Split failure detection: the failure percentage divides before scaling · case 05

Split failure detection returns a wrong result when the failure percentage divides before scaling.

Traffic signal timing plans◈ Members↗
FA-68286

Conflict monitor fault scan: compatible pairs are stored in the order given · case 01

Conflict monitor fault scan returns a wrong result when compatible pairs are stored in the order given.

Traffic signal timing plans● Open access↗
FA-68287

Conflict monitor fault scan: compatible pairs are stored in the order given · case 02

Conflict monitor fault scan returns a wrong result when compatible pairs are stored in the order given.

Traffic signal timing plans◈ Members↗
FA-68288

Conflict monitor fault scan: compatible pairs are stored in the order given · case 03

Conflict monitor fault scan returns a wrong result when compatible pairs are stored in the order given.

Traffic signal timing plans◈ Members↗
FA-68289

Conflict monitor fault scan: compatible pairs are stored in the order given · case 04

Conflict monitor fault scan returns a wrong result when compatible pairs are stored in the order given.

Traffic signal timing plans◈ Members↗
FA-68290

Conflict monitor fault scan: compatible pairs are stored in the order given · case 05

Conflict monitor fault scan returns a wrong result when compatible pairs are stored in the order given.

Traffic signal timing plans◈ Members↗
FA-68291

Conflict monitor fault scan: yellow indications are left out of the conflict check · case 01

Conflict monitor fault scan returns a wrong result when yellow indications are left out of the conflict check.

Traffic signal timing plans● Open access↗
FA-68292

Conflict monitor fault scan: yellow indications are left out of the conflict check · case 02

Conflict monitor fault scan returns a wrong result when yellow indications are left out of the conflict check.

Traffic signal timing plans◈ Members↗
FA-68293

Conflict monitor fault scan: yellow indications are left out of the conflict check · case 03

Conflict monitor fault scan returns a wrong result when yellow indications are left out of the conflict check.

Traffic signal timing plans◈ Members↗
FA-68294

Conflict monitor fault scan: yellow indications are left out of the conflict check · case 04

Conflict monitor fault scan returns a wrong result when yellow indications are left out of the conflict check.

Traffic signal timing plans◈ Members↗
FA-68295

Conflict monitor fault scan: yellow indications are left out of the conflict check · case 05

Conflict monitor fault scan returns a wrong result when yellow indications are left out of the conflict check.

Traffic signal timing plans◈ Members↗
FA-68296

Conflict monitor fault scan: disabled channels showing green still enter the conflict check · case 01

Conflict monitor fault scan returns a wrong result when disabled channels showing green still enter the conflict check.

Traffic signal timing plans● Open access↗
FA-68297

Conflict monitor fault scan: disabled channels showing green still enter the conflict check · case 02

Conflict monitor fault scan returns a wrong result when disabled channels showing green still enter the conflict check.

Traffic signal timing plans◈ Members↗
FA-68298

Conflict monitor fault scan: disabled channels showing green still enter the conflict check · case 03

Conflict monitor fault scan returns a wrong result when disabled channels showing green still enter the conflict check.

Traffic signal timing plans◈ Members↗
FA-68299

Conflict monitor fault scan: disabled channels showing green still enter the conflict check · case 04

Conflict monitor fault scan returns a wrong result when disabled channels showing green still enter the conflict check.

Traffic signal timing plans◈ Members↗
FA-68300

Conflict monitor fault scan: disabled channels showing green still enter the conflict check · case 05

Conflict monitor fault scan returns a wrong result when disabled channels showing green still enter the conflict check.

Traffic signal timing plans◈ 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 ↗