End of class expedition summaries #953
Annotations
19 errors and 6 warnings
|
tests (ubuntu-latest | Python 3.12)
Canceling since a higher priority waiting request for CI-refs/pull/309/merge exists
|
|
tests (ubuntu-latest | Python 3.12)
ENOENT: no such file or directory, lstat '/home/runner/work/_temp/setup-micromamba/micromamba-shell'
|
|
tests (ubuntu-latest | Python 3.12)
The operation was canceled.
|
|
tests (ubuntu-latest | Python 3.10)
Canceling since a higher priority waiting request for CI-refs/pull/309/merge exists
|
|
tests (ubuntu-latest | Python 3.10)
ENOENT: no such file or directory, lstat '/home/runner/work/_temp/setup-micromamba/micromamba-shell'
|
|
tests (ubuntu-latest | Python 3.10)
The operation was canceled.
|
|
tests (macos-14 | Python 3.10)
Canceling since a higher priority waiting request for CI-refs/pull/309/merge exists
|
|
tests (macos-14 | Python 3.10)
ENOENT: no such file or directory, lstat '/Users/runner/work/_temp/setup-micromamba/micromamba-shell'
|
|
tests (macos-14 | Python 3.10)
The operation was canceled.
|
|
tests (macos-14 | Python 3.12)
Canceling since a higher priority waiting request for CI-refs/pull/309/merge exists
|
|
tests (macos-14 | Python 3.12)
ENOENT: no such file or directory, lstat '/Users/runner/work/_temp/setup-micromamba/micromamba-shell'
|
|
tests (macos-14 | Python 3.12)
The operation was canceled.
|
|
tests (windows-latest | Python 3.12)
Canceling since a higher priority waiting request for CI-refs/pull/309/merge exists
|
|
tests (windows-latest | Python 3.12)
Could not find micromamba activate ship in C:\Users\runneradmin\.bash_profile
|
|
tests (windows-latest | Python 3.12)
The operation was canceled.
|
|
tests (windows-latest | Python 3.10)
Canceling since a higher priority waiting request for CI-refs/pull/309/merge exists
|
|
tests (windows-latest | Python 3.10)
Could not find micromamba activate ship in C:\Users\runneradmin\.bash_profile
|
|
tests (windows-latest | Python 3.10)
The operation was canceled.
|
|
CI
Canceling since a higher priority waiting request for CI-refs/pull/309/merge exists
|
|
tests (ubuntu-latest | Python 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, mamba-org/setup-micromamba@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
tests (ubuntu-latest | Python 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, mamba-org/setup-micromamba@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
tests (macos-14 | Python 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, mamba-org/setup-micromamba@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
tests (macos-14 | Python 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, mamba-org/setup-micromamba@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
tests (windows-latest | Python 3.12)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, mamba-org/setup-micromamba@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
tests (windows-latest | Python 3.10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, mamba-org/setup-micromamba@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|