Re: [PATCH] tests/avocado/machine_aspeed.py: Update SDK images

[Cédric Le Goater]

On 8/28/23 17:50, Philippe Mathieu-Daudé wrote:
> On 28/8/23 16:33, Cédric Le Goater wrote:
> > On 8/28/23 15:54, Joel Stanley wrote:
> > > On Mon, 28 Aug 2023 at 09:01, Cédric Le Goater <clg@kaod.org> wrote:
> > > > Switch to the latest v8.06 release which introduces interesting
> > > > changes for the AST2600 I2C and I3C models. Also take the AST2600 A2
> > > > images instead of the default since QEMU tries to model The AST2600 A3
> > > > SoC.
> > >
> > > Is there any value in testing both the old and the new images?
> >
> > For QEMU default tests, I think using the latest version of a test image
> > is just fine, or we will end up with a very long avocado test run. That
> > said we could make an exception when a HW feature is only activated in a
> > specific version.
> >
> > I run pre-PR tests with more images (buildroot, mainline, sdk, openbmc,
> > provided by other vendors) but only the SDK v08.X images have decent
> > results. v07.02 and v04.05 have issues. It could be a software issue.
>
> I'd rather keep all tests committed in the repository, only having the
> latest one picked up by default. That way other developer can reproduce
> maintainers pre-PR suites.
I could add a few static images but not all. Most flash and eMMC images
are generated on the fly for test purposes with the latest kernel
(OpenBMC and mainline), U-Boot (OpenBMC and mainline), rootfs (OpenBMC
and buildroot). This is a large zoo. PPC is similar.

C.