FAILURE MAP
← Case archive

FA-99225 / Checkpoint tensor mapping / Member archive

Checkpoint mapping: tied parameter aliases load conflicting values · case 05

tied parameter aliases load conflicting values.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

For alias groups, return one value per group only if all supplied members agree; absent groups are omitted.

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
conflict[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 ↗