Re: "make check-acceptance" takes way too long

From: "Cédric Le Goater" <clg@kaod.org>
To: "Cleber Rosa" <crosa@redhat.com>, "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Beraldo Leal" <bleal@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Stefano Brivio" <sbrivio@redhat.com>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: "make check-acceptance" takes way too long
Date: Tue, 1 Feb 2022 18:59:12 +0100	[thread overview]
Message-ID: <4dda34d4-a84c-183c-52e7-dd996bb610f8@kaod.org> (raw)
In-Reply-To: <CA+bd_6JF5iRKufxVa=6TEtR-eH65iiiG-oarWRHkavX-3E-p1Q@mail.gmail.com>

On 2/1/22 17:01, Cleber Rosa wrote:
> On Tue, Feb 1, 2022 at 6:25 AM Alex Bennée <alex.bennee@linaro.org> wrote:
>>
>> We have up to now tried really hard as a project to avoid building and
>> hosting our own binaries to avoid theoretical* GPL compliance issues.
>> This is why we've ended up relying so much on distros to build and host
>> binaries we can use. Most QEMU developers have their own personal zoo of
>> kernels and userspaces which they use for testing. I use custom kernels
>> with a buildroot user space in initramfs for example. We even use the
>> qemu advent calendar for a number of our avocado tests but we basically
>> push responsibility for GPL compliance to the individual developers in
>> that case.
>>
>> *theoretical in so far I suspect most people would be happy with a
>> reference to an upstream repo/commit and .config even if that is not to
>> the letter of the "offer of source code" required for true compliance.
>>
> 
> Yes, it'd be fine (great, really!) if a lightweight distro (or
> kernels/initrd) were to
> be maintained and identified as an "official" QEMU pick.  Putting the binaries
> in the source tree though, brings all sorts of compliance issues.

FWIW, before avocado, I am using linux+buildroot images for PPC
and running a simple "boot-net-login-poweroff" script for each
machine/CPU QEMU can test :

ref405ep : Linux /init login DONE (PASSED)
bamboo : Linux /init net login DONE (PASSED)
sam460ex : Linux Linux /init net login DONE (PASSED)
g3beige-604 : FW Linux Linux /init net login DONE (PASSED)
g3beige-g3 : FW Linux Linux /init net login DONE (PASSED)
mac99-g4 : FW Linux Linux /init net login DONE (PASSED)
mac99-7447 : FW Linux Linux /init net login DONE (PASSED)
mac99-7448 : FW Linux Linux /init net login DONE (PASSED)
mac99-7450 : FW Linux Linux /init net login DONE (PASSED)
mpc8544ds : Linux /init net login DONE (PASSED)
e500mc : Linux /init net login DONE (PASSED)
40p : FW login DONE (PASSED) # this one is a special case
e5500 : Linux /init net login DONE (PASSED)
e6500 : Linux /init net login DONE (PASSED)
g5-32 : FW Linux Linux /init net login DONE (PASSED)
g5-64 : FW Linux Linux /init net login DONE (PASSED)
pseries-970 : FW Linux Linux /init net login DONE (PASSED)
pseries-970mp : FW Linux Linux /init net login DONE (PASSED)
pseries-POWER5+ : FW Linux Linux /init net login DONE (PASSED)
pseries : FW Linux Linux /init net login DONE (PASSED)
pseriesle8 : FW Linux Linux /init net login DONE (PASSED)
pseriesle9 : FW Linux Linux /init net login DONE (PASSED)
pseriesle10 : FW Linux Linux /init net login DONE (PASSED)
powernv8 : FW Linux /init net login DONE (PASSED)
powernv9 : FW Linux /init net login DONE (PASSED)

Images are here :

   https://github.com/legoater/qemu-ppc-boot/tree/main/buildroot

Buildroot has a testsuite using QEMU and they have been nice enough
to take new QEMU boards for PPC.

Thanks,

C.

> 
> The downloading of the images at test "setup time" is still a better approach,
> given that tests will simply skip if the download is not possible.
> 
> - Cleber.
> 
> 