-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
HADOOP-17769. Upgrade JUnit to 4.13.2. fixes TestBlockRecovery #3131
Conversation
💔 -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.
Looks good. You should also update the junit version in the LICENSE-binary file.
(Better to run mvn dependency:tree to also check for the version of transitive dependencies)
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, I applied the patch manually and confirmed the test passed.
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.
Tried the mvn dependency tree on trunk, it looks fine.
@jojochuang do you mean this file?
https://github.com/apache/hadoop/blob/trunk/licenses-binary/LICENSE-junit.txt
Couldn't find any version mentioned.
+1 |
I think the file exists in trunk but not in branch-2.10. Line 505 in 10b79a2
|
Oh yeah sorry I wasn't aware this is for branch-2.10. No issue now. +1 |
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 @jojochuang , @aajisaka , @ayushtkn and @ferhui for the reviews and feedback. |
Merged. Thanx Everyone!!! |
HADOOP-17769 Upgrade JUnit to 4.13.2
JUnit 4.13.1 has a bug that is reported in Junit issue-1652 Timeout ThreadGroups should not be destroyed.
The bug has been fixed in Junit-4.13.2
Backporting PR-3130 to branch-2.10