On Thu, Mar 27, 2025 at 10:31:18AM -0300, Fabio Estevam wrote: > Hi Miquel, > > On Wed, Mar 26, 2025 at 12:01 PM Miquel Raynal > <miquel.ray...@bootlin.com> wrote: > > > I rebased this work on the latest next, fixed the conflicts, adapted my > > changes to use Svyatoslav's work, fixed the CI. > > v5 still fails in CI: > > https://source.denx.de/u-boot/custodians/u-boot-imx/-/pipelines/25364
And the exact failure is: https://source.denx.de/u-boot/custodians/u-boot-imx/-/jobs/1078073#L259 Which looks like a series conflict or test needing to be updated, rather than a "what the heck???" kind of failure like before. > > Then I pushed a PR to trigger azure tests and figured out you applied more > > patches (imx8 clock related) which conflicted. So I rebased again and > > fixed the conflicts. > > > > Azure testing is failing though. I just pushed an empty branch with just > > today's 'next' and it is already failing, my series does not produce > > additional warnings as far as I can see. > > > > So I am sending a series that has been tested locally. dm unit tests > > pass, v5 is on its way. > > If I remove your series, I don't see any test failure: > > https://source.denx.de/u-boot/custodians/u-boot-imx/-/pipelines/25365 > > I don't know about the Azure failure. Please work with the team and > make sure v6 passes in CI. I see that the Azure failure is: https://dev.azure.com/u-boot/u-boot/_build/results?buildId=10824&view=results which was the unfortunate "next is broken because master has a fix and next has a test that needed updating now" that happened this week with -rc5 being merged. Sorry about that, it's fixed now. -- Tom
signature.asc
Description: PGP signature
