Generic cryptocb support #829
bigbretttest-build-cmake-script.yml
on: pull_request
Matrix: wolfboot_build_script_test
Annotations
30 errors and 13 warnings
|
Build wolfBoot (target=stm32wb)
The process '/usr/bin/git' failed with exit code 128
|
|
Build wolfBoot (target=stm32wb)
Fetched in submodule path 'lib/wolfHSM', but it did not contain 977bf187e7a57a184493dcd216eb9a328f381865. Direct fetching of that commit failed.
|
|
Build wolfBoot (target=stm32wb)
expected 'acknowledgments'
|
|
Build wolfBoot (target=stm32wb)
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32wb)
expected 'acknowledgments'
|
|
Build wolfBoot (target=stm32wb)
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32wb)
clone of 'https://github.com/wolfSSL/wolfssl.git' into submodule path '/__w/wolfBoot/wolfBoot/lib/wolfssl' failed
|
|
Build wolfBoot (target=stm32wb)
unable to access 'https://github.com/wolfSSL/wolfssl.git/': The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32wb)
clone of 'https://github.com/wolfSSL/wolfPKCS11.git' into submodule path '/__w/wolfBoot/wolfBoot/lib/wolfPKCS11' failed
|
|
Build wolfBoot (target=stm32wb)
unable to access 'https://github.com/wolfSSL/wolfPKCS11.git/': The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32h7)
The process '/usr/bin/git' failed with exit code 128
|
|
Build wolfBoot (target=stm32h7)
Fetched in submodule path 'lib/wolfHSM', but it did not contain 977bf187e7a57a184493dcd216eb9a328f381865. Direct fetching of that commit failed.
|
|
Build wolfBoot (target=stm32h7)
unable to access 'https://github.com/wolfssl/wolfhsm.git/': The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32h7)
unable to access 'https://github.com/wolfssl/wolfhsm.git/': The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32f7)
The process '/usr/bin/git' failed with exit code 128
|
|
Build wolfBoot (target=stm32f7)
Fetched in submodule path 'lib/wolfHSM', but it did not contain 977bf187e7a57a184493dcd216eb9a328f381865. Direct fetching of that commit failed.
|
|
Build wolfBoot (target=stm32f7)
expected 'packfile'
|
|
Build wolfBoot (target=stm32f7)
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32c0)
unable to access 'https://github.com/wolfSSL/wolfPKCS11.git/': The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32c0)
clone of 'https://github.com/wolfSSL/wolfssl.git' into submodule path '/__w/wolfBoot/wolfBoot/lib/wolfssl' failed
|
|
Build wolfBoot (target=stm32c0)
unable to access 'https://github.com/wolfSSL/wolfssl.git/': The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32g0)
The process '/usr/bin/git' failed with exit code 128
|
|
Build wolfBoot (target=stm32g0)
Fetched in submodule path 'lib/wolfHSM', but it did not contain 977bf187e7a57a184493dcd216eb9a328f381865. Direct fetching of that commit failed.
|
|
Build wolfBoot (target=stm32g0)
expected 'acknowledgments'
|
|
Build wolfBoot (target=stm32g0)
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32f4)
expected 'acknowledgments'
|
|
Build wolfBoot (target=stm32f4)
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32h5)
unable to access 'https://github.com/wolfSSL/wolfBoot/': The requested URL returned error: 500
|
|
Build wolfBoot (target=stm32h5)
expected 'packfile'
|
|
Build wolfBoot (target=stm32h5)
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
Build wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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 wolfBoot (target=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 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/
|