Skip to content

executor: log reason when TiFlash RPC context is unavailable #6964

executor: log reason when TiFlash RPC context is unavailable

executor: log reason when TiFlash RPC context is unavailable #6964

Triggered via pull request May 11, 2026 11:12
Status Failure
Total duration 2m 9s
Artifacts

bazel-build-crossbuild.yml

on: pull_request
Matrix: Bazel Crossbuild
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 3 warnings
Bazel Crossbuild (ubuntu-24.04-arm)
Process completed with exit code 2.
Bazel Crossbuild (ubuntu-latest)
The strategy configuration was canceled because "master.ubuntu-24_04-arm" failed
Bazel Crossbuild (ubuntu-latest)
Process completed with exit code 2.
Bazel Crossbuild (macos-latest)
The strategy configuration was canceled because "master.ubuntu-24_04-arm" failed
Bazel Crossbuild (macos-latest)
The operation was canceled.
Bazel Crossbuild (ubuntu-24.04-arm)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazel-contrib/setup-bazel@0.16.0. 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/
Bazel Crossbuild (ubuntu-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazel-contrib/setup-bazel@0.16.0. 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/
Bazel Crossbuild (macos-latest)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazel-contrib/setup-bazel@0.16.0. 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/