From: Eduardo Habkost <ehabkost@redhat.com>
To: "Emilio G. Cota" <cota@braap.org>
Cc: Greg Kurz <groug@kaod.org>, Thomas Huth <thuth@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] travis failures
Date: Mon, 7 Jan 2019 14:42:43 -0200 [thread overview]
Message-ID: <20190107164243.GR4157@habkost.net> (raw)
In-Reply-To: <20181221182810.GA11197@flamenco>
On Fri, Dec 21, 2018 at 01:28:10PM -0500, Emilio G. Cota wrote:
> On Fri, Dec 21, 2018 at 11:26:34 +0100, Greg Kurz wrote:
> > 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.
>
> Yes, this was being discussed in this thread:
>
> https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg01638.html
>
> I haven't heard from Eduardo in a while, I guess he's off for the
> holidays.
Yes, sorry. :)
>
> My latest suggestion was to try a branch where test-qht-par is
> standalone, instead of using system(3) to call qht-bench--see
> this message:
> https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg02056.html
>
> Can anyone please try that? Or at least let me know how to run
> a test Travis build so that I can debug this faster.
I don't remember the exact steps, but I think you should be able
to trigger Travis jobs on your GitHub branches by just logging
into travis-ci.org using your GitHub account.
I have pushed your test-qht-par branch to my repository, and the
jobs are still failing:
https://travis-ci.org/ehabkost/qemu-hacks/jobs/475580438
--
Eduardo
prev parent reply other threads:[~2019-01-07 16:52 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
2018-12-21 10:26 ` Greg Kurz
2018-12-21 18:28 ` Emilio G. Cota
2019-01-07 16:42 ` Eduardo Habkost [this message]
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=20190107164243.GR4157@habkost.net \
--to=ehabkost@redhat.com \
--cc=aik@ozlabs.ru \
--cc=cota@braap.org \
--cc=groug@kaod.org \
--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).