owned-gpu-smoke-2c3b248-7c03a644
failed —
Hypothesis
With the derived image assigned to the correct owned worker, the complete tiny smoke will pass through the verified sibling-container and scoped named-volume topology.
Why run it
Confirms or falsifies the tokenizer, renderer, CUDA forward/backward, checkpoint read-back, and durable named-volume artifact recovery path.
Written result
Status: failed at the adapter-output contract after successful GPU work.
The tokenizer and renderer passed, the RTX 4080 completed one forward/backward step, checkpoint read-back passed, and the 16,179-byte checkpoint was durably recovered with SHA-256 77e93414e04707efb0469718426bb2364d5a7b22e575e519124d5c628442348f. The run is still classified as failed because the inherited NGC entrypoint printed its banner before the JSON result and the adapter correctly rejected mixed stdout. A new run will bypass the image entrypoint explicitly.
State transitions
- planned2026-09-20T09:16:31Z
- staged2026-09-20T09:17:49Z
- failed2026-09-20T09:18:15Zngc_entrypoint_banner_broke_json_contract
Run record
Verbatim from runs/owned-gpu-smoke-2c3b248-7c03a644/run.yaml, the record committed before launch.
e3b0c44298fc1c14…7c03a6440fe64d2a…