Repository navigation
Enable nightly build to test 2.15 - #3983
Merged
Merged
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/tutorials/3983
Note: Links to docs will display an error until the docs builds have been completed. ⏳ No Failures, 2 PendingAs of commit 4ffceae with merge base c8ccbbf ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
atalman
added a commit
that referenced
this pull request
Oct 28, 2026
Follow-up to #3983: switch the 2.15 nightly/test build from cu130 to cu132. - `.jenkins/build.sh`: `--index-url https://download.pytorch.org/whl/test/cu130` -> `.../test/cu132` on the `USE_NIGHTLY` path and the commented reference line. `torch==2.15.0+cu132` is published for cp312 on x86_64 and aarch64 on the `test/cu132` index (it is also on the stable `cu132` index). The channel stays `test`; only the CUDA suffix changes. `bash -n .jenkins/build.sh` passes. The nightly job itself has not been run against cu132 yet, so the runner driver compatibility with CUDA 13.2 is unverified. AI assistance (Claude) was used for this change. Co-authored-by: Andrey Talman <atalman@users.noreply.github.com>
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
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.
Summary
Branch-cut step to start testing the 2.15 release in tutorials. Mirrors #3955 ("Enable nightly build to test 2.14").
.jenkins/build.sh: pintorch==2.15.0(from thetestchannel, cu130) on theUSE_NIGHTLYpath and the commented reference line; update the2.14 -> 2.15comment.No workflow change is needed: the
pushonmaintrigger in.github/workflows/build-tutorials-nightly.ymlis still enabled from the 2.13 cycle, so the nightly tutorials build already runs onmainand will pick up the 2.15 RC binaries with this pin..ci/docker/requirements.txtis intentionally left attorch==2.14— that gets bumped to 2.15 at the later "move to stable binaries" step, once 2.15 is released.Verification
torch==2.15.0+cu130is published on the test channel for cp312 on both x86_64 and aarch64. Resolving the exact install command frombuild.shagainst that index (uv pip install --dry-run) picks:bash -n .jenkins/build.shpasses. The nightly job itself has not run yet.The channel stays cu130, as in the 2.12 to 2.14 cycles. 2.15's default wheel is CUDA 13.2, and
2.15.0is also on the test channel for cu132 and cu134; moving the tutorials job to one of those is a separate change.Release playbook reference (2.14 -> 2.15)
requirements.txt)