-
Notifications
You must be signed in to change notification settings - Fork 368
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
Restore optimized num nodes. #1351
Conversation
On titan, the aprun command is now correct but num_nodes was incorrect due to not using the 'optimized' num nodes that task maker was programmed to use with aprun long ago. This commit restores that capability. [BFB]
@jgfouca and @amametjanov , I am leaving on vacation tomorrow, and won't be able to get to this in a timely fashion. Az, as you identified the problem originally, I hope that you will be willing to integrate this as well. |
@worleyph was this a planned vacation or is the SE team making you want to cut loose? |
:-) - no, a real vacation, though, being "retired", vacation is a funny concept. Planned trip to visit relatives. How about "non-ACME travel with limited network access". |
Did case.setup on the same PE layout from the original issue. Latest git master (v1.0.0-beta.1-80-g48fc6b3) shows
which is incorrect. After switching to this branch and
Machine-specific BFB update: skipping integration tests. |
Restore optimized num nodes: On titan, the aprun command is now correct but num_nodes was incorrect due to not using the 'optimized' num nodes that task maker was programmed to use with aprun long ago. This commit restores that capability. Fixes #1255 [BFB]
On titan, the aprun command is now correct but num_nodes was
incorrect due to not using the 'optimized' num nodes that task maker
was programmed to use with aprun long ago. This commit restores
that capability.
Fixes #1255
[BFB]