From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:43598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fGRPS-0005t6-Cn for qemu-devel@nongnu.org; Wed, 09 May 2018 11:53:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fGRPO-00078V-Eu for qemu-devel@nongnu.org; Wed, 09 May 2018 11:53:42 -0400 Received: from mail-wr0-x241.google.com ([2a00:1450:400c:c0c::241]:44961) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fGRPO-000777-8e for qemu-devel@nongnu.org; Wed, 09 May 2018 11:53:38 -0400 Received: by mail-wr0-x241.google.com with SMTP id y15-v6so24368350wrg.11 for ; Wed, 09 May 2018 08:53:37 -0700 (PDT) References: <20180426135755.GI29865@localhost.localdomain> From: Alex =?utf-8?Q?Benn=C3=A9e?= In-reply-to: Date: Wed, 09 May 2018 16:53:35 +0100 Message-ID: <87po24vn9c.fsf@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] Who is running QEMU automated tests, and when? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Clark Cc: Peter Maydell , Yash Mankad , Thomas Huth , Eduardo Habkost , Palmer Dabbelt , Markus Armbruster , QEMU Developers , Andrew Waterman , Cleber Rosa , Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= Michael Clark writes: > On Fri, Apr 27, 2018 at 2:04 AM, Peter Maydell > wrote: > >> On 26 April 2018 at 14:57, Eduardo Habkost wrote: >> > Peter, do you have additional tests you run before merging a pull >> > request? Additional test sets run before tagging a release? >> >> I run make && make check, on a variety of hosts, before merging >> any pull request. That's the only testing I do, and I don't >> do anything more before I do a tag. >> > > This is what I do on riscv, however it is not yet automated: > > > We could bring a snapshot of riscv-tests into the QEMU tree however it > would be best if they retained the BSD license so we can share locally > added tests with upstream as upstream is adding tests periodically. Certainly it would be worth considering some smoke tests for tests/tcg/riscv that at least verify the basics CPU features work as expected. I've got some ideas for packaging more extensive test suites like LTP and kvm-unit-tests but would like to get simple linux-user stuff up and running first. > > We would like to automate all of this and we are working towards that goa= l. > One of the dependencies for docker tests are the riscv toolchain packages > and we are working on this... I got riscv64 working with the SID toolchain: https://github.com/stsquad/qemu/commit/db0a108b9a0efdeeb2f63e670595c5e28e= 236a97 Once I've fixed it up to use snapshots.debian.org it will be in v4 of the TCG tests. > Adding port specific tests, like riscv tests to QEMU not only benefits the > particular port but also exercises a log of generic code such as the TCG, > the IO system, IO mutex, Virt IO and many other shared code paths. I agree it would be worthwhile testing. System tests are a bit more complicated in terms of code required although we have some for CRIS/MIPS/Xtensa/lm32 which need re-enabling - although toolchains for the more esoteric architectures is a pain. -- Alex Benn=C3=A9e