From: Willy Tarreau <w@1wt.eu>
To: Zhangjin Wu <falcon@tinylab.org>
Cc: arnd@arndb.de, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, thomas@t-8ch.de
Subject: Re: [PATCH v1 4/5] selftests/nolibc: report: extrude the test status line
Date: Mon, 10 Jul 2023 08:30:27 +0200 [thread overview]
Message-ID: <ZKulgwwDjubkZuTa@1wt.eu> (raw)
In-Reply-To: <20230709192652.97668-1-falcon@tinylab.org>
Hi Zhangjin,
On Mon, Jul 10, 2023 at 03:26:52AM +0800, Zhangjin Wu wrote:
> > On Thu, Jul 06, 2023 at 05:11:17PM +0800, Zhangjin Wu wrote:
> > > two newlines are added around the test summary line to extrude the test
> > > status.
> >
> > But then we're back to making it annoying to check, having to figure
> > if we need to grep -A or grep -B etc. With grep 'status:' we would get
> > a synthetic status and the counters together. Why do you think it's
> > not convenient ? Or am I the only one considering it useful to just
> > run grep "status:" on all output files and figure a global status at
> > once ?
>
> Sorry, Willy, my commit message may mislead you a little.
>
> The newlines are added around the whole test summary line (with the
> status info), not only around the 'status info' ;-)
Ah OK, thanks for clarifying this!
> It is not for status grep, it is for developers to easily see the whole
> summary line at a glance
I understand but both work hand-in-hand, as every time you'll perform
a slight change, you'll necessarily rerun the whole series on all archs
to confirm, which is why I'm particularly annoying about the ability to
grep!
> And further, if not consider pure-text, the colors may be more helpful,
> for example, red for failed/failure, yellow for skipped/warning, green
> for passed/success, for example:
>
> $ echo | awk 'END{printf("138 test(s): \033[32m135\033[0m passed, \033[33m 2\033[0m skipped, \033[31m 1\033[0m failed => status: \033[31mfailure\033[0m\n");}'
> 138 test(s): 135 passed, 2 skipped, 1 failed => status: failure
>
> But as we can see, the color control code is not readable and it may
> break the simple "status: failure" grep, we should use something like
> "status: .*failure" ;-)
Colors may only be used when stdout is a terminal, and still, some might
find it annonying (for example some distros use unreadably dark colors
that were apparently never tested over a black background, forcing users
to highlight the text by selecting it with the mouse to read it). Better
not start to play with this IMO, that's not really needed and may be more
annoying to some than helpful to most.
Thanks,
Willy
next prev parent reply other threads:[~2023-07-10 6:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 9:02 [PATCH v1 0/5] selftests/nolibc: report: print test status Zhangjin Wu
2023-07-06 9:03 ` [PATCH v1 1/5] selftests/nolibc: report: print a summarized " 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 [this message]
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=ZKulgwwDjubkZuTa@1wt.eu \
--to=w@1wt.eu \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=thomas@t-8ch.de \
/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