-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-50866][INFRA] Limit GHA job execution time to up to 2 hours #49544
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
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
I wonder if 2 hours is too short .... |
Member
Author
|
According to my observation, I guess the above pytorch and Let's see. I'll re-trigger again after the above PR is merged. |
HyukjinKwon
approved these changes
Jan 17, 2025
Member
Author
|
Thank you! |
zhengruifeng
approved these changes
Jan 17, 2025
acf60ea to
c7be7c7
Compare
Member
Author
|
Thank you all. I just rebased this to the master to bring SPARK-50863 . |
LuciferYang
approved these changes
Jan 17, 2025
Member
Author
dongjoon-hyun
added a commit
that referenced
this pull request
Jan 17, 2025
### What changes were proposed in this pull request? This PR aims to limit GHA job execution time to up to 2 hours. ### Why are the changes needed? To prevent a silent regression in terms of the GitHub Action execution time. - #49539 ### Does this PR introduce _any_ user-facing change? No, this is a infra-only change. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #49544 from dongjoon-hyun/SPARK-50866. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org> (cherry picked from commit 3b0ac45) Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
Member
Author
|
Merged to master/4.0. Thank you again, @HyukjinKwon , @zhengruifeng , @LuciferYang . |
Closed
zifeif2
pushed a commit
to zifeif2/spark
that referenced
this pull request
Nov 14, 2025
### What changes were proposed in this pull request? This PR aims to limit GHA job execution time to up to 2 hours. ### Why are the changes needed? To prevent a silent regression in terms of the GitHub Action execution time. - apache#49539 ### Does this PR introduce _any_ user-facing change? No, this is a infra-only change. ### How was this patch tested? Pass the CIs. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#49544 from dongjoon-hyun/SPARK-50866. Authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by: Dongjoon Hyun <dongjoon@apache.org> (cherry picked from commit 63008c7) Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

What changes were proposed in this pull request?
This PR aims to limit GHA job execution time to up to 2 hours.
Why are the changes needed?
To prevent a silent regression in terms of the GitHub Action execution time.
Does this PR introduce any user-facing change?
No, this is a infra-only change.
How was this patch tested?
Pass the CIs.
Was this patch authored or co-authored using generative AI tooling?
No.