-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pip install torchvision
started failing
#4689
Comments
Thanks for the report @zpapakipos
We keep having issues with this 0.2.2... #4665 #4085 #4076 Do you happen to have changed anything related to opencv or ffmpeg in Augly recently? |
@NicolasHug we haven't changed our dependencies in three months, and our workflow hasn't been updated since last month |
Thanks for the update. I'm not sure what can be causing this TBH. We're in the process of releasing torchvision 0.11 as we speak. I'm hoping that the issue will magically disappear once the binaries are up on PyPI, which should be by the end of the day. EDIT: actually, they're already up https://pypi.org/project/torchvision/#history |
sounds good, I'll comment on here once we determine if the issue is still persisting or not! [edit] just checked and it seems like we're still pulling 0.2.2 from a workflow 3hrs ago: https://github.com/facebookresearch/AugLy/runs/3967331383?check_suite_focus=true do you think it's worth specifying the specific torchvision version you mentioned instead of going by defaults? |
yes it'd be interesting to try with the constraint torchvision>=0.11 also maybe try a more verbose version of |
So I looked into what was the difference between our workflows from 3 days ago (which passed) and our newer ones that failed -- the difference was that in our newer workflows GitHub started to download python 3.10 as opposed to 3.9.7. For some reason, it seems as if newer versions of [edit] feel free to close this issue if it is expected behavior for newer torch versions to be unavailable in 3.10! our use case is unblocked for now :) |
Thanks for investigating, indeed 3.10 isn't supported by pytorch yet :) |
🐛 Describe the bug
We have a GitHub action workflow in our library AugLy which runs automatically when a PR is updated. This workflow suddenly started failing on the line
pip install pyre-check pytest torchvision
. See here a run of the workflow which succeeded 2 days ago & here the one that fails today. Looking at the error message & output (pasted below), this seems to be due to an error while installing torchvision.Full error message:
Versions
I can't run this since it's through a GitHub workflow.
The text was updated successfully, but these errors were encountered: