Generic cryptocb support #2524
bigbretttest-tpm.yml
on: pull_request
sim_tpm_debug
/
build
59s
sim_tpm_ecc256
/
build
47s
sim_tpm_ecc384
/
build
1m 10s
sim_tpm_rsa2048
/
build
1m 0s
sim_tpm_measured_ecc256
/
build
47s
sim_tpm_measured_ecc384
/
build
38s
sim_tpm_measured_rsa2048
/
build
56s
sim_tpm_keystore_ecc256
/
build
1m 21s
sim_tpm_keystore_ecc384
/
build
57s
sim_tpm_keystore_rsa2048
/
build
1m 2s
sim_tpm_keystore_noauth_ecc256
/
build
1m 15s
sim_tpm_keystore_noauth_ecc384
/
build
58s
sim_tpm_keystore_noauth_rsa2048
/
build
1m 40s
sim_tpm_seal_ecc256
/
build
1m 43s
sim_tpm_seal_ecc384
/
build
1m 14s
sim_tpm_seal_rsa2048
/
build
1m 38s
sim_tpm_seal_noauth_ecc256
/
build
1m 5s
sim_tpm_seal_noauth_ecc384
/
build
1m 0s
sim_tpm_seal_noauth_rsa2048
/
build
1m 1s
Annotations
61 errors and 19 warnings
|
sim_tpm_measured_ecc384 / build
The process '/usr/bin/git' failed with exit code 128
|
|
sim_tpm_measured_ecc384 / build
Fetched in submodule path 'lib/wolfHSM', but it did not contain 977bf187e7a57a184493dcd216eb9a328f381865. Direct fetching of that commit failed.
|
|
sim_tpm_measured_ecc384 / build
expected 'acknowledgments'
|
|
sim_tpm_measured_ecc384 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_keystore_noauth_rsa2048 / build
clone of 'https://github.com/wolfSSL/wolfPKCS11.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfPKCS11' failed
|
|
sim_tpm_keystore_noauth_rsa2048 / build
expected flush after ref listing
|
|
sim_tpm_keystore_noauth_rsa2048 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_keystore_noauth_rsa2048 / build
clone of 'https://github.com/wolfssl/wolfhsm.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfHSM' failed
|
|
sim_tpm_keystore_noauth_rsa2048 / build
unable to access 'https://github.com/wolfssl/wolfhsm.git/': The requested URL returned error: 500
|
|
sim_tpm_keystore_noauth_rsa2048 / build
expected 'packfile'
|
|
sim_tpm_keystore_noauth_rsa2048 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_measured_ecc256 / build
The process '/usr/bin/git' failed with exit code 128
|
|
sim_tpm_measured_ecc256 / build
Fetched in submodule path 'lib/wolfPSA', but it did not contain f289a6f12788237224f26635f8586b1f63c817e4. Direct fetching of that commit failed.
|
|
sim_tpm_measured_ecc256 / build
expected 'packfile'
|
|
sim_tpm_measured_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_measured_ecc256 / build
clone of 'https://github.com/wolfSSL/wolfssl.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfssl' failed
|
|
sim_tpm_measured_ecc256 / build
unable to access 'https://github.com/wolfSSL/wolfssl.git/': The requested URL returned error: 500
|
|
sim_tpm_keystore_ecc256 / build
clone of 'https://github.com/wolfssl/wolfhsm.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfHSM' failed
|
|
sim_tpm_keystore_ecc256 / build
expected 'packfile'
|
|
sim_tpm_keystore_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_ecc384 / build
clone of 'https://github.com/wolfssl/wolfhsm.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfHSM' failed
|
|
sim_tpm_ecc384 / build
unable to access 'https://github.com/wolfssl/wolfhsm.git/': The requested URL returned error: 500
|
|
sim_tpm_seal_ecc384 / build
clone of 'https://github.com/wolfssl/wolfhsm.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfHSM' failed
|
|
sim_tpm_seal_ecc384 / build
expected flush after ref listing
|
|
sim_tpm_seal_ecc384 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_ecc256 / build
The process '/usr/bin/git' failed with exit code 128
|
|
sim_tpm_ecc256 / build
Fetched in submodule path 'lib/wolfPKCS11', but it did not contain 8fec69592d99bf4d8f01e36acd16f7d27b4639f4. Direct fetching of that commit failed.
|
|
sim_tpm_ecc256 / build
expected 'acknowledgments'
|
|
sim_tpm_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_ecc256 / build
clone of 'https://github.com/wolfssl/wolfTPM' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfTPM' failed
|
|
sim_tpm_ecc256 / build
expected flush after ref listing
|
|
sim_tpm_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_seal_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_seal_ecc256 / build
clone of 'https://github.com/wolfssl/wolfTPM' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfTPM' failed
|
|
sim_tpm_seal_ecc256 / build
expected 'packfile'
|
|
sim_tpm_seal_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_seal_ecc256 / build
clone of 'https://github.com/wolfSSL/wolfPSA.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfPSA' failed
|
|
sim_tpm_seal_ecc256 / build
expected flush after ref listing
|
|
sim_tpm_seal_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_seal_ecc256 / build
clone of 'https://github.com/wolfssl/wolfhsm.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfHSM' failed
|
|
sim_tpm_seal_ecc256 / build
unable to access 'https://github.com/wolfssl/wolfhsm.git/': The requested URL returned error: 500
|
|
sim_tpm_seal_ecc256 / build
unable to access 'https://github.com/wolfSSL/wolfBoot/': The requested URL returned error: 500
|
|
sim_tpm_seal_ecc256 / build
unable to access 'https://github.com/kgoldman/ibmswtpm2/': The requested URL returned error: 500
|
|
sim_tpm_seal_rsa2048 / build
expected flush after ref listing
|
|
sim_tpm_seal_rsa2048 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_seal_rsa2048 / build
clone of 'https://github.com/wolfssl/wolfhsm.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfHSM' failed
|
|
sim_tpm_seal_rsa2048 / build
expected 'packfile'
|
|
sim_tpm_seal_rsa2048 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_seal_rsa2048 / build
expected flush after ref listing
|
|
sim_tpm_seal_rsa2048 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_keystore_noauth_ecc256 / build
clone of 'https://github.com/wolfssl/wolfTPM' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfTPM' failed
|
|
sim_tpm_keystore_noauth_ecc256 / build
unable to access 'https://github.com/wolfssl/wolfTPM/': The requested URL returned error: 500
|
|
sim_tpm_keystore_noauth_ecc256 / build
clone of 'https://github.com/wolfSSL/wolfssl.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfssl' failed
|
|
sim_tpm_keystore_noauth_ecc256 / build
expected flush after ref listing
|
|
sim_tpm_keystore_noauth_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_keystore_noauth_ecc256 / build
clone of 'https://github.com/wolfssl/wolfTPM' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfTPM' failed
|
|
sim_tpm_keystore_noauth_ecc256 / build
unable to access 'https://github.com/wolfssl/wolfTPM/': The requested URL returned error: 500
|
|
sim_tpm_keystore_noauth_ecc256 / build
clone of 'https://github.com/wolfSSL/wolfPKCS11.git' into submodule path '/home/runner/work/wolfBoot/wolfBoot/lib/wolfPKCS11' failed
|
|
sim_tpm_keystore_noauth_ecc256 / build
expected flush after ref listing
|
|
sim_tpm_keystore_noauth_ecc256 / build
RPC failed; HTTP 500 curl 22 The requested URL returned error: 500
|
|
sim_tpm_keystore_noauth_ecc256 / build
unable to access 'https://github.com/kgoldman/ibmswtpm2/': The requested URL returned error: 500
|
|
sim_tpm_measured_ecc384 / build
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/
|
|
sim_tpm_debug / build
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/
|
|
sim_tpm_keystore_noauth_rsa2048 / build
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/
|
|
sim_tpm_measured_rsa2048 / build
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/
|
|
sim_tpm_rsa2048 / build
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/
|
|
sim_tpm_keystore_ecc384 / build
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/
|
|
sim_tpm_measured_ecc256 / build
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/
|
|
sim_tpm_keystore_ecc256 / build
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/
|
|
sim_tpm_ecc384 / build
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/
|
|
sim_tpm_seal_ecc384 / build
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/
|
|
sim_tpm_seal_noauth_ecc384 / build
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/
|
|
sim_tpm_seal_noauth_ecc256 / build
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/
|
|
sim_tpm_ecc256 / build
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/
|
|
sim_tpm_seal_ecc256 / build
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/
|
|
sim_tpm_keystore_rsa2048 / build
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/
|
|
sim_tpm_seal_rsa2048 / build
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/
|
|
sim_tpm_keystore_noauth_ecc256 / build
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/
|
|
sim_tpm_seal_noauth_rsa2048 / build
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/
|
|
sim_tpm_keystore_noauth_ecc384 / build
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/
|