qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Status and RFC of patchew testings on QEMU
Date: Wed, 19 Jul 2017 15:46:43 +0800	[thread overview]
Message-ID: <20170719074643.GA30261@lemon> (raw)
In-Reply-To: <20170718094247.GD11927@redhat.com>

On Tue, 07/18 10:42, Daniel P. Berrange wrote:
> On Tue, Jul 18, 2017 at 10:37:30AM +0100, Peter Maydell wrote:
> > On 18 July 2017 at 10:11, Thomas Huth <thuth@redhat.com> wrote:
> > > Could the test be rewritten to provide a proper timeout handling
> > > instead? Tests should clearly fail after a while instead of hanging
> > > forever...
> > > Or maybe we could add some magic that the troublesome tests are not
> > > executed if a certain environment variable is set, so we could skip them
> > > in these automated setups here?
> > 
> > I think it's always going to be possible that some bug in
> > QEMU results in a test hanging -- so it must be down to
> > the test harness to deal with hanging tests. And then
> > once you have that functionality in the test harness it
> > doesn't matter quite so much whether an individual test
> > has its own timeout handling or not.
> 
> If the tests are all inside a docker container, then dealing with a hanging
> test is no more difficult than waiting a suitable amount of time and then
> telling docker to destroy the container.

Yes, the context here is non-x86 or non-Linux which are not as easy to run
docker.

Running tests in a VM would be great, but the harness is missing.

Fam

  reply	other threads:[~2017-07-19  7:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17  6:35 [Qemu-devel] Status and RFC of patchew testings on QEMU Fam Zheng
2017-07-17  9:05 ` Stefan Hajnoczi
2017-07-17  9:28   ` Peter Maydell
2017-07-17  9:39     ` Fam Zheng
2017-07-17 10:06       ` Peter Maydell
2017-07-17 10:26         ` Daniel P. Berrange
2017-07-25  9:58           ` Peter Maydell
2017-07-27 11:03             ` Fam Zheng
2017-07-27 11:30               ` Gerd Hoffmann
2017-07-17 10:03   ` Daniel P. Berrange
2017-07-17  9:41 ` Thomas Huth
2017-07-17 10:20   ` Daniel P. Berrange
2017-07-17 11:00     ` Peter Maydell
2017-07-17 11:06       ` Daniel P. Berrange
2017-07-28  5:59     ` Philippe Mathieu-Daudé
2017-07-17 23:17   ` Fam Zheng
2017-07-18  9:11     ` Thomas Huth
2017-07-18  9:37       ` Peter Maydell
2017-07-18  9:42         ` Daniel P. Berrange
2017-07-19  7:46           ` Fam Zheng [this message]
2017-07-17 10:02 ` Daniel P. Berrange
2017-07-21  3:24   ` Fam Zheng
2017-07-17 10:39 ` Kevin Wolf
2017-07-17 10:49   ` Peter Maydell
2017-07-17 11:31     ` Kevin Wolf
2017-07-17 13:40       ` Max Reitz
2017-07-28  5:56         ` Philippe Mathieu-Daudé
2017-07-17 23:28   ` Fam Zheng
2017-07-18 10:14     ` Daniel P. Berrange
2017-07-28  5:46 ` Philippe Mathieu-Daudé
2017-07-28  6:33   ` Fam Zheng
2017-07-28  7:18     ` Cornelia Huck

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=20170719074643.GA30261@lemon \
    --to=famz@redhat.com \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.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).