Skip to content

Nightly Release 2.x #955

Nightly Release 2.x

Nightly Release 2.x #955

Triggered via schedule June 4, 2026 11:17
Status Failure
Total duration 17m 44s
Artifacts 8

nightly-release.yml

on: schedule
Find Latest Release 2.x
27s
Find Latest Release 2.x
Matrix: fpga-subsystem
Matrix: fpga
Matrix: sw-emulator
Create New Release 2.x
0s
Create New Release 2.x
Publish https://caliptra-sw.github.io/  /  build
Publish https://caliptra-sw.github.io/ / build
Publish https://caliptra-sw.github.io/  /  deploy
Publish https://caliptra-sw.github.io/ / deploy
Fit to window
Zoom out
Zoom in

Annotations

40 errors and 56 warnings
sw-emulator Suite (latest, etrng, log) / build_and_test
Process completed with exit code 101.
sw-emulator Suite (latest, itrng, nolog) / build_and_test
Process completed with exit code 101.
FPGA Suite (hw-latest, itrng, nolog, ) / build_test_binaries
Process completed with exit code 101.
sw-emulator Suite (2.1, itrng, log) / build_and_test
Process completed with exit code 101.
sw-emulator Suite (2.1, itrng, nolog) / build_and_test
Process completed with exit code 101.
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), ) / build_test_binaries
Process completed with exit code 101.
sw-emulator Suite (latest, etrng, nolog) / build_and_test
Process completed with exit code 101.
FPGA Suite (rom-2.1, itrng, log, ocp-lock) / build_test_binaries
Process completed with exit code 101.
FPGA Suite (hw-latest, itrng, log, ocp-lock) / build_test_binaries
Process completed with exit code 101.
sw-emulator Suite (2.1, etrng, log) / build_and_test
Process completed with exit code 101.
sw-emulator Suite (latest, itrng, log) / build_and_test
Process completed with exit code 101.
FPGA Suite (hw-latest, itrng, nolog, ) / print_test_results
Process completed with exit code 101.
sw-emulator Suite (2.1, etrng, nolog) / build_and_test
Process completed with exit code 101.
FPGA Suite (rom-2.1, itrng, log, ) / build_test_binaries
Process completed with exit code 101.
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / build_test_binaries
Process completed with exit code 101.
FPGA Suite (hw-latest, itrng, nolog, ocp-lock) / build_test_binaries
Process completed with exit code 101.
FPGA Suite (hw-latest, itrng, log, ) / build_test_binaries
Process completed with exit code 101.
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), ) / print_test_results
Process completed with exit code 101.
FPGA Subsystem Suite (hw-latest, itrng, nolog, ocp-lock), ) / build_test_binaries
Process completed with exit code 101.
FPGA Suite (rom-2.1, itrng, log, ocp-lock) / print_test_results
Process completed with exit code 101.
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), flash-boot) / build_test_binaries
Process completed with exit code 101.
FPGA Suite (hw-latest, itrng, log, ocp-lock) / print_test_results
Process completed with exit code 101.
FPGA Suite (rom-2.1, itrng, log, ) / print_test_results
Process completed with exit code 101.
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / print_test_results
Process completed with exit code 101.
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), ) / build_test_binaries
Process completed with exit code 101.
FPGA Suite (hw-latest, itrng, nolog, ocp-lock) / print_test_results
Process completed with exit code 101.
FPGA Suite (hw-latest, itrng, log, ) / print_test_results
Process completed with exit code 101.
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), flash-boot) / print_test_results
Process completed with exit code 101.
FPGA Subsystem Suite (hw-latest, itrng, nolog, ocp-lock), ) / print_test_results
Process completed with exit code 101.
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), ) / print_test_results
Process completed with exit code 101.
FPGA Suite (rom-2.1, itrng, nolog, ) / build_test_binaries
Process completed with exit code 101.
FPGA Suite (rom-2.1, itrng, nolog, ) / print_test_results
Process completed with exit code 101.
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), flash-boot) / build_test_binaries
Process completed with exit code 101.
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), flash-boot) / print_test_results
Process completed with exit code 101.
FPGA Suite (rom-2.1, itrng, nolog, ocp-lock) / build_test_binaries
Process completed with exit code 101.
FPGA Suite (rom-2.1, itrng, nolog, ocp-lock) / print_test_results
Process completed with exit code 101.
sw-emulator Suite (latest, etrng, log) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, 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/
sw-emulator Suite (latest, itrng, nolog) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, 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/
FPGA Suite (hw-latest, itrng, nolog, ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
sw-emulator Suite (2.1, itrng, log) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, 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/
sw-emulator Suite (2.1, itrng, nolog) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, 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/
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
sw-emulator Suite (latest, etrng, nolog) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, 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/
FPGA Suite (rom-2.1, itrng, log, ocp-lock) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Suite (hw-latest, itrng, log, ocp-lock) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
sw-emulator Suite (2.1, etrng, log) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, 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/
sw-emulator Suite (latest, itrng, log) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, 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/
sw-emulator Suite (2.1, etrng, nolog) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, 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/
FPGA Suite (rom-2.1, itrng, log, ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Suite (rom-2.1, itrng, log, ) / build_test_binaries
Cache save failed.
FPGA Suite (rom-2.1, itrng, log, ) / build_test_binaries
Failed to restore:
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Suite (hw-latest, itrng, nolog, ocp-lock) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Suite (hw-latest, itrng, log, ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), flash-boot) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Subsystem Suite (hw-latest, itrng, nolog, ocp-lock), ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), flash-boot) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Subsystem Suite (hw-latest, itrng, nolog, ocp-lock), flash-boot) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Suite (rom-2.1, itrng, nolog, ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), flash-boot) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/
FPGA Suite (rom-2.1, itrng, nolog, ocp-lock) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3. 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/

Artifacts

Produced during runtime
Name Size Digest
caliptra-test-results-sw-emulator-hw-latest-etrng-log
150 Bytes
sha256:56374ae22cc32e72dd8b136d3219c60c8c8b67a0937542155fb7a7d9cc24fed5
caliptra-test-results-sw-emulator-hw-latest-etrng-nolog
150 Bytes
sha256:fd8eedf9f2a58a082785f08791564b71183c1da0a9d526b6a1d16312dfc40c0b
caliptra-test-results-sw-emulator-hw-latest-itrng-log
150 Bytes
sha256:fd8eedf9f2a58a082785f08791564b71183c1da0a9d526b6a1d16312dfc40c0b
caliptra-test-results-sw-emulator-hw-latest-itrng-nolog
150 Bytes
sha256:5ec82f6492f11659ee5f6e9d77a94e2e4ec2e3f46b2b0399c6b71336b452e96e
caliptra-test-results-sw-emulator-rom-2.1-etrng-log
150 Bytes
sha256:440edf43908506588c883cccb16963e06bb55ac5c85b732fea21e4d92b93987a
caliptra-test-results-sw-emulator-rom-2.1-etrng-nolog
150 Bytes
sha256:7983328cbdc3b1a6eadf11df4e0e0a02d73f7bdde6bd3c3b7a985bfcb71c338f
caliptra-test-results-sw-emulator-rom-2.1-itrng-log
150 Bytes
sha256:d09c35686ccd5484c1d9f1f4903ee16a3ed4ccb9d4a72dbf55f3bda49e74082c
caliptra-test-results-sw-emulator-rom-2.1-itrng-nolog
150 Bytes
sha256:ca0462d3dfbaf9f6e68aff1c563d002483d0ddd3285aa6045056d307a348cc61