All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: famz@redhat.com, "Alex Bennée" <alex.bennee@linaro.org>,
	stefanb@linux.vnet.ibm.com, marcandre.lureau@redhat.com,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 2/2] tests/Makefile: comment out flakey tests
Date: Fri, 25 May 2018 10:17:24 +0100	[thread overview]
Message-ID: <20180525091724.GC14757@stefanha-x1.localdomain> (raw)
In-Reply-To: <87h8n5dmrk.fsf@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]

On Fri, May 18, 2018 at 04:08:47PM +0100, Alex Bennée wrote:
> 
> Stefan Hajnoczi <stefanha@redhat.com> writes:
> 
> > On Fri, May 18, 2018 at 10:14:40AM +0100, Alex Bennée wrote:
> >> The following tests keep showing up in failed Travis runs:
> >>
> >>   - test-aio
> >
> > What is the issue?
> 
> GTESTER tests/test-thread-pool
> **
> ERROR:tests/test-aio.c:501:test_timer_schedule: assertion failed: (aio_poll(ctx, true))
> GTester: last random seed: R02S66126aca97f9606b33e5d7be7fc9b625
> make: *** [check-tests/test-aio] Error 1
> make: *** Waiting for unfinished jobs....

The test_timer_schedule test case relies on timing and is
non-deterministic.

I couldn't figure out how it managed to fail that specific assertion.
aio_poll(ctx, true) == false happens when aio_notify() was called but I
don't understand why it happened here.

However, I do see that this test case will fail if the machine is very
heavily loaded.  The test simply won't reach the places where it should
wait for the timer.  The timer may expire too early.

Maybe a steppable clock should be used (vmclock), but then the test
would have to be simplified because the aio_poll(ctx, true) part relies
on ppoll(2)'s timeout.

Any thoughts, Paolo?

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2018-05-25  9:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18  9:14 [Qemu-devel] [RFC PATCH 0/2] Travis Stability Patches Alex Bennée
2018-05-18  9:14 ` [Qemu-devel] [RFC PATCH 1/2] .travis.yml: disable linux-user build for gcov Alex Bennée
2018-05-18  9:14 ` [Qemu-devel] [RFC PATCH 2/2] tests/Makefile: comment out flakey tests Alex Bennée
2018-05-18  9:49   ` Paolo Bonzini
2018-05-18 10:02   ` Peter Maydell
2018-05-18 10:17   ` Peter Maydell
2018-05-18 12:02   ` Stefan Hajnoczi
2018-05-18 15:08     ` Alex Bennée
2018-05-25  9:17       ` Stefan Hajnoczi [this message]
2018-05-18 18:31   ` Peter Maydell
2018-05-19  6:10     ` Thomas Huth
2018-05-19 11:36       ` Peter Maydell
2018-05-22  6:01         ` Thomas Huth

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=20180525091724.GC14757@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=famz@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@linux.vnet.ibm.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 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.