From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, milosz.wasilewski@linaro.org,
kernelci@groups.io, JanSimon.Moeller@gmx.de
Cc: Guillaume Tucker <guillaume.tucker@gmail.com>
Subject: Re: KernelCI modular pipeline design document
Date: Mon, 11 Feb 2019 10:27:00 -0800 [thread overview]
Message-ID: <7h1s4egozv.fsf@baylibre.com> (raw)
In-Reply-To: <CAJrz+7L=iiJuhdYFU6YTytEGTpd_13E+BKYEqf1JEGq=7bmSSw@mail.gmail.com>
"Milosz Wasilewski" <milosz.wasilewski@linaro.org> writes:
> On Fri, 8 Feb 2019 at 16:33, "Jan-Simon Möller" <JanSimon.Moeller@gmx.de> wrote:
>>
>> Please do not just think of 'building the kernel' - ppl also want to test and record/visualize userspace tests (aka custom-built kernel+filesystem).
>> Yes, the linux kernel is the main focus for kernelci.org . But let's keep the other possible use-cases in mind.
>>
>
> I don't think this is a good idea. Having other use cases in mind
> takes you down a very deep rabbit hole. Creating a general purpose
> result reporting tool is hard. Kernelci reports on kernel results and
> (as I understand) does it right. You can use these tools for other
> purposes but that's a different story.
Yes, we're focused on kernel-focused testing, but there are multiple
ways to test the kernel, most of which require a combination of kernel +
userspace/distro.
I think Jan-Simon's point is that as we evolve, while we might focus on
buildroot/debian, we chould not design things in a way that prohibit
using the kernelCI code (and infra) for other types of kernel-focused
testing (e.g. Yocto, other distros, etc.)
Stated differently, the current *service* provided by kernelCI.org is
kernel-focused testing. But, we could (and should, IMO) write the
*software* behind that service in a way that it could be used more
generically if desired.
Kevin
next prev parent reply other threads:[~2019-02-11 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 17:57 KernelCI modular pipeline design document Guillaume Tucker
2019-02-08 16:20 ` "Jan-Simon Möller"
2019-02-11 12:41 ` Milosz Wasilewski
2019-02-11 18:27 ` Kevin Hilman [this message]
2019-02-11 21:56 ` Milosz Wasilewski
2019-02-12 1:14 ` Kevin Hilman
2019-02-12 13:36 ` Guillaume Tucker
2019-02-13 0:44 ` Kevin Hilman
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=7h1s4egozv.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=JanSimon.Moeller@gmx.de \
--cc=guillaume.tucker@gmail.com \
--cc=kernelci@groups.io \
--cc=milosz.wasilewski@linaro.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