GH-50819: [Release] Increase YUM verification timeout - #50835
Open
erichanwang wants to merge 1 commit into
Open
Conversation
erichanwang
requested review from
assignUser,
jonkeane,
kou and
raulcd
as code owners
August 9, 2026 19:45
|
|
|
|
uros-b
approved these changes
Aug 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Rationale for this change
The arm64 YUM release-verification job can exceed its 30-minute limit when the EPEL mirror is slow. Issue #50819 reports repeated timeouts during the 25.0.1 verification, including a package download taking about 15 minutes at roughly 23 kB/s. Increasing the shared matrix job timeout gives the verification enough time to complete under this documented slow-mirror condition.
What changes are included in this PR?
yumin.github/workflows/verify_rc.ymlfromtimeout-minutes: 30totimeout-minutes: 60.ubuntu-latestandubuntu-24.04-arm, so the timeout change applies to both architectures while keeping the workflow structure unchanged.Are these changes tested?
The workflow remains valid YAML, and
git diff --checkpasses. This is a CI configuration-only change; no runtime test is applicable.Are there any user-facing changes?
No direct user-facing API changes. Release verification is less likely to fail due to transient slow package mirrors.