From: Eduardo Habkost <ehabkost@redhat.com>
To: "Emilio G. Cota" <cota@braap.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Help needed: test-qht-par hangs on Travis
Date: Mon, 10 Dec 2018 15:47:15 -0200 [thread overview]
Message-ID: <20181210174715.GI4669@habkost.net> (raw)
In-Reply-To: <20181209222738.GA9292@flamenco>
On Sun, Dec 09, 2018 at 05:27:38PM -0500, Emilio G. Cota wrote:
> On Fri, Dec 07, 2018 at 18:41:07 -0200, Eduardo Habkost wrote:
> > I've noticed QEMU Travis builds are failing recently, and they
> > seem to happen only on the --enable-gprof jobs. I have enabled
> > V=1 and noticed that the jobs are hanging inside test-qht-par.
> >
> > Example here (look for "/qht/parallel/2threads-0%updates-1s"):
> >
> > https://travis-ci.org/ehabkost/qemu-hacks/jobs/465081311
> >
> > Does anybody have any idea why?
>
> So if I read that output correctly, it seems that the second
> test in qht-par never completes.
>
> Enabling gprof and gcov (as in that build) should just lower
> the throughput of the benchmark (test-qht-par invokes qht-bench),
[...]
Unrelated question: is there a specific reason why test-qht-par
is written in C using gtest, instead of being just a shell script
that runs qht-bench?
--
Eduardo
next prev parent reply other threads:[~2018-12-10 17:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 20:41 [Qemu-devel] Help needed: test-qht-par hangs on Travis Eduardo Habkost
2018-12-09 22:27 ` Emilio G. Cota
2018-12-10 16:36 ` Eduardo Habkost
2018-12-10 17:07 ` Emilio G. Cota
2018-12-10 17:34 ` Eduardo Habkost
2018-12-10 19:09 ` Eduardo Habkost
2019-01-10 20:58 ` Eduardo Habkost
2019-01-11 12:55 ` Paolo Bonzini
2018-12-10 17:47 ` Eduardo Habkost [this message]
2018-12-10 20:47 ` Emilio G. Cota
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=20181210174715.GI4669@habkost.net \
--to=ehabkost@redhat.com \
--cc=cota@braap.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.