Never force path during evaluation phase
#24
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
3noch
approved these changes
Sep 7, 2024
|
Thanks for the approval. What can we do to help move this along? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
builtins.baseNameOfandbuiltins.pathExistsrequires the derivation that providespathin its output to be built during evaluation phase. We have ax86_64-linuxHydra server with a MacOS machine as a remote builder. We evaluate all derivations on the main Hydra server, only distributing the actual building to MacOS.builtins.pathExistscaused the entire build process of MacOS derivations to run during evaluation. Those heavy work won't show as normal Hydra jobs, and the failures are shown in "Evaluation Error" tab.