mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
	linux-doc@vger.kernel.org, "Mark Brown" <broonie@kernel.org>,
	"Ricardo B. Marlière" <rbm@suse.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH 2/7] selftests: optionally record per-suite build and install results
Date: Thu, 15 Oct 2026 13:22:55 -0600	[thread overview]
Message-ID: <5bcc0ed9-b48d-483c-8bfa-ec31f111320e@linuxfoundation.org> (raw)
In-Reply-To: <20261014200115.1363363-3-sashal@kernel.org>

On 10/14/26 14:01, Sasha Levin wrote:
> By default the selftests build and installation succeed as long as one
> target succeeds, so that a single broken suite does not cost CI systems
> the coverage of all others; commit cad6f32665cb ("selftests: Deescalate
> error reporting") restored that policy after it had been tightened.
> The exit status of make therefore cannot tell which suites failed, and
> inspecting the installation is not reliable either: a suite whose
> compilation failed can still install its scripts.
> 
> Add an opt-in report. When KSFT_BUILD_REPORT names an absolute file,
> the all and install rules append one tab-separated record per target
> with the phase, the target name and the exit status of its recursive
> make. Generating the runlist is recorded as part of the install phase.
> The records are written without changing which targets are built or
> installed or the exit status of make, also with FORCE_TARGETS. Nothing
> is recorded by make -n, -t or -q, including when the selftests are
> built through the kernel's kselftest targets, which clear MAKEFLAGS.
> 
> The recording helper lives in a small fragment so that suites built
> from subdirectories can add records for them, and the variable is
> exported to sub-makes. A relative path is rejected, since every
> recursive make runs in a different directory. Keep the exit status of
> the runlist generation loop as before, and create an empty runlist for
> installations in which no target emits tests.
> 
> Document the format, version 1, and how to read it.
> 
> Link: https://lore.kernel.org/r/20260416-selftests-deescalate-error-reporting-v1-1-38e7c0536227@kernel.org
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
>   Documentation/dev-tools/kselftest.rst   | 38 +++++++++++++++++++++++++
>   tools/testing/selftests/Makefile        | 31 ++++++++++++++------
>   tools/testing/selftests/build_report.mk | 26 +++++++++++++++++
>   3 files changed, 87 insertions(+), 8 deletions(-)
>   create mode 100644 tools/testing/selftests/build_report.mk
> 

I picked this up for the next merge window. Patch is in kselftest next.

thanks,
-- Shuah

  reply	other threads:[~2026-10-15 19:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14 20:01 [PATCH 0/7] selftests: report per-suite build results without failing the build Sasha Levin
2026-10-14 20:01 ` [PATCH 1/7] selftests: keep the build status from wrapping to success Sasha Levin
2026-10-15 18:00   ` Mark Brown
2026-10-15 19:21     ` Shuah Khan
2026-10-14 20:01 ` [PATCH 2/7] selftests: optionally record per-suite build and install results Sasha Levin
2026-10-15 19:22   ` Shuah Khan [this message]
2026-10-14 20:01 ` [PATCH 3/7] selftests/futex: report failures of the functional subdirectory Sasha Levin
2026-10-14 20:01 ` [PATCH 4/7] kselftest/arm64: keep building and installing after a subdirectory fails Sasha Levin
2026-10-15 17:46   ` Catalin Marinas
2026-10-15 18:16   ` Mark Brown
2026-10-14 20:01 ` [PATCH 5/7] selftests/riscv: " Sasha Levin
2026-10-14 20:01 ` [PATCH 6/7] selftests/powerpc: report the outcome of each subdirectory Sasha Levin
2026-10-14 20:01 ` [PATCH 7/7] selftests/sparc64: report failures of the drivers subdirectory Sasha Levin

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=5bcc0ed9-b48d-483c-8bfa-ec31f111320e@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=broonie@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rbm@suse.com \
    --cc=sashal@kernel.org \
    --cc=shuah@kernel.org \
    /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®