-
Notifications
You must be signed in to change notification settings - Fork 12
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
remove G2G arg from run_command, consolidate gpu logic in buildenv #76
Conversation
Performance test launched https://jenkins.ginko.ch/job/pace-fv3core-performance-test/91/. |
Submitted performance test again for gpu, will appear at https://jenkins.ginko.ch/job/pace-fv3core-performance-test/93/. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Because the buildenv changes are backwards incompatible I will merge to main pointing to the buildenv branch, then merge the branch on buildenv, then merge a dependabot PR. |
## Infrastructure changes: - G2G is removed as an argument for run_command - DOCKER_BUILDKIT=1 is set in buildenv, not pace - PYTHONOPTIMIZE=TRUE is set in run_on_daint.sh, not in the slurm script - updated pace-util jenkins.sh to match buildenv run_command api Linked to ai2cm/pace#76
## Purpose A bug was introduced by #76 where an argument was removed but the argument number for the final argument (script filename) was not decremented in buildenv. This PR fixes that bug. Depends on ai2cm/buildenv#35. ## Infrastructure changes: - Fixed bug which causes scheduler script argument to be ignored in buildenv's run_command
Purpose
run_command currently takes a G2G argument we have hard-coded to always be false. This PR removes that argument, and moves several environment variables from pace into buildenv.
Depends on ai2cm/buildenv#32.
Infrastructure changes:
Checklist
Before submitting this PR, please make sure:
Additionally, if this PR contains code authored by new contributors: