From: Greg Kurz <groug@kaod.org>
To: Thomas Huth <thuth@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] travis failures
Date: Fri, 21 Dec 2018 09:36:23 +0100 [thread overview]
Message-ID: <20181221093623.738b71e9@bahia.lan> (raw)
In-Reply-To: <d5247b86-4c9c-0eff-7900-66443041f63e@redhat.com>
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
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.
next prev parent reply other threads:[~2018-12-21 8:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 3:06 [Qemu-devel] travis failures Alexey Kardashevskiy
2018-12-21 6:47 ` Thomas Huth
2018-12-21 8:36 ` Greg Kurz [this message]
2018-12-21 10:26 ` Greg Kurz
2018-12-21 18:28 ` Emilio G. Cota
2019-01-07 16:42 ` Eduardo Habkost
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181221093623.738b71e9@bahia.lan \
--to=groug@kaod.org \
--cc=aik@ozlabs.ru \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).