[PATCH] Gitlab: Add a "sage-lab" stage to access a board farm

Simon Glass sjg at chromium.org
Tue Nov 11 13:58:22 CET 2025


Hi Tom,

On Mon, 10 Nov 2025 at 08:42, Tom Rini <trini at konsulko.com> wrote:
>
> This is the Gitlab side of adding support for the board lab connected to
> the "konsulko-sage" runner. On the software side, this lab uses only
> upstream labgrid. On the hardware side, each device under test is
> connected to its own exporter (typically a Raspberry Pi 4) that must be
> turned on (and cleanly turned off) as part of a given test cycle.
>
> Add support for testing on a SolidRun Hummingboard 2 (imx6), Raspberry
> Pi 3 and Raspberry Pi 4. In all cases, we enable additional options to
> run more tests on the board. As we have some networking tests, we test
> both the legacy network stack and lwIP. In the case of Pi platforms, we
> test all of 32bit configuration, plain configuration and rpi_arm64, and
> again with and without lwIP.
>
> Signed-off-by: Tom Rini <trini at konsulko.com>
> ---
> Note that for the Pi platforms we enable/disable CMD_BOOTEFI_SELFTEST
> based on overall binary size. I've created
> https://source.denx.de/u-boot/custodians/u-boot-raspberrypi/-/issues/2
> to track addressing that issue.
> ---
>  .gitlab-ci-sage-lab.yml | 182 ++++++++++++++++++++++++++++++++++++++++
>  .gitlab-ci.yml          |   5 ++
>  2 files changed, 187 insertions(+)
>  create mode 100644 .gitlab-ci-sage-lab.yml

Would it be possible to add some docs about this? Does the exporting
rpi do a full system boot and then run some scripts to load things
onto the board, then shut down?

Regards,
Simon


More information about the U-Boot mailing list