Skip to content

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

Add support for esp32 network driver scanning for access points

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

Triggered via pull request March 11, 2026 03:36
Status Cancelled
Total duration 1h 0m 51s
Artifacts 6

pico-build.yaml

on: pull_request
build-atomvmlib
46s
build-atomvmlib
Matrix: pico
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 7 warnings
pico (pico2, -DPICO_PLATFORM=rp2350-riscv, -DAVM_DISABLE_JIT=OFF)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico2_w)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico, -DAVM_DISABLE_JIT=OFF)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico2_w, -DPICO_PLATFORM=rp2350-riscv, -DAVM_DISABLE_JIT=OFF)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico2_w, -DAVM_DISABLE_JIT=OFF)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico_w)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico_w)
A task was canceled.
pico (pico2_w, -DPICO_PLATFORM=rp2350-riscv)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico2_w, -DPICO_PLATFORM=rp2350-riscv)
The operation was canceled.
pico (pico2, -DPICO_PLATFORM=rp2350-riscv)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico2, -DPICO_PLATFORM=rp2350-riscv)
The operation was canceled.
pico (pico_w, -DAVM_DISABLE_JIT=OFF)
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
Pico Build
Canceling since a higher priority waiting request for Pico Build-refs/pull/1165/merge exists
pico (pico_w, -DAVM_DISABLE_JIT=OFF)
The operation was canceled.
build-atomvmlib
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, 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/
pico (pico)
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/download-artifact@v4, actions/upload-artifact@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/
pico (pico2)
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/download-artifact@v4, actions/upload-artifact@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/
pico (pico2, -DAVM_DISABLE_JIT=OFF)
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/download-artifact@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/
pico (pico2_w, -DPICO_PLATFORM=rp2350-riscv)
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/download-artifact@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/
pico (pico2, -DPICO_PLATFORM=rp2350-riscv)
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/download-artifact@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/
pico (pico_w, -DAVM_DISABLE_JIT=OFF)
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/download-artifact@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/

Artifacts

Produced during runtime
Name Size Digest
AtomVM-combined-pico-1165-merge.uf2
481 KB
sha256:1c2a14a10694f5c7ad02c469806b9f931573b1e7e1d4467febd7ab27f0f254b7
AtomVM-combined-pico2-1165-merge.uf2
463 KB
sha256:0aa9dde33361b9306f32d7121f03c5ec22c4bea972b0ab8ce9668770dbde6a19
AtomVM-pico-1165-merge.uf2
352 KB
sha256:50306242ec897538ed3032d63ec135115ed9cc62152aa2e28beef7564bfedec3
AtomVM-pico2-1165-merge.uf2
334 KB
sha256:a3cee05b2d73f8374247e6c0dcc6e6d135756cc44d4e2c0f54be794f698569b2
atomvmlib-uf2-files
258 KB
sha256:fc6da7224ad7fe5a24e082a14a69afec45e114260adf3b54eb586852872d9fcc
uf2tool
4 KB
sha256:c6654b65c9d236a2ddbafb34152efa6081e98c01df79293ed5c7279b62e47377