public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Shuah Khan <skhan@linuxfoundation.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>,
	Shuah Khan <shuah@kernel.org>
Cc: linux-kselftest@vger.kernel.org,
	"kernelci@groups.io" <kernelci@groups.io>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Collabora Kernel ML <kernel@collabora.com>,
	Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: kselftest tree on kernelci.org
Date: Wed, 2 Feb 2022 08:23:27 -0700	[thread overview]
Message-ID: <ece6ea91-c44b-0bea-c4a2-ec099fa94881@linuxfoundation.org> (raw)
In-Reply-To: <5fd1a35c-f84e-1c6a-4a3a-be76dda97ca3@collabora.com>

Hi Guillaume,

On 2/2/22 6:32 AM, Guillaume Tucker wrote:
> Hi Shuah,
> 
> I've made this PR to start monitoring the "fixes" branch from the
> kselftest tree on kernelci.org:
> 
>    https://github.com/kernelci/kernelci-core/pull/998
> 

Thank you.

> While kselftest changes eventually land in linux-next, monitoring
> your tree directly means we can test it earlier and potentially
> enable more build variants or experimental tests.  Since
> kernelci.org also builds and runs some kselftests we're regularly
> finding issues and people are sending fixes for them.  See this
> recent story for example:
> 
>    https://twitter.com/kernelci/status/1488831497259921409
> 
> Keeping an eye on kselftest patches with kernelci.org means we
> can verify that fixes do what they're supposed to do with a much
> larger test coverage than what individual developers can do.
> We've been applying kselftest fixes on a branch managed by
> kernelci.org to verify them in the past, but having the actual
> kselftest tree part of the workflow would seem much better.
> 

Absolutely.

> There are several branches in your tree, while "fixes" seemed
> like the most useful one to pick I see there is also a "kernelci"
> branch too but it hasn't been updated for a while, reviving it
> could give you the possibility to test patches through
> kernelci.org before applying them on other branches that get
> pulled into linux-next and mainline.
> 

This branch was a topic branch specific for changes I made for
kernelci runs to be cleaner - I should delete this.

If you are looking for other branches to monitor in addition to
"fixes" branch, the following are the ones to add:

next (for the merge window), kunit (kunit changes slated for merge window),
kunit-fixes

> Many things could potentially be done with arbitrary builds and
> tests etc.  These are some initial suggestions.  How does this
> sound?

Sounds great to me. Since selftest patches flow through various
subsystem trees, having kernelci keep an eye is great. This would
be another pair of eyes in addition to occasional tests I run and
Linaro (LKTP) monitoring next.

How often do you send reports - I will watch out for them. Thanks
again for taking the initiative to add kselftest to kernelci.

thanks,
-- Shuah

  reply	other threads:[~2022-02-02 15:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 13:32 kselftest tree on kernelci.org Guillaume Tucker
2022-02-02 15:23 ` Shuah Khan [this message]
2022-02-03 18:19   ` Guillaume Tucker
2022-02-03 22:48     ` Shuah Khan

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=ece6ea91-c44b-0bea-c4a2-ec099fa94881@linuxfoundation.org \
    --to=skhan@linuxfoundation.org \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernel@collabora.com \
    --cc=kernelci@groups.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@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