Skip to content

Add UART support to STM32 platform #7167

Add UART support to STM32 platform

Add UART support to STM32 platform #7167

Re-run triggered April 15, 2026 03:54
Status Failure
Total duration 27m 59s
Artifacts

build-and-test.yaml

on: pull_request
Matrix: build-and-test
Fit to window
Zoom out
Zoom in

Annotations

1 error and 38 warnings
build-and-test (cc, master, c++, main)
Could not mix rebar from any hex.pm mirror
build-and-test (cc, master, c++, main)
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/upload-artifact@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-and-test (cc, master, c++, main)
No files were found with the provided path: core/*. No artifacts will be uploaded.
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, 28, ubuntu-24.04, c++, 1.17, 3.24.0, -DAVM_USE_LIBSODIUM=ON, libsodium-dev)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
build-and-test (gcc-10, g++-10, gcc-10 g++-10): tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
Unused private function
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (gcc-10, g++-10, gcc-10 g++-10)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON): tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (cc, c++, -DAVM_USE_32BIT_FLOAT=ON -DAVM_WARNINGS_ARE_ERRORS=ON)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (clang-15, clang++-15, clang-15)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, 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/
build-and-test (clang-15, clang++-15, clang-15): tests/libs/estdlib/test_lists.erl#L491
the call to lists:append/2 will fail with a 'badarg' exception
build-and-test (clang-15, clang++-15, clang-15)
Unused private function
build-and-test (clang-15, clang++-15, clang-15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (clang-15, clang++-15, clang-15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (clang-15, clang++-15, clang-15)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
build-and-test (clang-15, clang++-15, clang-15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (clang-15, clang++-15, clang-15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it
build-and-test (clang-15, clang++-15, clang-15)
first..last inside match is deprecated, you must always match on the step: first..last//var or first..last//_ if you want to ignore it