Nightly Release 2.x #936
github-merge-queue[bot]nightly-release.yml
on: schedule
Find Latest Release 2.x
27s
Matrix: fpga-subsystem
Matrix: fpga
Matrix: sw-emulator
Publish https://caliptra-sw.github.io/
/
deploy
Annotations
4 errors and 120 warnings
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / test_artifacts_subsystem (3)
Process completed with exit code 100.
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (2)
Process completed with exit code 100.
|
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / test_artifacts_subsystem (2)
Failed to CreateArtifact: Unable to make request: ETIMEDOUT
If you are using self-hosted runners, please make sure your runner has access to all GitHub endpoints: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners#communication-between-self-hosted-runners-and-github
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), ) / test_artifacts_subsystem (4)
Process completed with exit code 100.
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), ) / build_test_binaries
Cache save failed.
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), ) / build_test_binaries
Failed to restore:
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
|
|
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), flash-boot) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
|
|
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
|
|
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (hw-latest, itrng, nolog, ocp-lock) / build_test_binaries
Cache save failed.
|
|
FPGA Suite (hw-latest, itrng, nolog, ocp-lock) / build_test_binaries
Failed to restore:
|
|
FPGA Suite (rom-2.1, itrng, log, ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.1, itrng, log, ) / build_test_binaries
Cache save failed.
|
|
FPGA Suite (rom-2.1, itrng, log, ) / build_test_binaries
Failed to restore:
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), flash-boot) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
|
|
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (hw-latest, itrng, log, ) / build_test_binaries
Cache save failed.
|
|
FPGA Suite (hw-latest, itrng, log, ) / build_test_binaries
Failed to restore:
|
|
FPGA Suite (rom-2.1, itrng, nolog, ocp-lock) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.1, itrng, nolog, ocp-lock) / build_test_binaries
Cache save failed.
|
|
FPGA Suite (rom-2.1, itrng, nolog, ocp-lock) / build_test_binaries
Failed to restore:
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
|
|
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (hw-latest, itrng, nolog, ) / build_test_binaries
Cache save failed.
|
|
FPGA Suite (hw-latest, itrng, nolog, ) / build_test_binaries
Failed to restore:
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (hw-latest, itrng, log, ocp-lock) / build_test_binaries
Cache save failed.
|
|
FPGA Suite (hw-latest, itrng, log, ocp-lock) / build_test_binaries
Failed to restore:
|
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / build_test_binaries
Cache save failed.
|
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / build_test_binaries
Failed to restore:
|
|
FPGA Suite (rom-2.1, itrng, log, ocp-lock) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.1, itrng, log, ocp-lock) / build_test_binaries
Cache save failed.
|
|
FPGA Suite (rom-2.1, itrng, log, ocp-lock) / build_test_binaries
Failed to restore:
|
|
FPGA Suite (rom-2.1, itrng, nolog, ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.1, itrng, nolog, ) / build_test_binaries
Cache save failed.
|
|
FPGA Suite (rom-2.1, itrng, nolog, ) / build_test_binaries
Failed to restore:
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), ) / build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
|
|
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sw-emulator Suite (2.1, etrng, nolog) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (hw-latest, itrng, nolog, ocp-lock) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sw-emulator Suite (2.1, itrng, nolog) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sw-emulator Suite (2.1, etrng, log) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
sw-emulator Suite (2.1, itrng, log) / build_and_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.1, itrng, log, ) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (hw-latest, itrng, log, ) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ocp-lock), flash-boot) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), ) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.1, itrng, nolog, ocp-lock) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (hw-latest, itrng, nolog, ) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (hw-latest, itrng, log, ocp-lock) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.1, itrng, log, ocp-lock) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), flash-boot) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ocp-lock), ) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Suite (rom-2.1, itrng, nolog, ) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ), flash-boot) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), flash-boot) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (hw-latest, itrng, nolog, ), ) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.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/download-artifact@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
FPGA Subsystem Suite (rom-2.1, itrng, nolog, ocp-lock), ) / print_test_results
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
caliptra-bitstream-fpga-realtime-latest-itrng-log-
Expired
|
14 MB |
sha256:36da8ad6278a4d518dcc2b39dc141834e2cc8d53b002af847fefc5a2184cf72d
|
|
|
caliptra-bitstream-fpga-realtime-latest-itrng-log-ocp-lock
Expired
|
14 MB |
sha256:4c2afbb602b040f4c758248ad688fabdfda9a12ccc6dfb2cca096b7ae05bb3b5
|
|
|
caliptra-bitstream-fpga-realtime-latest-itrng-nolog-
Expired
|
14 MB |
sha256:28ba8ab9359cded15e6ec61b2b6269d59bda4d2e87ec8969a874353252c63630
|
|
|
caliptra-bitstream-fpga-realtime-latest-itrng-nolog-ocp-lock
Expired
|
14 MB |
sha256:9ca7cce83ea3242d76b34869fcfbd9b20dcee87530e9a9c1a087cd1632865040
|
|
|
caliptra-bitstream-fpga-realtime-rom-2.1-itrng-log-
Expired
|
14 MB |
sha256:a115160ce6ba9a69e391c99359c1385e7cf38a282899be9a486602bc90b4ace2
|
|
|
caliptra-bitstream-fpga-realtime-rom-2.1-itrng-log-ocp-lock
Expired
|
14 MB |
sha256:3226222fb319bf5f94de6120b479b057d1e0485e144f2872ff8d7ecb46813b25
|
|
|
caliptra-bitstream-fpga-realtime-rom-2.1-itrng-nolog-
Expired
|
14 MB |
sha256:0cf247090ecde2a93057d29a5ac7950ac6436e9cbc32e3353ea20b59849bb52e
|
|
|
caliptra-bitstream-fpga-realtime-rom-2.1-itrng-nolog-ocp-lock
Expired
|
14 MB |
sha256:ad2b1a63b5a254f399a42866b9e8b4e9c7cefcc045a8950571b6ff2570508bfd
|
|
|
caliptra-bitstream-fpga-subsystem-realtime-latest-itrng-nolog--
Expired
|
18.8 MB |
sha256:75a8ca7a477690a2afd7c25b7c85122ccd2b308427750a3c96faa3cbd04eea30
|
|
|
caliptra-bitstream-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot
Expired
|
18.8 MB |
sha256:6be78dbd130b5da578f940e05d51c900def11990f55e0416f7173d89c1039155
|
|
|
caliptra-bitstream-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-
Expired
|
18.8 MB |
sha256:d26418c5bd2948ee306a6e39e4e6ea35d6a2c2215f3a82fa8e56190ad49d4fa7
|
|
|
caliptra-bitstream-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot
Expired
|
18.8 MB |
sha256:fc13622aee57a974540718659bca9cf033e7ed207a7baf01216b421a55350529
|
|
|
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1-itrng-nolog--
Expired
|
18.8 MB |
sha256:24a5dfbaf08459a7aa741744ec6fe7eea033108d251c0e15f7fbbe09d02e38c5
|
|
|
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1-itrng-nolog--flash-boot
Expired
|
18.8 MB |
sha256:d32769fc543d7a9cc452c6bc33e151ffdabeab78584ab03a70296d45deae75e9
|
|
|
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-
Expired
|
18.8 MB |
sha256:31082fec532374e8e48578387ec44164e14afcd839197561b15fce5dba1f6ba0
|
|
|
caliptra-bitstream-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-flash-boot
Expired
|
18.8 MB |
sha256:24a5dfbaf08459a7aa741744ec6fe7eea033108d251c0e15f7fbbe09d02e38c5
|
|
|
caliptra-test-binaries-fpga-realtime-latest-itrng-log-
Expired
|
78.9 MB |
sha256:b1834b5100d132bb68a36606d3ff62934198f3f9e473b273f53cd4d5b27b4b67
|
|
|
caliptra-test-binaries-fpga-realtime-latest-itrng-log-ocp-lock
Expired
|
78.9 MB |
sha256:c5440c5f334368efe6a96a483b8f4145c7e400c97a714ec0e5c8e8d263aeb3dc
|
|
|
caliptra-test-binaries-fpga-realtime-latest-itrng-nolog-
Expired
|
78.9 MB |
sha256:7eb258d2ad1615f2077afb4ae9cdfc706a4800d117ad0e37aee9a9584148513b
|
|
|
caliptra-test-binaries-fpga-realtime-latest-itrng-nolog-ocp-lock
Expired
|
78.9 MB |
sha256:b4dd787a293f34cfc74ea5a74748c4b8a3941c80fad4bf406422bfd1ece55cf6
|
|
|
caliptra-test-binaries-fpga-realtime-rom-2.1-itrng-log-
Expired
|
78.9 MB |
sha256:0863606b61c1d827db6ae0ca094ab2d20592d85b5570275bff596396f560583b
|
|
|
caliptra-test-binaries-fpga-realtime-rom-2.1-itrng-log-ocp-lock
Expired
|
78.9 MB |
sha256:60047c3de57218793f30d34b5b8a4005b1dd7b6bd5df251e786e09a3ffa25942
|
|
|
caliptra-test-binaries-fpga-realtime-rom-2.1-itrng-nolog-
Expired
|
78.9 MB |
sha256:1684b7134a6aa1c6aa3af0acdc4d4a7c6ea94617dea164f6bac26ecdf0da2e22
|
|
|
caliptra-test-binaries-fpga-realtime-rom-2.1-itrng-nolog-ocp-lock
Expired
|
78.9 MB |
sha256:d0d92a5240e4ea09775b3088cd78229ced957ac27138966f4b73dadfc28d1afb
|
|
|
caliptra-test-binaries-fpga-subsystem-realtime-latest-itrng-nolog--
Expired
|
79.4 MB |
sha256:d6fcce15b9b98577e160c1d4f0c90bfb797bacec6b69fb234250bc5ca30c27ef
|
|
|
caliptra-test-binaries-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot
Expired
|
79.5 MB |
sha256:b9d70660635d2316bce6a1a378923b0c6e81df5b6ff9228d552b57972f28a1ef
|
|
|
caliptra-test-binaries-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-
Expired
|
79.4 MB |
sha256:fc05c8c18f6d6d6977f1cb9a957ddb7830559194e6c6d2d64020eefc4a692394
|
|
|
caliptra-test-binaries-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot
Expired
|
79.4 MB |
sha256:de8aa56d62850ab7b55a321636f548dc6e144fd8a7b713eb55ce0b9cab936c0b
|
|
|
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1-itrng-nolog--
Expired
|
79.4 MB |
sha256:224851ee2a16beffa815aeb0dc018fb855f1519e0f424a03483f0381165de22b
|
|
|
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1-itrng-nolog--flash-boot
Expired
|
79.5 MB |
sha256:fb80baf3d13d670def1d8eb7664551be3bed5b56640b26b9f153e307f961efaf
|
|
|
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-
Expired
|
79.4 MB |
sha256:a575b8d75b398533c7b09fe32cbbe0851400413db9b91ed4fff8b0abfb341688
|
|
|
caliptra-test-binaries-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-flash-boot
Expired
|
79.4 MB |
sha256:020e73e41d692fed21d99925d4916826e6891c92a2d0eb464874a06b487e25f7
|
|
|
caliptra-test-firmware-fpga-realtime-latest-itrng-log-
Expired
|
25.4 MB |
sha256:54d603e2d2cbfce61fedcfcc3548111e8da44cd7c203608aeffaf126a27bcb24
|
|
|
caliptra-test-firmware-fpga-realtime-latest-itrng-log-ocp-lock
Expired
|
25.4 MB |
sha256:d9a6a82481ed891a52003c175b8c47b05db4b8ba543cb97d2457e95835e6ecc4
|
|
|
caliptra-test-firmware-fpga-realtime-latest-itrng-nolog-
Expired
|
25.4 MB |
sha256:ebdc206a1d7df2cdba90ce5b1f2f14ba5185ee8593eec9d76235db08fbbd9541
|
|
|
caliptra-test-firmware-fpga-realtime-latest-itrng-nolog-ocp-lock
Expired
|
25.4 MB |
sha256:9ecce02c4a2a21ad552e85562052a71545bb938b08146be8759e90870b2f1b9d
|
|
|
caliptra-test-firmware-fpga-realtime-rom-2.1-itrng-log-
Expired
|
25.4 MB |
sha256:f713ad769fd7ccaef8d043786c41772bed55374ab38ec5576ed7630d69b09ad5
|
|
|
caliptra-test-firmware-fpga-realtime-rom-2.1-itrng-log-ocp-lock
Expired
|
25.4 MB |
sha256:cd27bcd52313451cafe199d38ede491fec055ecea524c071a58c606f24e6663f
|
|
|
caliptra-test-firmware-fpga-realtime-rom-2.1-itrng-nolog-
Expired
|
25.4 MB |
sha256:3e58a91cc878162a4e0e804aaf4af3920e282fcddb6b5ac324c73be72b2b9d3c
|
|
|
caliptra-test-firmware-fpga-realtime-rom-2.1-itrng-nolog-ocp-lock
Expired
|
25.4 MB |
sha256:ecabb134745810a26536af6417d08f566986ca233098c95c23d27186678aa71e
|
|
|
caliptra-test-firmware-fpga-subsystem-realtime-latest-itrng-nolog--
Expired
|
25.5 MB |
sha256:745201cf67ebb16129cdb2b63b6f1317eff64a96accb728fa3d59841ed457335
|
|
|
caliptra-test-firmware-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot
Expired
|
25.5 MB |
sha256:0a474a2a9133f25bfa3c82cf08ff0d6c8dddbc7a7fe557c6b9f81a9e59d28a5b
|
|
|
caliptra-test-firmware-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-
Expired
|
25.5 MB |
sha256:648fc4ebb418e81cd62b14aa41c7b87cebd25d6aae3da36832570142d52bcfa5
|
|
|
caliptra-test-firmware-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot
Expired
|
25.5 MB |
sha256:4379da342ea7105736d60bc64a718d42b58d617a265cd719079094c211a60be4
|
|
|
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1-itrng-nolog--
Expired
|
25.5 MB |
sha256:53a8615ae1aa73ce0363e82736fed01093f830fcdc1796c6ef554001b42cdcc7
|
|
|
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1-itrng-nolog--flash-boot
Expired
|
25.5 MB |
sha256:ceb84964c89443e01af6bb9f79b4b0dee940b3227d3bb6eb04e496ee47bd0969
|
|
|
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-
Expired
|
25.5 MB |
sha256:51efe33456cd5231195106769872b2367b0ad85e1119147b15a4583691a61263
|
|
|
caliptra-test-firmware-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-flash-boot
Expired
|
25.5 MB |
sha256:5638de98f806706516ab73704ca8c60b8f4908dc74e1f719040a41851e730180
|
|
|
caliptra-test-results-fpga-realtime-latest-itrng-log--1
|
536 KB |
sha256:220e587d963819a8adc217dd023138095640f70e9ba8f6ad27e2dc3444d39ff0
|
|
|
caliptra-test-results-fpga-realtime-latest-itrng-log--2
|
722 KB |
sha256:1f52877180f3adde608b3a36236c013b52d4de7d2cba0f5faa8b980b33dd6fe7
|
|
|
caliptra-test-results-fpga-realtime-latest-itrng-log-ocp-lock-1
|
536 KB |
sha256:cbc98b62b7f232fdef8d8de0a45739796068675ae22c883676ad0c47b12cf09a
|
|
|
caliptra-test-results-fpga-realtime-latest-itrng-log-ocp-lock-2
|
722 KB |
sha256:741a715f4c307d2228052b2ffe97e93ab3d331e17f3d90ce53d701912eb07cd8
|
|
|
caliptra-test-results-fpga-realtime-latest-itrng-nolog--1
|
377 KB |
sha256:cbb773c20e659f13b42145ed38f9228a4b7efbff8ea676ee9981cb909d5f4555
|
|
|
caliptra-test-results-fpga-realtime-latest-itrng-nolog--2
|
418 KB |
sha256:bf254d728bddf4ccffa5c787d2ddd16c3d6c35ea22f5ebe25c7b7e5f98dc6cb5
|
|
|
caliptra-test-results-fpga-realtime-latest-itrng-nolog-ocp-lock-1
|
376 KB |
sha256:27194cf0586a1ad506f01a2d1177d9426365b50d1392ff39ae371b686f53f822
|
|
|
caliptra-test-results-fpga-realtime-latest-itrng-nolog-ocp-lock-2
|
418 KB |
sha256:340c318813437b4f31d566d66750c0ce3380ff3b8a3d106d0185be5e06dc1193
|
|
|
caliptra-test-results-fpga-realtime-rom-2.1-itrng-log--1
|
530 KB |
sha256:8a0c45c1a9fbb805d4c127b5f2fb1c53cbb53f032587cf2fadfa4d12010e2ffa
|
|
|
caliptra-test-results-fpga-realtime-rom-2.1-itrng-log--2
|
707 KB |
sha256:54ce70e13fe4e1ce899022c4e81e880f197592f88fce0a1c939f3018e1dd80d8
|
|
|
caliptra-test-results-fpga-realtime-rom-2.1-itrng-log-ocp-lock-1
|
530 KB |
sha256:2175904fa1561e6535293cc39480c9977c49aa9328b37e3d01255b7698172fb1
|
|
|
caliptra-test-results-fpga-realtime-rom-2.1-itrng-log-ocp-lock-2
|
708 KB |
sha256:b84fc1385c0cde486a9324c566494592d890e91256ff2904065e58f7aa13763e
|
|
|
caliptra-test-results-fpga-realtime-rom-2.1-itrng-nolog--1
|
377 KB |
sha256:c8d88a25c139a9ad1ee303ea2bbcab70ef798811e4f2cc14419cd8ccc7adb7d8
|
|
|
caliptra-test-results-fpga-realtime-rom-2.1-itrng-nolog--2
|
418 KB |
sha256:a085ffc203683a13713ccab86c716eb8c828f1a4bbea3f5adbd450815a157407
|
|
|
caliptra-test-results-fpga-realtime-rom-2.1-itrng-nolog-ocp-lock-1
|
376 KB |
sha256:d0532e264fc889e4fd37b7dabe5d4143d61fdbb2d9e06fe2a9337b1ff5292f70
|
|
|
caliptra-test-results-fpga-realtime-rom-2.1-itrng-nolog-ocp-lock-2
|
418 KB |
sha256:03b637db3c0fb53729052f04accc7d7bcf5a02fa2e52b6193fe568b8ba3f9385
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog---1
|
415 KB |
sha256:699da85728a029bd32ff3242b8e40153e45416a7f2b3465e630c972e90ee2d85
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog---3
|
34.1 KB |
sha256:d900350b7561828c87c02cfbacf619687895121922532c3325ee01921745f836
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog---4
|
264 KB |
sha256:7f288cd226bd2d5e3574688bd2b3a68083ad311febc8af320c6dcaf95a3978a4
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot-1
|
443 KB |
sha256:1b49553c735fe657d8ecef05812d8339501afb5c11ee51e354a78df14aa01abc
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot-2
|
405 KB |
sha256:73be6d073641f5cf9aded04e03e677b95bda3ca236fabfb3564ce1dcb4c78e2c
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot-3
|
484 KB |
sha256:96a120fb9f643d82ae0c882a813f87fefc02459a9823ec0e7acef024aec8948a
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog--flash-boot-4
|
289 KB |
sha256:14774b699ad685673122edb8274ea3d80fa25a6090ace6333497d0e1c5f2847c
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock--1
|
417 KB |
sha256:e415d33174bd23728a55179e9e081233ef998f9aa3ea12f4e7d9a6acb8b8a9b0
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock--2
|
380 KB |
sha256:875b60b61061917e6a1d14c874f9da9d31f212a76a090882d43ca092831d6b35
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock--3
|
458 KB |
sha256:9b33b7104161a4798bd8b872d658a1bec2e384f9935666f884311d4afc43d501
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock--4
|
262 KB |
sha256:328ae5191e6097eb645e38ac45124615accdc61915235ea03d8a480e2eb2fa2c
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot-1
|
443 KB |
sha256:13d48babfef2d27c4920f198565502a09654c9f6106d46c82e9550e3d1388060
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot-2
|
407 KB |
sha256:2ec389d521628b3d0748233661d3a3799d05d0437be551442253cc6a87e4c54e
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot-3
|
484 KB |
sha256:831a93837b4f308ed8bf036658f4d0bc728629e6c138cf169252fd34e7524c34
|
|
|
caliptra-test-results-fpga-subsystem-realtime-latest-itrng-nolog-ocp-lock-flash-boot-4
|
285 KB |
sha256:341536a322bfaf859ce42c0198dce6667a1573e6acc60523059559fbfd5cc800
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog---1
|
416 KB |
sha256:eccac86345257dd60cc2a1278aabd2cb9033a2d2ba0783c4484ddb027dd0dcb5
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog---2
|
381 KB |
sha256:4ef1b180f82f33e1d147d241557128e9b71908a4d4b88957a90739caa161129b
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog---3
|
458 KB |
sha256:97432f8e06d106f6c379a271cde13950c906e4d888ca5e6bf8446d43af1de714
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog---4
|
263 KB |
sha256:3b9fd9b4c461dc7dd0c07b6c2a47cd4c4726735e5cbdf3ab6a8729674f4bee18
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog--flash-boot-1
|
442 KB |
sha256:abebd7174c0e17fabd7e3b99a10f7da7b5dad9768d10d4b0edc19e915daa08da
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog--flash-boot-2
|
405 KB |
sha256:67de6c3418c076fe6dc7a14538d404fd63a41aadfe4b18bd423027e6cd38c35f
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog--flash-boot-3
|
486 KB |
sha256:f2f114e9780c5da083072a99eab3e79a55fae3d0b3bb1e34f8c0ed4a333571d7
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog--flash-boot-4
|
295 KB |
sha256:57395ef681a43d9459ae8c99c78f4c94a0970d28bcbeead232835a5d467dc32c
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock--1
|
415 KB |
sha256:99f9506feae9e25ed43e69e5defd357c0aecb1f188b3b24c5e6a5db6f6337c97
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock--2
|
32.7 KB |
sha256:fe877eb77e7e6ec630cf46fb9f98a586fc83e65f1ab61034d61220271d3c448e
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock--3
|
456 KB |
sha256:ddc25b4ae265adaab283527a849c51aee0f858ec3ebfea2beb37a51e15602dd6
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock--4
|
265 KB |
sha256:c4209fbf6dbb0012e1a75c7f9c58f39e5f25c6c7f87555629d0b4064b75c19fd
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-flash-boot-1
|
447 KB |
sha256:2eba48a01b69e65b0da5b86ae82366163d6ee5e487a7552edc70921cb0f7fcab
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-flash-boot-2
|
408 KB |
sha256:13ce29096eaacc548f4f5c675357bc3a8e1d46a8fc22e6b3c6e8c1e156be5a88
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-flash-boot-3
|
485 KB |
sha256:e0e3fb3dc1e86471b1634485e928c104afd2e6aea49fc733666341d18c5132ab
|
|
|
caliptra-test-results-fpga-subsystem-realtime-rom-2.1-itrng-nolog-ocp-lock-flash-boot-4
|
286 KB |
sha256:506d8b10a04cab50b1087ebf9b8768d450b8c676ae66ed1adab8fe47db094d60
|
|
|
caliptra-test-results-sw-emulator-hw-latest-etrng-log
|
1.41 MB |
sha256:b35aada6f5b06d8a86ec0fc28c3e695d87a914f8a4273b1ac114fd0866e5aa73
|
|
|
caliptra-test-results-sw-emulator-hw-latest-etrng-nolog
|
872 KB |
sha256:64482bf48a5e10083da65c8c16f50d71cae718060cbcdbeb617a19c52b8a5862
|
|
|
caliptra-test-results-sw-emulator-hw-latest-itrng-log
|
1.4 MB |
sha256:34f7d307bda325c2d8ef5a98835ba5a51209853159b36e16a4269c23fe4489f1
|
|
|
caliptra-test-results-sw-emulator-hw-latest-itrng-nolog
|
872 KB |
sha256:9e845b995ab120fea4a85a1d1cfe7631484c9aceaf516515aa4def3e89458aa6
|
|
|
caliptra-test-results-sw-emulator-rom-2.1-etrng-log
|
1.38 MB |
sha256:aa40b4e9a13e6b2a0b09f5026676b15aa4bf2fdbdb9f26cfdec3a327d3c9401d
|
|
|
caliptra-test-results-sw-emulator-rom-2.1-etrng-nolog
|
874 KB |
sha256:aeb4a18548251e5a539cc68f9ee7c2ae2187d6958d94d76823e310fa21de076e
|
|
|
caliptra-test-results-sw-emulator-rom-2.1-itrng-log
|
1.38 MB |
sha256:18dd9d5e44cebb0ed11f6dc635f9a0c9728e40c0b35994a48f73c39a16cf1656
|
|
|
caliptra-test-results-sw-emulator-rom-2.1-itrng-nolog
|
871 KB |
sha256:38912730ad4bb2caed2a307b16a80f9c42e359ebf5ff300793baaa49a9fa1bad
|
|