Skip to content

Support multiple forced ChatGPT workspace ids in config and requirements #25580

Support multiple forced ChatGPT workspace ids in config and requirements

Support multiple forced ChatGPT workspace ids in config and requirements #25580

Triggered via pull request April 15, 2026 21:12
Status Failure
Total duration 20m 58s
Artifacts 11

bazel.yml

on: pull_request
Matrix: clippy
Matrix: test
Matrix: verify-release-build
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 26 warnings
Bazel clippy on ubuntu-24.04 for x86_64-unknown-linux-gnu
Process completed with exit code 1.
Verify release build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Process completed with exit code 1.
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Process completed with exit code 1.
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-musl
Process completed with exit code 1.
Verify release build on macos-15-xlarge for aarch64-apple-darwin
Process completed with exit code 1.
Bazel clippy on macos-15-xlarge for aarch64-apple-darwin
Process completed with exit code 1.
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Process completed with exit code 1.
Local Bazel build on macos-15-xlarge for x86_64-apple-darwin
Process completed with exit code 1.
Verify release build on windows-latest for x86_64-pc-windows-gnullvm
Process completed with exit code 1.
Local Bazel build on windows-latest for x86_64-pc-windows-gnullvm
Process completed with exit code 1.
Bazel clippy on ubuntu-24.04 for x86_64-unknown-linux-gnu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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 clippy on ubuntu-24.04 for x86_64-unknown-linux-gnu
Failed to restore: Cache service responded with 400
Verify release build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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/
Verify release build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Failed to restore: Cache service responded with 400
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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/
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
Failed to restore: Cache service responded with 400
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-musl
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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/
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-musl
Failed to restore: Cache service responded with 400
Verify release build on macos-15-xlarge for aarch64-apple-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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/
Verify release build on macos-15-xlarge for aarch64-apple-darwin
Failed to restore: Cache service responded with 400
Bazel clippy on macos-15-xlarge for aarch64-apple-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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 clippy on macos-15-xlarge for aarch64-apple-darwin
Cache save failed.
Bazel clippy on macos-15-xlarge for aarch64-apple-darwin
Failed to restore: Cache service responded with 400
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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/
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Failed to restore: Cache service responded with 400
Bazel clippy on windows-latest for x86_64-pc-windows-gnullvm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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 clippy on windows-latest for x86_64-pc-windows-gnullvm
Failed to restore: Cache service responded with 400
Local Bazel build on macos-15-xlarge for x86_64-apple-darwin
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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/
Local Bazel build on macos-15-xlarge for x86_64-apple-darwin
Failed to restore: Cache service responded with 400
Verify release build on windows-latest for x86_64-pc-windows-gnullvm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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/
Verify release build on windows-latest for x86_64-pc-windows-gnullvm
Failed to restore: Cache service responded with 400
Local Bazel build on windows-latest for x86_64-pc-windows-gnullvm
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: bazelbuild/setup-bazelisk@b39c379c82683a5f25d34f0d062761f62693e0b2. 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/
Local Bazel build on windows-latest for x86_64-pc-windows-gnullvm
Failed to restore: Cache service responded with 400

Artifacts

Produced during runtime
Name Size Digest
bazel-execution-logs-clippy-aarch64-apple-darwin
8.02 MB
sha256:43da15cafaf825632b2cec4c0bf6749d1b66f2f3a4d323d34e8a238117eba27a
bazel-execution-logs-clippy-x86_64-pc-windows-gnullvm
3.83 MB
sha256:fb3ed85b0a844dda57cf5fe2726796ea8fdfc9c0fd473b9e5102c8040f94f2b4
bazel-execution-logs-clippy-x86_64-unknown-linux-gnu
6.33 MB
sha256:aa4889bd8ae00845f11430dc65b988bc4edce67a523ee45c19570f0051e32f78
bazel-execution-logs-test-aarch64-apple-darwin
8.09 MB
sha256:1a47662922a8d05ec34696994c94e3f9a8af71c19f8a8076706e0794cce8f51f
bazel-execution-logs-test-x86_64-apple-darwin
8.1 MB
sha256:fe4eb64b4cf9949fe685b876adee93e1e4d4d0eed46c66bae7df4b089be5300d
bazel-execution-logs-test-x86_64-pc-windows-gnullvm
4.73 MB
sha256:0b6e681cea58666ac85397604a0a0b08429d3adf47df2a2347d95a258d9aeea6
bazel-execution-logs-test-x86_64-unknown-linux-gnu
6.44 MB
sha256:4e7ded979665f352788c7f116f09ec39800e166beb28ad92c8936368886d3554
bazel-execution-logs-test-x86_64-unknown-linux-musl
6.42 MB
sha256:ff89b34c4a3291156e278abb9638262aeda8d56c17e3d57e5b15fb28ec3a927d
bazel-execution-logs-verify-release-build-aarch64-apple-darwin
7.91 MB
sha256:a657dbf3697dcb7f1d1956f8fbf2fbd4072a20627b32ad7eb22a6a5f7079261e
bazel-execution-logs-verify-release-build-x86_64-pc-windows-gnullvm
4.58 MB
sha256:8c90ae216e7f1e95613f855034001d109714cc64e46f0427cc6376bc0eaaaaf9
bazel-execution-logs-verify-release-build-x86_64-unknown-linux-gnu
6.24 MB
sha256:acce592bd5b0c2da5b5e857952de1f9e1153bd044f12f38d6b08684c300cb452