Move away from recursive calls when computing the EIP-712 type_hash #2370
apaillier-ledgerbuild_and_functional_tests.yml
on: pull_request
Build application using the reusable workflow
/
...
/
Retrieve application metadata
19s
Build Clone app using the reusable workflow
/
...
/
Retrieve application metadata
15s
Build Memory application using the reusable workflow
/
...
/
Retrieve application metadata
21s
Matrix: Build application using the reusable workflow / Build application for all selected devices
Matrix: Build application using the reusable workflow / Build application for all selected devices (target branch)
Matrix: Build Clone app using the reusable workflow / Build application for all selected devices
Matrix: Build Clone app using the reusable workflow / Build application for all selected devices (target branch)
Matrix: Build Memory application using the reusable workflow / Build application for all selected devices
Matrix: Build Memory application using the reusable workflow / Build application for all selected devices (target branch)
Build application using the reusable workflow
/
Merge build artifacts
5s
Build application using the reusable workflow
/
Merge build artifacts (target branch)
0s
Build Clone app using the reusable workflow
/
Merge build artifacts
4s
Build Clone app using the reusable workflow
/
Merge build artifacts (target branch)
Build Memory application using the reusable workflow
/
Merge build artifacts
7s
Build Memory application using the reusable workflow
/
Merge build artifacts (target branch)
Build application using the reusable workflow
/
Report ELF section sizes and post PR comment
0s
Build Clone app using the reusable workflow
/
Report ELF section sizes and post PR comment
0s
Build Memory application using the reusable workflow
/
Report ELF section sizes and post PR comment
0s
Run Memory tests using the reusable workflow
/
...
/
Retrieve application metadata
18s
Run ragger tests using the reusable workflow
/
...
/
Retrieve application metadata
15s
Run Memory tests using the reusable workflow
/
...
/
Retrieve tests metadata
18s
Run ragger tests using the reusable workflow
/
...
/
Retrieve tests metadata
14s
Run ragger Clone tests using the reusable workflow
/
...
/
Retrieve application metadata
16s
Run ragger Clone tests using the reusable workflow
/
...
/
Retrieve tests metadata
20s
Matrix: Run Memory tests using the reusable workflow / Functional tests with Ragger
Matrix: Run ragger tests using the reusable workflow / Functional tests with Ragger
Matrix: Run ragger Clone tests using the reusable workflow / Functional tests with Ragger
Run Memory tests using the reusable workflow
/
Post stack consumption summary on PR
Run Memory tests using the reusable workflow
/
Merge pytest logs
6s
Run Memory tests using the reusable workflow
/
Merge snapshots artifacts
2s
Run ragger tests using the reusable workflow
/
Merge snapshots artifacts
Run ragger tests using the reusable workflow
/
Post stack consumption summary on PR
Run ragger tests using the reusable workflow
/
Merge pytest logs
Run ragger Clone tests using the reusable workflow
/
Merge snapshots artifacts
4s
Run ragger Clone tests using the reusable workflow
/
Post stack consumption summary on PR
0s
Run ragger Clone tests using the reusable workflow
/
Merge pytest logs
0s
Run Memory tests using the reusable workflow
/
...
/
Commit new snapshots
Run ragger tests using the reusable workflow
/
...
/
Commit new snapshots
Run ragger Clone tests using the reusable workflow
/
...
/
Commit new snapshots
Process pytest logs
9s
Annotations
4 errors and 3 warnings
|
Run ragger tests using the reusable workflow / Functional tests with Ragger (nanosp)
The run was canceled by @apaillier-ledger.
|
|
Run ragger tests using the reusable workflow / Functional tests with Ragger (nanosp)
The operation was canceled.
|
|
Build and run functional tests using ragger through reusable workflow
The run was canceled by @apaillier-ledger.
|
|
Build and run functional tests using ragger through reusable workflow
The run was canceled by @apaillier-ledger.
|
|
Build Clone app using the reusable workflow / Merge build artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact/merge@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/
|
|
Build Memory application using the reusable workflow / Merge build artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact/merge@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/
|
|
Build application using the reusable workflow / Merge build artifacts
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact/merge@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 | |
|---|---|---|---|
|
clone_elfs
|
69.3 KB |
sha256:ac398c27e1e7b10584766139686779b0a38310d8e210ca45a92e72c96521e256
|
|
|
memory_elfs
|
532 KB |
sha256:3d8ad38ebf2b28424c9167d7af0a5867c832ca28c1a5171056e718765819ff93
|
|
|
pytest-logs-combined
|
415 KB |
sha256:a16cbd875aed367ae99dd40466b3abac2bf94c1c9917c632ebebe9f41e6d7416
|
|
|
pytest-logs-nanox
|
415 KB |
sha256:12e53e3f0f0cfcb450e723aad8605bb42281c09a920ae2c36a2d470cbdc15adc
|
|
|
ragger_elfs
|
1.95 MB |
sha256:5e5170a9216b1bbdaf4a8edce05020ae9a7c7d684d6ed3653341bfc5c968df77
|
|