-
Notifications
You must be signed in to change notification settings - Fork 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
HADOOP-19528. Update Surefire plugin to 3.5.3 #7574
base: trunk
Are you sure you want to change the base?
Conversation
💔 -1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
(!) A patch to the testing environment has been detected. |
💔 -1 overall
This message was automatically generated. |
(!) A patch to the testing environment has been detected. |
💔 -1 overall
This message was automatically generated. |
@stoty Thank you very much for your contribution! However, I believe that upgrading the versions of the Surefire plugin and JUnit may not be possible for the time being. I had planned to upgrade the Surefire plugin twice, but after each upgrade, some unit tests failed to execute, so the plugin upgrade has been temporarily put on hold. As for JUnit, it is still in a mixed state (with JUnit 4 and JUnit 5 being used together) within Hadoop. I hope to consider upgrading to a major version once the transition to JUnit 5 is complete. |
Thanks for looking into this, @slfan1989 . I'm still looking into some related failures, but so far the failing tests are not failing because 3.5.3 is causing problems, but because the tests fail (in some cases time out) silently with the 3.0.0M4 , so it's not that 3.5.3 causes the tests failures, but rather 3.0.0-M4 does not correctly report them. I'm going to open/link tickets for these issues as I identify them. |
Description of PR
Hadoop currently uses the old 3.0.0-M2 surefire version, which swallows all errors in the test class setup @BeforeAll methods.
This leads to some tests not being run and not being reported as failing/erroring.
Update to the latest version, which fixes this issue.
Note that this may well cause new test failures, which were previously unreported, but that's not a problem with this patch.
How was this patch tested?
Ran it on JDK24, where some previously silently failing test properly errored out.
For code changes:
LICENSE
,LICENSE-binary
,NOTICE-binary
files?