On Fri, Sep 27, 2019 at 11:42:25AM +0100, Andre Przywara wrote:
> For some tests we mix variable diagnostic output with the test name,
> which leads to variable test line, confusing some higher level
> frameworks.
>
> Split the output to always use the same test name for a certain test,
> and put diagnostic output on a separate line using the INFO: tag.
>
> Signed-off-by: Andre Przywara <andre.przywara@xxxxxxx>
> ---
> arm/selftest.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/arm/selftest.c b/arm/selftest.c
> index 28a17f7..a0c1ab8 100644
> --- a/arm/selftest.c
> +++ b/arm/selftest.c
> @@ -43,13 +43,16 @@ static void check_setup(int argc, char **argv)
> phys_addr_t memsize = PHYS_END - PHYS_OFFSET;
> phys_addr_t expected = ((phys_addr_t)val)*1024*1024;
>
> - report("size = %" PRIu64 " MB", memsize == expected,
> - memsize/1024/1024);
> + report("memory size matches expectation",
> + memsize == expected);
> + report_info("found %" PRIu64 " MB", memsize/1024/1024);
> ++nr_tests;
>
> } else if (strcmp(argv[i], "smp") == 0) {
>
> - report("nr_cpus = %d", nr_cpus == (int)val, nr_cpus);
> + report("number of CPUs matches expectation",
> + nr_cpus == (int)val);
> + report_info("found %d CPUs", nr_cpus);
> ++nr_tests;
> }
>
> --
> 2.17.1
>
Reviewed-by: Andrew Jones <drjones@xxxxxxxxxx>
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
