Hi Tom, On Tue, 12 May 2026 at 00:00, Tom Rini <[email protected]> wrote: > > I didn't realise I could trigger a pipeline run so thanks for the > > information. Anyhow, I triggered a run for v6 and it completed and I > > couldn't actually find where the error in the result. I triggered it > > again for the v7 and it passed too. Is there something I should check > > before I send it again? The run is here: > > https://github.com/u-boot/u-boot/pull/964/checks > > That's very strange. I just re-checked v6 and still get: > https://source.denx.de/u-boot/u-boot/-/jobs/1446347 and both Azure and > Gitlab run the job the same way. Can you trigger it locally with > allyesconfig ?
Before adding a new patch to fix the issue, building allyesconfig locally gave me the same error as your CI pipeline had and that went away when I fixed it. Cheers, Daniel
