print warning when 'eb' command is not found in $PATH and for empty robot search path#3006
Merged
akesandgren merged 1 commit intoeasybuilders:developfrom Sep 16, 2019
Merged
Conversation
Contributor
|
Going in, thanks @boegel! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Using EasyBuild with an empty robot search path is likely to end in tears, so we should print a warning for it.
The location of the
ebcommand is used as a fallback to determine the default robot search path, and having a setup where EasyBuild works (when run withpython -m easybuild.main) without having theebcommand available is weird, so deserves a warning as well.