Bump @babel/traverse from 7.17.0 to 7.23.2 (#208) #526
fcollonvalbuild.yml
on: push
All tests on Ubuntu Mamba Python 3.9
43m 47s
Matrix: test-all-os
Matrix: test-backend-conda
Matrix: test-backend-mamba
Annotations
7 errors and 15 warnings
|
Test server with Conda Python 3.9
Process completed with exit code 1.
|
|
Test server with Conda Python 3.7
The operation was canceled.
|
|
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.7
The operation was canceled.
|
|
Test Conda Python 3.7 on macos-latest
Process completed with exit code 1.
|
|
All tests on Ubuntu Mamba Python 3.9
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
|
|
Test Conda Python 3.7 on windows-latest
The operation was canceled.
|
|
Test server with Conda Python 3.9
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Test server with Conda Python 3.7
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Test server with Mamba Python 3.8
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
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.11.*|3.9.*|3.8.*|3.7.*',build='0_73_pypy|1_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|2_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.*',build='0_73_pypy|1_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|2_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='0_73_pypy|1_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|2_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='0_73_pypy|1_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|5_73_pypy|0_73_pypy|0_73_pypy|1_73_pypy|2_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 (conda):
- 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 _libgcc_mutex conflicts for:
pycosat -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
lz4-c -> libgcc-ng[version='>=9.3.0'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
libgomp -> _libgcc_mutex==0.1[build='main|conda_forge']
libsolv -> libgcc-ng[version='>=10.3.0'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
libarchive -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
libnghttp2 -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
libmamba -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
_openmp_mutex -> _libgcc_mutex==0.1[build='main|conda_forge']
libcurl -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
conda-package-handling -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
libgcc-ng -> _libgcc_mutex[version='*|0.1|0.1',build='main|conda_forge|main']
cryptography -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
yaml-cpp -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
libedit -> libgcc-ng[version='>=7.5.0'] -> _libgcc_mutex[version='*|0.1|0.1',build='main|conda_forge|main']
libssh2 -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|conda_forge|main']
readline -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0
|
|
Test server with Mamba Python 3.7
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Test server with Mamba Python 3.7
Mamba support is still experimental and can result in differently solved environments!
|
|
Test Conda Python 3.7 on macos-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Test Conda Python 3.7 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/
|
|
All tests on Ubuntu Mamba Python 3.9
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
All tests on Ubuntu Mamba Python 3.9
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/
|
|
All tests on Ubuntu Mamba Python 3.9
Mamba support is still experimental and can result in differently solved environments!
|
|
All tests on Ubuntu Mamba Python 3.9
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.11.*|3.9.*|3.8.*|3.7.*',build='0_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|1_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.*',build='0_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|1_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='0_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|1_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='0_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|1_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 (setuptools):
- 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 _libgcc_mutex conflicts for:
zstandard -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
reproc -> libgcc-ng[version='>=9.4.0'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
mamba -> libgcc-ng[version='>=9.4.0'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
cryptography -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
bzip2 -> libgcc-ng[version='>=9.3.0'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
ncurses -> libgcc-ng[version='>=10.3.0'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
libsolv -> libgcc-ng[version='>=10.3.0'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
icu -> libgcc-ng[version='>=10.3.0'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
libarchive -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
sqlite -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
zlib -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
conda-package-handling -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
lz4-c -> libgcc-ng[version='>=9.3.0'] -> _libgcc_mutex[version='*|0.1',build='conda_forge|main|main']
xz -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1|0.1',build='conda_forge|main|main']
ruamel.yaml -> libgcc-ng[version='>=12'] -> _libgcc_mutex[versi
|
|
Test Conda Python 3.7 on windows-latest
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Test Conda Python 3.7 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/
|