From: "Guillaume Tucker" <guillaume.tucker@gmail.com>
To: kernelci@groups.io
Subject: Testing with distros
Date: Fri, 22 Jun 2018 13:34:00 +0100 [thread overview]
Message-ID: <82611570-bbc6-cfaf-e4bc-9b99a899ccb8@collabora.com> (raw)
Hi,
One subject that comes up regularly is about testing distributions
against upstream kernels in KernelCI. We've been historically using a
bare buildroot user-space to do boot testing and run very low-level test
cases. We're now starting to produce Debian root file systems for more
advanced test plans and extend the coverage of kernel-user interfaces
(DRM, V4L2...).
It seems like there would also be some value in having tests that
capture distro user-space breakages due to kernel changes. This may
mean building upstream kernels with a distro config, booting with a
fixed stable user-space from that distro and detecting new failures.
The next part to be defined would be what tests to run with these
distros, as even booting means choosing which services to start etc...
The point being to increase kernel test coverage without ending up
testing the user-space itself as this would seem outside of the scope of
KernelCI.
Does this sound like a path worth exploring?
Best wishes,
Guillaume
next reply other threads:[~2018-06-22 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 12:34 Guillaume Tucker [this message]
2018-06-22 18:35 ` getting started? micah.parrish
2018-06-28 13:11 ` [kernelci] " Matt Hart
2018-06-28 17:53 ` Micah Parrish
2018-07-26 22:22 ` Kevin Hilman
2018-06-27 23:05 ` [kernelci] Testing with distros Kevin Hilman
2018-06-28 13:13 ` Matt Hart
2018-07-02 8:07 ` Tomeu Vizoso
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=82611570-bbc6-cfaf-e4bc-9b99a899ccb8@collabora.com \
--to=guillaume.tucker@gmail.com \
--cc=kernelci@groups.io \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.