Skip to content

test(hw): runtime device-tree overlay lifecycle for AD9081+ZCU102 and ADRV9009+ZC706 #88

test(hw): runtime device-tree overlay lifecycle for AD9081+ZCU102 and ADRV9009+ZC706

test(hw): runtime device-tree overlay lifecycle for AD9081+ZCU102 and ADRV9009+ZC706 #88

Triggered via pull request April 24, 2026 15:20
Status Success
Total duration 8m 14s
Artifacts 12

hardware-test.yml

on: pull_request
preflight
4s
preflight
Matrix: hw-coord
Matrix: hw-direct
PR Test Summary
21s
PR Test Summary
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
hw-direct (nuc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dorny/test-reporter@v1. 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/
hw-direct (bq)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dorny/test-reporter@v1. 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/
hw-coord (nuc)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dorny/test-reporter@v1. 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/
hw-coord (bq)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dorny/test-reporter@v1. 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/
hw-direct (mini2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dorny/test-reporter@v1. 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/
hw-coord (mini2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4, dorny/test-reporter@v1. 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/
PR Test Summary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
hw-coord-bq-output
89.7 KB
sha256:7733bb211ae030c02d4d04711ce7456a8345e94cc4e3675668584e080ec5b179
hw-coord-mini2-output
142 KB
sha256:3ebe4d3beee5746bc5e05490db45ec43ccbd13b20250eb4de599ba2df6f3fed3
hw-coord-nuc-output
554 Bytes
sha256:026f6b3b4b2595a6a1bb36ed7af51a15c471b80c3ce8c7ea7db3360f51164a4e
hw-direct-bq-output
89.6 KB
sha256:9b71d1c51f1b53fb48667fa0c35dcac6c5296096d85df689fa9405532ee64bd3
hw-direct-mini2-output
142 KB
sha256:0707cae72cc6430edfc86eb39156505cb565162f605e021feb81866ad0bd45af
hw-direct-nuc-output
541 Bytes
sha256:52ad8d122dad28e23e72bf0d35c67430f0440742792b3d7f1fa862db88c1ad48
junit-hw-coord-bq
489 Bytes
sha256:1909fa205cc3a7bf1bacdbcc80369d8ec5dbb54c5b3f52f3032a86cd7af6d60b
junit-hw-coord-mini2
519 Bytes
sha256:9fddce642f7839f33aa2bade147cb28424fb6f46493752f2426db1561acb24ec
junit-hw-coord-nuc
554 Bytes
sha256:026f6b3b4b2595a6a1bb36ed7af51a15c471b80c3ce8c7ea7db3360f51164a4e
junit-hw-direct-bq
457 Bytes
sha256:078be69a4ba342400bc81d3fded7485d279b9d03dabff17a2b3d066cecab45a5
junit-hw-direct-mini2
479 Bytes
sha256:b56905665cc3add4739783114cbed399160fe0dea81bda76c9ac1e653c5333c9
junit-hw-direct-nuc
541 Bytes
sha256:52ad8d122dad28e23e72bf0d35c67430f0440742792b3d7f1fa862db88c1ad48