voonhous commented on PR #19919: URL: https://github.com/apache/hudi/pull/19919#issuecomment-5643440699
Per-job execution time, this PR's run ([34670498897](https://github.com/apache/hudi/actions/runs/34670498897), [34670498928](https://github.com/apache/hudi/actions/runs/34670498928)) against #19918's run ([34668461677](https://github.com/apache/hudi/actions/runs/34668461677), [34668461644](https://github.com/apache/hudi/actions/runs/34668461644)). Same code apart from this change. Queue time excluded. | job | #19918 run (min) | this PR (min) | delta (min) | |---|---|---|---| | integration-tests | 37 | 28 | -9 | | test-common-and-other-modules | 34 | 34 | 0 | | test-flink-1 | 32 | 31 | -1 | | test-flink-2 | 23 | 23 | 0 | | test-hudi-hadoop-mr-and-hudi-java-client | 11 | 10 | -1 | | test-spark-client-and-hadoop-common | 33 | 34 | +1 | | test-spark-java17-fta | 30 | 35 | +5 | | test-spark-java17-ftb | 29 | 28 | -1 | | test-spark-java17-scala-dml-1 | 40 | 38 | -2 | | test-spark-java17-scala-dml-2 | 22 | 31 | +9 | | test-spark-java17-scala-other-1 | 40 | 40 | 0 | | test-spark-java17-scala-other-2 | 37 | 30 | -7 | | test-spark-java17-ut-fat-and-ftc | 36 | 37 | +1 | | test-spark-java17-ut-functional | 28 | 28 | 0 | | test-spark-java17-ut-other | 29 | 32 | +3 | | test-utilities-rest | 22 | 22 | 0 | | test-utilities-streamer | 31 | 30 | -1 | | validate-bundle-spark4 | 10 | 10 | 0 | | validate-bundles | 16 | 16 | 0 | | total | 541 | 539 | -2 | Only integration-tests changed code-wise. Its build step went from 646 s to 479 s (66 modules to 30) and its IT step from 1390 s to 1028 s (64 modules verified to 4). The IT step's log lists the same 25 test classes as before (the 14 integration-test classes plus hudi-integ-test's 11 unit classes), with the same per-module totals. The rest of the delta is runner drift on untouched jobs, in both directions. -- 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]
