hydra evaluations are slow #36

Closed
opened 2 years ago by sb10q · 3 comments
sb10q commented 2 years ago
Owner

#23

https://git.m-labs.hk/M-Labs/nix-scripts/pulls/23#issuecomment-1156

(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?

(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?
Poster
Owner

board-generated-beta / board-generated

``board-generated-beta`` / ``board-generated``
Poster
Owner

Looking good now, thanks.

Looking good now, thanks.
sb10q closed this issue 2 years ago
Sign in to join this conversation.
No Label
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: M-Labs/nix-scripts#36
Loading…
There is no content yet.