From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: w@1wt.eu, arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, tanyuan@tinylab.org
Subject: Re: [PATCH v1 1/3] selftests/nolibc: allow report with existing test log
Date: Fri, 4 Aug 2023 17:30:52 +0200 [thread overview]
Message-ID: <fc316639-10c7-46d3-a897-9553606aba2d@t-8ch.de> (raw)
In-Reply-To: <a2879d1ef44fd482a63a8d1a41527289ebcd501b.1691073180.git.falcon@tinylab.org>
On 2023-08-03 22:44:47+0800, Zhangjin Wu wrote:
> After the tests finish, it is valuable to report and summarize with
> existing test log.
>
> This avoid rerun or run the tests again when not necessary.
>
> Signed-off-by: Zhangjin Wu <falcon@tinylab.org>
Reviewed-by: Thomas Weißschuh <linux@weissschuh.net>
> ---
> tools/testing/selftests/nolibc/Makefile | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/tools/testing/selftests/nolibc/Makefile b/tools/testing/selftests/nolibc/Makefile
> index 16cc33db54e3..51fef5e6a152 100644
> --- a/tools/testing/selftests/nolibc/Makefile
> +++ b/tools/testing/selftests/nolibc/Makefile
> @@ -225,6 +225,10 @@ rerun:
> $(Q)qemu-system-$(QEMU_ARCH) -display none -no-reboot -kernel "$(srctree)/$(IMAGE)" -serial stdio $(QEMU_ARGS) > "$(CURDIR)/run.out"
> $(Q)$(REPORT) $(CURDIR)/run.out
>
> +# report with existing test log
> +report:
> + $(Q)$(REPORT) $(CURDIR)/run.out
> +
> clean:
> $(call QUIET_CLEAN, sysroot)
> $(Q)rm -rf sysroot
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-08-04 15:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 14:43 [PATCH v1 0/3] selftests/nolibc: add misc improvments Zhangjin Wu
2023-08-03 14:44 ` [PATCH v1 1/3] selftests/nolibc: allow report with existing test log Zhangjin Wu
2023-08-04 15:30 ` Thomas Weißschuh [this message]
2023-08-03 14:45 ` [PATCH v1 2/3] selftests/nolibc: fix up O= option support Zhangjin Wu
2023-08-04 6:25 ` Thomas Weißschuh
2023-08-04 7:43 ` Zhangjin Wu
2023-08-04 15:05 ` Thomas Weißschuh
2023-08-04 15:52 ` Zhangjin Wu
2023-08-04 16:02 ` Thomas Weißschuh
2023-08-04 16:29 ` Zhangjin Wu
2023-08-04 17:51 ` Thomas Weißschuh
2023-08-04 17:54 ` Willy Tarreau
2023-08-04 18:40 ` Zhangjin Wu
2023-08-04 18:43 ` Willy Tarreau
2023-08-04 19:17 ` Zhangjin Wu
2023-08-03 14:47 ` [PATCH v1 3/3] tools/nolibc: stackprotector.h: make __stack_chk_init static Zhangjin Wu
2023-08-04 15:38 ` Thomas Weißschuh
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=fc316639-10c7-46d3-a897-9553606aba2d@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tanyuan@tinylab.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®