In addition to Bridle's own examples, it should also be possible to build specific Zephyr upstream examples with an alternative configuration base with the Bridle-owned specifications. For this purpose, the new tags zephyr and bridle must be introduced and respected. For the GitHub workflows, this makes the explicit naming of individual test roots unnecessary. The selection is made exclusively via the newly introduced tags.
Avoid RAM overflow on qemu_cortex_m0
Since Zephyr upstream PR 74435, the sensor shell commands rely on a complete integration of the sensor ASYNC API incl. RTIO subsystem with a thread pool for a dedicated RTIO work queue. This exceeds the 16KB RAM of the Cortex M0 emulator by far. The only option available at the moment is to disable the sensor shell commands.
Protect supported display shields
In preparation to PR #238, #243 and #245 the GH pipeline have to catch all currently display shields by simple builds as integration tests.
Restructuring QA integration tests for samples
In addition to Bridle's own examples, it should also be possible to build specific Zephyr upstream examples with an alternative configuration base with the Bridle-owned specifications. For this purpose, the new tags
zephyrandbridlemust be introduced and respected. For the GitHub workflows, this makes the explicit naming of individual test roots unnecessary. The selection is made exclusively via the newly introduced tags.Avoid RAM overflow on
qemu_cortex_m0Since Zephyr upstream PR 74435, the sensor shell commands rely on a complete integration of the sensor ASYNC API incl. RTIO subsystem with a thread pool for a dedicated RTIO work queue. This exceeds the 16KB RAM of the Cortex M0 emulator by far. The only option available at the moment is to disable the sensor shell commands.
Protect supported display shields
In preparation to PR #238, #243 and #245 the GH pipeline have to catch all currently display shields by simple builds as integration tests.