Skip to content

platform: acp_7_x: add a comment to test push is working or not #23293

platform: acp_7_x: add a comment to test push is working or not

platform: acp_7_x: add a comment to test push is working or not #23293

Triggered via push June 3, 2026 05:51
Status Cancelled
Total duration 12m 27s
Artifacts 13

zephyr.yml

on: push
Matrix: build-linux
Matrix: build-windows
compare-linux-win
24s
compare-linux-win
Fit to window
Zoom out
Zoom in

Annotations

20 errors, 28 warnings, and 8 notices
build-windows (mnfst, tgl)
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
build-windows (-d, mnfst, lnl)
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
build-windows (-d, mnfst, lnl)
The operation was canceled.
build-windows (mnfst, imx8 imx8x)
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
build-windows (mnfst, imx8 imx8x)
No files were found with the provided path: D:\a\sof\sof/workspace/build-sof-staging D:\a\sof\sof/workspace/**/compile_commands.json. No artifacts will be uploaded.
build-windows (mnfst, imx8 imx8x)
The operation was canceled.
build-windows (mnfst, lnl)
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
build-windows (mnfst, lnl)
The operation was canceled.
build-windows (mnfst, tgl-h)
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
build-windows (mnfst, tgl-h)
No files were found with the provided path: D:\a\sof\sof/workspace/build-sof-staging D:\a\sof\sof/workspace/**/compile_commands.json. No artifacts will be uploaded.
build-windows (mnfst, tgl-h)
The operation was canceled.
build-windows (mnfst, mtl)
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
build-windows (mnfst, mtl)
No files were found with the provided path: D:\a\sof\sof/workspace/build-sof-staging D:\a\sof\sof/workspace/**/compile_commands.json. No artifacts will be uploaded.
build-windows (mnfst, mtl)
The operation was canceled.
build-windows (mnfst, ptl)
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
build-windows (mnfst, ptl)
The operation was canceled.
build-windows (mnfst, imx8m imx8ulp)
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
build-windows (mnfst, imx8m imx8ulp)
The operation was canceled.
Zephyr
Canceling since a higher priority waiting request for Zephyr-push-refs/heads/origin/amd-acp7b-stable exists
compare-linux-win
Process completed with exit code 1.
manifest-check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
LP64-WIP
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (mnfst, tgl)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (mnfst, lnl)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (-d, mnfst, lnl)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (mnfst, tgl-h)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (mnfst, mtl)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (mnfst, imx8 imx8x)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (mnfst, imx8m imx8ulp)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (mnfst, ptl)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-linux (mnfst, wcl imx95)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, tgl)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, tgl)
Failed to restore:
build-windows (-d, mnfst, lnl)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (-d, mnfst, lnl)
Failed to restore:
build-windows (mnfst, imx8 imx8x)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, imx8 imx8x)
Failed to restore:
build-windows (mnfst, lnl)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, lnl)
Failed to restore:
build-windows (mnfst, tgl-h)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, tgl-h)
Failed to restore:
build-windows (mnfst, mtl)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, mtl)
Failed to restore:
build-windows (mnfst, ptl)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, ptl)
Failed to restore:
build-windows (mnfst, imx8m imx8ulp)
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/setup-python@v5, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, imx8m imx8ulp)
Failed to restore:
compare-linux-win
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-windows (mnfst, tgl)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows (-d, mnfst, lnl)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows (mnfst, imx8 imx8x)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows (mnfst, lnl)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows (mnfst, tgl-h)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows (mnfst, mtl)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows (mnfst, ptl)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
build-windows (mnfst, imx8m imx8ulp)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
linux-build imx8 imx8x
7.65 MB
sha256:3aac2c85eb705e9de4c3ab2e5e9185bc3a25343944f6da541297adc3755ec02e
linux-build imx8m imx8ulp
7.57 MB
sha256:460ec2f3e681f9cd8476f0cc6d10b94504d450cf579e01f35319668cd8367e3d
linux-build lnl
12.7 MB
sha256:00792d0865ff13ba68da2843d084d0bd64a7ddda59de10d86ee40baf6eb0d921
linux-build mtl
14.6 MB
sha256:803cddf51482ff7b1c25842638abee44168c4db8c7afd16d209b84a308fcedf3
linux-build ptl
16.6 MB
sha256:ce44ae6fea1345b29f61961308cb982b5c97725bb593531331dce9ad444d773f
linux-build tgl
11.9 MB
sha256:5be2ebfeb85594580da73c01a798bb6950a9fe7c0fca84a4a9b2a52e813c39c8
linux-build tgl-h
11.4 MB
sha256:28b66e7d93c74a8a70b4e8be54d9fb7ac71dbb94ba7466dbeb8189574e412cf0
linux-build wcl imx95
17.3 MB
sha256:93b2418593b66d0b532cef976e08e1ddc4617dc52dd8f3b2abf5d23a80a02581
linux-build -d lnl
13.6 MB
sha256:f2fa0c3026e54188147ebce95033063ed0bc4832a497be3905779487b421db2a
windows-build imx8m imx8ulp
3.79 MB
sha256:b2b9e18f08a1bd5a5dd5c45a3216acec22859fb0846c13f8cb968c2fd6b44495
windows-build lnl
20.9 KB
sha256:3a50d46d9c62b8dae3018adcd0dac687d2e32150c3467c4d39887e3cb9cff50f
windows-build ptl
22.3 KB
sha256:99b17bf79ad6f5f4c6793ac48b61ddba5e296b8385cb0c4c1e49c374ce49491e
windows-build tgl
11.9 MB
sha256:0063a60642ae80ffe96d63288130803db5db4cf76b8eff831e75b7004507bf5a