userspace: DP: application: switch to vregion #22924
lyakhzephyr.yml
on: pull_request
Matrix: build-linux
Matrix: build-windows
manifest-check
3m 10s
LP64-WIP
3m 21s
compare-linux-win
27s
Annotations
38 errors and 20 warnings
|
build-linux (-d, mnfst, lnl)
Process completed with exit code 1.
|
|
LP64-WIP
Process completed with exit code 1.
|
|
build-linux (mnfst, tgl)
Process completed with exit code 1.
|
|
build-linux (mnfst, tgl-h)
Process completed with exit code 1.
|
|
build-linux (mnfst, mtl)
Process completed with exit code 1.
|
|
build-linux (mnfst, lnl)
Process completed with exit code 1.
|
|
build-linux (mnfst, imx8m imx8ulp)
Process completed with exit code 1.
|
|
build-windows (mnfst, ptl)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg exists
|
|
build-windows (mnfst, ptl)
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, ptl)
The operation was canceled.
|
|
build-linux (mnfst, imx8 imx8x)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg exists
|
|
build-linux (mnfst, imx8 imx8x)
No files were found with the provided path: build-sof-staging
./**/compile_commands.json. No artifacts will be uploaded.
|
|
build-linux (mnfst, imx8 imx8x)
The operation was canceled.
|
|
build-windows (mnfst, lnl)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg exists
|
|
build-windows (mnfst, lnl)
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, lnl)
The operation was canceled.
|
|
build-windows (mnfst, tgl)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg exists
|
|
build-windows (mnfst, tgl)
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)
The operation was canceled.
|
|
build-linux (mnfst, wcl imx95)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg exists
|
|
build-linux (mnfst, wcl imx95)
The operation was canceled.
|
|
build-windows (mnfst, imx8m imx8ulp)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg exists
|
|
build-windows (mnfst, imx8m imx8ulp)
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, imx8m imx8ulp)
The operation was canceled.
|
|
build-windows (mnfst, tgl-h)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg 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 (-d, mnfst, lnl)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg exists
|
|
build-windows (-d, mnfst, lnl)
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 (-d, mnfst, lnl)
The operation was canceled.
|
|
build-windows (mnfst, mtl)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg 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, imx8 imx8x)
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg 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.
|
|
compare-linux-win
Process completed with exit code 1.
|
|
Zephyr
Canceling since a higher priority waiting request for Zephyr-pull_request-vreg exists
|
|
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 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-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 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/
|
|
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 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-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 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-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 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-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 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-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 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-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 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-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 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-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 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-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 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-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/upload-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/
|
|
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 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-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 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-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 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-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 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-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 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-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 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-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 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/
|
|
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 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 | |
|---|---|---|---|
|
linux-build imx8m imx8ulp
|
15.1 KB |
sha256:fc933c74f42db28d8f51f45d7303cc5af22ec5301609b6cbbf699b08aaaeab82
|
|
|
linux-build lnl
|
19.4 KB |
sha256:367b3379db51bde524e84b6df54fca297b8b25726783a35fd52bc82413291d21
|
|
|
linux-build mtl
|
20.7 KB |
sha256:15e331ad99574a9b58db20f68f53e40652788264275cc3f6a005e28596f0b886
|
|
|
linux-build ptl
|
16.4 MB |
sha256:505031971bb9698faa7e0f57ed4626f414f111aa26e7d91f38ba7d90101b9b8c
|
|
|
linux-build tgl
|
17.9 KB |
sha256:087d88a2bf93aacede76fcfe6dd42070bf7498cef96522c968793c1ce654ecff
|
|
|
linux-build tgl-h
|
17.8 KB |
sha256:7b4f20d5feabd5aca234fc69da457115b03cf5b1ce8512d476a098b4c93b1f07
|
|
|
linux-build wcl imx95
|
13.4 MB |
sha256:1babf1aacf9515fe8ae86ac11dea5bdae2a8a2726e6f45ddb6b0acadf747c288
|
|
|
linux-build -d lnl
|
20.6 KB |
sha256:6c7653e8d3ddaa848ecd85cc7353a3a98a93decc294d4705c9a77b94ac64bc11
|
|