-
Notifications
You must be signed in to change notification settings - Fork 55
Development environment fails to build basicsr #69
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
Could you please check if you have enough disk space when executing |
Disk space looks fine:
So today I tried to reproduce it, but I couldn't do it until I completely remove all the conda and pip cache, and force the basicsr lib to rebuild again. I am guessing that once you have a successful build, pip starts using it, so you don't go to its setup.py, and you don't run into the issue. So to reproduce, you need a clean state, I did:
I ended up removing the |
Okay, found another similar issue XPixelGroup/BasicSR#571, then it's possibly due to file path length limitation on windows:
|
Yes! that was it! Completely forgot about that 260 characters limitation on Windows. For reference:
Thank you @Nuullll! |
Uh oh!
There was an error while loading. Please reload this page.
Describe the bug
Trying to deploy a development environment in Meteor Lake.
Run into a problem was while running the following command: https://github.com/intel/AI-Playground/blob/main/readme.md?plain=1#L57
The root cause (I think) is that basicsr is using a legacy format of setup.py.
To solve that, I had to install dependencies following the recommended command in the log:
pip install --use-pep517
I think updating the docs might be needed.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Instructions on readme.md for development environment setup should work
Screenshots
Sharing logs:
Environment (please complete the following information):
Additional context
There are additional problems with the basicsr library, this is the first one I encountered
The text was updated successfully, but these errors were encountered: