Merged
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/audio/4179
Note: Links to docs will display an error until the docs builds have been completed. This comment was automatically generated by Dr. CI and updates every 15 minutes. |
zxiiro
approved these changes
Feb 19, 2026
pytorchmergebot
pushed a commit
to pytorch/pytorch
that referenced
this pull request
Feb 19, 2026
Similar to: vision: pytorch/vision#9393 audio: pytorch/audio#4179 TLDR. Reason for using dual upload: [Sippy](https://developers.cloudflare.com/r2/data-migration/sippy/) on demand Cloudflare migration is enabled on our R2 account. I do see we are running installs from R2 successfully :[ https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607477#step:12:53](https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607477#step:12:53) Log: Collecting torch Downloading[ https://download-r2.pytorch.org/whl/nightly/cu129/torch-2.11.0.dev20260212%2Bcu129-cp314-cp314-manylinux_2_28_x86_64.whl.metadata](https://download-r2.pytorch.org/whl/nightly/cu129/torch-2.11.0.dev20260212%2Bcu129-cp314-cp314-manylinux_2_28_x86_64.whl.metadata) (29 kB) Collecting filelock (from torch) However when I naviagate to /whl/nightly/cu129 r2 folder in R2 account I don’t see any torch-2.11 files. Does it mean on every request files are being synced from AWS ? And hence either getting timeouts or 499 or 404 errors. From Sippy documentation once synced, files should be stored on our r2 folder. Example of a failure: https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607377 Pull Request resolved: #175352 Approved by: https://github.com/seemethere, https://github.com/malfet, https://github.com/zxiiro
norx1991
pushed a commit
to pytorch/pytorch
that referenced
this pull request
Feb 24, 2026
Similar to: vision: pytorch/vision#9393 audio: pytorch/audio#4179 TLDR. Reason for using dual upload: [Sippy](https://developers.cloudflare.com/r2/data-migration/sippy/) on demand Cloudflare migration is enabled on our R2 account. I do see we are running installs from R2 successfully :[ https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607477#step:12:53](https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607477#step:12:53) Log: Collecting torch Downloading[ https://download-r2.pytorch.org/whl/nightly/cu129/torch-2.11.0.dev20260212%2Bcu129-cp314-cp314-manylinux_2_28_x86_64.whl.metadata](https://download-r2.pytorch.org/whl/nightly/cu129/torch-2.11.0.dev20260212%2Bcu129-cp314-cp314-manylinux_2_28_x86_64.whl.metadata) (29 kB) Collecting filelock (from torch) However when I naviagate to /whl/nightly/cu129 r2 folder in R2 account I don’t see any torch-2.11 files. Does it mean on every request files are being synced from AWS ? And hence either getting timeouts or 499 or 404 errors. From Sippy documentation once synced, files should be stored on our r2 folder. Example of a failure: https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607377 Pull Request resolved: #175352 Approved by: https://github.com/seemethere, https://github.com/malfet, https://github.com/zxiiro
EmanueleCoradin
pushed a commit
to EmanueleCoradin/pytorch
that referenced
this pull request
Mar 30, 2026
Similar to: vision: pytorch/vision#9393 audio: pytorch/audio#4179 TLDR. Reason for using dual upload: [Sippy](https://developers.cloudflare.com/r2/data-migration/sippy/) on demand Cloudflare migration is enabled on our R2 account. I do see we are running installs from R2 successfully :[ https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607477#step:12:53](https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607477#step:12:53) Log: Collecting torch Downloading[ https://download-r2.pytorch.org/whl/nightly/cu129/torch-2.11.0.dev20260212%2Bcu129-cp314-cp314-manylinux_2_28_x86_64.whl.metadata](https://download-r2.pytorch.org/whl/nightly/cu129/torch-2.11.0.dev20260212%2Bcu129-cp314-cp314-manylinux_2_28_x86_64.whl.metadata) (29 kB) Collecting filelock (from torch) However when I naviagate to /whl/nightly/cu129 r2 folder in R2 account I don’t see any torch-2.11 files. Does it mean on every request files are being synced from AWS ? And hence either getting timeouts or 499 or 404 errors. From Sippy documentation once synced, files should be stored on our r2 folder. Example of a failure: https://github.com/meta-pytorch/torchcomms/actions/runs/21960287284/job/63435607377 Pull Request resolved: pytorch#175352 Approved by: https://github.com/seemethere, https://github.com/malfet, https://github.com/zxiiro
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.
This brings back dual upload