Skip to content
Subsystem FPGA Build

Address test_generate_csr_envelop_stress timeouts #3988

Sign in to view logs

Address test_generate_csr_envelop_stress timeouts

Address test_generate_csr_envelop_stress timeouts #3988

Triggered via pull request June 13, 2026 00:42
@nquartonnquarton
opened #3880
nquarton:csr_stress_test_ss_fpga_workaround
Status Success
Total duration 1h 44m 20s
Artifacts 7

fpga-subsystem.yml

on: pull_request
check_cache
44s
check_cache
build_test_binaries
19m 54s
build_test_binaries
check_mcu_commit
5s
check_mcu_commit
Matrix: test_artifacts_subsystem
print_test_results
28s
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 (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 (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 (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:ab81463e48ef191ac37b5485ed2dcd6b572c23366a6650af4c99ea853c3c6af0
caliptra-test-binaries Expired
84 MB
sha256:2755934eb38d45c8ce25a83e299c4bc63ceb55fce0170513eba4add7c039911e
caliptra-test-firmware Expired
26 MB
sha256:82fd63126bc110316956a4b7d125bf0ff1f0d28705b6d9cc20f2c6b92ce47b39
caliptra-test-results-1
492 KB
sha256:cd8daa50969856a5c7851d9a0aec34e4c891069a897e78a4879f30d6c4fd33b2
caliptra-test-results-2
509 KB
sha256:a08701516f0dff8918711157d0efa8ac88baa9c563d2be3ca5e14e78cfe7b5a8
caliptra-test-results-3
495 KB
sha256:86a37e08aa8394f8d90745538a076fee0072b13d2805582920ab17a5c05d9d56
caliptra-test-results-4
455 KB
sha256:d1665994364dda26bc043fb450721efd77c378c0947f5673bd7ae34701fcf128