From: Fam Zheng <famz@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Status and RFC of patchew testings on QEMU
Date: Tue, 18 Jul 2017 07:17:21 +0800 [thread overview]
Message-ID: <20170717231721.GE2585@lemon> (raw)
In-Reply-To: <b718f71c-5208-298a-4fb9-0c2fea3146ec@redhat.com>
On Mon, 07/17 11:41, Thomas Huth wrote:
> On 17.07.2017 08:35, Fam Zheng wrote:
> > Hi all,
> >
> > Today I've included a fourth type of the automatic patchew replies: FreeBSD.
> >
> > So far we have these tests running by patchew on each patch series:
> >
> > * Docker tests
> > Basically it is
> > make docker-test-quick@centos6 \
> > docker-test-build@min-glib \
> > docker-test-mingw@fedora"
> >
> > * checkpatch.pl
> > Each patch is fed to ./scripts/checkpatch.pl and all errors are reported.
> >
> > * s390x
> > It runs on a machine shared by Fedora team, basically only "./configure and
> > make", because "make check" hanging is tricky to deal with from an
> > automation perspective. (Ideas?)
>
> Is there any check that could hang "forever"? I think most of the checks
> should have a proper timeout of one or two minutes, don't they?
>
> Maybe you could also simply run the "make check" with the "timeout"
> command to avoid that it hangs forever?
Not every operation has a timeout in our tests, with the usual culprit being
vhost-user-test.
timeout can terminate make and directly invoked qtest commands, but qemu
processes that block or hang cannot be cleaned up.
Fam
next prev parent reply other threads:[~2017-07-17 23:17 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 [this message]
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
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=20170717231721.GE2585@lemon \
--to=famz@redhat.com \
--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 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.