All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Fam Zheng" <famz@redhat.com>,
	"Stefan Berger" <stefanb@linux.vnet.ibm.com>,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 2/2] tests/Makefile: comment out flakey tests
Date: Sat, 19 May 2018 12:36:40 +0100	[thread overview]
Message-ID: <CAFEAcA-9miwQ_JK4VFcFMgWc=XCb_Qf3W4ZFk59csXUGdnAMDA@mail.gmail.com> (raw)
In-Reply-To: <dd2d19de-eba5-90be-5f01-ff9fd268685f@redhat.com>

On 19 May 2018 at 07:10, Thomas Huth <thuth@redhat.com> wrote:
> On 18.05.2018 20:31, Peter Maydell wrote:
>> Another flaky test for the collection:
>>
>> TEST: tests/boot-serial-test... (pid=25144)
>>   /sparc64/boot-serial/sun4u:                                          **
>> ERROR:/home/petmay01/linaro/qemu-for-merges/tests/boot-serial-test.c:140:check_guest_output:
>> assertion failed: (output_ok)
>> FAIL
>>
>> Probably another "overly optimistic timeout" setting. (Failed
>> for me on x86-64 host just now.)
>
> That test normally finishes within 3 seconds on my machine. The test
> timeout is 60 seconds. How much load did you have on that machine to go
> from 3s to 60s ?

The machine is my desktop box; I didn't notice anything too
terrible while I was using it interactively at the same time
the test build was running. The test build will run at -j8;
it might also have been during a different -j8 build/test
on the same machine for a different source tree.

60s is quite a long time, so maybe there's an intermittent
deadlock in there instead...

thanks
-- PMM

  reply	other threads:[~2018-05-19 11:37 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
2018-05-18 18:31   ` Peter Maydell
2018-05-19  6:10     ` Thomas Huth
2018-05-19 11:36       ` Peter Maydell [this message]
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='CAFEAcA-9miwQ_JK4VFcFMgWc=XCb_Qf3W4ZFk59csXUGdnAMDA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --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 \
    --cc=stefanha@redhat.com \
    --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 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.