From: Joe Lawrence <joe.lawrence@redhat.com>
To: linux-kselftest@vger.kernel.org, linux-kbuild@vger.kernel.org
Cc: Joe Lawrence <joe.lawrence@redhat.com>
Subject: Build-time tests?
Date: Wed, 8 May 2019 15:30:22 -0400 [thread overview]
Message-ID: <20190508191341.GA17963@redhat.com> (raw)
Hello kbuild, kselftest,
I've been working on a patchset which adds an additional build script to
the toolchain when compiling livepatches. There are a few kernel
section features in which this script does not yet support, but can
detect and abort when it encounters. To test this detection, I've
written a small set of kernel modules that require such sections.
A few questions:
Is build-testing out of scope for kernel selftests? For expediency,
it was really easy to spin out new lib/livepatch kernel modules.
Does kbuild support the notion of expected failure? In this case, the
build script returns a non-zero error and the build stops.
Am I trying to fit a square peg in a round hole? I could easily keep
these build tests in a private branch, but could they exist in a
different format somewhere else in the tree?
Suggestions welcome,
-- Joe
next reply other threads:[~2019-05-08 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 19:30 Joe Lawrence [this message]
2019-05-12 12:23 ` Build-time tests? Masahiro Yamada
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=20190508191341.GA17963@redhat.com \
--to=joe.lawrence@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kselftest@vger.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