Build Test Distribute #21517
build-test-distribute.yml
on: schedule
config
/
prepare-config
21s
Matrix: prepare-image / linux-image-build-upload
Matrix: prepare-image / linux-vcpkg-build-upload
Matrix: prepare-image / windows-vcpkg-build-upload
Matrix: macos-build-test / macos-build-test
versioning-and-release-url
/
versioning-and-release-url
5s
debug-config
2s
Matrix: windows-build-test / windows-build-test
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
Matrix: test-pip-build / manylinux-pip-build
Waiting for pending jobs
Matrix: test-pip-build / macos-pip-build
Waiting for pending jobs
update-dev-documentation
/
update-documentation
4m 33s
Matrix: test-pip-build / manylinux-pip-test
Waiting for pending jobs
test-pip-build
/
...
/
update-documentation
Matrix: test-pip-build / macos-pip-test
Waiting for pending jobs
Matrix: test-pip-build / windows-pip-test
Waiting for pending jobs
test-distribution
/
macos-test
4m 19s
test-distribution
/
windows-test
3m 10s
Matrix: test-distribution / linux-arm64-test
Matrix: test-distribution / linux-x64-test
test-pip-build
/
delete-artifacts
update-artifacts
23s
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
6s
Annotations
21 errors and 162 warnings
|
macos-build-test / macos-build-test (arm64, Release)
gettext 0.26_1 is already installed
To upgrade to 1.0, run:
brew upgrade gettext
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, Clang 20, true)
Process completed with exit code 1.
|
|
macos-build-test / macos-build-test (arm64, Debug)
Process completed with exit code 1.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, arm64, GCC 11, true)
Process completed with exit code 1.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, GCC 11, true)
Process completed with exit code 1.
|
|
windows-build-test / windows-build-test (msvc-2019, Debug, MSBuild, 2024.10.21, windows-2025, C:\Program Files\Microso...
Process completed with exit code 1.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu24, Release, Clang, /usr/bin/clang++-18, /usr/bin/clang-18, 23, ON, ...
Process completed with exit code 1.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu24, Debug, Clang, /usr/bin/clang++-18, /usr/bin/clang-18, 23, ON, OFF)
Process completed with exit code 1.
|
|
windows-build-test / windows-build-test (msvc-2019, Release, MSBuild, 2024.10.21, windows-2025, C:\Program Files\Micro...
Process completed with exit code 1.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, x64, GCC 11, true)
Process completed with exit code 1.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, Clang 20, true)
Process completed with exit code 1.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu22, Debug, Clang, /usr/bin/clang++-14, /usr/bin/clang-14, 20, ON, OFF)
Process completed with exit code 1.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu24, Debug, GCC, /usr/bin/g++-14, /usr/bin/gcc-14, 23, OFF, OFF)
Process completed with exit code 1.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu24, Debug, GCC, /usr/bin/g++-13, /usr/bin/gcc-13, 23, ON, OFF)
Process completed with exit code 1.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu22, Release, Clang, /usr/bin/clang++-14, /usr/bin/clang-14, 20, ON, ...
Process completed with exit code 1.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, GCC 11, true)
Process completed with exit code 1.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu22, Debug, GCC, /usr/bin/g++-12, /usr/bin/gcc-12, 23, ON, OFF)
Process completed with exit code 1.
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, MSBuild, 2026.03.18, windows-2025, C:\Program Files\Microso...
Process completed with exit code 1.
|
|
windows-build-test / windows-build-test (msvc-2022, Release, MSBuild, 2026.03.18, windows-2025, C:\Program Files\Micro...
Process completed with exit code 1.
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...
Process completed with exit code 1.
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...
Process completed with exit code 1.
|
|
config / prepare-config
'before' field is missing in event payload - changes will be detected from last commit
|
|
config / prepare-config
'before' field is missing in event payload - changes will be detected from last commit
|
|
config / prepare-config
'before' field is missing in event payload - changes will be detected from last commit
|
|
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/
|
|
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/
|
|
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/
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
macos-build-test / macos-build-test (arm64, Release)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
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
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, arm64, Clang 20, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, arm64, Clang 20, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, arm64, Clang 20, true)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, Clang 20, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Clang 20, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, Clang 20, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, Clang 20, true)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
macos-build-test / macos-build-test (arm64, Debug)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
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)
gettext 1.0 is already installed and up-to-date.
To reinstall 1.0, run:
brew reinstall gettext
|
|
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.2 is already installed and up-to-date.
To reinstall 3.6.2, 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.57 is already installed and up-to-date.
To reinstall 1.6.57, 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
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, arm64, GCC 11, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, GCC 11, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, arm64, GCC 11, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, arm64, GCC 11, true)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, GCC 11, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, GCC 11, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, arm64, GCC 11, true)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
windows-build-test / windows-build-test (msvc-2019, Debug, MSBuild, 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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Debug, MSBuild, 2024.10.21, windows-2025, C:\Program Files\Microso...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2019, Debug, MSBuild, 2024.10.21, windows-2025, C:\Program Files\Microso...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu24, Release, Clang, /usr/bin/clang++-18, /usr/bin/clang-18, 23, ON, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Clang, /usr/bin/clang++-18, /usr/bin/clang-18, 23, ON, ...
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu24, Debug, Clang, /usr/bin/clang++-18, /usr/bin/clang-18, 23, ON, OFF)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Debug, Clang, /usr/bin/clang++-18, /usr/bin/clang-18, 23, ON, OFF)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
windows-build-test / windows-build-test (msvc-2019, Release, MSBuild, 2024.10.21, windows-2025, C:\Program Files\Micro...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, MSBuild, 2024.10.21, windows-2025, C:\Program Files\Micro...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2019, Release, MSBuild, 2024.10.21, windows-2025, C:\Program Files\Micro...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, x64, Clang 20, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, x64, Clang 20, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, x64, Clang 20, true)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
windows-build-test / windows-build-test (msvc-2019, Debug, CMake, 2024.10.21, windows-2025, C:\Program Files\Microsoft...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Debug, CMake, 2024.10.21, windows-2025, C:\Program Files\Microsoft...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2019, Debug, CMake, 2024.10.21, windows-2025, C:\Program Files\Microsoft...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2019, Release, CMake, 2024.10.21, windows-2025, C:\Program Files\Microso...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, x64, GCC 11, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, GCC 11, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, x64, GCC 11, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Release, x64, GCC 11, true)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, Clang 20, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Clang 20, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, Clang 20, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, Clang 20, true)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu22, Debug, Clang, /usr/bin/clang++-14, /usr/bin/clang-14, 20, ON, OFF)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Debug, Clang, /usr/bin/clang++-14, /usr/bin/clang-14, 20, ON, OFF)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu24, Debug, 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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Debug, GCC, /usr/bin/g++-14, /usr/bin/gcc-14, 23, OFF, OFF)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu24, Debug, GCC, /usr/bin/g++-13, /usr/bin/gcc-13, 23, ON, OFF)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Debug, GCC, /usr/bin/g++-13, /usr/bin/gcc-13, 23, ON, OFF)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu22, Release, Clang, /usr/bin/clang++-14, /usr/bin/clang-14, 20, ON, ...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Clang, /usr/bin/clang++-14, /usr/bin/clang-14, 20, ON, ...
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, GCC 11, true)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, GCC 11, true)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
linux-vcpkg-build-test / linux-vcpkg-build-test (Debug, x64, GCC 11, true)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
ubuntu-x64-build-test / ubuntu-x64-build-test (ubuntu22, Debug, GCC, /usr/bin/g++-12, /usr/bin/gcc-12, 23, ON, OFF)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, Debug, GCC, /usr/bin/g++-12, /usr/bin/gcc-12, 23, ON, OFF)
No files were found with the provided path: time_log/. No artifacts will be uploaded.
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, MSBuild, 2026.03.18, windows-2025, C:\Program Files\Microso...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
|
|
windows-build-test / windows-build-test (msvc-2022, Release, MSBuild, 2026.03.18, windows-2025, C:\Program Files\Micro...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, MSBuild, 2026.03.18, windows-2025, C:\Program Files\Micro...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2022, Release, MSBuild, 2026.03.18, windows-2025, C:\Program Files\Micro...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L543
XML comment has badly formed XML -- 'The character(s) '(' cannot be used at this location.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L543
XML comment has badly formed XML -- 'Missing equals sign between attribute and attribute value.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L543
XML comment has badly formed XML -- 'Missing equals sign between attribute and attribute value.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L543
XML comment has badly formed XML -- 'Whitespace is not allowed at this location.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L112
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L108
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'minDistSq'.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L107
XML comment has badly formed XML -- 'The character(s) '(' cannot be used at this location.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L107
XML comment has badly formed XML -- 'Missing equals sign between attribute and attribute value.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L107
XML comment has badly formed XML -- 'Missing equals sign between attribute and attribute value.'
|
|
windows-build-test / windows-build-test (msvc-2022, Debug, CMake, 2026.03.18, windows-2025, C:\Program Files\Microsoft...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L107
XML comment has badly formed XML -- 'Whitespace is not allowed at this location.'
|
|
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L543
XML comment has badly formed XML -- 'The character(s) '(' cannot be used at this location.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L543
XML comment has badly formed XML -- 'Missing equals sign between attribute and attribute value.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L543
XML comment has badly formed XML -- 'Missing equals sign between attribute and attribute value.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L543
XML comment has badly formed XML -- 'Whitespace is not allowed at this location.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L112
XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L108
XML comment has badly formed XML -- 'End tag 'summary' does not match the start tag 'minDistSq'.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L107
XML comment has badly formed XML -- 'The character(s) '(' cannot be used at this location.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L107
XML comment has badly formed XML -- 'Missing equals sign between attribute and attribute value.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L107
XML comment has badly formed XML -- 'Missing equals sign between attribute and attribute value.'
|
|
windows-build-test / windows-build-test (msvc-2022, Release, CMake, 2026.03.18, windows-2025, C:\Program Files\Microso...:
source/MRDotNet2/src/MRCMesh/MRFastWindingNumber.cs#L107
XML comment has badly formed XML -- 'Whitespace is not allowed at this location.'
|
|
|
|
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/cache@v4, actions/upload-artifact@v4, aws-actions/configure-aws-credentials@e3dd6a429d7300a6a4c196c26e071d42e0343502. 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)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
macos-build-test / macos-build-test (x64, Release)
Unexpected input(s) 'mrbind', valid inputs are ['autotest_data_s3_url', 'build_config', 'pytest_args', 'smoke', 'test_artifacts_path', 'upload_test_artifacts']
|
|
macos-build-test / macos-build-test (x64, 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 (x64, Release)
gettext 1.0 is already installed and up-to-date.
To reinstall 1.0, run:
brew reinstall gettext
|
|
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
|
|
test-distribution / macos-test
llvm@14 was installed but not linked because llvm@18 is already installed.
To link this version, run:
brew link llvm@14
|
|
test-distribution / macos-test
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
test-distribution / macos-test
openssl@3 3.6.1 is already installed and up-to-date.
To reinstall 3.6.1, run:
brew reinstall openssl@3
|
|
test-distribution / macos-test
ninja 1.13.2 is already installed and up-to-date.
To reinstall 1.13.2, run:
brew reinstall ninja
|
|
test-distribution / macos-test
libzip 1.11.4_1 is already installed and up-to-date.
To reinstall 1.11.4_1, run:
brew reinstall libzip
|
|
test-distribution / macos-test
libtiff 4.7.1_1 is already installed and up-to-date.
To reinstall 4.7.1_1, run:
brew reinstall libtiff
|
|
test-distribution / macos-test
libpng 1.6.56 is already installed and up-to-date.
To reinstall 1.6.56, run:
brew reinstall libpng
|
|
test-distribution / macos-test
jpeg-turbo 3.1.4.1 is already installed and up-to-date.
To reinstall 3.1.4.1, run:
brew reinstall jpeg-turbo
|
|
test-distribution / macos-test
cmake 4.3.1 is already installed and up-to-date.
To reinstall 4.3.1, run:
brew reinstall cmake
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
time_log
Expired
|
182 Bytes |
sha256:ccdef0f2389cdc4ec558a422c90f949cd80a9da126973e30c78123f433a0ac9a
|
|