[PATCH] CI: Update sjg lab to match currently actively boards

[Tom Rini]

On Tue, Mar 17, 2026 at 07:18:35AM -0600, Simon Glass wrote:

> Various updates:
> - c4 lack signing so does not currently build
> - samus hardware is non-functional
> - colibrimx8, rockpro64, rock3a, rock5b, rpi5, tk1 and play are new
> 
> Signed-off-by: Simon Glass <sjg at chromium.org>
> 
> ---
> A sample run is here:
> 
> https://source.denx.de/u-boot/custodians/u-boot-dm/-/pipelines/29552
> 
> At present, coral, play, rpi5, snow and vf2 appear to be genuinely
> broken on -next
> 
> The ff3399 board needs some investigation.
> 
>  .gitlab-ci.yml | 46 ++++++++++++++++++++++++++++++++++++----------
>  1 file changed, 36 insertions(+), 10 deletions(-)

I have two sets of problems with this patch.

One, it doesn't do, but perhaps I wasn't clear enough when bringing it
up, change it so that failure to pass is a job failure (it's currently a
warning). This in turn means people can't tell expected failure from new
failure.

Two, when you had previously gone about adding at least colibrimx8 I
noted that this extended how you were having labgrid build U-Boot in an
even further non-upstreamable manner. As the sage lab yaml shows, we can
bring in external binaries for buildman (and binman) to find and use.
We'll need to extend that logic a bit, to be sure, but it's a solvable
problem with the baseline already there.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20260325/34531f9f/attachment.sig>