docs: kselftest: Document the FORCE_TARGETS build variable

FORCE_TARGETS has been part of the kselftest build system for
some time but is absent from the developer documentation. Without
an entry here, users relying on kselftest in CI pipelines would
have to read the selftests Makefile directly to discover the
option.

A build that exits zero despite some targets failing can mask
real breakage and mislead automated systems into reporting
success. Add a dedicated section so that CI authors can easily
find and adopt FORCE_TARGETS=1 to turn such silent partial
failures into hard errors.

Link: https://lore.kernel.org/r/20260417-selftests-docs-v1-1-32e4a78214eb@suse.com
Signed-off-by: Ricardo B. Marlière <rbm@suse.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
This commit is contained in:
Ricardo B. Marlière 2026-04-17 14:36:28 -03:00 committed by Shuah Khan
parent 254f49634e
commit bb86954a67

View File

@ -126,6 +126,18 @@ dedicated skiplist::
See the top-level tools/testing/selftests/Makefile for the list of all
possible targets.
Requiring all targets to build successfully
===========================================
By default, the build succeeds as long as at least one target builds
without error. Set ``FORCE_TARGETS=1`` to instead require every target to
build successfully; make will abort as soon as any target fails::
$ make -C tools/testing/selftests FORCE_TARGETS=1
This applies to both the ``all`` and ``install`` targets and is useful in
CI environments where a silent partial build would be misleading.
Running the full range hotplug selftests
========================================