You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 323ccf1
Browse filesBrowse the repository at this point in the historyBrowse files
dist: report remote compile exit codes as exit codes, not signals
`From<ProcessOutput> for process::Output` had the same problem as the
nvcc path: `ProcessOutput::code` is a real exit code (`status.code()` on
the build server), but the client turned it back with
`ExitStatus::from_raw`, which takes a wait status on Unix, so a remote
compile failing with exit code 1 showed up as "killed by signal 1".
The conversion now lives in one place, `util::exit_status_from_code`,
used by both `dist` and `nvcc`, with tests for the helper and for the
`ProcessOutput` round trip.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VszvDmRRPP1UcwozsUMY1L
0 commit comments