Skip to content

Bump postcss from 8.4.6 to 8.4.31 #523

Bump postcss from 8.4.6 to 8.4.31

Bump postcss from 8.4.6 to 8.4.31 #523

Triggered via pull request October 8, 2023 08:40
Status Failure
Total duration 1h 0m 29s
Artifacts

build.yml

on: pull_request
All tests on Ubuntu Mamba Python 3.9
47m 20s
All tests on Ubuntu Mamba Python 3.9
Matrix: test-all-os
Matrix: test-backend-conda
Matrix: test-backend-mamba
Fit to window
Zoom out
Zoom in

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 Conda Python 3.7 on macos-latest
Process completed with exit code 1.
Test server with Mamba Python 3.7
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
Test server with Mamba Python 3.8
The operation was canceled.
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 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/
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 server with Mamba Python 3.7
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='1_73_pypy|4_73_pypy|5_73_pypy|0_73_pypy|1_73_pypy|0_73_pypy|5_73_pypy|3_73_pypy|2_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.*',build='1_73_pypy|4_73_pypy|5_73_pypy|0_73_pypy|1_73_pypy|0_73_pypy|5_73_pypy|3_73_pypy|2_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|4_73_pypy|5_73_pypy|0_73_pypy|1_73_pypy|0_73_pypy|5_73_pypy|3_73_pypy|2_73_pypy|0_73_pypy'] - jsonpointer -> python[version='2.7.*|3.5.*|3.6.*|3.4.*'] - packaging -> python[version='>=3.0,<=3.9'] - six -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|3.4.*|>=3.9,<3.10.0a0|>=3.5,<3.6.0a0'] - 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|4_73_pypy|5_73_pypy|0_73_pypy|1_73_pypy|0_73_pypy|5_73_pypy|3_73_pypy|2_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 lzo conflicts for: libarchive -> lzo[version='>=2.10,<3.0a0'] libmamba -> libarchive[version='>=3.5.2,<3.6.0a0'] -> lzo[version='>=2.10,<3.0a0'] conda-package-handling -> libarchive[version='>=3.3.3'] -> lzo[version='>=2.10,<3.0a0'] mamba -> libarchive[version='>=3.5.2,<3.6.0a0'] -> lzo[version='>=2.10,<3.0a0'] Package libarchive conflicts for: libmamba -> libarchive[version='>=3.3.3,<3.6.0a0|>=3.5.1,<3.6.0a0|>=3.5.2,<3.6.0a0|>=3.6.2,<3.7.0a0|>=3.6.1,<3.7.0a0|>=3.4.2,<3.5.0a0'] conda-package-handling -> libarchive[version='>=3.3.3'] libmambapy -> libmamba==1.0.0=h9eff5f0_2 -> libarchive[version='>=3.4.2,<3.5.0a0|>=3.5.2,<3.6.0a0|>=3.6.2,<3.7.0a0|>=3.6.1,<3.7.0a0'] conda[version='>=23.5.2'] -> conda-package-handling[version='>=1.3.0'] -> libarchive[version='>=3.3.3'] conda-package-handling -> python-libarchive-c -> libarchive mamba -> libarchive[version='>=3.3.3,<3.6.0a0|>=3.5.1,<3.6.0a0|>=3.5.2,<3.6.0a0'] Package zlib conflicts for: libmamba -> libarchive[version='>=3.5.2,<3.6.0a0'] -> zlib[version='>=1.2.11,<1.3.0a0|>=1.2.12,<1.3.0a0|>=1.2.13,<1.3.0a0'] pip -> python[version='>=3.7'] -> zlib[version='1.2.*|1.2.11|>=1.2.11,<1.3.0a0|>=1.2.13,<1.3.0a0|>=1.2.12,<1.3.0a0|1.2.8|1.2.11.*'] six -> python -> zlib[version='1.2.*|1.2.11|>=1.2.11,<1.3.0a0|1.2.8|1.2.11.*|>=1.2.13,<1.3.0a0|>=1.2.12,<1.3.0a0'] idna -> python[version='>=3.6'] -> zlib[version='1.2.*|1.2.11|>=1.2.11,<1.3.0a0|1.
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!
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|1_73_pypy|2_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy|0_73_pypy'] - 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|2_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|5_73_pypy|1_73_pypy|0_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='0_73_pypy|1_73_pypy|2_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|5_73_pypy|1_73_pypy|0_73_pypy|0_73_pypy'] - jsonpointer -> python[version='2.7.*|3.5.*|3.6.*|3.4.*'] - packaging -> python[version='>=3.0,<=3.9'] - six -> python[version='2.7.*|3.5.*|3.6.*|>=2.7,<2.8.0a0|>=3.6,<3.7.0a0|>=3.8,<3.9.0a0|>=3.7,<3.8.0a0|3.4.*|>=3.9,<3.10.0a0|>=3.5,<3.6.0a0'] - 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|2_73_pypy|3_73_pypy|4_73_pypy|5_73_pypy|5_73_pypy|1_73_pypy|0_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 _libgcc_mutex conflicts for: libxml2 -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] ruamel.yaml -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] pcre2 -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] zstd -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] libgomp -> _libgcc_mutex==0.1[build='main|conda_forge'] lz4-c -> libgcc-ng[version='>=9.3.0'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] ncurses -> libgcc-ng[version='>=10.3.0'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] c-ares -> libgcc-ng[version='>=9.4.0'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] libgcc-ng -> _libgcc_mutex[version='*|0.1|0.1',build='main|main|conda_forge'] cryptography -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] krb5 -> libgcc-ng[version='>=10.3.0'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] zlib -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] reproc -> libgcc-ng[version='>=9.4.0'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] yaml-cpp -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1',build='main|main|conda_forge'] python=3.11 -> libgcc-ng[version='>=12'] -> _libgcc_mutex[version='*|0.1'
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/