Re: [Qemu-devel] travis failures

[Greg Kurz <groug@kaod.org>]

On Fri, 21 Dec 2018 09:36:23 +0100
Greg Kurz <groug@kaod.org> wrote:

> On Fri, 21 Dec 2018 07:47:07 +0100
> Thomas Huth <thuth@redhat.com> 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
> 

Today with tests/test-qht-par again:

https://travis-ci.org/gkurz/qemu/jobs/470871251#L4455

Cc'ing Emilio for suggestions on how to go forward with this.

> 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.
> 
>