voonhous commented on PR #18816: URL: https://github.com/apache/hudi/pull/18816#issuecomment-5467301094
## CI cost of re-enabling hudi-cli From the Azure task logs of this PR's three builds (16694/16695/16696) vs the 12 most recent successful builds on other PRs. **Azure**, job `UT_FT_10` (`UT FT common & other modules`), per maven invocation: | phase | other PRs | this PR | |---|---|---| | `clean install` | 15:39 - 21:22 | 16:08 / 16:34 / 16:32 | | UT job10 modules | 36:40 - 40:33 | 37:18 / 39:21 / 38:49 | | UT hudi-utilities | 12:08 - 14:10 | 12:35 / 13:24 / 13:00 | | FT job10 modules | 3:44 - 4:02 | 13:09 / 13:39 / 14:20 | The reactor summaries attribute it exactly: `hudi-cli` is 9:19 / 9:38 / 10:27 in the FT invocation, 16-18 s in the UT one. So **+10 min on one job**, all of it functional tests, taking that job from ~73 to ~83 min. No other Azure job changes. **GitHub Actions**: `test-hudi-cli` runs 19.0 min (8.6 install, 0.3 UT, 9.7 FT) against a 72.3 min critical path, so no wall-clock change; +19 runner-minutes out of 607. Two things worth recording: - Job totals across PRs do not measure this. `UT_FT_10`'s install phase swings 15:39 to 40:09 (#19777 was 37:26 in build 16674 and 16:03 in 16668, same branch), which is bigger than the hudi-cli delta. - `UT_FT_10` has a 120 min timeout. A slow-install draw plus hudi-cli is ~107 min, so headroom on those builds drops from ~23 to ~13 min. If that bites, the fix is a separate Azure job rather than the catch-all list. -- 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]
