-
Notifications
You must be signed in to change notification settings - Fork 541
./install_executorch.sh fails on pip due to dependency conflicts #9445
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
Comments
It seems like the CI does “./install_executorch.sh --use-pt-pinned-commit” which i assume is avoiding this by pulling a different pin. Not sure why the default is then “a random later” version? perhaps the other way round which is a pin by default, and --use-latest-pt if you want to explore... |
@Jack-Khuu who is the right PoC to resolve this? cc: @byjlw @mergennachin |
@jathu @larryliu0820 are the build/install PoC, not @Jack-Khuu @perheld - i'm actually trying to reproduce on my machine -- tried on both mac and linux, it is able to succeed to install_executorch.sh could you try again on the latest main? |
|
ok I looked at our run book that listed Jack for everything else |
I retried on latest and first got the problem but I was now able to fix it with a --clean
I did a run with For ref this was on We going to see if I could verify #9453 |
A spoke too soon I still get the error, I by a mixup put back the change per mention e.g set the version to NIGHTLY_VERSION = "dev20250310" in install_requirements.py And now with #9453 merged the workaround dont work anymore, I assume you have to "revert" all chnagewd back to dev20250310 |
I encountered a similar error when using the latest release v0.5.0. After running
|
Doesnt look like this is resolved yet cc next oncall @JacobSzwejbka |
@perheld we updated the version on main, please try again |
Works fine now. I was worried I was going insane and nobody else seeing this. 😅 |
Worked for me also |
🐛 Describe the bug
Cloning and setting up a new executorch as such:
Results in a dependency problem:
The only workaround I have right now is to change install_requirements.py
Versions
Running on latest greatest
cc @larryliu0820 @jathu @lucylq
The text was updated successfully, but these errors were encountered: