Skip to content

Tests

Tests #548

Triggered via schedule February 12, 2024 13:19
Status Failure
Total duration 1m 15s
Artifacts

tests.yaml

on: schedule
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 20 warnings
Build (3.6 | ubuntu-latest)
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
Build (3.8 | ubuntu-latest)
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
Build (3.7 | ubuntu-latest)
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
Build (3.9 | ubuntu-latest)
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
Build (3.10 | ubuntu-latest)
The process '/usr/share/miniconda/condabin/conda' failed with exit code 1
Build (3.6 | ubuntu-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v1, conda-incubator/setup-miniconda@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build (3.6 | ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (3.6 | ubuntu-latest)
Mamba support is still experimental and can result in differently solved environments!
Build (3.6 | ubuntu-latest)
LibMambaUnsatisfiableError: Encountered problems while solving: - package mamba-1.0.0-py311h51e3938_2 requires conda >=4.8,<23.4, but none of the providers can be installed Could not solve for environment specs The following packages are incompatible ├─ conda 23.11.0 is installable with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ └─ conda 23.11.0, which can be installed; ├─ mamba is installable with the potential options │ ├─ mamba [0.0.10|0.0.7|0.0.8|0.0.9|0.1.0] would require │ │ └─ python >=2.7,<2.8.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ mamba [0.1.2|0.10.0|...|1.0.0] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ mamba [0.10.0|0.11.1|...|1.0.0] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ ├─ mamba [0.18.1|0.18.2|...|1.0.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ └─ mamba 1.0.0 would require │ └─ conda >=4.8,<23.4 with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0], which can be installed (as previously explained); │ ├─ conda [22.11.1|22.9.0|23.1.0|23.3.0|23.3.1] conflicts with any installable versions previously reported; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [4.10.0|4.10.1|...|4.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ └─ conda [4.8.0|4.8.1|4.8.2|4.8.3|4.8.4] would require │ └─ python >=2.7,<2.8.0a0 , which can be installed; └─ pin-1 is not installable because it requires └─ python 3.11.* , which conflicts with any installable versions previously reported. Pins seem to be involved in the conflict. Currently pinned specs: - python 3.11.* (labeled as 'pin-1')
Build (3.8 | ubuntu-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v1, conda-incubator/setup-miniconda@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build (3.8 | ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (3.8 | ubuntu-latest)
Mamba support is still experimental and can result in differently solved environments!
Build (3.8 | ubuntu-latest)
LibMambaUnsatisfiableError: Encountered problems while solving: - package mamba-1.0.0-py311h51e3938_2 requires conda >=4.8,<23.4, but none of the providers can be installed Could not solve for environment specs The following packages are incompatible ├─ conda 23.11.0 is installable with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ └─ conda 23.11.0, which can be installed; ├─ mamba is installable with the potential options │ ├─ mamba [0.0.10|0.0.7|0.0.8|0.0.9|0.1.0] would require │ │ └─ python >=2.7,<2.8.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ mamba [0.1.2|0.10.0|...|1.0.0] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ mamba [0.10.0|0.11.1|...|1.0.0] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ ├─ mamba [0.18.1|0.18.2|...|1.0.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ └─ mamba 1.0.0 would require │ └─ conda >=4.8,<23.4 with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0], which can be installed (as previously explained); │ ├─ conda [22.11.1|22.9.0|23.1.0|23.3.0|23.3.1] conflicts with any installable versions previously reported; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [4.10.0|4.10.1|...|4.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ └─ conda [4.8.0|4.8.1|4.8.2|4.8.3|4.8.4] would require │ └─ python >=2.7,<2.8.0a0 , which can be installed; └─ pin-1 is not installable because it requires └─ python 3.11.* , which conflicts with any installable versions previously reported. Pins seem to be involved in the conflict. Currently pinned specs: - python 3.11.* (labeled as 'pin-1')
Build (3.7 | ubuntu-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v1, conda-incubator/setup-miniconda@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build (3.7 | ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (3.7 | ubuntu-latest)
Mamba support is still experimental and can result in differently solved environments!
Build (3.7 | ubuntu-latest)
LibMambaUnsatisfiableError: Encountered problems while solving: - package mamba-1.0.0-py311h51e3938_2 requires conda >=4.8,<23.4, but none of the providers can be installed Could not solve for environment specs The following packages are incompatible ├─ conda 23.11.0 is installable with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ └─ conda 23.11.0, which can be installed; ├─ mamba is installable with the potential options │ ├─ mamba [0.0.10|0.0.7|0.0.8|0.0.9|0.1.0] would require │ │ └─ python >=2.7,<2.8.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ mamba [0.1.2|0.10.0|...|1.0.0] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ mamba [0.10.0|0.11.1|...|1.0.0] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ ├─ mamba [0.18.1|0.18.2|...|1.0.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ └─ mamba 1.0.0 would require │ └─ conda >=4.8,<23.4 with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0], which can be installed (as previously explained); │ ├─ conda [22.11.1|22.9.0|23.1.0|23.3.0|23.3.1] conflicts with any installable versions previously reported; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [4.10.0|4.10.1|...|4.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ └─ conda [4.8.0|4.8.1|4.8.2|4.8.3|4.8.4] would require │ └─ python >=2.7,<2.8.0a0 , which can be installed; └─ pin-1 is not installable because it requires └─ python 3.11.* , which conflicts with any installable versions previously reported. Pins seem to be involved in the conflict. Currently pinned specs: - python 3.11.* (labeled as 'pin-1')
Build (3.9 | ubuntu-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v1, conda-incubator/setup-miniconda@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build (3.9 | ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (3.9 | ubuntu-latest)
Mamba support is still experimental and can result in differently solved environments!
Build (3.9 | ubuntu-latest)
LibMambaUnsatisfiableError: Encountered problems while solving: - package mamba-1.0.0-py311h51e3938_2 requires conda >=4.8,<23.4, but none of the providers can be installed Could not solve for environment specs The following packages are incompatible ├─ conda 23.11.0 is installable with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ └─ conda 23.11.0, which can be installed; ├─ mamba is installable with the potential options │ ├─ mamba [0.0.10|0.0.7|0.0.8|0.0.9|0.1.0] would require │ │ └─ python >=2.7,<2.8.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ mamba [0.1.2|0.10.0|...|1.0.0] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ mamba [0.10.0|0.11.1|...|1.0.0] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ ├─ mamba [0.18.1|0.18.2|...|1.0.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ └─ mamba 1.0.0 would require │ └─ conda >=4.8,<23.4 with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0], which can be installed (as previously explained); │ ├─ conda [22.11.1|22.9.0|23.1.0|23.3.0|23.3.1] conflicts with any installable versions previously reported; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [4.10.0|4.10.1|...|4.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ └─ conda [4.8.0|4.8.1|4.8.2|4.8.3|4.8.4] would require │ └─ python >=2.7,<2.8.0a0 , which can be installed; └─ pin-1 is not installable because it requires └─ python 3.11.* , which conflicts with any installable versions previously reported. Pins seem to be involved in the conflict. Currently pinned specs: - python 3.11.* (labeled as 'pin-1')
Build (3.10 | ubuntu-latest)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v1, conda-incubator/setup-miniconda@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build (3.10 | ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (3.10 | ubuntu-latest)
Mamba support is still experimental and can result in differently solved environments!
Build (3.10 | ubuntu-latest)
LibMambaUnsatisfiableError: Encountered problems while solving: - package mamba-1.0.0-py311h51e3938_2 requires conda >=4.8,<23.4, but none of the providers can be installed Could not solve for environment specs The following packages are incompatible ├─ conda 23.11.0 is installable with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ └─ conda 23.11.0, which can be installed; ├─ mamba is installable with the potential options │ ├─ mamba [0.0.10|0.0.7|0.0.8|0.0.9|0.1.0] would require │ │ └─ python >=2.7,<2.8.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ ├─ mamba [0.0.10|0.0.7|...|0.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ mamba [0.1.2|0.10.0|...|1.0.0] would require │ │ └─ python >=3.8,<3.9.0a0 , which can be installed; │ ├─ mamba [0.10.0|0.11.1|...|1.0.0] would require │ │ └─ python >=3.9,<3.10.0a0 , which can be installed; │ ├─ mamba [0.18.1|0.18.2|...|1.0.0] would require │ │ └─ python >=3.10,<3.11.0a0 , which can be installed; │ └─ mamba 1.0.0 would require │ └─ conda >=4.8,<23.4 with the potential options │ ├─ conda [22.11.0|22.11.1|...|4.14.0], which can be installed (as previously explained); │ ├─ conda [22.11.1|22.9.0|23.1.0|23.3.0|23.3.1] conflicts with any installable versions previously reported; │ ├─ conda [22.11.0|22.11.1|...|4.9.2] would require │ │ └─ python >=3.7,<3.8.0a0 , which can be installed; │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [22.11.0|22.11.1|...|4.9.2], which can be installed (as previously explained); │ ├─ conda [4.10.0|4.10.1|...|4.9.2] would require │ │ └─ python >=3.6,<3.7.0a0 , which can be installed; │ └─ conda [4.8.0|4.8.1|4.8.2|4.8.3|4.8.4] would require │ └─ python >=2.7,<2.8.0a0 , which can be installed; └─ pin-1 is not installable because it requires └─ python 3.11.* , which conflicts with any installable versions previously reported. Pins seem to be involved in the conflict. Currently pinned specs: - python 3.11.* (labeled as 'pin-1')