Skip to content

Faster unit selection sorting. #5628

Faster unit selection sorting.

Faster unit selection sorting. #5628

Triggered via pull request May 14, 2026 10:47
Status Failure
Total duration 9m 22s
Artifacts

all-tests.yml

on: pull_request
Matrix: run
Fit to window
Zoom out
Zoom in

Annotations

7 errors, 6 warnings, and 2 notices
ubuntu-latest Python 3.10
Process completed with exit code 1.
ubuntu-latest Python 3.13
Process completed with exit code 1.
macos-latest Python 3.13
Process completed with exit code 1.
macos-latest Python 3.10
Process completed with exit code 1.
macos-latest Python 3.10
WARNING: Cache entry deserialization failed, entry ignored
windows-latest Python 3.10
Process completed with exit code 1.
windows-latest Python 3.13
Process completed with exit code 1.
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: tj-actions/changed-files@v46.0.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
ubuntu-latest Python 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46.0.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
macos-latest Python 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46.0.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
macos-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: tj-actions/changed-files@v46.0.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
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: tj-actions/changed-files@v46.0.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
windows-latest Python 3.13
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: tj-actions/changed-files@v46.0.1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
windows-latest Python 3.10
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026
windows-latest Python 3.13
NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by May 12, 2026