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

Shuffle preserves playing head · case 01

Shuffling replaces the playing entry with the first random candidate.

Media playlist state● Open access↗
FA-11102

Shuffle preserves playing head · case 02

Shuffling replaces the playing entry with the first random candidate.

Media playlist state◈ Members↗
FA-11103

Shuffle preserves playing head · case 03

Shuffling replaces the playing entry with the first random candidate.

Media playlist state◈ Members↗
FA-11104

Shuffle preserves playing head · case 04

Shuffling replaces the playing entry with the first random candidate.

Media playlist state◈ Members↗
FA-11105

Shuffle preserves playing head · case 05

Shuffling replaces the playing entry with the first random candidate.

Media playlist state◈ Members↗
FA-11106

Manifest merge by sequence · case 01

Appending a refreshed manifest duplicates overlapping sequence numbers.

Streaming segment lifecycle● Open access↗
FA-11107

Manifest merge by sequence · case 02

Appending a refreshed manifest duplicates overlapping sequence numbers.

Streaming segment lifecycle◈ Members↗
FA-11108

Manifest merge by sequence · case 03

Appending a refreshed manifest duplicates overlapping sequence numbers.

Streaming segment lifecycle◈ Members↗
FA-11109

Manifest merge by sequence · case 04

Appending a refreshed manifest duplicates overlapping sequence numbers.

Streaming segment lifecycle◈ Members↗
FA-11110

Manifest merge by sequence · case 05

Appending a refreshed manifest duplicates overlapping sequence numbers.

Streaming segment lifecycle◈ Members↗
FA-11111

Live window prune absolute sequence · case 01

An absolute sequence number is applied as a local array slice offset.

Streaming segment lifecycle● Open access↗
FA-11112

Live window prune absolute sequence · case 02

An absolute sequence number is applied as a local array slice offset.

Streaming segment lifecycle◈ Members↗
FA-11113

Live window prune absolute sequence · case 03

An absolute sequence number is applied as a local array slice offset.

Streaming segment lifecycle◈ Members↗
FA-11114

Live window prune absolute sequence · case 04

An absolute sequence number is applied as a local array slice offset.

Streaming segment lifecycle◈ Members↗
FA-11115

Live window prune absolute sequence · case 05

An absolute sequence number is applied as a local array slice offset.

Streaming segment lifecycle◈ Members↗
FA-11116

Discontinuity base increments on prune · case 01

A sliding manifest window loses discontinuity history when old segments disappear.

Streaming segment lifecycle● Open access↗
FA-11117

Discontinuity base increments on prune · case 02

A sliding manifest window loses discontinuity history when old segments disappear.

Streaming segment lifecycle◈ Members↗
FA-11118

Discontinuity base increments on prune · case 03

A sliding manifest window loses discontinuity history when old segments disappear.

Streaming segment lifecycle◈ Members↗
FA-11119

Discontinuity base increments on prune · case 04

A sliding manifest window loses discontinuity history when old segments disappear.

Streaming segment lifecycle◈ Members↗
FA-11120

Discontinuity base increments on prune · case 05

A sliding manifest window loses discontinuity history when old segments disappear.

Streaming segment lifecycle◈ Members↗
FA-11121

Segment uri relative resolution · case 01

The manifest filename is incorrectly treated as a directory.

Streaming segment lifecycle● Open access↗
FA-11122

Segment uri relative resolution · case 02

The manifest filename is incorrectly treated as a directory.

Streaming segment lifecycle◈ Members↗
FA-11123

Segment uri relative resolution · case 03

The manifest filename is incorrectly treated as a directory.

Streaming segment lifecycle◈ Members↗
FA-11124

Segment uri relative resolution · case 04

The manifest filename is incorrectly treated as a directory.

Streaming segment lifecycle◈ Members↗
FA-11125

Segment uri relative resolution · case 05

The manifest filename is incorrectly treated as a directory.

Streaming segment lifecycle◈ Members↗
FA-11126

Segment byte range inclusive header · case 01

Adding full byte length fetches one byte from the following range.

Streaming segment lifecycle● Open access↗
FA-11127

Segment byte range inclusive header · case 02

Adding full byte length fetches one byte from the following range.

Streaming segment lifecycle◈ Members↗
FA-11128

Segment byte range inclusive header · case 03

Adding full byte length fetches one byte from the following range.

Streaming segment lifecycle◈ Members↗
FA-11129

Segment byte range inclusive header · case 04

Adding full byte length fetches one byte from the following range.

Streaming segment lifecycle◈ Members↗
FA-11130

Segment byte range inclusive header · case 05

Adding full byte length fetches one byte from the following range.

Streaming segment lifecycle◈ Members↗
FA-11131

Implicit range offset resource scope · case 01

An omitted range offset carries over from an unrelated resource URI.

Streaming segment lifecycle● Open access↗
FA-11132

Implicit range offset resource scope · case 02

An omitted range offset carries over from an unrelated resource URI.

Streaming segment lifecycle◈ Members↗
FA-11133

Implicit range offset resource scope · case 03

An omitted range offset carries over from an unrelated resource URI.

Streaming segment lifecycle◈ Members↗
FA-11134

Implicit range offset resource scope · case 04

An omitted range offset carries over from an unrelated resource URI.

Streaming segment lifecycle◈ Members↗
FA-11135

Implicit range offset resource scope · case 05

An omitted range offset carries over from an unrelated resource URI.

Streaming segment lifecycle◈ Members↗
FA-11136

Init segment before media · case 01

Media data is appended before its required decoder initialization data.

Streaming segment lifecycle● Open access↗
FA-11137

Init segment before media · case 02

Media data is appended before its required decoder initialization data.

Streaming segment lifecycle◈ Members↗
FA-11138

Init segment before media · case 03

Media data is appended before its required decoder initialization data.

Streaming segment lifecycle◈ Members↗
FA-11139

Init segment before media · case 04

Media data is appended before its required decoder initialization data.

Streaming segment lifecycle◈ Members↗
FA-11140

Init segment before media · case 05

Media data is appended before its required decoder initialization data.

Streaming segment lifecycle◈ Members↗
FA-11141

Segment cache key includes rendition · case 01

Two quality renditions share a sequence number and collide in the segment cache.

Streaming segment lifecycle● Open access↗
FA-11142

Segment cache key includes rendition · case 02

Two quality renditions share a sequence number and collide in the segment cache.

Streaming segment lifecycle◈ Members↗
FA-11143

Segment cache key includes rendition · case 03

Two quality renditions share a sequence number and collide in the segment cache.

Streaming segment lifecycle◈ Members↗
FA-11144

Segment cache key includes rendition · case 04

Two quality renditions share a sequence number and collide in the segment cache.

Streaming segment lifecycle◈ Members↗
FA-11145

Segment cache key includes rendition · case 05

Two quality renditions share a sequence number and collide in the segment cache.

Streaming segment lifecycle◈ Members↗
FA-11146

Download chunks offset assembly · case 01

Appending in download completion order corrupts segment byte order.

Streaming segment lifecycle● Open access↗
FA-11147

Download chunks offset assembly · case 02

Appending in download completion order corrupts segment byte order.

Streaming segment lifecycle◈ Members↗
FA-11148

Download chunks offset assembly · case 03

Appending in download completion order corrupts segment byte order.

Streaming segment lifecycle◈ Members↗
FA-11149

Download chunks offset assembly · case 04

Appending in download completion order corrupts segment byte order.

Streaming segment lifecycle◈ Members↗
FA-11150

Download chunks offset assembly · case 05

Appending in download completion order corrupts segment byte order.

Streaming segment lifecycle◈ Members↗
FA-11151

Partial segment replacement · case 01

A retried part is appended as a duplicate part rather than updating its stored payload.

Streaming segment lifecycle● Open access↗
FA-11152

Partial segment replacement · case 02

A retried part is appended as a duplicate part rather than updating its stored payload.

Streaming segment lifecycle◈ Members↗
FA-11153

Partial segment replacement · case 03

A retried part is appended as a duplicate part rather than updating its stored payload.

Streaming segment lifecycle◈ Members↗
FA-11154

Partial segment replacement · case 04

A retried part is appended as a duplicate part rather than updating its stored payload.

Streaming segment lifecycle◈ Members↗
FA-11155

Partial segment replacement · case 05

A retried part is appended as a duplicate part rather than updating its stored payload.

Streaming segment lifecycle◈ Members↗
FA-11156

Download failure restores pending · case 01

Removing a failed download from inflight without requeueing permanently loses that segment.

Streaming segment lifecycle● Open access↗
FA-11157

Download failure restores pending · case 02

Removing a failed download from inflight without requeueing permanently loses that segment.

Streaming segment lifecycle◈ Members↗
FA-11158

Download failure restores pending · case 03

Removing a failed download from inflight without requeueing permanently loses that segment.

Streaming segment lifecycle◈ Members↗
FA-11159

Download failure restores pending · case 04

Removing a failed download from inflight without requeueing permanently loses that segment.

Streaming segment lifecycle◈ Members↗
FA-11160

Download failure restores pending · case 05

Removing a failed download from inflight without requeueing permanently loses that segment.

Streaming segment lifecycle◈ Members↗
FA-11161

Segment eviction retains shared init · case 01

Evicting one media segment deletes initialization bytes needed by other segments.

Streaming segment lifecycle● Open access↗
FA-11162

Segment eviction retains shared init · case 02

Evicting one media segment deletes initialization bytes needed by other segments.

Streaming segment lifecycle◈ Members↗
FA-11163

Segment eviction retains shared init · case 03

Evicting one media segment deletes initialization bytes needed by other segments.

Streaming segment lifecycle◈ Members↗
FA-11164

Segment eviction retains shared init · case 04

Evicting one media segment deletes initialization bytes needed by other segments.

Streaming segment lifecycle◈ Members↗
FA-11165

Segment eviction retains shared init · case 05

Evicting one media segment deletes initialization bytes needed by other segments.

Streaming segment lifecycle◈ Members↗
FA-11166

Segment append must finish before next · case 01

A second append is started while the previous asynchronous append is still active.

Streaming segment lifecycle● Open access↗
FA-11167

Segment append must finish before next · case 02

A second append is started while the previous asynchronous append is still active.

Streaming segment lifecycle◈ Members↗
FA-11168

Segment append must finish before next · case 03

A second append is started while the previous asynchronous append is still active.

Streaming segment lifecycle◈ Members↗
FA-11169

Segment append must finish before next · case 04

A second append is started while the previous asynchronous append is still active.

Streaming segment lifecycle◈ Members↗
FA-11170

Segment append must finish before next · case 05

A second append is started while the previous asynchronous append is still active.

Streaming segment lifecycle◈ Members↗
FA-11171

Append failure keeps uncommitted segment · case 01

Append completion is treated as success even when the decoder rejected the segment.

Streaming segment lifecycle● Open access↗
FA-11172

Append failure keeps uncommitted segment · case 02

Append completion is treated as success even when the decoder rejected the segment.

Streaming segment lifecycle◈ Members↗
FA-11173

Append failure keeps uncommitted segment · case 03

Append completion is treated as success even when the decoder rejected the segment.

Streaming segment lifecycle◈ Members↗
FA-11174

Append failure keeps uncommitted segment · case 04

Append completion is treated as success even when the decoder rejected the segment.

Streaming segment lifecycle◈ Members↗
FA-11175

Append failure keeps uncommitted segment · case 05

Append completion is treated as success even when the decoder rejected the segment.

Streaming segment lifecycle◈ Members↗
FA-11176

End of stream waits for queued appends · case 01

The stream ends before all declared media segments have been appended.

Streaming segment lifecycle● Open access↗
FA-11177

End of stream waits for queued appends · case 02

The stream ends before all declared media segments have been appended.

Streaming segment lifecycle◈ Members↗
FA-11178

End of stream waits for queued appends · case 03

The stream ends before all declared media segments have been appended.

Streaming segment lifecycle◈ Members↗
FA-11179

End of stream waits for queued appends · case 04

The stream ends before all declared media segments have been appended.

Streaming segment lifecycle◈ Members↗
FA-11180

End of stream waits for queued appends · case 05

The stream ends before all declared media segments have been appended.

Streaming segment lifecycle◈ Members↗
FA-11181

Segment selection by time interval · case 01

Inclusive segment ends select the previous segment at a shared boundary.

Streaming segment lifecycle● Open access↗
FA-11182

Segment selection by time interval · case 02

Inclusive segment ends select the previous segment at a shared boundary.

Streaming segment lifecycle◈ Members↗
FA-11183

Segment selection by time interval · case 03

Inclusive segment ends select the previous segment at a shared boundary.

Streaming segment lifecycle◈ Members↗
FA-11184

Segment selection by time interval · case 04

Inclusive segment ends select the previous segment at a shared boundary.

Streaming segment lifecycle◈ Members↗
FA-11185

Segment selection by time interval · case 05

Inclusive segment ends select the previous segment at a shared boundary.

Streaming segment lifecycle◈ Members↗
FA-11186

Segment priority seek distance · case 01

Numeric download order fills old segments before the seek target.

Streaming segment lifecycle● Open access↗
FA-11187

Segment priority seek distance · case 02

Numeric download order fills old segments before the seek target.

Streaming segment lifecycle◈ Members↗
FA-11188

Segment priority seek distance · case 03

Numeric download order fills old segments before the seek target.

Streaming segment lifecycle◈ Members↗
FA-11189

Segment priority seek distance · case 04

Numeric download order fills old segments before the seek target.

Streaming segment lifecycle◈ Members↗
FA-11190

Segment priority seek distance · case 05

Numeric download order fills old segments before the seek target.

Streaming segment lifecycle◈ Members↗
FA-11191

Rendition switch discards old pending · case 01

Quality switching leaves obsolete old-rendition downloads queued.

Streaming segment lifecycle● Open access↗
FA-11192

Rendition switch discards old pending · case 02

Quality switching leaves obsolete old-rendition downloads queued.

Streaming segment lifecycle◈ Members↗
FA-11193

Rendition switch discards old pending · case 03

Quality switching leaves obsolete old-rendition downloads queued.

Streaming segment lifecycle◈ Members↗
FA-11194

Rendition switch discards old pending · case 04

Quality switching leaves obsolete old-rendition downloads queued.

Streaming segment lifecycle◈ Members↗
FA-11195

Rendition switch discards old pending · case 05

Quality switching leaves obsolete old-rendition downloads queued.

Streaming segment lifecycle◈ Members↗
FA-11196

Manifest refresh retains terminal flag · case 01

A failed refresh resets terminal state from incomplete metadata.

Streaming segment lifecycle● Open access↗
FA-11197

Manifest refresh retains terminal flag · case 02

A failed refresh resets terminal state from incomplete metadata.

Streaming segment lifecycle◈ Members↗
FA-11198

Manifest refresh retains terminal flag · case 03

A failed refresh resets terminal state from incomplete metadata.

Streaming segment lifecycle◈ Members↗
FA-11199

Manifest refresh retains terminal flag · case 04

A failed refresh resets terminal state from incomplete metadata.

Streaming segment lifecycle◈ Members↗
FA-11200

Manifest refresh retains terminal flag · case 05

A failed refresh resets terminal state from incomplete metadata.

Streaming segment lifecycle◈ 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 ↗