public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 0/5] selftests/nolibc: report: print test status
Date: Sun, 9 Jul 2023 10:58:29 +0200	[thread overview]
Message-ID: <20230709085829.GC9321@1wt.eu> (raw)
In-Reply-To: <cover.1688633188.git.falcon@tinylab.org>

Hi Zhangjin,

On Thu, Jul 06, 2023 at 05:02:26PM +0800, Zhangjin Wu wrote:
> 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'.

So as I mentioned with some commits, I *do* find it important to
preserve the convenience of grepping for a single word to from 20
test reports at once and visually check all statuses (and in this
sense I like your preference for aligning the words to make them
more readable). But having to guess some grep context and see the
output garbled clearly does the opposite of what we were looking
for in my opinion. Also, I think there's no need for having 5
separate patches to add/remove a line feed. Better discuss an
output format that matches everyone's needs and change it at once,
this will make the patch more reviewable than having individual
changes like this.

thanks,
willy

  parent reply	other threads:[~2023-07-09  8:58 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
2023-07-06  9:12 ` [PATCH v1 5/5] selftests/nolibc: report: add newline before test failures Zhangjin Wu
2023-07-09  8:58 ` Willy Tarreau [this message]
2023-07-09 19:44   ` [PATCH v1 0/5] selftests/nolibc: report: print test status 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=20230709085829.GC9321@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