Skip to content

Scheduled bazel cache update #571

Scheduled bazel cache update

Scheduled bazel cache update #571

Triggered via schedule June 14, 2026 12:48
Status Success
Total duration 15m 27s
Artifacts
update-cache  /  set-variables
6s
update-cache / set-variables
update-cache  /  update-cvd-test-bazel-cache
11m 6s
update-cache / update-cvd-test-bazel-cache
update-cache  /  update-bazel-cache-and-deploy-debian-package-arm64
12m 12s
update-cache / update-bazel-cache-and-deploy-debian-package-arm64
update-cache  /  update-bazel-cache-and-deploy-debian-package-amd64
15m 14s
update-cache / update-bazel-cache-and-deploy-debian-package-amd64
update-cache  /  deploy-docker-image-arm64
update-cache / deploy-docker-image-arm64
update-cache  /  deploy-gigabyte-ampere-installer-arm64
update-cache / deploy-gigabyte-ampere-installer-arm64
update-cache  /  deploy-docker-image-amd64
0s
update-cache / deploy-docker-image-amd64
update-cache  /  deploy-docker-manifest
0s
update-cache / deploy-docker-manifest
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
update-cache / update-cvd-test-bazel-cache
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
update-cache / update-bazel-cache-and-deploy-debian-package-arm64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
update-cache / update-bazel-cache-and-deploy-debian-package-arm64
The command [sudo apt-get remove -y azure-cli google-chrome-stable firefox powershell mono-devel libgl1-mesa-dri --fix-missing] failed to complete successfully. Proceeding...
update-cache / update-bazel-cache-and-deploy-debian-package-amd64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/