The tests / zephyr job of "Build CI" is red on the Pico 2 W BLE branch (run 34253440312), so the mpy-cross artifacts on that branch come from an otherwise-failing run.
I have not established the cause. From a glance at the log it dies around the native_sim port setup installing i386 SDL dependencies (libsdl2-dev:i386, libgpg-error0:i386 …), which looks like environment/infra rather than our changes. But that is a guess, and two of the changes on these branches are port-wide and could plausibly break a test:
ports/zephyr-cp/prj.conf gained CONFIG_NVS_INIT_BAD_MEMORY_REGION=y (affects every board)ports/zephyr-cp/cptools/compat2driver.py gained one mapping entry
First thing to check: whether tests / zephyr is also red on main / upstream. If it is, this is pre-existing and unrelated. If it is green there, it's ours and needs bisecting.
Tracking this so a red CI job on the BLE stack isn't quietly accepted.
The
tests / zephyrjob of "Build CI" is red on the Pico 2 W BLE branch (run 34253440312), so the mpy-cross artifacts on that branch come from an otherwise-failing run.I have not established the cause. From a glance at the log it dies around the
native_simport setup installing i386 SDL dependencies (libsdl2-dev:i386,libgpg-error0:i386…), which looks like environment/infra rather than our changes. But that is a guess, and two of the changes on these branches are port-wide and could plausibly break a test:ports/zephyr-cp/prj.confgainedCONFIG_NVS_INIT_BAD_MEMORY_REGION=y(affects every board)ports/zephyr-cp/cptools/compat2driver.pygained one mapping entryFirst thing to check: whether
tests / zephyris also red onmain/ upstream. If it is, this is pre-existing and unrelated. If it is green there, it's ours and needs bisecting.Tracking this so a red CI job on the BLE stack isn't quietly accepted.