Skip to content

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

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 #87

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

hardware-test.yml

on: pull_request
preflight
4s
preflight
Matrix: hw-coord
Matrix: hw-direct
PR Test Summary
16s
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-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 (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:b1475ac51c81c737a2c69111f5bebf6eec760f2ea12eac55ccbbc61fc2797ca5
hw-coord-mini2-output
142 KB
sha256:f2bf0207232d7cf242801f62a6c12b63347c63eb7c229700b9db3acbe8fa5801
hw-coord-nuc-output
555 Bytes
sha256:dc02886e082161780f8689ab63aecd75f55a55360d132c2861bcac0a89f150ba
hw-direct-bq-output
89.7 KB
sha256:49d1b243289c4a58c5d6528a18e235fecd6a2c69f6c31ab8d33ded16922c4570
hw-direct-mini2-output
142 KB
sha256:bdd46a9d6d5f916a817092c52f1bc4eb6077a6ab5bfdd894e2fc1cd04ec57633
hw-direct-nuc-output
542 Bytes
sha256:34849fd24f75b8f88efdaffe4bc69538f32b6dfc00e904a1ce1935cbdaebc905
junit-hw-coord-bq
491 Bytes
sha256:79c2079da3db4d3e3e66f85f577b53381e98db91da413c6094d4ec6e7e9ad0b4
junit-hw-coord-mini2
518 Bytes
sha256:afca3be2e07a882a9b7d41782007ef28bbb47b6810e82f28682b9362106d3a1e
junit-hw-coord-nuc
555 Bytes
sha256:dc02886e082161780f8689ab63aecd75f55a55360d132c2861bcac0a89f150ba
junit-hw-direct-bq
459 Bytes
sha256:eb1afce1b80c30a75bddd4f2a9ea6a4042a29a60fb7002ecd18653d4b8e6bba9
junit-hw-direct-mini2
478 Bytes
sha256:02453de1d93f035bb2547d703dbc219f6b4a41d1a0e5bffaa0c90882aeec2a21
junit-hw-direct-nuc
542 Bytes
sha256:34849fd24f75b8f88efdaffe4bc69538f32b6dfc00e904a1ce1935cbdaebc905