Skip to content

NXP T2080 / CW VPX3-152: VxWorks 7 64-bit boot support #948

NXP T2080 / CW VPX3-152: VxWorks 7 64-bit boot support

NXP T2080 / CW VPX3-152: VxWorks 7 64-bit boot support #948

Triggered via pull request May 15, 2026 23:03
Status Success
Total duration 4m 45s
Artifacts 12

test-build-cmake-windows.yml

on: pull_request
Matrix: Build on Windows
Fit to window
Zoom out
Zoom in

Annotations

12 warnings and 12 notices
Build on Windows (stm32g0)
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 on Windows (stm32u5)
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 on Windows (stm32l5)
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 on Windows (stm32wb)
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 on Windows (stm32l4)
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 on Windows (stm32f1)
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 on Windows (stm32f7)
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 on Windows (stm32c0)
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 on Windows (stm32h7)
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 on Windows (stm32f4)
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 on Windows (stm32h5)
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 on Windows (stm32l0)
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 on Windows (stm32g0)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32u5)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32l5)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32wb)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32l4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32f1)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32f7)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32c0)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32h7)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32f4)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32h5)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Build on Windows (stm32l0)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
wolfboot-stm32c0
158 KB
sha256:84dea939e16f9b86e7a5d18410a44debcfbc158b1279baebc57ccbef2a4f78a7
wolfboot-stm32f1
164 KB
sha256:1e4015deaf018f168d008bb8c08d318d9858a93af581441d17f932583f732dcf
wolfboot-stm32f4
167 KB
sha256:4aaf3b5ea8809cb353cd0ed4577fd6458a036941da5bd7fe78db61d906f286cb
wolfboot-stm32f7
166 KB
sha256:916fb7514bfa19c6b5628b14f1ea9362a5f00d40df97b798ff76412e9e585cd2
wolfboot-stm32g0
30.5 KB
sha256:ca3bbf55aee0f59c5465e780889d4514fe9bdf0179f964e9046da1f06393c578
wolfboot-stm32h5
747 KB
sha256:838ded49be603736c488e709f3eba78d385ddc06940b13f177a77e9e0ef16e29
wolfboot-stm32h7
37.4 KB
sha256:691f4fb0a658759a94cd56f20046a5ffa948539824322b12978553ac8064f39b
wolfboot-stm32l0
35.4 KB
sha256:4ad78e62aad0d1fa49b8c2d9e6d08389be0ec826db701c63d23bf5f13a22d7d4
wolfboot-stm32l4
301 KB
sha256:d38446a283f60731aaa79fd30e4f700608ce34fde5d198b21d9f7c35e2ea373f
wolfboot-stm32l5
1.97 KB
sha256:eea10cd82ccc533dd88d27549f7bbce7da79b9f3b187a93d5c8489adf7b53675
wolfboot-stm32u5
36.6 KB
sha256:6383492ee43a967449091039d9ebc0533929ac17c1861daaba7862c6337822b0
wolfboot-stm32wb
1.96 KB
sha256:c32f5deb687c1b5db829cefba7ae1e447f9120652117f2679c724002f6f5cad6