FAILURE MAP
← Case archive

FA-99170 / Checkpoint tensor mapping / Member archive

Checkpoint mapping: renaming collisions are not rejected · case 05

renaming collisions are not rejected.

Member previewVariant 5 · 3 implementations · 6 checks per implementation

Case contract

Apply exact-name renames to [name,value] pairs and return sorted pairs; if two inputs map to one output name, return [].

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
collision[["x", 2], ["x", 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 ↗