andygrove opened a new pull request, #7682:
URL: https://github.com/apache/datafusion-comet/pull/7682

   ## Which issue does this PR close?
   
   Backport of #7679 to `branch-1.2`. #7679 is approved but not merged yet, so 
this should merge after it. There is no issue.
   
   ## Rationale for this change
   
   No job in the workflows sets `timeout-minutes`, so each one gets GitHub's 
six hour default. A hung suite holds a runner, and its pipeline, for six hours 
before it reports a failure. This came up while investigating CI failures on 
the `branch-1.2` backports, and the branch has the same workflows, so it needs 
the same limits. CI changes for the branch's own build qualify for a backport 
(see the backporting guide).
   
   ## What changes are included in this PR?
   
   The same limits as #7679, applied to the jobs this branch has. The 
cherry-pick conflicted in three places, all because `branch-1.2` is older than 
`main`:
   
   - `ci_fork.yml` does not exist here, so its change is dropped.
   - `pr_build_linux.yml` has no `linux-test-native-executors` job, so that 
limit is dropped. The other limits are unchanged.
   - `docs.yaml` builds and publishes in one job instead of separate build and 
deploy jobs. That job gets the 60 minute build limit.
   - `label_prs.yml` has a job that #7679 does not touch, because `main` no 
longer has it in this form. It gets a 10 minute limit like the other labelling 
jobs.
   
   Every job with `runs-on` now has `timeout-minutes`. The README section is 
unchanged from #7679 and its references (`pr_build_linux.yml`, 
`spark_sql_test_reusable.yml`, the merge queue's 
`check_response_timeout_minutes: 300`) all exist on this branch.
   
   ## How are these changes tested?
   
   `actionlint`, `dev/ci/check-ci-config.py` and `prettier --check` on the 
README pass. A script confirmed that every job with `runs-on` has 
`timeout-minutes`. This pull request's own CI runs under the new limits.
   


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