From: Zhangjin Wu <falcon@tinylab.org>
To: w@1wt.eu
Cc: falcon@tinylab.org, arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, thomas@t-8ch.de
Subject: [PATCH v1 0/5] selftests/nolibc: report: print test status
Date: Thu, 6 Jul 2023 17:02:26 +0800 [thread overview]
Message-ID: <cover.1688633188.git.falcon@tinylab.org> (raw)
Hi, Willy
As you suggested, the 'status: [success|warning|failure]' info is added
to the summary line, with additional newlines around this line to
extrude the status info. at the same time, the total tests is printed,
the passed, skipped and failed values are aligned with '%03d'.
This patchset is based on 20230705-nolibc-series2 of nolibc repo[1].
The test result looks like:
...
138 test(s): 135 passed, 002 skipped, 001 failed => status: failure
See all results in /labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc/run.out
Or:
...
137 test(s): 134 passed, 003 skipped, 000 failed => status: warning
See all results in /labs/linux-lab/src/linux-stable/tools/testing/selftests/nolibc/run.out
Best regards,
Zhangjin
---
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/wtarreau/nolibc.git
Zhangjin Wu (5):
selftests/nolibc: report: print a summarized test status
selftests/nolibc: report: print total tests
selftests/nolibc: report: align passed, skipped and failed
selftests/nolibc: report: extrude the test status line
selftests/nolibc: report: add newline before test failures
tools/testing/selftests/nolibc/Makefile | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.25.1
next reply other threads:[~2023-07-06 9:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 9:02 Zhangjin Wu [this message]
2023-07-06 9:03 ` [PATCH v1 1/5] selftests/nolibc: report: print a summarized test status Zhangjin Wu
2023-07-06 9:08 ` [PATCH v1 2/5] selftests/nolibc: report: print total tests Zhangjin Wu
2023-07-06 9:10 ` [PATCH v1 3/5] selftests/nolibc: report: align passed, skipped and failed Zhangjin Wu
2023-07-09 8:51 ` Willy Tarreau
2023-07-09 18:51 ` Zhangjin Wu
2023-07-06 9:11 ` [PATCH v1 4/5] selftests/nolibc: report: extrude the test status line Zhangjin Wu
2023-07-09 8:54 ` Willy Tarreau
2023-07-09 19:26 ` Zhangjin Wu
2023-07-10 6:30 ` Willy Tarreau
2023-07-06 9:12 ` [PATCH v1 5/5] selftests/nolibc: report: add newline before test failures Zhangjin Wu
2023-07-09 8:58 ` [PATCH v1 0/5] selftests/nolibc: report: print test status Willy Tarreau
2023-07-09 19:44 ` Zhangjin Wu
2023-07-10 6:32 ` Willy Tarreau
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=cover.1688633188.git.falcon@tinylab.org \
--to=falcon@tinylab.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=thomas@t-8ch.de \
--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