-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
CI broken #13082
Comments
In the rerun of the last working commit, the Installation dependencies took 1m40s in the failing case and 5m56s in the working one. Also in the working case there are multiple line A candidate is the latest release of https://github.com/jupyterlab/hatch-jupyter-builder |
Another candidate is hatchling v1.9.0: https://github.com/pypa/hatch/releases/tag/hatchling-v1.9.0 |
Some discrepancy seen with hatch-jupyter-builder. With version 0.5.3, pip install -e triggers: |
A fix proposal has been opened upstream: jupyterlab/hatch-jupyter-builder#68 |
Description
Since a day or so, the CI is broken.
The pathologic error seen are:
For JS tests when running
jlpm run build
For other tests
etc
See for example https://github.com/jupyterlab/jupyterlab/pull/12899/checks
By curiosity I ran a second time the JS tests on the last master commit that passed and it failed (you can see it by switching from attempt 1 and attempt 2): https://github.com/jupyterlab/jupyterlab/actions/runs/3035624109
This calls for an external impact - certainly related to the
pip install -e .[dev,test]
that does not runjlpm install
on the current folder.The text was updated successfully, but these errors were encountered: