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
Notice the spack cloning when you type benchpark version
Expected behavior
Are we subsequently using the cloned spack? If not, should we be having instructions here - or move the version check to after a workspace is created?
Supercomputer (please complete the following information):
system: any
The text was updated successfully, but these errors were encountered:
In main.py, import benchpark.cmd.audit calls bootstrapper.bootstrap(), which is what installs ramble and spack if they do not already exist in the path (i.e. will happen for fresh install).
One way I can think of to address this is to check before the import and exit if using benchpark -V or benchpark --version, like here #595
Describe the bug
benchpark version
clones spackTo Reproduce
Steps to reproduce the behavior:
benchpark version
Expected behavior
Are we subsequently using the cloned spack? If not, should we be having instructions here - or move the version check to after a workspace is created?
Supercomputer (please complete the following information):
The text was updated successfully, but these errors were encountered: