SSH connection dropping when copying outputs should not abort the entire build tree #922

Open
opened 2025-07-19 07:16:01 +00:00 by k900 · 3 comments
Member

When copying outputs from a remote builder on a bad connection, and the connection drops midway, the entire build tree is aborted with "truncated NAR encountered", followed by "some outputs are unexpectedly invalid".

The actual error is fine - the connection did drop, and we can't recover from that; however, killing all the concurrently running builds is bad.

When copying outputs from a remote builder on a bad connection, and the connection drops midway, the entire build tree is aborted with "truncated NAR encountered", followed by "some outputs are unexpectedly invalid". The actual error is fine - the connection _did_ drop, and we can't recover from that; however, killing all the concurrently running builds is bad.
Owner

duplicate of #878?

duplicate of #878?
Author
Member

Nope, this kills everything even with --keep-going.

Nope, this kills everything even with --keep-going.
Owner

well thank fuck this codebase has historically been a perfect fount of consistent behavior

well thank fuck this codebase has historically been a perfect fount of consistent behavior
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#922
No description provided.