-
Notifications
You must be signed in to change notification settings - Fork 37
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
Adjusting gitlab yml for internal trigger of ci #200
Conversation
@JoshuaSBrown you should probably remove the |
Now that the regression tests are passing this is good to go. @pgrete When this is merged the commits should definitely be squashed. |
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.
I have two small final comments and then this can go squashed into developed.
CHANGELOG.md
Outdated
@@ -4,6 +4,7 @@ | |||
|
|||
### Added (new features/APIs/variables/...) | |||
- [[PR 335]](https://github.com/lanl/parthenon/pull/335) Support for project-relative `MACHINE_CFG` with `@PAR_ROOT@` | |||
- [[PR 200]](https://github.com/lanl/parthenon/pull/200) Adds support for running ci on power9 nodes. |
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.
This should probably be moved to the new Infrastructure heading.
.gitlab-ci-darwin.yml
Outdated
MODULE_MPI: "openmpi/p9/4.0.2-gcc_7.4.0" | ||
NUM_GPU_DEVICES_PER_NODE: 2 | ||
NUM_MPI_PROC_TESTING: 2 | ||
OMP_NUM_THREADS: 40 |
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.
OMP_NUM_THREADS: 40 | |
OMP_NUM_THREADS: 1 |
As long as we don't have proper threading support I strongly suggest to set num threads to 1. On the machine I using using more threads significantly slows down the code (in addition to technically not being properly supported).
PR Summary
Currently, testing triggering of internal ci for use on darwin. Preliminary testing is complete. Ci makes use of build scripts that are located in /scripts/darwin. The reason for using scripts was to help isolate the gitlab ci instance from the user environment.
PR Checklist