All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tomeu Vizoso" <tomeu.vizoso@collabora.com>
To: kernelci@groups.io, Guillaume Tucker <guillaume.tucker@gmail.com>
Subject: Re: [kernelci] Testing with distros
Date: Mon, 2 Jul 2018 10:07:20 +0200	[thread overview]
Message-ID: <502ea174-4e44-8e2f-33a2-3c6db85949a1@collabora.com> (raw)
In-Reply-To: <7hd0wbkeyj.fsf@baylibre.com>

On 06/28/2018 01:05 AM, Kevin Hilman wrote:
> "Guillaume Tucker" <guillaume.tucker@gmail.com> writes:
> 
>> 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?
> 
> It definitely sounds like a path worth exploring, but personally, I'd
> rather get our kernel-focused testing (and reporting!) figured out using
> our debian baseline before tackling distros.

I would prefer if distros ran mainline kernels in their own CI, then 
reported the bugs upstream after triage. And ideally, added tests against 
the kernel ABI to kernelci.

Regards,

Tomeu

> In particular, I think a kselftest and/or LTP testplan should probably
> be next on the list.
> 
> Kevin
> 
> 
> 

      parent reply	other threads:[~2018-07-02  8:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 12:34 Testing with distros Guillaume Tucker
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 [this message]

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=502ea174-4e44-8e2f-33a2-3c6db85949a1@collabora.com \
    --to=tomeu.vizoso@collabora.com \
    --cc=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.