Skip to content

Subsystem FPGA Build #3989

Subsystem FPGA Build

Subsystem FPGA Build #3989

Triggered via merge group June 13, 2026 15:00
Status Success
Total duration 1h 1m 0s
Artifacts 7

fpga-subsystem.yml

on: merge_group
check_cache
36s
check_cache
build_test_binaries
28m 5s
build_test_binaries
check_mcu_commit
3s
check_mcu_commit
Matrix: test_artifacts_subsystem
print_test_results
27s
print_test_results
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
build_test_binaries
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v3, actions/cache/save@v3, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build_test_binaries
Cache save failed.
build_test_binaries
Failed to restore:
test_artifacts_subsystem (2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test_artifacts_subsystem (4)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test_artifacts_subsystem (3)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test_artifacts_subsystem (1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
caliptra-bitstream Expired
19.9 MB
sha256:2cf878255d09e0318d50bb036c20ca4f318d7c0f51c04afa654545d1c0cf5b46
caliptra-test-binaries Expired
84 MB
sha256:cb31309a9788be91e0a0a1b52e652b2519020a2b4c2968172449d30727815f34
caliptra-test-firmware Expired
26 MB
sha256:f53e7aeadfc90d89fd432750c7ad027ead9696cab8fe3e6cc8de56d631772a9e
caliptra-test-results-1
490 KB
sha256:78babc643ffba2307b3b3caf4cfba43ab950418bbbe90a0219bede9c45122ac5
caliptra-test-results-2
508 KB
sha256:ba40209a09903461748a49ded4a96930e3d97bb0ac57847b0e74c93f241e7cf3
caliptra-test-results-3
497 KB
sha256:192dc1ceb6fcde8640d89a1f9d29c7120ebc75f8928b17366db70979807ea0a7
caliptra-test-results-4
453 KB
sha256:b4bf4e0176242261a6be66cd264f3ad8cb2f03d40225b40cc7b185986031000f