Skip to content

MCP

MCP #21500

Triggered via pull request April 14, 2026 15:07
Status Cancelled
Total duration 14m 28s
Artifacts 3

build-test-distribute.yml

on: pull_request
config  /  prepare-config
20s
config / prepare-config
Matrix: prepare-image / linux-image-build-upload
Matrix: prepare-image / linux-vcpkg-build-upload
Matrix: prepare-image / windows-vcpkg-build-upload
prepare-image  /  always-success
2s
prepare-image / always-success
Matrix: macos-build-test / macos-build-test
versioning-and-release-url  /  versioning-and-release-url
4s
versioning-and-release-url / versioning-and-release-url
debug-config
3s
debug-config
Matrix: windows-build-test / windows-build-test
test-pip-build  /  setup
test-pip-build / setup
Matrix: linux-vcpkg-build-test / linux-vcpkg-build-test
Matrix: ubuntu-arm64-build-test / ubuntu-arm-build-test
Matrix: emscripten-build-test / emscripten-build
Matrix: ubuntu-x64-build-test / ubuntu-x64-build-test
update-win-version  /  update-win-version
update-win-version / update-win-version
Matrix: test-pip-build / manylinux-pip-build
Waiting for pending jobs
Matrix: test-pip-build / macos-pip-build
Waiting for pending jobs
test-pip-build  /  windows-pip-build
test-pip-build / windows-pip-build
create-nuget-package
0s
create-nuget-package
update-dev-documentation  /  update-documentation
update-dev-documentation / update-documentation
Matrix: test-pip-build / manylinux-pip-test
Waiting for pending jobs
test-pip-build  /  ...  /  update-documentation
test-pip-build / update-documentation / update-documentation
Matrix: test-pip-build / macos-pip-test
Waiting for pending jobs
Matrix: test-pip-build / windows-pip-test
Waiting for pending jobs
upload-distributions
0s
upload-distributions
test-pip-build  /  upload-to-release
test-pip-build / upload-to-release
windows-unity-test  /  Start unity instance
windows-unity-test / Start unity instance
collect-stats
24s
collect-stats
test-distribution  /  macos-test
test-distribution / macos-test
test-distribution  /  windows-test
test-distribution / windows-test
Matrix: test-distribution / linux-arm64-test
Waiting for pending jobs
Matrix: test-distribution / linux-x64-test
Waiting for pending jobs
test-pip-build  /  ...  /  setup
test-pip-build / post-release-test / setup
test-pip-build  /  delete-artifacts
test-pip-build / delete-artifacts
windows-unity-test  /  unity-nuget-test
windows-unity-test / unity-nuget-test
update-artifacts
12s
update-artifacts
Matrix: test-pip-build / post-release-test / pip-test-linux
Waiting for pending jobs
Matrix: test-pip-build / post-release-test / pip-test-macos
Waiting for pending jobs
Matrix: test-pip-build / post-release-test / pip-test-windows
Waiting for pending jobs
windows-unity-test  /  stop-instance
windows-unity-test / stop-instance
Fit to window
Zoom out
Zoom in

Annotations

35 errors and 49 warnings
macos-build-test / macos-build-test (arm64, Debug)
Process completed with exit code 1.
ubuntu-arm64-build-test / ubuntu-arm-build-test (ubuntu24, Release)
The operation was canceled.
ubuntu-arm64-build-test / ubuntu-arm-build-test (ubuntu22, Release)
The operation was canceled.
macos-build-test / macos-build-test (x64, Release)
The operation was canceled.
macos-build-test / macos-build-test (arm64, Release)
A task was canceled.
Build Test Distribute
The run was canceled by @adalisk-emikhaylov.
Build Test Distribute
The run was canceled by @adalisk-emikhaylov.
Build Test Distribute
The run was canceled by @adalisk-emikhaylov.
Build Test Distribute
The run was canceled by @adalisk-emikhaylov.
Build Test Distribute
The run was canceled by @adalisk-emikhaylov.
Build Test Distribute
The run was canceled by @adalisk-emikhaylov.
emscripten-build-test / emscripten-build (Singlethreaded)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-build-test / macos-build-test (arm64, Debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-build-test / macos-build-test (arm64, Debug)
llvm@18 18.1.8 is already installed and up-to-date. To reinstall 18.1.8, run: brew reinstall llvm@18
macos-build-test / macos-build-test (arm64, Debug)
llvm@14 was installed but not linked because llvm@18 is already installed. To link this version, run: brew link llvm@14
macos-build-test / macos-build-test (arm64, Debug)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
macos-build-test / macos-build-test (arm64, Debug)
openssl@3 3.6.1 is already installed and up-to-date. To reinstall 3.6.1, run: brew reinstall openssl@3
macos-build-test / macos-build-test (arm64, Debug)
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
macos-build-test / macos-build-test (arm64, Debug)
libtiff 4.7.1_1 is already installed and up-to-date. To reinstall 4.7.1_1, run: brew reinstall libtiff
macos-build-test / macos-build-test (arm64, Debug)
libpng 1.6.56 is already installed and up-to-date. To reinstall 1.6.56, run: brew reinstall libpng
macos-build-test / macos-build-test (arm64, Debug)
jpeg-turbo 3.1.4.1 is already installed and up-to-date. To reinstall 3.1.4.1, run: brew reinstall jpeg-turbo
macos-build-test / macos-build-test (arm64, Debug)
cmake 4.3.1 is already installed and up-to-date. To reinstall 4.3.1, run: brew reinstall cmake
emscripten-build-test / emscripten-build (Multithreaded-64Bit)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
emscripten-build-test / emscripten-build (Multithreaded)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-x64-build-test / ubuntu-x64-build-test (ubuntu22, Release, GCC, /usr/bin/g++-12, /usr/bin/gcc-12, 23, ON, ON)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-arm64-build-test / ubuntu-arm-build-test (ubuntu24, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, GCC 11, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-x64-build-test / ubuntu-x64-build-test (ubuntu24, Release, GCC, /usr/bin/g++-14, /usr/bin/gcc-14, 23, OFF, OFF)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-arm64-build-test / ubuntu-arm-build-test (ubuntu22, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, x64, Clang 20, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, GCC 11, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-x64-build-test / ubuntu-x64-build-test (ubuntu24, Release, GCC, /usr/bin/g++-13, /usr/bin/gcc-13, 23, ON, ON)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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/
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, arm64, Clang 20, false)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-build-test / windows-build-test (msvc-2019, Release, CMake, 2024.10.21, windows-2025, C:\Program Files\Microso...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-build-test / windows-build-test (msvc-2022, Debug, MSBuild, 2026.03.18, windows-2025, C:\Program Files\Microso...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-build-test / macos-build-test (x64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-build-test / macos-build-test (x64, Release)
llvm@14 was installed but not linked because llvm@18 is already installed. To link this version, run: brew link llvm@14
macos-build-test / macos-build-test (x64, Release)
pkgconf 2.5.1 is already installed and up-to-date. To reinstall 2.5.1, run: brew reinstall pkgconf
macos-build-test / macos-build-test (x64, Release)
openssl@3 3.6.1 is already installed and up-to-date. To reinstall 3.6.1, run: brew reinstall openssl@3
macos-build-test / macos-build-test (x64, Release)
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
macos-build-test / macos-build-test (x64, Release)
libzip 1.11.4_1 is already installed and up-to-date. To reinstall 1.11.4_1, run: brew reinstall libzip
macos-build-test / macos-build-test (x64, Release)
libtiff 4.7.1_1 is already installed and up-to-date. To reinstall 4.7.1_1, run: brew reinstall libtiff
macos-build-test / macos-build-test (x64, Release)
libpng 1.6.56 is already installed and up-to-date. To reinstall 1.6.56, run: brew reinstall libpng
macos-build-test / macos-build-test (x64, Release)
jpeg-turbo 3.1.4.1 is already installed and up-to-date. To reinstall 3.1.4.1, run: brew reinstall jpeg-turbo
macos-build-test / macos-build-test (x64, Release)
cmake 4.3.1 is already installed and up-to-date. To reinstall 4.3.1, run: brew reinstall cmake
macos-build-test / macos-build-test (arm64, Release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. 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-build-test / macos-build-test (arm64, Release)
llvm@18 18.1.8 is already installed and up-to-date. To reinstall 18.1.8, run: brew reinstall llvm@18
macos-build-test / macos-build-test (arm64, Release)
grep 3.12 is already installed and up-to-date. To reinstall 3.12, run: brew reinstall grep
macos-build-test / macos-build-test (arm64, Release)
make 4.4.1 is already installed and up-to-date. To reinstall 4.4.1, run: brew reinstall make
macos-build-test / macos-build-test (arm64, Release)
jsoncpp 1.9.6 is already installed and up-to-date. To reinstall 1.9.6, run: brew reinstall jsoncpp
macos-build-test / macos-build-test (arm64, Release)
jpeg-turbo 3.1.4.1 is already installed and up-to-date. To reinstall 3.1.4.1, run: brew reinstall jpeg-turbo
macos-build-test / macos-build-test (arm64, Release)
hidapi 0.15.0 is already installed and up-to-date. To reinstall 0.15.0, run: brew reinstall hidapi
macos-build-test / macos-build-test (arm64, Release)
glfw 3.4 is already installed and up-to-date. To reinstall 3.4, run: brew reinstall glfw
macos-build-test / macos-build-test (arm64, Release)
gdcm 3.2.2_1 is already installed and up-to-date. To reinstall 3.2.2_1, run: brew reinstall gdcm
macos-build-test / macos-build-test (arm64, Release)
fmt 12.1.0 is already installed and up-to-date. To reinstall 12.1.0, run: brew reinstall fmt
macos-build-test / macos-build-test (arm64, Release)
eigen 5.0.1 is already installed and up-to-date. To reinstall 5.0.1, run: brew reinstall eigen
macos-build-test / macos-build-test (arm64, Release)
cpr 1.14.2 is already installed and up-to-date. To reinstall 1.14.2, run: brew reinstall cpr
macos-build-test / macos-build-test (arm64, Release)
cmake 4.3.1 is already installed and up-to-date. To reinstall 4.3.1, run: brew reinstall cmake
macos-build-test / macos-build-test (arm64, Release)
boost 1.90.0_1 is already installed and up-to-date. To reinstall 1.90.0_1, run: brew reinstall boost

Artifacts

Produced during runtime
Name Size Digest
CBindings Expired
2.3 MB
sha256:ec7e1c2796d6cff60c4b776856c17fd725ed12701162e014b970cd3886c211ad
CsharpBindings Expired
3.95 MB
sha256:96148832857de38d7ed4c21925dea2c0e5a0d6b620c3a4d012c0acec84f29b07
time_log Expired
182 Bytes
sha256:d395720b9716de52477d94f6cda83586d77d2ab62052c3ea82a4f5686d6a32c6