From: Anthony PERARD <anthony.perard@citrix.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 15:33:42 +0100 [thread overview]
Message-ID: <20180427143342.GA15594@perard> (raw)
In-Reply-To: <20180426135755.GI29865@localhost.localdomain>
On Thu, Apr 26, 2018 at 10:57:55AM -0300, 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?
> * When do you run them? What triggers a new test run?
FYI, we do test QEMU with Xen. But that mostly integration test. I guess
not much of QEMU is tested.
osstest run with the upstream QEMU tree about once a day, if the tree as
changed or if the last test run failed. The test result is sent to
xen-devel ml.
As for what is runned, it mostly starts Xen guests, do migrate, with
different configuration.
Regards,
--
Anthony PERARD
next prev parent reply other threads:[~2018-04-27 14:33 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
2018-04-27 19:23 ` Eduardo Habkost
2018-04-27 14:33 ` Anthony PERARD [this message]
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=20180427143342.GA15594@perard \
--to=anthony.perard@citrix.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 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).