Upgrade fro JupyterLab 4 #529
Triggered via pull request
November 26, 2023 17:44
Status
Failure
Total duration
29m 56s
Artifacts
–
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
build.yml
on: pull_request
build
1m 20s
Check Links
41s
Matrix: test-all-os
Matrix: test-backend-conda
Matrix: test-backend-mamba
test_isolated
0s
Annotations
10 errors and 5 warnings
Check Links
Process completed with exit code 1.
|
build
Process completed with exit code 127.
|
Test server with Conda Python 3.11
Process completed with exit code 1.
|
Test server with Conda Python 3.8
The job was canceled because "_3_11" failed.
|
Test server with Conda Python 3.8
The operation was canceled.
|
Test Conda Python 3.11 on macos-latest
Process completed with exit code 1.
|
Test Conda Python 3.11 on windows-latest
Process completed with exit code 1.
|
Test server with Mamba Python 3.8
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
|
Test server with Mamba Python 3.11
The job was canceled because "_3_8" failed.
|
Test server with Mamba Python 3.11
The operation was canceled.
|
Test Conda Python 3.11 on macos-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test Conda Python 3.11 on windows-latest
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Test server with Mamba Python 3.8
Mamba support is still experimental and can result in differently solved environments!
|
Test server with Mamba Python 3.8
UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:
Specifications:
- brotlipy -> python[version='3.10.*|3.4.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|>=3.12,<3.13.0a0|3.11.*|3.9.*|3.8.*|3.7.*',build='1_73_pypy|2_73_pypy|3_73_pypy|0_73_pypy|1_73_pypy|0_73_pypy|5_73_pypy|5_73_pypy|4_73_pypy|0_73_pypy']
- certifi -> python[version='3.10.*|3.7.*|3.8.*|3.9.*']
- cffi -> python[version='2.7.*|3.5.*|3.6.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|>=3.10,<3.11.0a0|>=3.9,<3.10.0a0|>=3.11,<3.12.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|>=3.6,<3.7.0a0|3.7.9|3.6.9|3.6.9|3.6.9|>=2.7,<2.8.0a0|3.6.9|>=3.5,<3.6.0a0|3.4.*|>=3.12,<3.13.0a0',build='1_73_pypy|2_73_pypy|3_73_pypy|0_73_pypy|1_73_pypy|0_73_pypy|5_73_pypy|5_73_pypy|4_73_pypy|0_73_pypy']
- conda-content-trust -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.5,<3.6.0a0|3.4.*']
- cryptography -> python[version='3.10.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|3.8.*|3.11.*|3.9.*|3.7.*|3.4.*|>=3.6|>=3.5|<=3.3',build='1_73_pypy|2_73_pypy|3_73_pypy|0_73_pypy|1_73_pypy|0_73_pypy|5_73_pypy|5_73_pypy|4_73_pypy|0_73_pypy']
- jsonpointer -> python[version='2.7.*|3.5.*|3.6.*|3.4.*']
- packaging -> python[version='>=3.0,<=3.9']
- zstandard -> python[version='3.10.*|3.11.*|3.6.12|3.6.12|3.7.10|3.7.10|3.7.12|3.8.12|3.9.10|3.7.9|3.6.9|3.6.9|3.6.9|3.6.9|>=3.5,<3.6.0a0|3.8.*|3.9.*|3.7.*',build='1_73_pypy|2_73_pypy|3_73_pypy|0_73_pypy|1_73_pypy|0_73_pypy|5_73_pypy|5_73_pypy|4_73_pypy|0_73_pypy']
Your python: python=3.11
If python is on the left-most side of the chain, that's the version you've asked for.
When python appears to the right, that indicates that the thing on the left is somehow
not available for the python version you are constrained to. Note that conda will not
change your python version to a different minor version unless you explicitly specify
that.
The following specifications were found to be incompatible with a past
explicit spec that is not an explicit spec in this operation (pip):
- mamba -> conda[version='4.6.*|4.6.*|4.7.*|>=4.7.12,<4.13.0a0|>=4.8,<23.4|>=4.8,<5|>=4.8,<23.9.0a0|>=4.8,<4.13.0a0|>=4.7.12,<4.8']
- mamba -> conda[version='>=4.8,<23.4'] -> setuptools[version='>=31.0.1|>=60.0.0']
- mamba -> python[version='>=3.10,<3.11.0a0'] -> pip
The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versions
Package libuuid conflicts for:
ruamel.yaml -> python[version='>=3.9,<3.10.0a0'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
pycparser -> python[version='2.7.*|>=3.4'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
wheel -> python[version='>=3.7'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
conda-content-trust -> python[version='>=3.5'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
python=3.11 -> libuuid[version='>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
conda[version='>=23.9.0'] -> python[version='>=3.10,<3.11.0a0'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
pyopenssl -> python[version='>=3.6'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
idna -> python[version='>=3.6'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
tqdm -> python[version='>=2.7'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
setuptools -> python[version='>=3.7'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
brotlipy -> python[version='>=3.10,<3.11.0a0'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
pip -> python[version='>=3.7'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
cffi -> python[version='>=3.9,<3.10.0a0'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a0']
pysocks -> python[version='>=3.8'] -> libuuid[version='>=1.0.3,<2.0a0|>=1.41.5,<2.0a0|>=2.32.1,<3.0a
|
Test server with Mamba Python 3.11
Mamba support is still experimental and can result in differently solved environments!
|