FAILURE MAP
← Case archive

FA-99160 / Checkpoint tensor mapping / Member archive

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

arrival order changes reconstructed shard order.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Shards are [index, values]; concatenate values in ascending index order. Indices are unique.

Why this case matters

A bounded offline model of checkpoint tensor bookkeeping in a training workflow.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
reverse[3, 0][0, 3]Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗