You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems this is actually not only related to --include-easyblocks-from-pr...
For instance, if you mix that local file with files from --from-pr, you get the same behaviour, but it seems it never came up before (?) because that's a weird scenario
The workaround is either to use the absolute path as @boegel mentioned, or to add the folder where the local easyconfig is to the robot path, e.g. in this case with -r .
Now, the reason this happens is that the extract_file method, called from download_repo, changes the working directory (see also #2858), and in fact everything that comes after download_repo seems to rely on that...
@migueldiascosta I'm changing download_repo so it doesn't have the side effect of changing directories anymore in #3486
As far as I can tell, nothing that calls download_repo relies on the changing of directories at all?
The explicit change_dir is just a change we made as a part of #3292 when we changed extract_file...
Example:
Using absolute path to easyconfig instead via
eb $PWD/AABQUS-2019.eb ...
does work...The text was updated successfully, but these errors were encountered: