It's a consequence of our changes to avoid repeated Vivado runs. (#1)
For Nix to know what inputs to build, it now has to generate Cargo and Vivado input for each jobset at evaluation time.
Unless we want to do undo all these changes, I propose running artiq code-generation in a separate jobset. Name?
(Issue pertains to artiq-full)
It's a consequence of our changes to avoid repeated Vivado runs. (#1)
For Nix to know what inputs to build, it now has to generate Cargo and Vivado input for each jobset at evaluation time.
Unless we want to do undo all these changes, I propose running artiq code-generation in a separate jobset. Name?
#23
(Issue pertains to artiq-full)
It's a consequence of our changes to avoid repeated Vivado runs. (#1)
For Nix to know what inputs to build, it now has to generate Cargo and Vivado input for each jobset at evaluation time.
Unless we want to do undo all these changes, I propose running artiq code-generation in a separate jobset. Name?
board-generated-beta/board-generatedLooking good now, thanks.