[CI] Support dev releases + derive index URL in full PyTorch test dispatch (#5781)#5815
Conversation
…ispatch Allow release_type == dev to dispatch full PyTorch tests (in addition to nightly), and stop hardcoding the nightly package index URL. The index URL is now resolved from the release type via a shared MULTI_ARCH_INDEX_URLS helper, so dev runs test against the dev index instead of nightly wheels. Closes #5781
|
Closes #5781. Stacked on #5813 (#5755 generalization) — base will be retargeted to Changes:
Note on cadence: this is a safe no-op for dev until a scheduled wrapper passes |
I'm confused by the git state here. This is still stacked on the users/ethanwee1/full-test-generalize-families branch but #5813 is closed. |
|
@ScottTodd you're right about the git state — this PR was stacked on the now-closed #5813 branch ( Closing in favor of #6449, which rebuilds the still-relevant half of #5781 as a small change against
The |
Summary
Lets
devreleases dispatch the full PyTorch test suite (in addition tonightly) and stops hardcoding the nightly package index URL, so dev runs test against the dev index rather than nightly wheels.Closes #5781.
What changed
build_tools/github_actions/multi_arch_release_urls.py(new): single source of truth for therelease_type -> multi-arch index URLmapping, with a small CLI that emits thepackage_index_urlGitHub Actions output.build_tools/github_actions/publish_pytorch_to_release_bucket.py: importsMULTI_ARCH_INDEX_URLSfrom the shared helper instead of defining its own copy (no behavior change)..github/workflows/multi_arch_release_linux_pytorch_wheels.yml:setup_full_test_matrixnow resolvespackage_index_urlfromrelease_typeand exposes it as an output.PACKAGE_INDEX_URLfrom that output instead of a hardcoded nightly literal.release_type == 'nightly'or'dev'.Cadence / safety
This is a safe no-op for dev until a scheduled wrapper passes
run_full_pytorch_tests=truefor dev releases — the dispatch only fires when that flag is set, so frequent on-demand dev builds will not trigger a full-test storm. Adding the dev schedule itself is a rockrel-side change (mirrors the existing nightly schedule).Test plan
multi_arch_release_urls_test.py(new)publish_pytorch_to_release_bucket_test.py(unchanged, still passes after refactor)configure_pytorch_test_matrix_test.py,workflow_dispatch_inputs_test.py