From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Thomas Huth <thuth@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 8/8] tests: Run device-crash-test on "make check"
Date: Mon, 12 Mar 2018 15:23:05 -0300 [thread overview]
Message-ID: <20180312182305.GC28578@localhost.localdomain> (raw)
In-Reply-To: <20180309202827.12085-9-ehabkost@redhat.com>
On Fri, Mar 09, 2018 at 05:28:27PM -0300, Eduardo Habkost wrote:
> Run a subset of tests using device-crash-test on "make check", to
> help us catch device crashes earlier.
>
> This also add a "check-device-crash-test-full" rule, that will
> check all machine/device combinations.
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> tests/Makefile.include | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/tests/Makefile.include b/tests/Makefile.include
> index ef9b88c369..0ba641b8d4 100644
> --- a/tests/Makefile.include
> +++ b/tests/Makefile.include
> @@ -942,6 +942,17 @@ check-decodetree:
> ./check.sh "$(PYTHON)" "$(SRC_PATH)/scripts/decodetree.py", \
> TEST, decodetree.py)
>
> +CRASH_TEST = $(SRC_PATH)/scripts/device-crash-test
> +CRASH_TEST_OPTIONS = $(if $(V),-v,-q)
> +CRASH_TEST_BINARIES = $(foreach TARGET,$(TARGETS), $(TARGET)-softmmu/qemu-system-$(TARGET))
> +
> +.PHONY: check-device-crash-quick
> +check-device-crash-quick:
> + $(CRASH_TEST) $(CRASH_TEST_OPTIONS) -t machine=DEFAULT accel=tcg -- $(CRASH_TEST_BINARIES)
> +
> +check-device-crash-full:
> + $(CRASH_TEST) $(CRASH_TEST_OPTIONS) -F $(CRASH_TEST_BINARIES)
> +
> # Consolidated targets
>
> .PHONY: check-qapi-schema check-qtest check-unit check check-clean
> @@ -950,7 +961,7 @@ check-qtest: $(patsubst %,check-qtest-%, $(QTEST_TARGETS))
> check-unit: $(patsubst %,check-%, $(check-unit-y))
> check-speed: $(patsubst %,check-%, $(check-speed-y))
> check-block: $(patsubst %,check-%, $(check-block-y))
> -check: check-qapi-schema check-unit check-qtest check-decodetree
> +check: check-qapi-schema check-unit check-qtest check-decodetree check-device-crash-quick
Making device-crash-test work with Python 3 will take more work
than I have expected, so I won't try to include it on "make
check" yet.
I will send a version that only adds the "check-device-crash-*"
rules, so people can start running "make check-device-crash-quick"
on their scripts if they know the host has Python 2.7 available.
--
Eduardo
next prev parent reply other threads:[~2018-03-12 18:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 20:28 [Qemu-devel] [PATCH 0/8] tests: Run device-crash-test on "make check" Eduardo Habkost
2018-03-09 20:28 ` [Qemu-devel] [PATCH 1/8] device-crash-test: Refactor loglevel configuration code Eduardo Habkost
2018-03-09 20:28 ` [Qemu-devel] [PATCH 2/8] device-crash-test: Add examples to script documentation Eduardo Habkost
2018-03-09 20:28 ` [Qemu-devel] [PATCH 3/8] device-crash-test: Accept machine=DEFAULT to test the default machine Eduardo Habkost
2018-03-09 20:28 ` [Qemu-devel] [PATCH 4/8] device-crash-test: New known crashes Eduardo Habkost
2018-03-09 20:28 ` [Qemu-devel] [PATCH 5/8] device-crash-test: Remove runnable-machine check Eduardo Habkost
2018-03-09 20:28 ` [Qemu-devel] [PATCH 6/8] device-crash-test: Use WARN for known crashes Eduardo Habkost
2018-03-09 20:28 ` [Qemu-devel] [PATCH 7/8] device-crash-test: Don't print warnings in quiet mode Eduardo Habkost
2018-03-09 20:28 ` [Qemu-devel] [PATCH 8/8] tests: Run device-crash-test on "make check" Eduardo Habkost
2018-03-12 18:23 ` Eduardo Habkost [this message]
2018-03-12 18:25 ` [Qemu-devel] [PATCH v2 8/8] tests: Add check-device-crash-* rules Eduardo Habkost
2018-03-09 20:48 ` [Qemu-devel] [PATCH 0/8] tests: Run device-crash-test on "make check" no-reply
2018-03-09 20:55 ` Eduardo Habkost
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=20180312182305.GC28578@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=crosa@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).