-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
runtime_env not using the right env? #17086
Comments
script
|
this is using 1.4.1, checking master |
It's probably easier to check on the latest nightly rather than on master, because master requires you to manually include the wheel link in the runtime env. I'll check the latest nightly. I just ran it on 1.4.1 on Mac OS and got the following (after deleting unrelated messages):
The "invalid syntax" error continues forever, so it seems like Python 2 is being used somehow? |
error on master
|
Just tested on the nightly. If you make the installs non-concurrent like this:
then it succeeds. However, if you use the original script, the concurrent installs cause an issue:
There's probably an issue with how we're using FileLock to prevent concurrent installs. |
According to https://stackoverflow.com/questions/58210335/is-conda-install-a-thread-safe-operation conda installs should not be run concurrently, even if you are installing different conda environments. Currently the lock we use is per-env; I'll change it to a global lock for all conda installs and see if that fixes the problem. |
The text was updated successfully, but these errors were encountered: