public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yohei Kojima <yk@y-koj.net>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: Shuah Khan <shuah@kernel.org>,
	Brendan Jackman <jackmanb@google.com>,
	Shuah Khan <skhan@linuxfoundation.org>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] selftests: runner: Avoid spurious warning about missing failures file
Date: Thu, 9 Apr 2026 22:38:56 +0900	[thread overview]
Message-ID: <ader8C3F2uOY7ro6@desktop.y-koj.net> (raw)
In-Reply-To: <20260224-kselftest-fix-failures-file-v2-1-2bfb8f5cb6a8@linutronix.de>

On Tue, Feb 24, 2026 at 04:37:56PM +0100, Thomas Weißschuh wrote:
> When runner.sh is *not* executed via run_kselftest.sh, the variable
> $kselftest_failures_file does not exist. This triggers a harmless but
> annyoing warning from runner.sh if a test fails:
> 
> tools/testing/selftests/kselftest/runner.sh: line 50: : No such file or directory
> 
> Silence the spurious warning.
> 
> Fixes: d9e6269e3303 ("selftests/run_kselftest.sh: exit with error if tests fail")
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> Reviewed-By: Brendan Jackman <jackmanb@google.com>

Hi all,

It seems this patch hasn't been picked up yet, although it already got
reviewed by Brendan. This bug is also mentioned by a netdev maintainer
and several developers [1], so I think it would be nice to have this
patch merged.

[1]: https://lore.kernel.org/lkml/20260112135326.7ce71119@kernel.org/

I confirmed that it still applies to 7.0-rc7. I also tested it by adding
a failing test to net and namespaces selftests, and confirmed that the
error disappeared.

Tested-by: Yohei Kojima <yk@y-koj.net>

Thanks,
Yohei

> ---
> Changes in v2:
> - Rebase on v7.0-rc1
> - Pick up review tag
> - Link to v1: https://lore.kernel.org/r/20260128-kselftest-fix-failures-file-v1-1-b58072c66317@linutronix.de
> ---
>  tools/testing/selftests/kselftest/runner.sh | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/kselftest/runner.sh b/tools/testing/selftests/kselftest/runner.sh
> index 3a62039fa621..1eb935b6f790 100644
> --- a/tools/testing/selftests/kselftest/runner.sh
> +++ b/tools/testing/selftests/kselftest/runner.sh
> @@ -47,7 +47,7 @@ tap_timeout()
>  report_failure()
>  {
>  	echo "not ok $*"
> -	echo "$*" >> "$kselftest_failures_file"
> +	echo "$*" >> "${kselftest_failures_file:-/dev/null}"
>  }
>  
>  run_one()
> 
> ---
> base-commit: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f
> change-id: 20260128-kselftest-fix-failures-file-8b38692c2a3c
> 
> Best regards,
> -- 
> Thomas Weißschuh <thomas.weissschuh@linutronix.de>
> 

      reply	other threads:[~2026-04-09 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-24 15:37 [PATCH v2] selftests: runner: Avoid spurious warning about missing failures file Thomas Weißschuh
2026-04-09 13:38 ` Yohei Kojima [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=ader8C3F2uOY7ro6@desktop.y-koj.net \
    --to=yk@y-koj.net \
    --cc=jackmanb@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=skhan@linuxfoundation.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