Bump registry-build timeout from 30m to 45m#66185
Merged
kaxil merged 1 commit intoapache:mainfrom Apr 30, 2026
Merged
Conversation
Recent successful full builds run 26-30 minutes (most recent: 29m49s, 26m13s, 20m43s). The 30-minute timeout left near-zero headroom -- a modest pypistats slowdown or transient registry/network blip during the per-provider PyPI fetches in `extract_metadata.py` would race the timeout and silently fail the registry update. After apache#66100 (#1305 fix), `registry-build.yml` fires automatically on every wave-release dispatch. Bumping the timeout to 45 minutes gives meaningful headroom without going so high that a genuinely stuck job sits around forever.
kaxil
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jscheffl and
potiuk
as code owners
boring-cyborg
Bot
added
area:dev-tools
area:registry
backport-to-v3-2-test
jscheffl
approved these changes
Apr 30, 2026
Contributor
Backport failed to create: v3-2-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 41750f4 v3-2-testThis should apply the commit to the v3-2-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
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
2 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.
Recent successful full registry builds run 26-30 minutes (most recent: 29m49s, 26m13s, 20m43s). The 30-minute job timeout left near-zero headroom -- a pypistats slowdown or transient network blip during the ~86 sequential per-provider PyPI fetches in
extract_metadata.pywould race the timeout and silently fail the registry update.After #66100,
registry-build.ymlfires automatically on every wave-release dispatch, so this exposure is now hot.Fix
Bump
timeout-minutes: 30to45on thebuild-and-publish-registryjob. 45 minutes gives ~50% headroom over current full-build runtime without going so high that a genuinely stuck job sits around forever.Why not parallelise PyPI fetches instead
The real underlying cost is ~86 sequential
urllibcalls to pypistats.org and pypi.org inextract_metadata.py:fetch_pypi_downloads/fetch_pypi_dates. Parallelising those (e.g.,concurrent.futures.ThreadPoolExecutor) would actually shrink the build, not just give it more rope. That's a meaningful follow-up but lives indev/registry/extract_metadata.py, not in workflow YAML, and shouldn't block this trivial timeout bump that unblocks the immediate timeout race.Was generative AI tooling used to co-author this PR?