Skip to content

[CI] Fixing bazel shutdown #48225

[CI] Fixing bazel shutdown

[CI] Fixing bazel shutdown #48225

Triggered via pull request March 20, 2026 23:26
Status Failure
Total duration 14m 29s
Artifacts

ci.yml

on: pull_request
Matrix: runtime
Matrix: runtime_tracing
runtime_small
3m 35s
runtime_small
linux_x64_bazel  /  linux_x64_bazel
8m 57s
linux_x64_bazel / linux_x64_bazel
linux_x64_clang  /  linux_x64_clang
6m 14s
linux_x64_clang / linux_x64_clang
linux_x64_clang_asan  /  linux_x64_clang_asan
11m 52s
linux_x64_clang_asan / linux_x64_clang_asan
linux_x64_clang_ubsan  /  linux_x64_clang_ubsan
7m 10s
linux_x64_clang_ubsan / linux_x64_clang_ubsan
linux_arm64_clang  /  linux_arm64_clang
linux_arm64_clang / linux_arm64_clang
linux_x64_clang_byollvm  /  linux_x64_clang_byollvm
linux_x64_clang_byollvm / linux_x64_clang_byollvm
linux_x64_clang_debug  /  linux_x64_clang_debug
linux_x64_clang_debug / linux_x64_clang_debug
linux_x64_clang_tsan  /  linux_x64_clang_tsan
linux_x64_clang_tsan / linux_x64_clang_tsan
linux_x64_gcc  /  linux_x64_gcc
linux_x64_gcc / linux_x64_gcc
macos_arm64_clang  /  macos_arm64_clang
macos_arm64_clang / macos_arm64_clang
macos_x64_clang  /  macos_x64_clang
macos_x64_clang / macos_x64_clang
windows_x64_msvc  /  windows_x64_msvc
windows_x64_msvc / windows_x64_msvc
ci_summary  /  summary
2s
ci_summary / summary
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 6 warnings
linux_x64_bazel / linux_x64_bazel
Process completed with exit code 123.
ci_summary / summary
Process completed with exit code 1.
runtime_tracing :: macos-14 :: tracy
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
runtime_tracing :: macos-14 :: console
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
runtime :: macos-14
ninja 1.13.2 is already installed and up-to-date. To reinstall 1.13.2, run: brew reinstall ninja
runtime_tracing :: windows-2022 :: console
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. 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/
runtime_tracing :: windows-2022 :: tracy
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. 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/
runtime :: windows-2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ilammy/msvc-dev-cmd@0b201ec74fa43914dc39ae48a89fd1d8cb592756. 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/