Bring back constituents to Hydra #340
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a commit from @Ma27 https://git.lix.systems/ma27/nix-eval-jobs/commit/5ce92e2c4d318b30edaafa4d8664b9e15e941f32 I rebased. Thanks @Ma27!
This (or something like it) is needed for
nix-eval-jobsto replacehydra-eval-jobs.The part about finding
_hydraAggregate/constituentsis basically derived fromhydra-eval-jobs, however the part aboutnamedConstituentshas been changed: we still stream out jobs when they appear, however we suppress this for aggregate jobs.These jobs are post-processed at the end, i.e. if
namedConstituentsexist, these will be mapped to the drvPath of the other jobs. Then, the drv will be rewritten to contain the drvPath of said jobs[1] and the JSON containing the rewrittendrvPathwill be printed out.[1] This was an optimization to reduce the memory footprint of
evaluating e.g. the
testedjob in nixpkgs.(cherry picked from commit 76f32ed29e25b22d69467d28b72efcc9ac22e1bf)