Skip to content

Add support for Banana Pi BPI-R4 #1183

Add support for Banana Pi BPI-R4

Add support for Banana Pi BPI-R4 #1183

Triggered via pull request April 10, 2026 06:37
Status Failure
Total duration 7m 56s
Artifacts

trigger.yml

on: pull_request
check-trigger
4s
check-trigger
unit-test  /  Build infix x86_64_minimal
2m 30s
unit-test / Build infix x86_64_minimal
build-x86_64  /  Build infix x86_64_minimal
5m 11s
build-x86_64 / Build infix x86_64_minimal
build-aarch64  /  Build infix aarch64_minimal
2m 38s
build-aarch64 / Build infix aarch64_minimal
build-arm  /  Build infix arm_minimal
4m 2s
build-arm / Build infix arm_minimal
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_minimal
Process completed with exit code 2.
build-arm / Build infix arm_minimal
Process completed with exit code 2.
build-x86_64 / Build infix x86_64_minimal
Process completed with exit code 2.
unit-test / Build infix x86_64_minimal
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. 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/
build-aarch64 / Build infix aarch64_minimal
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. 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/
build-arm / Build infix arm_minimal
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. 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/
build-x86_64 / Build infix x86_64_minimal
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. 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/