Skip to content

Test in OP-TEE Repo #54

Test in OP-TEE Repo

Test in OP-TEE Repo #54

Triggered via schedule April 14, 2026 02:10
Status Success
Total duration 1h 23m 57s
Artifacts

test_in_optee_repo.yml

on: schedule
test-on-amd64-host  /  OPTEE-repo-build-and-run-examples-64bit-TAs
1h 19m
test-on-amd64-host / OPTEE-repo-build-and-run-examples-64bit-TAs
test-on-amd64-host  /  OPTEE-repo-build-and-run-examples-32bit-TAs
1h 23m
test-on-amd64-host / OPTEE-repo-build-and-run-examples-32bit-TAs
test-on-arm64-host  /  OPTEE-repo-build-and-run-examples-64bit-TAs
55m 51s
test-on-arm64-host / OPTEE-repo-build-and-run-examples-64bit-TAs
test-on-arm64-host  /  OPTEE-repo-build-and-run-examples-32bit-TAs
54m 6s
test-on-arm64-host / OPTEE-repo-build-and-run-examples-32bit-TAs
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test-on-arm64-host / OPTEE-repo-build-and-run-examples-32bit-TAs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
test-on-arm64-host / OPTEE-repo-build-and-run-examples-64bit-TAs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
test-on-amd64-host / OPTEE-repo-build-and-run-examples-64bit-TAs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/
test-on-amd64-host / OPTEE-repo-build-and-run-examples-32bit-TAs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@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/