Azure CI times out on scala UT
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
Example [https://dev.azure.com/apachehudi/hudi-oss-ci/_build/results?buildId=2944&view=results.] Got the same thing in my other PRs as well. Like [https://github.com/apache/hudi/pull/12572] which is nothing but add some logging.
The scala spark UT data source is hitting the 2hr runtime limit and got cancelled. We should increase the timeout to 2.5 hr as a short term mitigation and in the next sprint we figure out the long running ones and see how they can be improved.
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-8893
- Type: New Feature
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with Azure build 2944 and the CI definition that runs the Scala Spark unit tests; PR 12572 provides context that the timeout also affects logging-only changes. Locate the two-hour limit, update it to 2.5 hours, and verify that the job no longer cancels at two hours.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, scala
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100