mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brendan Jackman <jackmanb@google.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
	"Brendan Jackman" <jackmanb@google.com>
Cc: Shuah Khan <shuah@kernel.org>, <linux-kselftest@vger.kernel.org>,
	 <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] selftests/run_kselftest.sh: exit with error if tests fail
Date: Fri, 31 Oct 2025 12:57:06 +0000	[thread overview]
Message-ID: <DDWIW4V2X9EX.1VQ2QCG6AU78R@google.com> (raw)
In-Reply-To: <80dec5ff-a9b2-4622-9dc9-ac65ca06e187@linutronix.de>

On Fri Oct 31, 2025 at 12:48 PM UTC, Thomas Weißschuh wrote:
> Hi Brendan,
>
> Oct 14, 2025 16:45:32 Brendan Jackman <jackmanb@google.com>:
>
> (...)
>
>> In case any user depends on the current behaviour, such as running this
>> from a script with `set -e` and parsing the result for failures
>> afterwards, add a flag they can set to get the old behaviour, namely
>> --no-error-on-fail.
>
> IMO this new flag is also unnecessary.
> The user can just do "|| true" when needed.
>

`|| true` is not the same thing, if you do that then you completely hide
all failures of the script. With --no-error-on-fail you just skip the
specific case of tests failing.

I did say somewhere in a previous thread that this distinction (test
failure vs test harness failure) is always gonna be a bit sketchy for
this script since it's running on the kernel under test. But that
doesn't mean we should give up on it completely completely.

      reply	other threads:[~2025-10-31 12:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 14:45 Brendan Jackman
2025-10-31 12:44 ` Brendan Jackman
2025-10-31 12:48 ` Thomas Weißschuh
2025-10-31 12:57   ` Brendan Jackman [this message]

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=DDWIW4V2X9EX.1VQ2QCG6AU78R@google.com \
    --to=jackmanb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=thomas.weissschuh@linutronix.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

all inboxes | Powered by JetHome®