[codex-analytics] add token usage metadata #23542
Annotations
8 errors and 19 warnings
|
Bazel clippy 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.
|
|
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Process completed with exit code 1.
|
|
Bazel clippy 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.
|
|
Local Bazel build on ubuntu-24.04 for x86_64-unknown-linux-gnu
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 windows-latest for x86_64-pc-windows-gnullvm
Process completed with exit code 1.
|
|
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@v3. 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
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@v3. 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
|
|
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@v3. 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
Cache save failed.
|
|
Local Bazel build on macos-15-xlarge for aarch64-apple-darwin
Failed to restore: Cache service responded with 400
|
|
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@v3. 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
|
|
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@v3. 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
|
|
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@v3. 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
Cache save failed.
|
|
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 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@v3. 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
|
|
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@v3. 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
Cache save failed.
|
|
Bazel clippy 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
|
7.81 MB |
sha256:2173d0e5acf6c6c95b41a6c8bbc55a60f5d3105cb14f24f1b54432e055d5ffee
|
|
|
bazel-execution-logs-clippy-x86_64-pc-windows-gnullvm
|
3.82 MB |
sha256:27bfec13218ddca6b2124a6b33c4d7436dbb8f8a9fe12588eb116017aca6d587
|
|
|
bazel-execution-logs-clippy-x86_64-unknown-linux-gnu
|
6.13 MB |
sha256:836c9af81b36c2ffda107b64e800b1934bcf111e89c76699f055ee48725cef3c
|
|
|
bazel-execution-logs-test-aarch64-apple-darwin
|
7.94 MB |
sha256:7e44c8d1f3a43ee14718727f8f69d54ef00743241d61d2a175f3f6b44c2cc2ac
|
|
|
bazel-execution-logs-test-x86_64-apple-darwin
|
7.85 MB |
sha256:bb6af126f5cebc75b676afc91931bffac6314241e23e6c1cd88b62f7f3ba6035
|
|
|
bazel-execution-logs-test-x86_64-pc-windows-gnullvm
|
4.62 MB |
sha256:a276632bf37fda9820dd46550f10140f42a55f5e9e076787e3adda24bcc4a118
|
|
|
bazel-execution-logs-test-x86_64-unknown-linux-gnu
|
6.2 MB |
sha256:ab70b5a8db73be25078650591803e72d9d62541bb549ed1e80c178cfc8a554ef
|
|
|
bazel-execution-logs-test-x86_64-unknown-linux-musl
|
6.21 MB |
sha256:b7a69b03bc609238a7e258b5c2ea9bf6a1cfe1b6e77c2eec009de314bdf3a3d4
|
|