Skip to content

ADD: Add progress to BatchJob response #719

ADD: Add progress to BatchJob response

ADD: Add progress to BatchJob response #719

Triggered via push March 13, 2026 20:02
Status Success
Total duration 14m 58s
Artifacts

build.yaml

on: push
build - macos-latest - clang++
7m 35s
build - macos-latest - clang++
build - windows-latest - msvc
14m 54s
build - windows-latest - msvc
Matrix: ubuntu
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build - macos-latest - clang++
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build - macos-latest - clang++
zstd 1.5.7_1 is already installed and up-to-date. To reinstall 1.5.7_1, run: brew reinstall zstd
build - macos-latest - clang++
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
build - macos-latest - clang++
openssl@3 3.6.1 is already installed and up-to-date. To reinstall 3.6.1, run: brew reinstall openssl@3
build - macos-latest - clang++
cmake 4.2.3 is already installed and up-to-date. To reinstall 4.2.3, run: brew reinstall cmake
build - ubuntu-latest - clang++
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build - ubuntu-latest - g++
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build - windows-latest - msvc
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/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/