voonhous opened a new pull request, #19933:
URL: https://github.com/apache/hudi/pull/19933

   ### Describe the issue this Pull Request addresses
   
   Part of #19524, stacked on #19931. Every Java CI job pays about five minutes 
of checkout and build before its tests. 
`test-hudi-hadoop-mr-and-hudi-java-client` ran 9 minutes in total, and 
`test-utilities-rest` 18 to 22, on the same JDK 11 lane, so the small job's 
tests fit inside the other with room under the run's longest jobs.
   
   ### Summary and Changelog
   
   - `test-utilities-rest` becomes `test-utilities-rest-hadoop-mr-java-client`: 
its build also covers `hudi-hadoop-mr` and `hudi-client/hudi-java-client`, and 
their unit-test step runs after the utilities steps, verbatim.
   - The Codecov upload carries both flags (`utilities`, 
`hadoop-mr-java-client`), so the flag views keep their history.
   - `test-hudi-hadoop-mr-and-hudi-java-client` is removed. Java CI goes from 
14 jobs to 13.
   
   Measurement, three samples: the merged job's duration against 18 to 22 plus 
9 before, the run's runner-minutes, and the run's longest job (which should not 
move).
   
   | metric | before | sample 1 | sample 2 | sample 3 |
   |---|---|---|---|---|
   | merged job | 18 to 22 and 9, two jobs | pending | pending | pending |
   | runner-minutes per run | 489 to 534 | pending | pending | pending |
   | run's longest job | 33 to 36 | pending | pending | pending |
   
   ### Impact
   
   CI configuration only.
   
   ### Risk Level
   
   low. Same commands, same lane; only the job boundary moves.
   
   ### Documentation Update
   
   none
   
   ### Contributor's checklist
   
   - [x] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [x] Enough context is provided in the sections above
   - [x] Adequate tests were added if applicable
   


-- 
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]

Reply via email to