Skip to content

Merge pull request #1449 from kernelkit/kernel-upgrade-399f2582-484c-… #1136

Merge pull request #1449 from kernelkit/kernel-upgrade-399f2582-484c-…

Merge pull request #1449 from kernelkit/kernel-upgrade-399f2582-484c-… #1136

Triggered via push March 17, 2026 07:18
Status Failure
Total duration 5m 40s
Artifacts

trigger.yml

on: push
check-trigger
4s
check-trigger
unit-test  /  Build infix x86_64
1m 15s
unit-test / Build infix x86_64
build-x86_64  /  Build infix x86_64
3m 12s
build-x86_64 / Build infix x86_64
build-aarch64  /  Build infix aarch64
3m 7s
build-aarch64 / Build infix aarch64
build-arm  /  Build infix arm
4m 10s
build-arm / Build infix arm
test-run-x86_64  /  test
test-run-x86_64 / test
test-publish-x86_64  /  Upload Latest Build
test-publish-x86_64 / Upload Latest Build
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
build-aarch64 / Build infix aarch64
Process completed with exit code 2.
build-x86_64 / Build infix x86_64
Process completed with exit code 2.
build-arm / Build infix arm
Process completed with exit code 2.
unit-test / Build infix x86_64
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/checkout@v4. 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/
build-aarch64 / Build infix aarch64
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/checkout@v4. 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/
build-x86_64 / Build infix x86_64
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/checkout@v4. 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/
build-arm / Build infix arm
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/checkout@v4. 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/