Skip to content

Conversation

@mergennachin
Copy link
Contributor

@mergennachin mergennachin commented Aug 4, 2025

For failing mosh test, https://hud.pytorch.org/hud/pytorch/executorch/main/1?per_page=50&name_filter=test-moshi-linux&mergeEphemeralLF=true

First, ./install_executorch.sh correctly installs PyTorch nightly:
Successfully installed torch-2.9.0.dev20250725+cpu

Then processes requirements-examples.txt which contains timm==1.0.7
When installing timm, pip detects a dependency conflict and downgrades PyTorch to 2.4.1

Let's try adding --extra-index-url

@pytorch-bot
Copy link

pytorch-bot bot commented Aug 4, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13110

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 3 Pending

As of commit 40d353e with merge base 4ce7078 (image):

NEW FAILURES - The following jobs have failed:

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Aug 4, 2025
@github-actions
Copy link

github-actions bot commented Aug 4, 2025

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

@kirklandsign
Copy link
Contributor

  ERROR: HTTP error 403 while getting https://download.pytorch.org/whl/nightly/nvidia_cuda_nvrtc_cu12-12.1.105-py3-none-manylinux1_x86_64.whl (from https://download.pytorch.org/whl/nightly/cpu/nvidia-cuda-nvrtc-cu12/)
ERROR: Could not install requirement nvidia-cuda-nvrtc-cu12==12.1.105 from https://download.pytorch.org/whl/nightly/nvidia_cuda_nvrtc_cu12-12.1.105-py3-none-manylinux1_x86_64.whl (from torch->timm==1.0.7->-r requirements-examples.txt (line 4)) because of HTTP error 403 Client Error: Forbidden for url: https://download.pytorch.org/whl/nightly/nvidia_cuda_nvrtc_cu12-12.1.105-py3-none-manylinux1_x86_64.whl for URL https://download.pytorch.org/whl/nightly/nvidia_cuda_nvrtc_cu12-12.1.105-py3-none-manylinux1_x86_64.whl (from https://download.pytorch.org/whl/nightly/cpu/nvidia-cuda-nvrtc-cu12/)

Not sure where is that URL https://download.pytorch.org/whl/nightly/nvidia_cuda_nvrtc_cu12-12.1.105-py3-none-manylinux1_x86_64.whl from. Should be https://download.pytorch.org/whl/cu121/nvidia_cuda_nvrtc_cu12-12.1.105-py3-none-manylinux1_x86_64.whl#sha256=339b385f50c309763ca65456ec75e17bbefcbbf2893f462cb8b90584cd27a1c2 ?

@mergennachin mergennachin force-pushed the mergennachin-patch-2 branch from eed5f35 to 0cb65de Compare August 8, 2025 20:29
@mergennachin mergennachin force-pushed the mergennachin-patch-2 branch from 0cb65de to 40d353e Compare August 8, 2025 20:42
@mergennachin mergennachin merged commit 50ffe44 into main Aug 8, 2025
232 of 235 checks passed
@mergennachin mergennachin deleted the mergennachin-patch-2 branch August 8, 2025 23:28
agrima1304 pushed a commit to agrima1304/executorch that referenced this pull request Aug 26, 2025
…rement-examples.txt (pytorch#13110)

For failing mosh test,
https://hud.pytorch.org/hud/pytorch/executorch/main/1?per_page=50&name_filter=test-moshi-linux&mergeEphemeralLF=true

First, ./install_executorch.sh correctly installs PyTorch nightly:
Successfully installed torch-2.9.0.dev20250725+cpu

Then processes requirements-examples.txt which contains timm==1.0.7
When installing timm, pip detects a dependency conflict and downgrades
PyTorch to 2.4.1

Let's try adding --extra-index-url
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants