voonhous opened a new pull request, #19931: URL: https://github.com/apache/hudi/pull/19931
### Describe the issue this Pull Request addresses Part of #19524, stacked on #19919. The nine Java 17 Spark test jobs have no `timeout-minutes`, so a job whose surefire fork stops answering runs to GitHub's six-hour default and holds a runner for that long. ### Summary and Changelog - `timeout-minutes: 75` on `test-spark-java17-ut-functional`, `ut-other`, `ut-fat-and-ftc`, `fta`, `ftb`, `scala-dml-1`, `scala-dml-2`, `scala-other-1` and `scala-other-2`, the value `test-spark-client-and-hadoop-common` already uses. The other five test jobs already have one (40 to 90). The longest of the nine measured 44 minutes on a slow runner under the resharded workflow, so the cap only fires on a hang. <details> <summary>The hang that motivated it</summary> On attempt 3 of [run 34711686507](https://github.com/apache/hudi/actions/runs/34711686507), `ut-other` ([job 103611929617](https://github.com/apache/hudi/actions/runs/34711686507/job/103611929617)) finished all 184 hudi-common test classes green in 26 seconds, then printed nothing for 76 minutes: the surefire fork never reported completion, and the runner had to kill Maven and one fork JVM when the job was cancelled by hand. The same commit's two earlier attempts ran the job in 32 minutes. Surefire's `forkedProcessExitTimeoutInSeconds` did not fire because the fork never reached the exit path it guards. </details> ### Impact CI configuration only. ### Risk Level low. A job that legitimately needs more than 75 minutes would fail; none of the nine has come within 30 minutes of that. ### 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]
