voonhous commented on issue #16448: URL: https://github.com/apache/hudi/issues/16448#issuecomment-5467301857
## What it costs to run hudi-cli again The module was dropped from the catch-all lists to cut CI runtime, so here is the measured price of putting it back, from #18816's Azure logs vs the 12 most recent successful builds on other PRs: - **Azure**: `UT_FT_10` (`UT FT common & other modules`) goes from ~73 to ~83 min. The reactor summary pins it on `hudi-cli` itself: 9:19 / 9:38 / 10:27 in the functional-test invocation and 16-18 s in the unit-test one. That phase alone goes 3:50 -> ~13:45, since the functional suite starts a SparkSession per test class. No other Azure job changes. - **GitHub Actions**: #18816 adds `test-hudi-cli` as its own job, 19.0 min (8.6 install, 0.3 UT, 9.7 FT) against a 72.3 min critical path. No wall-clock change, +19 runner-minutes out of 607. So ~10 min on one Azure job for 113 tests and the module's coverage going ~15% -> ~43%. Caveat for anyone re-measuring: `UT_FT_10`'s install phase swings 15:39 to 40:09 across builds, so comparing job totals between PRs measures agent luck, not tests. Per-invocation table in https://github.com/apache/hudi/pull/18816#issuecomment-5467301094. -- 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]
