From: Andrew Jones <ajones@ventanamicro.com>
To: kvm-riscv@lists.infradead.org
Subject: [PATCH V2 4/6] riscv: Enable gen_report() to print the wrong value in case of failure
Date: Wed, 13 Mar 2024 12:19:00 +0100 [thread overview]
Message-ID: <20240313-5ecfc895c3e1aed8a053c0da@orel> (raw)
In-Reply-To: <20240313084644.277426-5-cem@kernel.org>
On Wed, Mar 13, 2024 at 09:46:22AM +0100, cem at kernel.org wrote:
> From: Carlos Maiolino <cem@kernel.org>
>
> If the test fails because the expected value doesn't match, it's
> useful to know what value was actually printed.
>
> Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
> ---
> V2:
> - Reduce subject to fit 70 chars
> - Use report_info() to output expected vs received values,
> leaving only necessary information for parsers on report()
>
> riscv/sbi.c | 17 +++++++++++------
> 1 file changed, 11 insertions(+), 6 deletions(-)
>
> diff --git a/riscv/sbi.c b/riscv/sbi.c
> index 76f6111d..bc0f5c68 100644
> --- a/riscv/sbi.c
> +++ b/riscv/sbi.c
> @@ -25,10 +25,15 @@ static bool env_or_skip(const char *env)
> return true;
> }
>
> -static void gen_report(struct sbiret *ret, long expected)
> +static void gen_report(struct sbiret *ret,
> + long expected_error, long expected_value)
> {
> - report(!ret->error, "no sbi.error");
> - report(ret->value == expected, "expected sbi.value");
> + if (ret->value != expected_value)
This should be
if (ret->error != expected_error || ret->value != expected_value)
> + report_info("expected (error: %ld, value: %ld), received: (error: %ld, value %ld)\n",
> + expected_error, expected_value, ret->error, ret->value);
> +
> + report(ret->error == expected_error, "expected sbi.error");
> + report(ret->value == expected_value, "expected sbi.value");
nit: We can reduce some code clutter with
bool check_error = ret->error == expected_error;
bool check_value = ret->value == expected_value;
if (!check_error || !check_value)
report_info(...);
report(check_error, ...);
report(check_value, ...);
> }
>
> static void check_base(void)
> @@ -42,14 +47,14 @@ static void check_base(void)
> if (env_or_skip("MVENDORID")) {
> expected = strtol(getenv("MVENDORID"), NULL, 0);
> ret = sbi_ecall(SBI_EXT_BASE, SBI_EXT_BASE_GET_MVENDORID, 0, 0, 0, 0, 0, 0);
> - gen_report(&ret, expected);
> + gen_report(&ret, 0, expected);
> }
> report_prefix_pop();
>
> report_prefix_push("probe_ext");
> expected = getenv("PROBE_EXT") ? strtol(getenv("PROBE_EXT"), NULL, 0) : 1;
> ret = sbi_ecall(SBI_EXT_BASE, SBI_EXT_BASE_PROBE_EXT, SBI_EXT_BASE, 0, 0, 0, 0, 0);
> - gen_report(&ret, expected);
> + gen_report(&ret, 0, expected);
> report_prefix_pop();
>
> report_prefix_push("marchid");
> @@ -57,7 +62,7 @@ static void check_base(void)
> expected = strtol(getenv("MARCHID"), NULL, 0);
> ret = sbi_ecall(SBI_EXT_BASE, SBI_EXT_BASE_PROBE_EXT,
> SBI_EXT_BASE_GET_MARCHID, 0, 0, 0, 0, 0);
> - gen_report(&ret, expected);
> + gen_report(&ret, 0, expected);
> }
> report_prefix_pop();
>
> --
> 2.44.0
>
Thanks,
drew
next prev parent reply other threads:[~2024-03-13 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 8:46 [PATCH V2 0/6] Add riscv tests to cover the base extension specs cem
2024-03-13 8:46 ` [PATCH V2 1/6] riscv: Add test to probe SBI Extension cem
2024-03-13 11:06 ` Andrew Jones
2024-03-13 8:46 ` [PATCH V2 2/6] riscv: Factor out environment variable check and report generation cem
2024-03-13 11:11 ` Andrew Jones
2024-03-13 8:46 ` [PATCH V2 3/6] riscv: Implement test for architecture ID register cem
2024-03-13 11:21 ` Andrew Jones
2024-03-13 8:46 ` [PATCH V2 4/6] riscv: Enable gen_report() to print the wrong value in case of failure cem
2024-03-13 11:19 ` Andrew Jones [this message]
2024-03-13 8:46 ` [PATCH V2 5/6] riscv: Test for specific SBI implementation ID cem
2024-03-13 11:23 ` Andrew Jones
2024-03-13 11:28 ` Andrew Jones
2024-03-13 8:46 ` [PATCH 6/6] riscv: Add a wrapper to call sbi_ecall for base extension cem
2024-03-13 11:33 ` Andrew Jones
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=20240313-5ecfc895c3e1aed8a053c0da@orel \
--to=ajones@ventanamicro.com \
--cc=kvm-riscv@lists.infradead.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