-
Notifications
You must be signed in to change notification settings - Fork 117
[bugfix] Fix Slurm backend failures when trying node lists with inexistent nodes #713
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
[bugfix] Fix Slurm backend failures when trying node lists with inexistent nodes #713
Conversation
|
@kraushm Why this is a WIP? |
|
Hello @kraushm, Thank you for updating! Cheers! There are no PEP8 issues in this Pull Request!Do see the ReFrame Coding Style Guide Comment last updated at 2019-03-14 15:01:56 UTC |
4e217f5 to
041941a
Compare
|
@jenkins-cscs retry kesch |
Codecov Report
@@ Coverage Diff @@
## master #713 +/- ##
==========================================
- Coverage 91.82% 91.79% -0.03%
==========================================
Files 77 77
Lines 9488 9491 +3
==========================================
Hits 8712 8712
- Misses 776 779 +3
Continue to review full report at Codecov.
|
victorusu
left a comment
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
teojgo
left a comment
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. Tested both with valid and invalid node names and works fine.
|
@jenkins-cscs retry daint |
vkarak
left a comment
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
Modifying the way the set of available nodes is built in SLURM, in order to prevent erroneous entries (e. g. "not found")
Fixes #694