kumarUjjawal opened a new pull request, #27577:
URL: https://github.com/apache/datafusion/pull/27577

   ## Which issue does this PR close?
   
   Related to #25148. This follows apache/datafusion-comet#7679.
   
   ## Rationale for this change
   
   GitHub Actions defaults to six hours per job. Explicit job timeouts let CI 
report a hung job sooner and free its runner.
   
   ## What changes are included in this PR?
   
   - Add timeouts to the 49 runner jobs that lacked one, so all 52 runner jobs 
have an explicit limit.
   - Use recent successful Runs-On and GitHub-hosted jobs, including fork runs, 
to size the limits. The Linux test took up to about 10 minutes upstream and 25 
minutes on a fork in the sample. Its 90-minute limit leaves room for cold 
caches. [Upstream 
run](https://github.com/apache/datafusion/actions/runs/44273230362/job/134695832557),
 [fork 
run](https://github.com/kumarUjjawal/datafusion/actions/runs/42294482708/job/128158781944).
   - Use the existing 15-minute `ubuntu-slim` runner limit for the docs jobs.
   - Document how to choose and adjust job timeouts in the contributor guide.
   
   ## What is the testing strategy for this PR?
   
   Parsed all 20 workflows and verified every runner job has a timeout. 
Compared the parsed YAML against `main` to confirm the timeout additions are 
the only workflow changes. The existing CI-script tests, required-check 
mapping, and Prettier checks passed.
   
   ## Are there any user-facing changes?
   
   CI jobs now stop when they reach their configured timeout.
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to