Skip to content

Installation

Installation #199

Triggered via schedule September 9, 2024 03:02
Status Failure
Total duration 35s
Artifacts

installation.yml

on: schedule
Matrix: build-conda
Matrix: build-pip
Fit to window
Zoom out
Zoom in

Annotations

27 errors and 8 warnings
build-conda (macos-latest, 3.9)
No installed conda 'base' environment found at !If you are using this action in a self-hosted runner that already provides its own Miniconda installation, please specify its location with a `CONDA` environment variable. If you want us to download and install Miniconda or Miniforge for you, add `miniconda-version: "latest"` or `miniforge-version: "latest"`, respectively, to the parameters for this action.
build-conda (macos-latest, 3.8)
No installed conda 'base' environment found at !If you are using this action in a self-hosted runner that already provides its own Miniconda installation, please specify its location with a `CONDA` environment variable. If you want us to download and install Miniconda or Miniforge for you, add `miniconda-version: "latest"` or `miniforge-version: "latest"`, respectively, to the parameters for this action.
build-conda (macos-latest, 3.10)
The job was canceled because "macos-latest_3_9" failed.
build-conda (macos-latest, 3.10)
No installed conda 'base' environment found at !If you are using this action in a self-hosted runner that already provides its own Miniconda installation, please specify its location with a `CONDA` environment variable. If you want us to download and install Miniconda or Miniforge for you, add `miniconda-version: "latest"` or `miniforge-version: "latest"`, respectively, to the parameters for this action.
build-conda (macos-latest, 3.11)
The job was canceled because "macos-latest_3_9" failed.
build-conda (macos-latest, 3.11)
No installed conda 'base' environment found at !If you are using this action in a self-hosted runner that already provides its own Miniconda installation, please specify its location with a `CONDA` environment variable. If you want us to download and install Miniconda or Miniforge for you, add `miniconda-version: "latest"` or `miniforge-version: "latest"`, respectively, to the parameters for this action.
build-conda (ubuntu-latest, 3.10)
The job was canceled because "macos-latest_3_9" failed.
build-conda (ubuntu-latest, 3.10)
The operation was canceled.
build-conda (ubuntu-latest, 3.11)
The job was canceled because "macos-latest_3_9" failed.
build-conda (ubuntu-latest, 3.11)
The operation was canceled.
build-conda (ubuntu-latest, 3.8)
The job was canceled because "macos-latest_3_9" failed.
build-conda (ubuntu-latest, 3.8)
The operation was canceled.
build-conda (windows-latest, 3.9)
The job was canceled because "macos-latest_3_9" failed.
build-conda (windows-latest, 3.9)
The operation was canceled.
build-conda (windows-latest, 3.11)
The job was canceled because "macos-latest_3_9" failed.
build-conda (windows-latest, 3.11)
The operation was canceled.
build-conda (ubuntu-latest, 3.9)
The job was canceled because "macos-latest_3_9" failed.
build-conda (ubuntu-latest, 3.9)
The operation was canceled.
build-conda (windows-latest, 3.8)
The job was canceled because "macos-latest_3_9" failed.
build-conda (windows-latest, 3.8)
The operation was canceled.
build-conda (windows-latest, 3.10)
The job was canceled because "macos-latest_3_9" failed.
build-conda (windows-latest, 3.10)
The operation was canceled.
build-pip (ubuntu-latest, 3.11)
Process completed with exit code 1.
build-pip (ubuntu-latest, 3.9)
The job was canceled because "ubuntu-latest_3_11" failed.
build-pip (ubuntu-latest, 3.9)
Process completed with exit code 1.
build-pip (ubuntu-latest, 3.10)
The job was canceled because "ubuntu-latest_3_11" failed.
build-pip (ubuntu-latest, 3.10)
Process completed with exit code 1.
build-conda (macos-latest, 3.9)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-conda (macos-latest, 3.9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, conda-incubator/setup-miniconda@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-conda (macos-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-conda (macos-latest, 3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, conda-incubator/setup-miniconda@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-pip (ubuntu-latest, 3.8)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-pip (ubuntu-latest, 3.8)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build-pip (ubuntu-latest, 3.11)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-pip (ubuntu-latest, 3.11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-python@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/