Skip to content
Subsystem FPGA Build

Subsystem FPGA Build #3993

Sign in to view logs

Subsystem FPGA Build

Subsystem FPGA Build #3993

Triggered via merge group June 15, 2026 17:35
@clundin25clundin25
⁠ aaab5f0
Status Success
Total duration 57m 47s
Artifacts 7

fpga-subsystem.yml

on: merge_group
check_cache
39s
check_cache
build_test_binaries
19m 50s
build_test_binaries
check_mcu_commit
4s
check_mcu_commit
Matrix: test_artifacts_subsystem
print_test_results
26s
print_test_results
Fit to window
Zoom out
Zoom in

Annotations

6 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
Failed to restore:
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/
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 (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 (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/

Artifacts

Produced during runtime
Name Size Digest
caliptra-bitstream Expired
19.9 MB
sha256:d73999f403e1ebf5a6c24f409e85ce44a62c9a0bef63b051b674060f202c3ceb
caliptra-test-binaries Expired
84 MB
sha256:3338db741c3cb48564b19dee102396f91a457d50ab130a379adecf7a1b0e5d21
caliptra-test-firmware Expired
26.1 MB
sha256:04bd67db73be2b49a8e822b8f6a0c5a7b5beeb16531575fcabaf0551b7de9575
caliptra-test-results-1
491 KB
sha256:e8c004f9107b6d59e7e71859f7790843cf92698d85c2f7084cc895ace2dd8e25
caliptra-test-results-2
514 KB
sha256:f30ffc190429be5e03f93f70d76eaad1a06a262f40bdda28dae796a05b218911
caliptra-test-results-3
506 KB
sha256:9fa2d09bdfa1f65fc9486906e035e62f480099fedad36453d43db311dae969c4
caliptra-test-results-4
471 KB
sha256:edb227438cb2e9654765d233e97407ecfc653340253e0841a2bfa46821371b96