-
Notifications
You must be signed in to change notification settings - Fork 117
[feat] Allow flexible node allocation to select nodes in any state #1374
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
[feat] Allow flexible node allocation to select nodes in any state #1374
Conversation
* Add unittests * Update documentation
bb3446a to
bfbc02d
Compare
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.
This PR is mixed with commits from other PRs. Can you fix it?
Yes I made a mistake when pushing because it have forked from another branch. |
|
Hello @teojgo, 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 2020-06-22 08:32:08 UTC |
Codecov Report
@@ Coverage Diff @@
## master #1374 +/- ##
==========================================
+ Coverage 91.68% 91.75% +0.06%
==========================================
Files 83 83
Lines 12714 12712 -2
==========================================
+ Hits 11657 11664 +7
+ Misses 1057 1048 -9
Continue to review full report at Codecov.
|
ekouts
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
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.
I can still see stale changes from the constraint PR. Plus there is another error that exists also in master most probably. If you pass --flex-alloc-nodes without an argument, it will complain, whereas it should just assume idle.
But isn't the point of having it to pass an argument. There is no default if the argument is used. Should I put one? |
|
Yeah not using the option at all implies idle |
|
But if you use the option an argument is required |
|
Ok, now I get it. But we should still change the documentation of the command line option: |
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
Fixes #1032