From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
"Ed Maste" <emaste@freebsd.org>,
qemu-block@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, "Christophe Fergeau" <cfergeau@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>
Subject: Re: [Qemu-devel] [PATCH v3 6/7] tests/qemu-iotests/group: Re-use the "auto" group for tests that can always run
Date: Tue, 07 May 2019 15:22:09 +0200 [thread overview]
Message-ID: <87ef5acsce.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190502084506.8009-7-thuth@redhat.com> (Thomas Huth's message of "Thu, 2 May 2019 10:45:05 +0200")
Thomas Huth <thuth@redhat.com> writes:
> Currently, all tests are in the "auto" group. This is a little bit pointless.
> OTOH, we need a group for the tests that we can automatically run during
> "make check" each time, too. Tests in this new group are supposed to run
> with every possible QEMU configuration, for example they must run with every
> QEMU binary (also non-x86), without failing when an optional features is
> missing (but reporting "skip" is ok), and be able to run on all kind of host
> filesystems and users (i.e. also as "nobody" or "root").
> So let's use the "auto" group for this class of tests now. The initial
> list has been determined by running the iotests with non-x86 QEMU targets
> and with our CI pipelines on Gitlab, Cirrus-CI and Travis (i.e. including
> macOS and FreeBSD).
I wonder whether we should additionally limit "make check" to "quick"
tests. How slow are the non-quick auto tests for you?
next prev parent reply other threads:[~2019-05-07 13:23 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 8:44 [Qemu-devel] [PATCH v3 0/7] tests/qemu-iotests: Run basic iotests during "make check" Thomas Huth
2019-05-02 8:44 ` Thomas Huth
2019-05-02 8:45 ` [Qemu-devel] [PATCH v3 1/7] tests/qemu-iotests/005: Add a sanity check for large sparse file support Thomas Huth
2019-05-02 8:45 ` Thomas Huth
2019-05-02 17:37 ` Alex Bennée
2019-05-02 17:37 ` Alex Bennée
2019-05-02 8:45 ` [Qemu-devel] [PATCH v3 2/7] tests/qemu-iotests/check: Pick a default machine if necessary Thomas Huth
2019-05-02 8:45 ` Thomas Huth
2019-05-02 8:45 ` [Qemu-devel] [PATCH v3 3/7] tests/qemu-iotests: Do not hard-code the path to bash Thomas Huth
2019-05-02 8:45 ` Thomas Huth
2019-05-02 8:45 ` [Qemu-devel] [PATCH v3 4/7] cirrus / travis: Add gnu-sed and bash for macOS and FreeBSD Thomas Huth
2019-05-02 8:45 ` Thomas Huth
2019-05-02 8:45 ` [Qemu-devel] [PATCH v3 5/7] tests/qemu-iotests: Remove the "_supported_os Linux" line from many tests Thomas Huth
2019-05-02 8:45 ` Thomas Huth
2019-05-02 8:45 ` [Qemu-devel] [PATCH v3 6/7] tests/qemu-iotests/group: Re-use the "auto" group for tests that can always run Thomas Huth
2019-05-02 8:45 ` Thomas Huth
2019-05-07 13:22 ` Markus Armbruster [this message]
2019-05-07 15:22 ` Thomas Huth
2019-05-07 15:50 ` Eric Blake
2019-05-08 5:47 ` Thomas Huth
2019-05-10 8:55 ` Thomas Huth
2019-05-10 9:15 ` [Qemu-devel] [PATCH v4] " Thomas Huth
2019-05-10 11:38 ` [Qemu-devel] [PATCH v3 6/7] " Markus Armbruster
2019-05-10 14:21 ` Kevin Wolf
2019-05-10 15:29 ` Markus Armbruster
2019-05-10 16:07 ` Kevin Wolf
2019-05-08 12:46 ` Markus Armbruster
2019-05-02 8:45 ` [Qemu-devel] [PATCH v3 7/7] tests: Run the iotests during "make check" again Thomas Huth
2019-05-02 8:45 ` Thomas Huth
2019-05-03 9:53 ` Alex Bennée
2019-05-03 9:53 ` Alex Bennée
2019-05-03 10:03 ` Thomas Huth
2019-05-03 10:03 ` Thomas Huth
2019-05-09 18:08 ` Max Reitz
2019-05-10 4:29 ` Thomas Huth
2019-05-10 13:34 ` Max Reitz
2019-05-10 13:36 ` Thomas Huth
2019-05-10 13:47 ` Max Reitz
2019-05-10 16:20 ` Thomas Huth
2019-05-10 17:40 ` Max Reitz
2019-05-10 13:38 ` Max Reitz
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=87ef5acsce.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cfergeau@redhat.com \
--cc=emaste@freebsd.org \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=lwhsu@freebsd.org \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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.