CI to stop testing meta-* layers not in tested machine

[Joel Stanley]

On Fri, 10 May 2019 at 18:46, Andrew Geissler <geissonator at gmail.com> wrote:
>
> On Fri, May 10, 2019 at 9:33 AM Patrick Venture <venture at google.com> wrote:
> > > I'd like to have a nuvoton based machine so we have some confidence
> > > that kernel bumps aren't broken.
> > >
> > > That would mean adding the evb-nuvoton or gsj machines to CI.
> >
> > I vote for the gsj machine.  Not that it's a democracy :)
>
> I gave this a try but ran into https://github.com/openbmc/openbmc/issues/3542
> Be great to get gsj into CI since it would give us a few new layers
> for coverage.

gsj is now supported in the kernel.

Andrew tried to build the machine and ran into u-boot issues which is
still blocking the machine's addition to our CI. Patrick, are you able
to look into that?

 https://github.com/openbmc/openbmc/issues/3542#issuecomment-501706892

Once we get the u-boot issue sorted out, I propose the following changes:

 - drop qemu from CI. 'qemu' is actually testing on a generic arm
machine. A few of us at IBM have a side project that has resulted in a
high quality Qemu support for the aspeed boards, so if you would like
to test in qemu I recommend grabbing palmetto or romulus and doing
that. So consider this dropping the generic qemu image and instead
focusing on the aspeed one.

 - add gsj. This gives us coverage of the nuvoton kernel and u-boot,
as well as the nuvoton specific layers

 - add swift. This is an ast2500-based system that we're looking to
use emmc flash with, and having testing for those images will be
useful

Cheers,

Joel