-
Notifications
You must be signed in to change notification settings - Fork 4k
GH-49184: [CI] AMD64 macOS 15-intel Python 3 consistently times out #49189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
|
|
We need to change the diff --git a/.github/workflows/python.yml b/.github/workflows/python.yml
index bc7fe3cd68..e9db71a8c7 100644
--- a/.github/workflows/python.yml
+++ b/.github/workflows/python.yml
@@ -142,7 +142,7 @@ jobs:
name: ${{ matrix.architecture }} macOS ${{ matrix.macos-version }} Python 3
runs-on: macos-${{ matrix.macos-version }}
if: ${{ !contains(github.event.pull_request.title, 'WIP') }}
- timeout-minutes: 60
+ timeout-minutes: 75
strategy:
fail-fast: false
matrix: |
92520c5 to
d9590d8
Compare
|
Thanks, @kou! Updated. |
|
BTW, can we speed up macOS jobs...? It seems that tests were finished in about 5min on Linux: https://github.com/apache/arrow/actions/runs/21831237516/job/62989873777#step:6:6707 But tests were finished in about 30min on macOS: https://github.com/apache/arrow/actions/runs/21831237516/job/62989873535#step:10:541 Have you profiled tests on macOS? |
|
@kou speeding up jobs would be best, indeed! I've been checking Build and why I see just around 7 successful completions in February (Perhaps using I will check Test phase and profiling options next. For now I've added "--durations=20 -v" on pytest Locally on M1 I get pytest finished in 86.44s (0:01:26) and the following test duration for comparison: |
|
ARM64 macOS 14 Python 3 shows deterioration For ARM64 macOS 14 Python 3 durations didn't print yet as it got cancelled at [ 99%] this time within the new 75m timeout setting. I will try to run once more with 90m timeout setting. |
|
AMD64 macOS 15-intel Python 3 finally succeeds in 1h 16m 47s |
Rationale for this change
Recent CI checks failing with the job
AMD64 macOS 15-intel Python 3being cancelled at 60 minutes.The job has exceeded the maximum execution time of 1h0m0sWhat changes are included in this PR?
Temporary timeout increase from 60 to 75 minutes for macOS Python 3 jobs (both ARM64 and Intel jobs as these have common setting.)
Are these changes tested?
To be tested on CI.
Are there any user-facing changes?
No.