[PATCH v4 00/12] Add imx8mp video support

[Tom Rini]

On Fri, Mar 28, 2025 at 09:39:23AM +0100, Miquel Raynal wrote:
> On 27/03/2025 at 08:14:42 -06, Tom Rini <trini at konsulko.com> wrote:
> 
> > 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.raynal at 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.
> 
> Yes, my question got lost somewhere else, so let me ask here as well.
> 
> I need the tests to run on the test.dts and not the default sandbox.dts.
> The documentation states to use -T for that when doing the checks
> locally. Unfortunately, the Azure pipelines do use the default sandbox
> DT. I can add few mostly useless nodes to the default DTS for the tests
> to pass, but I feel like this is not the correct approach.
> 
> Is there a way to tell Azure to run some of the unit tests (especially
> the DM ones) only with the test DT?

I saw the older email first, sorry. But I think the docs have become
disconnected from how things have been done practically.

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