Skip to content

Update test-py6s-conda-install-scheduled.yml #85

Update test-py6s-conda-install-scheduled.yml

Update test-py6s-conda-install-scheduled.yml #85

Triggered via push August 4, 2024 07:41
Status Failure
Total duration 22s
Artifacts

test-py6s.yml

on: push
Matrix: Test Py6S
Fit to window
Zoom out
Zoom in

Annotations

23 errors and 2 warnings
Test Py6S (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.
Test Py6S (macos-latest, 3.9)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (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.
Test Py6S (macos-latest, 3.8)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (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.
Test Py6S (macos-latest, 3.7)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (macos-latest, 3.7)
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.
Test Py6S (ubuntu-latest, 3.7)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (ubuntu-latest, 3.7)
The operation was canceled.
Test Py6S (ubuntu-latest, 3.10)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (ubuntu-latest, 3.10)
The operation was canceled.
Test Py6S (ubuntu-latest, 3.9)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (ubuntu-latest, 3.9)
The operation was canceled.
Test Py6S (ubuntu-latest, 3.8)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (ubuntu-latest, 3.8)
The operation was canceled.
Test Py6S (windows-latest, 3.9)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (windows-latest, 3.9)
The operation was canceled.
Test Py6S (windows-latest, 3.7)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (windows-latest, 3.7)
The operation was canceled.
Test Py6S (windows-latest, 3.8)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (windows-latest, 3.8)
The operation was canceled.
Test Py6S (windows-latest, 3.10)
The job was canceled because "macos-latest_3_10" failed.
Test Py6S (windows-latest, 3.10)
The operation was canceled.
Test Py6S (macos-latest, 3.10)
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/
Test Py6S (macos-latest, 3.10)
The following actions uses Node.js version which is deprecated 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/