FA-99172 / Checkpoint tensor mapping / Member archive
Checkpoint mapping: unexpected checkpoint tensors are accepted · case 02
unexpected checkpoint tensors are accepted.
Case contract
Return missing and unexpected names as sorted lists in a pair; names present in both sets are matched.
Why this case matters
A bounded offline model of checkpoint tensor bookkeeping in a training workflow.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| extra many | [[], []] | [[], ["y", "z"]] | 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 ↗