All of lore.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, linux-riscv@lists.infradead.org,
	thomas@t-8ch.de
Subject: Re: [PATCH 3/4] selftests/nolibc: always print the log file
Date: Mon, 5 Jun 2023 06:20:48 +0200	[thread overview]
Message-ID: <ZH1ioKUVOYGgDUj7@1wt.eu> (raw)
In-Reply-To: <835e118943d257b7a83066fb4fb77c0e5cf71534.1685936428.git.falcon@tinylab.org>

On Mon, Jun 05, 2023 at 11:57:44AM +0800, Zhangjin Wu wrote:
> This allows to check the other issues of the output file manually even
> when all of them passed.

Till now I preferred not to see it when everything was OK since it was
useless and permitted a quick visual check in the reports. Do you
really think it's useful ? If others prefer it that way we can change
it but I purposely added this test to "improve" the output (for me at
least). I'm interested in opinions here.

Willy

WARNING: multiple messages have this Message-ID (diff)
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, linux-riscv@lists.infradead.org,
	thomas@t-8ch.de
Subject: Re: [PATCH 3/4] selftests/nolibc: always print the log file
Date: Mon, 5 Jun 2023 06:20:48 +0200	[thread overview]
Message-ID: <ZH1ioKUVOYGgDUj7@1wt.eu> (raw)
In-Reply-To: <835e118943d257b7a83066fb4fb77c0e5cf71534.1685936428.git.falcon@tinylab.org>

On Mon, Jun 05, 2023 at 11:57:44AM +0800, Zhangjin Wu wrote:
> This allows to check the other issues of the output file manually even
> when all of them passed.

Till now I preferred not to see it when everything was OK since it was
useless and permitted a quick visual check in the reports. Do you
really think it's useful ? If others prefer it that way we can change
it but I purposely added this test to "improve" the output (for me at
least). I'm interested in opinions here.

Willy

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-06-05  4:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-05  3:47 [PATCH 0/4] selftests/nolibc: fix up and improve test report Zhangjin Wu
2023-06-05  3:47 ` Zhangjin Wu
2023-06-05  3:48 ` [PATCH 1/4] selftests/nolibc: add a test-report target Zhangjin Wu
2023-06-05  3:48   ` Zhangjin Wu
2023-06-05  4:18   ` Willy Tarreau
2023-06-05  4:18     ` Willy Tarreau
2023-06-05  6:54     ` Zhangjin Wu
2023-06-05  6:54       ` Zhangjin Wu
2023-06-07  5:52       ` Zhangjin Wu
2023-06-07  5:52         ` Zhangjin Wu
2023-06-07 12:45         ` Willy Tarreau
2023-06-07 12:45           ` Willy Tarreau
2023-06-07 14:15           ` Zhangjin Wu
2023-06-07 14:15             ` Zhangjin Wu
2023-06-05  3:50 ` [PATCH 2/4] selftests/nolibc: allow run test-report directly Zhangjin Wu
2023-06-05  3:50   ` Zhangjin Wu
2023-06-05  3:57 ` [PATCH 3/4] selftests/nolibc: always print the log file Zhangjin Wu
2023-06-05  3:57   ` Zhangjin Wu
2023-06-05  4:20   ` Willy Tarreau [this message]
2023-06-05  4:20     ` Willy Tarreau
2023-06-05  7:05     ` Zhangjin Wu
2023-06-05  7:05       ` Zhangjin Wu
2023-06-05  3:58 ` [PATCH 4/4] selftests/nolibc: fix up test-report for run target Zhangjin Wu
2023-06-05  3:58   ` Zhangjin Wu
2023-06-05  4:23   ` Willy Tarreau
2023-06-05  4:23     ` Willy Tarreau
2023-06-05  6:32 ` [PATCH 0/4] selftests/nolibc: fix up and improve test report Willy Tarreau
2023-06-05  6:32   ` Willy Tarreau
2023-06-05 10:53   ` Zhangjin Wu
2023-06-05 10:53     ` Zhangjin Wu
2023-06-06  4:50     ` Willy Tarreau
2023-06-06  4:50       ` 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=ZH1ioKUVOYGgDUj7@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=linux-riscv@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.