[SPARK-48097][INFRA] Limit GHA job execution time to up to 3 hours in build_and_test.yml
#46344
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 3 hours in
build_and_test.yml
in order to avoid idle hung time.New limit is applied for all jobs except three jobs (
precondition
,infra-image
, andbreaking-changes-buf
) which didn't get a hung situation before.Why are the changes needed?
Since SPARK-45010, Apache spark used 5 hours.
build_and_test.yml
#42727This is shorter than GitHub Action's the default value (6 hour) is used.
This PR reduces to
3 hour
to follow new ASF INFRA policy which has been applied since April 20, 2024.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual review.
Was this patch authored or co-authored using generative AI tooling?
No.