From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, pbonzini@redhat.com
Subject: [PATCH v2 0/4] tests/decode: Convert tests to meson
Date: Thu, 25 May 2023 19:12:24 -0700 [thread overview]
Message-ID: <20230526021228.1777917-1-richard.henderson@linaro.org> (raw)
Add --test-for-error to decodetree.py and convert the tests to meson.
This exposes an exception error that had been hidden by the fact that
the script as a whole did exit with error. Which proves that this is
a better way to run the tests.
r~
Richard Henderson (4):
decodetree: Add --test-for-error
decodetree: Fix recursion in prop_format and build_tree
decodetree: Diagnose empty pattern group
tests/decode: Convert tests to meson
scripts/decodetree.py | 19 ++++++++++---
tests/decode/check.sh | 24 ----------------
tests/decode/meson.build | 59 ++++++++++++++++++++++++++++++++++++++++
tests/meson.build | 5 +---
4 files changed, 75 insertions(+), 32 deletions(-)
delete mode 100755 tests/decode/check.sh
create mode 100644 tests/decode/meson.build
--
2.34.1
next reply other threads:[~2023-05-26 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 2:12 Richard Henderson [this message]
2023-05-26 2:12 ` [PATCH v2 1/4] decodetree: Add --test-for-error Richard Henderson
2023-05-26 2:12 ` [PATCH v2 2/4] decodetree: Fix recursion in prop_format and build_tree Richard Henderson
2023-05-26 2:12 ` [PATCH v2 3/4] decodetree: Diagnose empty pattern group Richard Henderson
2023-05-26 2:12 ` [PATCH v2 4/4] tests/decode: Convert tests to meson Richard Henderson
2023-05-26 9:06 ` [PATCH v2 0/4] " Philippe Mathieu-Daudé
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=20230526021228.1777917-1-richard.henderson@linaro.org \
--to=richard.henderson@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).