Skip to content

ci(health-check): maintain own buildkit cache per platform #31

ci(health-check): maintain own buildkit cache per platform

ci(health-check): maintain own buildkit cache per platform #31

Triggered via pull request April 21, 2026 01:02
Status Cancelled
Total duration 16m 21s
Artifacts

health-check-pr.yaml

on: pull_request
changed-files
7s
changed-files
require-label  /  require-label
3s
require-label / require-label
Matrix: health-check / docker-build
Fit to window
Zoom out
Zoom in

Annotations

8 errors, 4 warnings, and 1 notice
health-check / docker-build (nightly)
The run was canceled by @xmfcx.
health-check / docker-build (nightly)
The operation was canceled.
health-check / docker-build (main)
The run was canceled by @xmfcx.
health-check / docker-build (main)
The operation was canceled.
health-check / docker-build (main-arm64)
The run was canceled by @xmfcx.
health-check / docker-build (main-arm64)
The operation was canceled.
health-check-pr
The run was canceled by @xmfcx.
health-check-pr
The run was canceled by @xmfcx.
health-check / docker-build (nightly)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: reproducible-containers/buildkit-cache-dance@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/
health-check / docker-build (main)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: reproducible-containers/buildkit-cache-dance@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/
health-check / docker-build (main-arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: reproducible-containers/buildkit-cache-dance@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/
health-check / docker-build (main-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...
require-label / require-label
✅ The label is present: 'run:health-check'