Skip to content

Add support for esp32 network driver scanning for access points #4856

Add support for esp32 network driver scanning for access points

Add support for esp32 network driver scanning for access points #4856

Triggered via pull request March 11, 2026 04:37
Status Failure
Total duration 4m 33s
Artifacts

esp32-mkimage.yaml

on: pull_request
Matrix: esp32-release
Fit to window
Zoom out
Zoom in

Annotations

26 errors and 7 warnings
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c2, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32s3, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32s2, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c3)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32s2)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c3, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c6, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c5)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c61)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32p4)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32p4_pre_c6, -eli...
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32s3)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32h2, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32p4_pre, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c6)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32p4_c6)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c5, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32p4_pre)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32h2)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c61, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32p4, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32p4_pre_c6)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32p4_c6, -elixir)
The strategy configuration was canceled because "esp32-release._5_5_2_clang-14_clang___3" failed
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c2)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c2)
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
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c2)
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
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c2)
_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c2)
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
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c2)
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
esp32-release (5.5.2, clang-14, clang++-14, -O3, 27, 1.17, 3.24.0, clang-14, esp32c2)
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