From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:60945) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gaGIW-0005DM-9M for qemu-devel@nongnu.org; Fri, 21 Dec 2018 03:36:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gaGIR-0007Z4-76 for qemu-devel@nongnu.org; Fri, 21 Dec 2018 03:36:44 -0500 Received: from 20.mo4.mail-out.ovh.net ([46.105.33.73]:51063) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gaGIQ-0007Sw-Sq for qemu-devel@nongnu.org; Fri, 21 Dec 2018 03:36:39 -0500 Received: from player758.ha.ovh.net (unknown [10.109.146.211]) by mo4.mail-out.ovh.net (Postfix) with ESMTP id C05551C7800 for ; Fri, 21 Dec 2018 09:36:27 +0100 (CET) Date: Fri, 21 Dec 2018 09:36:23 +0100 From: Greg Kurz Message-ID: <20181221093623.738b71e9@bahia.lan> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] travis failures List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Thomas Huth Cc: Alexey Kardashevskiy , "qemu-devel@nongnu.org" On Fri, 21 Dec 2018 07:47:07 +0100 Thomas Huth wrote: > On 2018-12-21 04:06, Alexey Kardashevskiy wrote: > > Hi > > > > I am trying https://travis-ci.org/aik/qemu/ and that thing fails every > > time I am not so sure why. > > > > One example: > > https://travis-ci.org/aik/qemu/jobs/470796318 > > > > The errors are like this: > > > > GTESTER check-qtest-unicore32 > > GTESTER check-qtest-x86_64 > > Could not access KVM kernel module: No such file or directory > > qemu-system-x86_64: failed to initialize KVM: No such file or directory > > qemu-system-x86_64: Back to tcg accelerator > > > > > > Does anyone else see those? How do we fix them? Thanks. > > Some test are explicitly requesting "-M accel=kvm:tcg" and this is > causing this message if KVM is not available. We could maybe silence > them if qtest_enabled() ? > > Thomas > > I've also experienced a bunch of similar failures with travis, like: https://travis-ci.org/gkurz/qemu/jobs/466994463 The KVM error messages aren't directly related to the failure IMHO. In both cases, the cause of the failure seems to be: No output has been received in the last XXm0s, this potentially indicates a stalled build or something wrong with the build itself. Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received The build has been terminated and the last GTESTER line is for tests/test-qht-par: https://travis-ci.org/aik/qemu/jobs/470796318#L8219 https://travis-ci.org/gkurz/qemu/jobs/466994463#L4454 This has been recently discussed on qemu-devel: https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg01638.html But I haven't seen anything come out that yet.