Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Derivations built locally that have dependencies built remotely hang indefinitely on "Sending inputs" #1448

Open
hacker1024 opened this issue Feb 24, 2025 · 0 comments
Labels

Comments

@hacker1024
Copy link
Member

hacker1024 commented Feb 24, 2025

Describe the bug

When a local build has a dependency built remotely, it [the local build] hangs indefinitely on "Sending inputs". When this occurs, such builds cannot even be cancelled: Attempting to do so labels it a such, but the job still shows up in the machine status page and prevents the build queue from advancing.

Nothing significant appears to be logged on the Hydra server or remote builder.

Single-host builds still complete as normal.

Practical examples of such cases:

  • An aggregate job with constituents of another architecture
  • A deployment runCommandHook using a NixOS system closure for another architecture
  • A regular derivation depending on another with specific requiredSystemFeatures (untested)

To Reproduce

  1. Set up two machines: A Hydra server, and a remote builder
  2. Add a job to build a derivation on the server machine that depends on another derivation built on the remote builder. This can be done by either changing the system or requiredSystemFeatures.
  3. Note that the server-built build hangs on "Sending inputs"

Expected behavior

The remote dependency should be copied onto the server machine, and the build using it should complete successfully.

Screenshots

I'm pretty sure the "ssh" here is cosmetic - normal jobs have no issue with this builder, it doesn't actually seem to be using SSH.

Image

Hydra Server:

Additional context

I upgraded from 02e453f with Nix 2.19, which did not have this issue.

@hacker1024 hacker1024 added the bug label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant