-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
YARN-11390. TestResourceTrackerService.testNodeRemovalNormally ... #5190
Conversation
…own nodes should be 0 now expected: <1> but was: <0> - The hardcoded sleep what was used in the test was not the most stable solution - It was replaced with a polling assert
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.
@K0K0V0K , thank you for the patch. I entered one comment.
.../src/test/java/org/apache/hadoop/yarn/server/resourcemanager/TestResourceTrackerService.java
Show resolved
Hide resolved
🎊 +1 overall
This message was automatically generated. |
…own nodes should be 0 now expected: <1> but was: <0> - The hardcoded sleep what was used in the test was not the most stable solution - It was replaced with a polling assert
💔 -1 overall
This message was automatically generated. |
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.
+1
Thanks for incorporating the code review feedback, @K0K0V0K .
The failure in the latest CI run looks unrelated. I applied the patch locally and it ran clean.
I'll plan on committing this tomorrow.
…own nodes should be 0 now expected: <1> but was: <0> (apache#5190) Reviewed-by: Peter Szucs Signed-off-by: Chris Nauroth <cnauroth@apache.org>
…Shutdown nodes should be 0 now expected: <1> but was: <0>
Description of PR
How was this patch tested?
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?