Skip to content

Nightly Release 2.x #966

Nightly Release 2.x

Nightly Release 2.x #966

Triggered via schedule June 16, 2026 11:56
Status Failure
Total duration 4h 35m 24s
Artifacts 154

nightly-release.yml

on: schedule
Find Latest Release 2.x
30s
Find Latest Release 2.x
Matrix: fpga-subsystem
Matrix: fpga
Matrix: sw-emulator
Create New Release 2.x
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

4 errors and 154 warnings
FPGA Subsystem Suite (rom-2.1.1, itrng, nolog, ), ) / test_artifacts_subsystem (2)
Process completed with exit code 100.
FPGA Subsystem Suite (rom-2.1.0, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (1)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
FPGA Subsystem Suite (rom-2.1.0, itrng, nolog, ), ) / test_artifacts_subsystem (2)
Process completed with exit code 100.
FPGA Subsystem Suite (rom-2.1.0, itrng, nolog, ), ) / test_artifacts_subsystem (1)
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
FPGA Suite (rom-2.1.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/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 (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/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 (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/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.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/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.0, 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/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.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/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.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/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.0, 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/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.0, 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/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.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/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.0, 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/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, 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/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.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/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, 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/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 (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/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.0, 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/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.0, 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/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/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.0, 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.0, 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/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.0, 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/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.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/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 (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/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.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/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, 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/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.1, itrng, log, ocp-lock) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, 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/
FPGA Suite (rom-2.1.1, itrng, log, ocp-lock) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, 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/
FPGA Suite (rom-2.1.1, itrng, log, ) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.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/
sw-emulator Suite (2.1.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 (2.1.0, 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/
sw-emulator Suite (2.1.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.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 Suite (rom-2.1.1, itrng, log, ) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, 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/
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 (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/
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/
FPGA Suite (rom-2.1.0, itrng, log, ocp-lock) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ), ) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, log, ocp-lock) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, ocp-lock) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ), ) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ), ) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, ocp-lock) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ), ) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ), ) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ), ) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ), ) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ), ) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, log, ) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, log, ) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, log, ) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, log, ) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, ) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, ) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ocp-lock) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.1, itrng, nolog, ), flash-boot) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, log, ocp-lock) / test_artifacts (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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, log, ocp-lock) / test_artifacts (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ocp-lock), flash-boot) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ), ) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ), ) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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.0, itrng, nolog, ), ) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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 (hw-latest, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: 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/

Artifacts

Produced during runtime
Name Size Digest
caliptra-bitstream-fpga-realtime-latest-itrng-log- Expired
13.8 MB
sha256:dca5c523551cb58a2b75fbbc0a8f003b99594db5b31ba2dfee55f80542facbf8
caliptra-bitstream-fpga-realtime-latest-itrng-log-ocp-lock Expired
13.8 MB
sha256:ae609023452b4d859fe4275466b7478e821ae4c45098a7cf73fe45bb9e0fb2a6
caliptra-bitstream-fpga-realtime-latest-itrng-nolog- Expired
13.8 MB
sha256:ab9e6a0331a0a4b74a31a51046e524e81427f6576b5009ab33141cb2b9d74a85
caliptra-bitstream-fpga-realtime-latest-itrng-nolog-ocp-lock Expired
13.8 MB
sha256:3ccdb952bf41f636807a5c4fd3430a9f308ae82c8b948c009d4bef554343a289
caliptra-bitstream-fpga-realtime-rom-2.1.0-itrng-log- Expired
13.8 MB
sha256:c39861a7a70b67b1ee9bd8cf9edb3930ccd874894e915730cc0761ebb1032052
caliptra-bitstream-fpga-realtime-rom-2.1.0-itrng-log-ocp-lock Expired
13.8 MB
sha256:cd9f89c599a06cd2a7b56da5c7ac69b6fb7001ae884d837b2798bda363a22843
caliptra-bitstream-fpga-realtime-rom-2.1.0-itrng-nolog- Expired
13.8 MB
sha256:713b4a35e963059f1946ce0daf686f8b827df634f5e2389f874961a882f7c138
caliptra-bitstream-fpga-realtime-rom-2.1.0-itrng-nolog-ocp-lock Expired
13.8 MB
sha256:a1ee74f10427fe1df9e6f679b05358e58ca24595116ca527cc9f93a8c8d7594d
caliptra-bitstream-fpga-realtime-rom-2.1.1-itrng-log- Expired
13.8 MB
sha256:08d2fa104320b6ec04a1c2a7f36b08afd97e24f415555b6f6f11ddbb3ceb8a2a
caliptra-bitstream-fpga-realtime-rom-2.1.1-itrng-log-ocp-lock Expired
13.8 MB
sha256:4a26fd02d1d91837b4215b6b12388f651fcf4c40bdd79638213d816225e20bf0
caliptra-bitstream-fpga-realtime-rom-2.1.1-itrng-nolog- Expired
13.8 MB
sha256:310fe5b29b780adfd793b059572248d125f76448040d456efafef8865bae1907
caliptra-bitstream-fpga-realtime-rom-2.1.1-itrng-nolog-ocp-lock Expired
13.8 MB
sha256:a8f6e579cf0f0f9bd00411df9132bf52f74ab4edc65decc98573f01500377e98
caliptra-bitstream-fpga-subsystem-realtime-latest-itrng-nolog-- Expired
19.9 MB
sha256:05dc9c6925306c6d076c89f19f0c81b1f4c8073c7c41aa6999829dff8fd4523e
caliptra-bitstream-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot Expired
19.9 MB
sha256:648f0e95b1a2d1310ecccd3f2945db80037713de6c278af418b8a56330299549
caliptra-bitstream-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock- Expired
19.9 MB
sha256:7bfb05119cfe3412399c8395c5a189be4452e04b290f171977228d5d8559b0da
caliptra-bitstream-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot Expired
19.9 MB
sha256:079106415d035c6fad4d04e8d9f185fc406c9efa8bd42dd7a2f2c396b8646d10
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-- Expired
19.9 MB
sha256:093bb2976d0158f603dc1c8b634785882c013d9e7e718f6e051d7c6580a05e30
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog--flash-boot Expired
19.9 MB
sha256:58551819c6a0063b1aa13bcc9a9f71e7070644929dc2658f9f0b28d26e34e295
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock- Expired
19.9 MB
sha256:b9bee9b6209a0a7a5df291fbe863caca268d2c41364b85c43902a4036f132994
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock-flash-boot Expired
19.9 MB
sha256:368933210c90168e7db977e31d614778f66f1e3f38bdee90a33b61fd1fc252ef
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-- Expired
19.9 MB
sha256:b9bee9b6209a0a7a5df291fbe863caca268d2c41364b85c43902a4036f132994
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog--flash-boot Expired
19.9 MB
sha256:a2de642542c46d1860d5562d0a3523c415e4add0a968ec82b54bcd95a2c59d68
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock- Expired
19.9 MB
sha256:a8ededb9b944721288cc5a4593a2cae3f704cac493f5f92e94e9138e89f20ee2
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock-flash-boot Expired
19.9 MB
sha256:a9847a1efa41534d996b195b7ac3621148341f0c1b86be90de7e7c28814894e0
caliptra-test-binaries-fpga-realtime-latest-itrng-log- Expired
84.2 MB
sha256:6267298eb547616c9f248e6d3661dc7e62d357990080fd184bfcba40ebc5a809
caliptra-test-binaries-fpga-realtime-latest-itrng-log-ocp-lock Expired
84.2 MB
sha256:79bc77b4878bc038339044f2eaad081bc6c535f0cc10af64369d204e64578095
caliptra-test-binaries-fpga-realtime-latest-itrng-nolog- Expired
84.2 MB
sha256:13e6484311d2fa4a5583f66b29996bd95c60690ae3b20dd07765fef2423571a0
caliptra-test-binaries-fpga-realtime-latest-itrng-nolog-ocp-lock Expired
84.2 MB
sha256:fcfcf260c1a4e9eb3bea920b0cad71fa33987c9cf71bb17b97f1c7597134ef59
caliptra-test-binaries-fpga-realtime-rom-2.1.0-itrng-log- Expired
84.2 MB
sha256:cf5c9a28fe009478e9497e365b276fcc16998abaa99d12fefc2885bc91253243
caliptra-test-binaries-fpga-realtime-rom-2.1.0-itrng-log-ocp-lock Expired
84.2 MB
sha256:e17df7431f2ae951b74437cdf83defb460b4f03e3d2747f3cdc780d17dfc8e0f
caliptra-test-binaries-fpga-realtime-rom-2.1.0-itrng-nolog- Expired
84.2 MB
sha256:d73249f641f25e145640dcea36c5acbc18610af74e83d35d04c5b57e641bcd03
caliptra-test-binaries-fpga-realtime-rom-2.1.0-itrng-nolog-ocp-lock Expired
84.2 MB
sha256:864e58aa196aa7d2386442258180f293270a277a821d3a069a9e5cd5e2ab1350
caliptra-test-binaries-fpga-realtime-rom-2.1.1-itrng-log- Expired
84.2 MB
sha256:028725742fa2c81e050ee867762be4a7a4bcced11abe26410c8a70524d15b945
caliptra-test-binaries-fpga-realtime-rom-2.1.1-itrng-log-ocp-lock Expired
84.2 MB
sha256:25ec98dcbfb79a2d10481c7936bed05065fd01137caa8ecd53ec1d11a17cf4a1
caliptra-test-binaries-fpga-realtime-rom-2.1.1-itrng-nolog- Expired
84.2 MB
sha256:25c0d540583f54b3d50c2382a61cb7fedcee181d92678d4978a98c96804d0909
caliptra-test-binaries-fpga-realtime-rom-2.1.1-itrng-nolog-ocp-lock Expired
84.2 MB
sha256:f7e4f184e35c4c186c0246c7d23243e777316299cd93f34cae8f992c48ac821a
caliptra-test-binaries-fpga-subsystem-realtime-latest-itrng-nolog-- Expired
84.7 MB
sha256:c573fe76e2bf8ef8c417fb621a9480d787a1f434933022d08dbcb6d8c6a75274
caliptra-test-binaries-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot Expired
84.7 MB
sha256:acd6894c91edf18a38b344f3f526eacbef73ed76ed1b86075e1140df98320690
caliptra-test-binaries-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock- Expired
84.7 MB
sha256:b6e5227ded07b1f2765607a3d8da532b4e46b7abcc106713ce2810459da39cd5
caliptra-test-binaries-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot Expired
84.7 MB
sha256:f89941d55e87770a83d9fd19575508096c59a6c02d73044907f85e0a95724f93
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-- Expired
84.7 MB
sha256:332c55013551add5e82006828741f8724f479d055893415dda82c7cbd658e6c7
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog--flash-boot Expired
84.7 MB
sha256:13a4ec23615caee6b8e2ff84299304b974495055df02dae75f64e5ff8d05f01b
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock- Expired
84.7 MB
sha256:b2769a46b51054bb6200ac1029f6e07d38e49d97c62e8bbf00b65e1e5f89fed8
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock-flash-boot Expired
84.7 MB
sha256:f1bae98bb3ca35bc5c0a011242d6a3c31b38f9b2d8623a23158929ff23a56a60
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-- Expired
84.7 MB
sha256:82a726db99aaf1ff37e5a9d4df24e33e73c25f148edde0c4774756bf1cc4c312
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog--flash-boot Expired
84.7 MB
sha256:8d8bf524b64fd2bfd5f1fce286c21164d1638c9063b4349ed153086e946f8928
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock- Expired
84.7 MB
sha256:b846a68a2a8c8cd6d04f7d01ab0efdff538e991faa604d62c37bfa8f8a78137b
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock-flash-boot Expired
84.7 MB
sha256:463da30a795dda00e838a0a43415a944c07157893237de8441db7ab6fcdc8948
caliptra-test-firmware-fpga-realtime-latest-itrng-log- Expired
25.7 MB
sha256:b49ccbe18fe5824ae52efaf5fef46d221244c9fa01c83f8cd26b890b012112cc
caliptra-test-firmware-fpga-realtime-latest-itrng-log-ocp-lock Expired
25.7 MB
sha256:0f1cfe4f170edd76ef01e79f5c6af587203ba3dc6249dd749dc1e42524cc95b7
caliptra-test-firmware-fpga-realtime-latest-itrng-nolog- Expired
25.7 MB
sha256:992a49eb99f9656d0cb8fcda317ce01d47f7f44505e4a4f5adf186dc525ff46c
caliptra-test-firmware-fpga-realtime-latest-itrng-nolog-ocp-lock Expired
25.7 MB
sha256:f0505f9b96ce368f82c67fecb45b5e3371ba01466b415d400b8d078f4475454e
caliptra-test-firmware-fpga-realtime-rom-2.1.0-itrng-log- Expired
25.7 MB
sha256:58e9b2318742366e721d0482280ba6e1d2ee95180f1e5b4cebde674b96084e3f
caliptra-test-firmware-fpga-realtime-rom-2.1.0-itrng-log-ocp-lock Expired
25.7 MB
sha256:a176adc295422f1c8f62b4ca38ca6a9cf8b3e9b2a72839a71d7f4308adf6d49b
caliptra-test-firmware-fpga-realtime-rom-2.1.0-itrng-nolog- Expired
25.7 MB
sha256:b20f76a9c0fbf7c5b109a2e7cba1959fba5479360d2a9175c6b26362ecdba7bd
caliptra-test-firmware-fpga-realtime-rom-2.1.0-itrng-nolog-ocp-lock Expired
25.7 MB
sha256:313df726da32ba97af1596498bd0d46479e8e1d022bb4533b67f868e78b2d8b4
caliptra-test-firmware-fpga-realtime-rom-2.1.1-itrng-log- Expired
25.7 MB
sha256:6a663e7afb202280eb08c6608e82c234fc63504cc5928ad33550301d78d02878
caliptra-test-firmware-fpga-realtime-rom-2.1.1-itrng-log-ocp-lock Expired
25.7 MB
sha256:79355bd5099c9dfe0ef3238f82c5f4cc9633e52fa7ade9eabc9eba515f697538
caliptra-test-firmware-fpga-realtime-rom-2.1.1-itrng-nolog- Expired
25.7 MB
sha256:ae8a112c33e8366dd3d3932103bc51721a83360707f3f08b241bae5463cce3d1
caliptra-test-firmware-fpga-realtime-rom-2.1.1-itrng-nolog-ocp-lock Expired
25.7 MB
sha256:0644fb7dca2961f1e3e858af7e98c2cc8d521f9ce4d4772d61c7a42ee5b863db
caliptra-test-firmware-fpga-subsystem-realtime-latest-itrng-nolog-- Expired
25.7 MB
sha256:7fab559825cc56eb7a9e6a6b02a913e7f64dc40cc40e1036cc597001b5bd3a0c
caliptra-test-firmware-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot Expired
25.7 MB
sha256:79bafa73c4f56fed18febcbc9783c6418276f620c3759caada4603e5dd96ef54
caliptra-test-firmware-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock- Expired
25.7 MB
sha256:8f7d170ae4d7b3786f1c8f5d82d57c8d44b5315630de8bd774cf1758c2319645
caliptra-test-firmware-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot Expired
25.7 MB
sha256:fedf19a63fca588a72de2d6ae07d4f13f7917c50b8e93c166ba2f5eb60441d63
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-- Expired
25.7 MB
sha256:6a978c408c431199c70d090b5f8322ca50866af29d401764fad76d50be811ae6
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog--flash-boot Expired
25.7 MB
sha256:9d99c91e368061ea96131a89f9c8d6556d6fe53f4aa5dcd42132d0271b57145c
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock- Expired
25.7 MB
sha256:4fb37645d4d7146f3e176abf25715e6f9055d32b5c7c37913b61d591eb41f105
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock-flash-boot Expired
25.7 MB
sha256:71f6c814afc2a8f54dfadd4d6484f4a1bfad574bc60a921c44829285aeab61f3
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-- Expired
25.7 MB
sha256:a439ec9db4c427d2df81198dda2a8b6c561ae0948f7fa50cc215d360ed48d0d6
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog--flash-boot Expired
25.7 MB
sha256:1ce28c9916c9ede9bdd2569e2df196c63c1f27a4d53e34445f0a90e2a24830b2
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock- Expired
25.7 MB
sha256:a136f882eb46c0d1fd51caaebc59fddc5d8bb00251c29c3cc85d2278e8503527
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock-flash-boot Expired
25.7 MB
sha256:ebccff4223821ab960d5d4d4e280b8dd8d303f9d771f0954df7fe47e302779aa
caliptra-test-results-fpga-realtime-latest-itrng-log--1
687 KB
sha256:20d7cf9a3aa6ad0158bd4b9830e09fad740f9df65b15ccf6d5df44e79c148197
caliptra-test-results-fpga-realtime-latest-itrng-log--2
628 KB
sha256:fa958024b399d6bf6c7fd381be4da28c2fa0ab7338cf4819293294f15e7664d7
caliptra-test-results-fpga-realtime-latest-itrng-log-ocp-lock-1
687 KB
sha256:48a621cd2f2cc04084ce0838bf179e3f80b8c90d91c9b647ae85f5f4aa71d9dc
caliptra-test-results-fpga-realtime-latest-itrng-log-ocp-lock-2
627 KB
sha256:c895b8e037dc929a313027f197fbc5ee7fd28df8db83975d291c98564814aac5
caliptra-test-results-fpga-realtime-latest-itrng-nolog--1
497 KB
sha256:5b11ef59fc4904c0c1f5ca464d5e2ef324521439a8f7fdd13c6a88e2237559f3
caliptra-test-results-fpga-realtime-latest-itrng-nolog--2
341 KB
sha256:ed4e139ac3606f2798fbe60f1ee1c5aab67533b4f150521193466f1c88b1a613
caliptra-test-results-fpga-realtime-latest-itrng-nolog-ocp-lock-1
497 KB
sha256:e3c9272b87e183d471be4daececeb95b6535b9c8aaf5af9f3546d95d49981303
caliptra-test-results-fpga-realtime-latest-itrng-nolog-ocp-lock-2
342 KB
sha256:c5d597ccb6d1f63fc02c77c8bb2b6d6dc61238be888a079863ac21db82c5925e
caliptra-test-results-fpga-realtime-rom-2.1.0-itrng-log--1
680 KB
sha256:02bf3c6c7994347af348205ef920c3bc157c72cea0f6af69080eefb617170273
caliptra-test-results-fpga-realtime-rom-2.1.0-itrng-log--2
612 KB
sha256:f524f9d581a18f3eb2d3776d195ec53c967ab4fa0e4c055a0ab959e218c0ea0c
caliptra-test-results-fpga-realtime-rom-2.1.0-itrng-log-ocp-lock-1
679 KB
sha256:101a1151fd1d5cf5d4d070ee950a0173bb883b68f2ff323637a83d149a697f73
caliptra-test-results-fpga-realtime-rom-2.1.0-itrng-log-ocp-lock-2
612 KB
sha256:6818c1872c6c0da9df249ee41d5dd225d08260eb03bb5d5306a1e037276c88e3
caliptra-test-results-fpga-realtime-rom-2.1.0-itrng-nolog--1
497 KB
sha256:6a0c2576c359c21f1028771560f63e7daa550056bc9bd650488a3fed05c21ef9
caliptra-test-results-fpga-realtime-rom-2.1.0-itrng-nolog--2
341 KB
sha256:c048e39404e4014800e9e54913c95099d8050a7d9e0b58c25bda0e262e16c9e0
caliptra-test-results-fpga-realtime-rom-2.1.0-itrng-nolog-ocp-lock-1
497 KB
sha256:70aa2060f306a7b505ea73accdc609c960c7fbc5802adeef91a227fc70f3ca27
caliptra-test-results-fpga-realtime-rom-2.1.0-itrng-nolog-ocp-lock-2
341 KB
sha256:2bd9a21d00720859da3ee7c1327c1bf14442c3f0394e8c12d4c39724a90a0e64
caliptra-test-results-fpga-realtime-rom-2.1.1-itrng-log--1
688 KB
sha256:c746f66c8aae1fd4242567c2e3f46da38c9a84d060c29356ce304e5a033cd964
caliptra-test-results-fpga-realtime-rom-2.1.1-itrng-log--2
626 KB
sha256:93623a8186b1e2ae92611ecddf3ed3f655169f70f1b2312b1181968d30260e0b
caliptra-test-results-fpga-realtime-rom-2.1.1-itrng-log-ocp-lock-1
688 KB
sha256:93ffe1515328b0e27ef24415f9766db36268601ae08678c9c1dccc92e3ecdba8
caliptra-test-results-fpga-realtime-rom-2.1.1-itrng-log-ocp-lock-2
627 KB
sha256:23dc730bf55b551e8995b5fea59a0f8c5a4d4a0d2d5bac06e3549d19ca76f001
caliptra-test-results-fpga-realtime-rom-2.1.1-itrng-nolog--1
497 KB
sha256:6d289a465d2f14c37179de5ce6a0235113dddcde3f4c369e5fc9204965069cf5
caliptra-test-results-fpga-realtime-rom-2.1.1-itrng-nolog--2
341 KB
sha256:8c902c07d032e942e89efe7da0af0387d88bb474b51fc7d1e3a75eec7a08e533
caliptra-test-results-fpga-realtime-rom-2.1.1-itrng-nolog-ocp-lock-1
497 KB
sha256:3f6a5a5f3c2f99c983fab4716c86c25654f49757f9a444da8a96c725da72b9bd
caliptra-test-results-fpga-realtime-rom-2.1.1-itrng-nolog-ocp-lock-2
342 KB
sha256:f00fb7ea5697fb5fba67aa0b8eb251ff54e335427a62fff77d21f46b7ca31d59
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog---1
524 KB
sha256:214a86c9003629a6946ef478a961a25b7512681df2009e14d0b1a8feca5e595c
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog---2
342 KB
sha256:99506c0f925695f237205dc472d1a818e5b9471d082da780639c37c8b1df155a
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog---3
501 KB
sha256:7a5f599f88f1c2b6c42ab0d4476f96cdea3aeae7ae675f01801fb18a77d8ee06
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog---4
437 KB
sha256:40e75b47e12f1cc73532ef9703f8913f85d042564bfe2795bf0702a28ae203d3
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot-1
556 KB
sha256:9182b60a5c35e1640759b63d7c6dadfa4135fb3639393777ddd1cff261ad7fc1
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot-2
379 KB
sha256:40d04efa34cbb96e2617e8983e74335dde3289b08b7ac6b39045f7784ad8f623
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot-3
539 KB
sha256:37db1bc8a508a2d1cbead249cc117ee858a70dd207659ffa64faf80eb9a1a692
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot-4
475 KB
sha256:c9597c171c189198dbaed6e5dc85820e1e73db13c3be2f1951d2d286ff101cb8
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock--1
523 KB
sha256:342e7cc4c79147a76fb74022dc9c88a1a4927a9c769f642a6f44813e1bf12d6f
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock--2
346 KB
sha256:7e0472e19d591c965dd9bce80a91706ff778443b498cf3b286bcaceb8f49029f
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock--3
502 KB
sha256:f9056cecceac3fd1fa8d1a547a7744f40c1cf094f88f3c8828abc9bdd6a60471
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock--4
434 KB
sha256:370a257f7247b1df56aeec09c80ec90ef142e8f9c21a1f1c4b5f22f7f255333e
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot-1
557 KB
sha256:00f274923b272745dab1af477a9764f7b415a6eb5dfe4e49da601fe6583190cf
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot-2
377 KB
sha256:b131cdcd0796c4b94ddbbfc4e422b5adb206fd1e87807507b3f32adcba882191
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot-3
545 KB
sha256:221e2033d8a60f1fdd8ce4da60c9cddf43a1312cf71c1ade067d392dff6126e7
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot-4
471 KB
sha256:a7b01f0c89ca3f1b6cafcae8357ddebd1a47487cdd2bb754e2d0960f1c7f57ae
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog---2
347 KB
sha256:4bb62299bcf66b1bec64e4cb1069c937403a5f2d7942d78e48a7acac1e31fc25
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog---3
499 KB
sha256:1d2025a08d9016df8faa69d5a8473f70644d916b3ecc9b23c5d0d8165e104127
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog---4
434 KB
sha256:1e584ff28a993c4c0559dcca49aad48c0cb5de395d49bc07e1c187c0504cf11d
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog--flash-boot-2
375 KB
sha256:8d386c80abb719111759d19dbff21f2df31e1fd88d91348eb3f6339bfcf37224
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog--flash-boot-3
538 KB
sha256:aa16f079e061b9b42012dd15828f91aede2f885086e64d55fba0bbb2e7ddf550
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog--flash-boot-4
472 KB
sha256:63c44e43e21a65b65c9c4c97c299a4cf047e21e44a328c58fce6329a92241d22
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock--1
526 KB
sha256:c4930b582c143c271b9b11cfbb50c9f6e2e24558b86869e68a895c3a0d7a8193
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock--2
342 KB
sha256:da1a81bbe09dd80c6dad3a0bed93836d0f7c0f3052e0519debd4ddbcabd4d6d5
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock--3
500 KB
sha256:203eaf981d2f64c3cb2a70a6587f8486efdc81892382e3384aa1fa02010b4252
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock--4
436 KB
sha256:c24e36031922da49461ff8a202e610fb3350ab720016281a9c722ccccf4c6ceb
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock-flash-boot-1
560 KB
sha256:b9bc76103bcd3201c680b5f3283c7e877be86bfce22e2882250d73b1ec07bf55
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock-flash-boot-2
380 KB
sha256:d06a32edee5002ddd4d5647e540b096b035f35a74770cbdd33604e7876744ae0
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock-flash-boot-3
543 KB
sha256:728e0731df3cc815d08b7ba29525ff05a7218a331be29212bb82e7ca52ca0b5e
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.0-itrng-nolog-ocp-lock-flash-boot-4
472 KB
sha256:2b4f633647c5e6b286c70001b9c9ad728e721e119b4dc8f0fb2e973041a6ce1f
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog---1
524 KB
sha256:2b1ae6787924a9b1b662974589fda172750f37c8a9defa603c32a40af4f2ae35
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog---2
348 KB
sha256:86773e0f45a612ff3d4ef104cf9090193797b9091e80ee005a029f612d2cd3db
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog---3
503 KB
sha256:8a7251023f957e8b80d326da196557feaf95586ec5e5363e5194d96a03548831
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog---4
437 KB
sha256:4c9df9e50d0e3741cd4159b861a352aed78e810586a57ec6e6ae7cb1c8cab7e9
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog--flash-boot-1
559 KB
sha256:d70ed5e5590cdb2f097815ffe223e07cf11da5818e58c561632130e90ffe34a0
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog--flash-boot-2
378 KB
sha256:a2e5a5851286299320d863309017479b9cfa2cc6b9f11f778f35578b0f5487d1
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog--flash-boot-3
539 KB
sha256:109eec8a36acf46ed91e75e6665f65c70c3be52ef926952d1e3c7146fb906091
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog--flash-boot-4
479 KB
sha256:6ae8e9f0476c03ff9fc55108b00ea46939f5a062bec4cb7335475f19273e7e47
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock--1
521 KB
sha256:752fa55b7b942930d52ed4fe42d97684913fe954511f1df3c81013e3299c3e5b
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock--2
344 KB
sha256:88f1a17d421367d2753605737bfc606f931da36f6c5a8f61904690a0aa21a5e6
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock--3
501 KB
sha256:faa940fcc72a078ab187c4441d3ad14719f3d0ec2121ec36b6bd17f99b13ac42
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock--4
437 KB
sha256:2659df624b8c3132839831b5c22ccf919dfcf84ae265a49080bdeb11696f2017
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock-flash-boot-1
556 KB
sha256:def7f43d7e0739e5d4bd18133d9ef2b869bd4eccdeee83014d674a93c9ef18ce
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock-flash-boot-2
380 KB
sha256:e38f8433a49ab24d926e75f2c8650bf8189998de1533b161c650455a15a23b70
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock-flash-boot-3
538 KB
sha256:75243b0ff4995e5600798b487ce2b1620ab2ee38ab288e6c017c583950b19b99
caliptra-test-results-fpga-subsystem-realtime-rom-2.1.1-itrng-nolog-ocp-lock-flash-boot-4
477 KB
sha256:8968cede77f31474c1e2cd36d443ac50ba0c95304fbb001a6457a622f3173d5e
caliptra-test-results-sw-emulator-hw-latest-etrng-log
1.47 MB
sha256:0e559e2b726f2aee12e63b8535b1d9bd60e644d4595d540d894136386d897e0e
caliptra-test-results-sw-emulator-hw-latest-etrng-nolog
919 KB
sha256:1c9ab7c9aeab337453309906d2468dc360ba9e8b43fbfc8bca2e61c6a84b3698
caliptra-test-results-sw-emulator-hw-latest-itrng-log
1.46 MB
sha256:7a92711f5feaed46c0f542f70c4ecc332317c21530dd772c4b5d513d558c9f8c
caliptra-test-results-sw-emulator-hw-latest-itrng-nolog
919 KB
sha256:b1274012287a6490e0ad5cefe571a93765aced6c93cf14bd34b26617e07fc7c1
caliptra-test-results-sw-emulator-rom-2.1.0-etrng-log
1.43 MB
sha256:b7ef2f3bce26c935489720a5c730d45b482e2e8ab975796c20ab9c629f9c60b9
caliptra-test-results-sw-emulator-rom-2.1.0-etrng-nolog
915 KB
sha256:eb69491074be666755f4d8b39783bfb57c439c7c0b35dd7b2b9aec754be4fc87
caliptra-test-results-sw-emulator-rom-2.1.0-itrng-log
1.44 MB
sha256:d43cc763356efecf4c06050f9197be8bf66483f343363574b3c4d24bcee023ac
caliptra-test-results-sw-emulator-rom-2.1.0-itrng-nolog
917 KB
sha256:7fba1b92459a5837f37704c266d2e5dfa23eb32a8a77f6e200fe95b04cb44649
caliptra-test-results-sw-emulator-rom-2.1.1-etrng-log
1.46 MB
sha256:04d56cf39dc928599f4288af9c9dea0f9251303d7f634794894b5273d6299dc2
caliptra-test-results-sw-emulator-rom-2.1.1-etrng-nolog
917 KB
sha256:25f44bfd9fd1a1b9e9fd0cf0eb021f7261f2fe79b10350e014448d655f240a68
caliptra-test-results-sw-emulator-rom-2.1.1-itrng-log
1.46 MB
sha256:6858da63aeef181b602b9138fa967aa231bb995c9c9338d66c078a135d03423e
caliptra-test-results-sw-emulator-rom-2.1.1-itrng-nolog
917 KB
sha256:3c4d912a8a36b02346a42a1899eaebf7609cfbc7be0d522c9c7f38e33df492a5