From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60970) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fBhok-0007CB-Un for qemu-devel@nongnu.org; Thu, 26 Apr 2018 10:24:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fBhoh-0005CN-FY for qemu-devel@nongnu.org; Thu, 26 Apr 2018 10:24:14 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:48908 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fBhoh-0005C3-AA for qemu-devel@nongnu.org; Thu, 26 Apr 2018 10:24:11 -0400 Date: Thu, 26 Apr 2018 15:24:06 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Message-ID: <20180426142406.GO26812@redhat.com> Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= References: <20180426135755.GI29865@localhost.localdomain> <20180426141400.GM26812@redhat.com> <20180426142236.GJ29865@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180426142236.GJ29865@localhost.localdomain> 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: Eduardo Habkost Cc: Thomas Huth , Peter Maydell , Yash Mankad , =?utf-8?B?THVrw6HFoQ==?= Doktor , Markus Armbruster , Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= , qemu-devel@nongnu.org, Cleber Rosa On Thu, Apr 26, 2018 at 11:22:36AM -0300, Eduardo Habkost wrote: > On Thu, Apr 26, 2018 at 03:14:00PM +0100, Daniel P. Berrang=C3=A9 wrote= : > > On Thu, Apr 26, 2018 at 04:09:55PM +0200, Thomas Huth wrote: > > > On 26.04.2018 15:57, Eduardo Habkost wrote: > > > > (Starting a new thread, for more visibility) > > > >=20 > > > > (This was: Re: [Qemu-devel] [RFC PATCH] tests/device-introspect: = Test > > > > devices with all machines, not only with "none") > > > >=20 > > > > On Thu, Apr 26, 2018 at 01:54:43PM +0200, Markus Armbruster wrote= : > > > [...] > > > >> I don't mind having make check SPEED=3Dslow run more extensive t= ests. > > > >> Assuming we actually run them at least once in a while, which se= ems > > > >> doubtful. > > > >=20 > > > > We probably don't do that, but we really must be running a more > > > > extensive (and slower) test set at least once before every > > > > release. > > > >=20 > > > > Maybe some people are running SPEED=3Dslow tests, or even more > > > > extensive test suites like avocado-vt once in a while, but we > > > > need to know who is running them, and when. > > >=20 > > > At least I am running "make check SPEED=3Dslow" manually from time = to > > > time, especially when we enter the hard freeze period. > >=20 > > Hmm, we could get this done by travis. It has the concept of "cron jo= bs" > > for scheduling builds separately from pushes. > >=20 > > So we could keep the current travis jobs unchanged, but then add an > > use of SPEED=3Dslow when TRAVIS_EVENT_TYPE =3D=3D "cron" in the travi= s.yml, > > so we can get SPEED=3Dslow run once a day. Just have to be careful wh= ich > > jobs we make slow so we don't hit the 50 minute timeout. >=20 > I expect SPEED=3Dslow tests to eventually take longer than 50 > minutes, but we can try this and see what happens. We can run many jobs though so if qtests take longer than 50 mins, we cou= ld create 1 job per target arch. Regards, Daniel --=20 |: https://berrange.com -o- https://www.flickr.com/photos/dberran= ge :| |: https://libvirt.org -o- https://fstop138.berrange.c= om :| |: https://entangle-photo.org -o- https://www.instagram.com/dberran= ge :|