Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify absolute path to benchcab executable in the job script #95

Closed
SeanBryan51 opened this issue Jun 16, 2023 · 0 comments · Fixed by #117
Closed

Specify absolute path to benchcab executable in the job script #95

SeanBryan51 opened this issue Jun 16, 2023 · 0 comments · Fixed by #117
Assignees
Labels
enhancement New feature or request

Comments

@SeanBryan51
Copy link
Collaborator

We should specify the absolute path to the benchcab executable in the job script so that we don't run into path issues when running using a 'locally installed' version of benchcab. This will be helpful making code changes and testing them on NCI.

We can use a combination of sys.argv and shutil.which() to get the absolute path of the benchcab executable.

@SeanBryan51 SeanBryan51 added the enhancement New feature or request label Jun 16, 2023
@SeanBryan51 SeanBryan51 linked a pull request Jul 19, 2023 that will close this issue
@SeanBryan51 SeanBryan51 self-assigned this Jul 19, 2023
SeanBryan51 added a commit that referenced this issue Jul 19, 2023
This change specifies the absolute path to the benchcab executable in
the job script so that we don't run into path issues when running using
a 'locally installed' version of benchcab. This will be helpful making
code changes and testing them on NCI.

Fixes #95
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant