[BUG] - conda-store user journey tests failing with ImportError: cannot import name 'CalledProcessError' from 'conda_lock._vendor.poetry.utils._compat' #1095
Description
Describe the bug
As part of our tests in Nebari, we run the conda-store user journey tests. Recently, these started failing with the following message:
_______ ERROR collecting tests/_internal/plugins/lock/test_conda_lock.py _______
ImportError while importing test module '/home/runnerx/actions-runner/_work/nebari/nebari/conda-store/conda-store-server/tests/_internal/plugins/lock/test_conda_lock.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/home/runnerx/miniconda3/envs/conda-store-server-dev/lib/python3.11/importlib/__init__.py:126: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
tests/_internal/plugins/lock/test_conda_lock.py:9: in <module>
from conda_lock._vendor.poetry.utils._compat import CalledProcessError
E ImportError: cannot import name 'CalledProcessError' from 'conda_lock._vendor.poetry.utils._compat' (/home/runnerx/miniconda3/envs/conda-store-server-dev/lib/python3.11/site-packages/conda_lock/_vendor/poetry/utils/_compat.py)
You can see the full logs here. These were previously passing, as shown in these logs.
Looking at the logs, the relevant difference I see is:
Collecting conda-lock>=1.0.5 (from conda-store-server==2025.2.3.dev0)
- Downloading conda_lock-2.5.7-py3-none-any.whl.metadata (18 kB)
+ Downloading conda_lock-3.0.0-py3-none-any.whl.metadata (19 kB)Expected behavior
User journey tests should not be failing at the import level.
How to Reproduce the problem?
Run the user journey tests with conda-lock==3.0.0 installed.
Output
No response
Versions and dependencies used.
No response
Anything else?
No response