Skip to content
This repository was archived by the owner on Sep 10, 2025. It is now read-only.

Conversation

@mikekgfb
Copy link
Contributor

After #1305 removed dependence on torchvision, this PR drops torchvision installation as part of install_requirements.sh

After pytorch#1305 removed dependence on torchvision, this PR drops torchvision installation as part of install_requirements.sh
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 17, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchchat/1310

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

❌ 24 New Failures, 1 Cancelled Job

As of commit 2905670 with merge base 8c75754 (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOB - The following job was cancelled. Please retry:

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Meta Open Source bot. label Oct 17, 2024
Remove any remaining dependences on torchvision in install_requirements.sh
@Jack-Khuu
Copy link
Contributor

Looks like torchtune is looking for torchvision, but isn't being pulled it in as part of tune itself: https://github.com/pytorch/torchchat/actions/runs/11409026850/job/31753111489?pr=1310

@ebsmothers Is this intended behavior or have we imported tune improperly?

@mikekgfb
Copy link
Contributor Author

Never mind, we need torchvision for torchtune (and importing it transitively), so removing the only import of torchvision in model.py is not sufficient to be able to remove torchvision from the list of packages we depend on.

@mikekgfb mikekgfb closed this Oct 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants