Skip to content

Move CPP header guard in status_led #1812

Move CPP header guard in status_led

Move CPP header guard in status_led #1812

Triggered via pull request March 13, 2026 14:25
Status Success
Total duration 5m 56s
Artifacts

bazel_build.yml

on: pull_request
other-bazel-checks
23s
other-bazel-checks
Matrix: bazel-build-check
Fit to window
Zoom out
Zoom in

Annotations

21 warnings
other-bazel-checks
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/setup-python@v5, bazel-contrib/setup-bazel@0.9.0. 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/
other-bazel-checks
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at Object.<anonymous> (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.9.0/dist/node_modules/@actions/cache/lib/cache.js:175:1) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.9.0/dist/node_modules/@actions/cache/lib/cache.js:28:1)
other-bazel-checks
Error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved. at Object.<anonymous> (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.9.0/dist/node_modules/@actions/cache/lib/cache.js:175:1) at Generator.next (<anonymous>) at fulfilled (/home/runner/work/_actions/bazel-contrib/setup-bazel/0.9.0/dist/node_modules/@actions/cache/lib/cache.js:28:1)
other-bazel-checks
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Vh60aQAAAADf+uYn10VQSp+9EKjcvUcWQ0hJMzBFREdFMDIwOABFZGdl
other-bazel-checks
Failed to restore: Cache service responded with 400
other-bazel-checks
Failed to restore: Cache service responded with 400
other-bazel-checks
Failed to restore: Cache service responded with 400
bazel-build-check (ubuntu-latest)
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/setup-python@v5, bazel-contrib/setup-bazel@0.9.0. 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/
bazel-build-check (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Ox+0aQAAAAAaxxDRV/kASogdN9e0SaThUEhYMzFFREdFMDYxMwBFZGdl
bazel-build-check (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Oh+0aQAAAADSFe2qCTgfQpLfxzj7vZ7JUEhYMzFFREdFMDYxMwBFZGdl
bazel-build-check (ubuntu-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0OR+0aQAAAABzCqfbuSa4TKcsdxTLQbc+UEhYMzFFREdFMDYxMwBFZGdl
bazel-build-check (ubuntu-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (ubuntu-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (ubuntu-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (macos-latest)
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/setup-python@v5, bazel-contrib/setup-bazel@0.9.0. 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/
bazel-build-check (macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0nx+0aQAAAAA6rOCV2+cXQZh8IYzRk6PgUEhMMzBFREdFMDEyMgBFZGdl
bazel-build-check (macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0nh+0aQAAAAC5khqtjCg8S4NH4DneE7O5UEhMMzBFREdFMDEyMgBFZGdl
bazel-build-check (macos-latest)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0mh+0aQAAAAAikHQQxspdQaZ5bK/moOzOUEhMMzBFREdFMDEyMgBFZGdl
bazel-build-check (macos-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (macos-latest)
Failed to restore: Cache service responded with 400
bazel-build-check (macos-latest)
Failed to restore: Cache service responded with 400