-
Notifications
You must be signed in to change notification settings - Fork 371
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
Add machines muller-cpu/muller-gpu as NERSC internal testing machines similar to pm-cpu/pm-gpu #6154
Conversation
|
Note that I'm testing newer module versions on muller. This PR as-is should yield same config as current pm-cpu/pm-gpu. |
Now it says "This branch has conflicts that must be resolved". Does that mean I can't try to merge with next? |
No. Just resolve the conflicts. |
#6154) Initial add of 2 machines that are similar to perlmutter -- muller-gpu =~ pm-gpu, muller-cpu =~ pm-cpu. I can use these machines to test software stack changes before we use them on permutter. Only handful of nodes on each. Also, for one conus test (only tested in scream), I reduced the number of nodes needed for pm-gpu/muller-gpu. [BFB]
merged to next |
As expected, no problems with tests, merging to master. Don't have the green button as there were conflicts, so will try merging to master manually. |
Initial add of 2 machines that are similar to perlmutter -- muller-gpu =~ pm-gpu, muller-cpu =~ pm-cpu.
I can use these machines to test software stack changes before we use them on permutter.
Only handful of nodes on each.
Also, for one conus test (only tested in scream), I reduced the number of nodes needed for pm-gpu/muller-gpu.
[BFB]