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
Is your feature request related to a problem? Please describe.
Since NixOS tests can run on Darwin since a few months, OfBorg is trying to run them, but these tests rely on native Linux builds, which should be performed by a remote (or local VM) builder.
As an alternative, we could configure the OfBorg cluster in two layers, groups of machines, where the nodes in the top layer run the OfBorg evaluations, and the lower layer only performs builds.
The top layer would not receive remote build requests from other nodes in the top layer, and the lower layer only receives builds for the intended derivation system, making this setup acyclic.
If the top layer also performs builds for their native system, that also works, but is perhaps less effective at distributing work, as they can only be allowed to build locally evaluated derivations.
The docker-tools-cross VM test also has a multi-system derivation graph that requires remote builders to work. (Cross compile an image on one system, run on another)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Since NixOS tests can run on Darwin since a few months, OfBorg is trying to run them, but these tests rely on native Linux builds, which should be performed by a remote (or local VM) builder.
Describe the solution you'd like
Ideally, all OfBorg nodes can delegate a few builds to each other node, but the remote build implementation does not currently support cyclic remote builder setups.
As an alternative, we could configure the OfBorg cluster in two layers, groups of machines, where the nodes in the top layer run the OfBorg evaluations, and the lower layer only performs builds.
The top layer would not receive remote build requests from other nodes in the top layer, and the lower layer only receives builds for the intended derivation
system
, making this setup acyclic.If the top layer also performs builds for their native
system
, that also works, but is perhaps less effective at distributing work, as they can only be allowed to build locally evaluated derivations.Describe alternatives you've considered
Make the passthru tests use cross compilation. I don't think this is desirable; see NixOS/nixpkgs#317651 (review)
Additional context
The
docker-tools-cross
VM test also has a multi-system
derivation graph that requires remote builders to work. (Cross compile an image on onesystem
, run on another)The text was updated successfully, but these errors were encountered: