Skip to content

Lock App CRTP refactor #151085

Lock App CRTP refactor

Lock App CRTP refactor #151085

Triggered via pull request May 8, 2026 03:52
Status Success
Total duration 1h 4m 35s
Artifacts

unit_integration_test.yaml

on: pull_request
Matrix: Unit / Integration Tests
Fit to window
Zoom out
Zoom in

Annotations

15 warnings
Unit / Integration Tests (clang)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, haya14busa/action-cond@v1, pyTooling/Actions/with-post-step@cc576ce25a588e4fd623f3a4ea528f397141e931, Wandalen/wretry.action@v1.4.10_js_action. 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/
Unit / Integration Tests (clang)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Unit / Integration Tests (clang)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Unit / Integration Tests (mbedtls)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, haya14busa/action-cond@v1, pyTooling/Actions/with-post-step@cc576ce25a588e4fd623f3a4ea528f397141e931, Wandalen/wretry.action@v1.4.10_js_action. 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/
Unit / Integration Tests (mbedtls)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Unit / Integration Tests (mbedtls)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Unit / Integration Tests (main)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, haya14busa/action-cond@v1, pyTooling/Actions/with-post-step@cc576ce25a588e4fd623f3a4ea528f397141e931, Wandalen/wretry.action@v1.4.10_js_action. 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/
Unit / Integration Tests (main)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Unit / Integration Tests (main)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Unit / Integration Tests (rotating_device_id)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, haya14busa/action-cond@v1, pyTooling/Actions/with-post-step@cc576ce25a588e4fd623f3a4ea528f397141e931, Wandalen/wretry.action@v1.4.10_js_action. 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/
Unit / Integration Tests (rotating_device_id)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Unit / Integration Tests (rotating_device_id)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Unit / Integration Tests (icd)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: buildjet/cache/restore@v4, haya14busa/action-cond@v1, pyTooling/Actions/with-post-step@cc576ce25a588e4fd623f3a4ea528f397141e931, Wandalen/wretry.action@v1.4.10_js_action. 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/
Unit / Integration Tests (icd)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Unit / Integration Tests (icd)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.