Make a SDK use_case for w3c #2415
fbeutin-ledgerbuild_and_functional_tests.yml
on: pull_request
Build application using the reusable workflow
/
...
/
Retrieve application metadata
12s
Build Clone app using the reusable workflow
/
...
/
Retrieve application metadata
29s
Build Memory application using the reusable workflow
/
...
/
Retrieve application metadata
13s
Matrix: Build application using the reusable workflow / Build application for all selected devices
Matrix: Build application using the reusable workflow / Build target branch sources for all selected devices
Matrix: Build Clone app using the reusable workflow / Build application for all selected devices
Matrix: Build Clone app using the reusable workflow / Build target branch sources for all selected devices
Matrix: Build Memory application using the reusable workflow / Build application for all selected devices
Matrix: Build Memory application using the reusable workflow / Build target branch sources for all selected devices
Build application using the reusable workflow
/
Merge build artifacts
7s
Build application using the reusable workflow
/
Merge build artifacts (target branch)
8s
Build Clone app using the reusable workflow
/
Merge build artifacts
6s
Build Clone app using the reusable workflow
/
Merge build artifacts (target branch)
0s
Build Memory application using the reusable workflow
/
Merge build artifacts
6s
Build Memory application using the reusable workflow
/
Merge build artifacts (target branch)
0s
Build application using the reusable workflow
/
Report ELF section sizes and post PR comment
14s
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
14s
Run ragger tests using the reusable workflow
/
...
/
Retrieve application metadata
13s
Run Memory tests using the reusable workflow
/
...
/
Retrieve tests metadata
24s
Run ragger tests using the reusable workflow
/
...
/
Retrieve tests metadata
17s
Run ragger Clone tests using the reusable workflow
/
...
/
Retrieve application metadata
14s
Run ragger Clone tests using the reusable workflow
/
...
/
Retrieve tests metadata
22s
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
0s
Run Memory tests using the reusable workflow
/
Merge pytest logs
8s
Run Memory tests using the reusable workflow
/
Merge snapshots artifacts
2s
Run ragger tests using the reusable workflow
/
Merge snapshots artifacts
4s
Run ragger tests using the reusable workflow
/
Post stack consumption summary on PR
15s
Run ragger tests using the reusable workflow
/
Merge pytest logs
0s
Run ragger Clone tests using the reusable workflow
/
Merge snapshots artifacts
5s
Run ragger Clone tests using the reusable workflow
/
Post stack consumption summary on PR
9s
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
6s
Annotations
7 warnings
|
Build application using the reusable workflow / Merge build artifacts (target branch)
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 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 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 / Report ELF section sizes and post PR comment
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
|
|
Run ragger Clone tests using the reusable workflow / Post stack consumption summary on PR
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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/
|
|
Run ragger tests using the reusable workflow / Post stack consumption summary on PR
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@v7. 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_app_stack_consumption-apex_p
|
274 Bytes |
sha256:1131b042f87ffedde367842fb99565383916e2d918680a74b39aa0c9db3d6f69
|
|
|
clone_app_stack_consumption-flex
|
272 Bytes |
sha256:f6961daa4069f469578d11d6b57caef2906ca836ff0a2e8545f8877450670f30
|
|
|
clone_app_stack_consumption-nanosp
|
274 Bytes |
sha256:3e95d2c991789032b98e928a1a8064539ca83217fbb07d17de5f2f0cfc8ea284
|
|
|
clone_app_stack_consumption-nanox
|
274 Bytes |
sha256:299e7091da765899c018e25294b5a0a5f02bced7e58e6a14979983901ea33b9d
|
|
|
clone_app_stack_consumption-stax
|
271 Bytes |
sha256:a851a79332e3574b5e09b38af416ab4fdeb32fb93f6c0aa0d3f24f575ec17790
|
|
|
clone_elfs
|
69.3 KB |
sha256:3289938917b0524c5b575e426d389641c7f0183de06a0eaa01e874d2d9887964
|
|
|
memory_elfs
|
533 KB |
sha256:4a73da36cb68e99a8f1900a00010f6b9b36a0a4241652f66c98acf47f86f4461
|
|
|
pytest-logs-combined
|
418 KB |
sha256:a4e97e59cf27fe6eb381a3d756fdef3d86c3458c1e0aa784c41ade6e67a628c0
|
|
|
pytest-logs-nanox
|
418 KB |
sha256:ae3c8b8e7416d5b30e334b3904f3d613875ab5b1748a61f431e2eb6d3e72f04c
|
|
|
ragger_elfs
|
1.97 MB |
sha256:a87a3a33c86422d1b7c03870c077ffd99d6ebed68c5942bd709ea07d3a62718f
|
|
|
ragger_elfs_target
|
1.96 MB |
sha256:f89f8cbe0a2422c66054562371ebd45ae6c61dc9224944553b50f9cfc191db8d
|
|
|
stack-consumption-summary-apex_p
|
2.26 KB |
sha256:463f6b1fa5ff6b4b3ecb6ac259eee8332e3c61d1b905bfc2f93b1fad3bcdf18f
|
|
|
stack-consumption-summary-flex
|
2.22 KB |
sha256:75b531fe7413a33280db8a77eca000929b721b9cd0124fbb683aa25264a7fbdf
|
|
|
stack-consumption-summary-nanosp
|
2.15 KB |
sha256:017678b91a678f21f314183b6d4ea523ebbe6f1133626b3627cec5232a16ff9e
|
|
|
stack-consumption-summary-nanox
|
2.13 KB |
sha256:fc6415b75e40bdd8f78312ae66ce3c544d0eba70770060de42037674c9a76b02
|
|
|
stack-consumption-summary-stax
|
2.22 KB |
sha256:fdf6588adb740071ee29d7e4312a8e2cd1b4609bb125dc76e2c08fffe8d4c515
|
|