pan3793 opened a new pull request, #7995:
URL: https://github.com/apache/hadoop/pull/7995

   <!--
     Thanks for sending a pull request!
       1. If this is your first time, please read our contributor guidelines: 
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
       2. Make sure your PR title starts with JIRA issue id, e.g., 
'HADOOP-17799. Your PR title ...'.
   -->
   
   ### Description of PR
   
   older versions of surefire plugin use `failIfNoTests` while newer versions 
use `surefire.failIfNoSpecifiedTests` to configure whether to fail when no test 
cases are matched.
   
   there are a few modules use `hadoop-main` instead of `hadoop-project` as the 
parent, this PR moves the definition of `surefire.failIfNoSpecifiedTests` to 
the top-level `hadoop-main`'s `pom.xml` to fix the CI failure.
   
   ### How was this patch tested?
   
   Run locally.
   
   ```
   $ mvn verify -fae -am -pl 
hadoop-client-modules/hadoop-client-check-invariants -pl 
hadoop-client-modules/hadoop-client-check-test-invariants -pl 
hadoop-client-modules/hadoop-client-integration-tests -Dtest=NoUnitTests 
-Dmaven.javadoc.skip=true -Dcheckstyle.skip=true -Dspotbugs.skip=true
   ```
   
   Fails on trunk
   ```
   ...
   [INFO] 
------------------------------------------------------------------------
   [INFO] BUILD FAILURE
   [INFO] 
------------------------------------------------------------------------
   [INFO] Total time:  3.923 s
   [INFO] Finished at: 2025-09-24T14:29:15+08:00
   [INFO] 
------------------------------------------------------------------------
   [ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:3.2.5:test (default-test) on 
project hadoop-build-tools: No tests matching pattern "NoUnitTests" were 
executed! (Set -Dsurefire.failIfNoSpecifiedTests=false to ignore this error.) 
-> [Help 1]                                                                     
                                                                                
                                                                              
   [ERROR] 
   [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
   [ERROR] Re-run Maven using the -X switch to enable full debug logging.
   [ERROR] 
   [ERROR] For more information about the errors and possible solutions, please 
read the following articles:
   [ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
   [ERROR] 
   [ERROR] After correcting the problems, you can resume the build with the 
command
   [ERROR]   mvn <args> -rf :hadoop-build-tools
   ```
   
   Fixed in this PR.
   ```
   ...
   [INFO] 
------------------------------------------------------------------------
   [INFO] BUILD SUCCESS
   [INFO] 
------------------------------------------------------------------------
   [INFO] Total time:  09:04 min
   [INFO] Finished at: 2025-09-24T14:28:37+08:00
   [INFO] 
------------------------------------------------------------------------
   ```
   
   ### For code changes:
   
   - [x] Does the title or this PR starts with the corresponding JIRA issue id 
(e.g. 'HADOOP-17799. Your PR title ...')?
   - [ ] Object storage: have the integration tests been executed and the 
endpoint declared according to the connector-specific documentation?
   - [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
   - [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`, 
`NOTICE-binary` files?
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to