From: Fam Zheng <famz@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Yash Mankad" <ymankad@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Markus Armbruster" <armbru@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] Who is running QEMU automated tests, and when?
Date: Fri, 27 Apr 2018 11:10:54 +0800 [thread overview]
Message-ID: <20180427031054.GL17690@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180426135755.GI29865@localhost.localdomain>
On Thu, 04/26 10:57, Eduardo Habkost wrote:
> So, for anybody that runs automated QEMU tests once in a while,
> can we know:
>
> * What test cases are you running? Where can we get more
> information about the tests you run?
These currently run on patchew:
* checkpatch
* ./configure && make (s390 host)
* make docker-test-mingw@fedora
* make docker-test-quick@centos6
* make docker-test-build@min-glib
> * When do you run them? What triggers a new test run?
They are run against each series posted to qemu-devel@nongnu.org. All errors are
sent as reply to the cover letter with the concrete commands, env info and log.
(Should we create a wiki page to maintain information collected by this thread?)
Fam
next prev parent reply other threads:[~2018-04-27 3:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 13:57 [Qemu-devel] Who is running QEMU automated tests, and when? Eduardo Habkost
2018-04-26 14:04 ` Peter Maydell
2018-04-26 21:51 ` Michael Clark
2018-05-09 15:53 ` Alex Bennée
2018-05-09 16:25 ` Thomas Huth
2018-04-26 14:09 ` Thomas Huth
2018-04-26 14:14 ` Daniel P. Berrangé
2018-04-26 14:22 ` Eduardo Habkost
2018-04-26 14:24 ` Daniel P. Berrangé
2018-04-27 3:58 ` Thomas Huth
2018-04-27 8:57 ` Daniel P. Berrangé
2018-04-26 14:25 ` Thomas Huth
2018-04-26 15:45 ` Cornelia Huck
2018-04-27 3:10 ` Fam Zheng [this message]
2018-04-27 19:23 ` Eduardo Habkost
2018-04-27 14:33 ` Anthony PERARD
2018-04-27 19:13 ` Lukáš Doktor
2018-05-08 9:56 ` Stefan Hajnoczi
2018-05-08 18:13 ` John Snow
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=20180427031054.GL17690@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=armbru@redhat.com \
--cc=crosa@redhat.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=ymankad@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.