From: Philip Li <philip.li@intel.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: <kdevops@lists.linux.dev>, <oliver.sang@intel.com>
Subject: Re: Automation with 0-day & kdevops
Date: Tue, 19 Mar 2024 09:38:18 +0800 [thread overview]
Message-ID: <ZfjsijETQPJOzyBl@rli9-mobl> (raw)
In-Reply-To: <ZfSSjFZfh29IC6hd@bombadil.infradead.org>
On Fri, Mar 15, 2024 at 11:25:16AM -0700, Luis Chamberlain wrote:
> On Sun, Feb 25, 2024 at 07:28:00PM +0800, Philip Li wrote:
> > Thanks Luis, we are glad to collaborate on this. We will learn the detail of
> > kdevops that the website contains a lot of useful materials. And we will update
> > our progress to you next month for the questions and next steps.
>
> Hey Phillip,
>
> I reduced the list to just kdevops@lists.linux.dev
>
> just a heads up on a few things:
Thanks Luis, this month, the 0day side had started to experiment the very basic
kdevops test, such as blktests loop/block, to gather experience. We are still
in the internal discussion to understand the test model and whether the bot can
integrate with it.
The runtime testing in 0day has kind different design and is bisection driven
to identify the bad commit of regression. We are thinking of how to trigger
bisection based on the diff, how to avoid duplication to what 0day is testing, etc.
We will continue the experiment and have the discussion in the mail thread
soon.
>
> * guestfs is now default -- that should be tried as it is what we
> will build up, and it also has the guestfs/<name>/serial.txt
> * you should try enable the kdevops systemd-remote-journal
> * the kernel selftest baseline -- that needs more love but should be
> easy to complete
>
> We're also discord so we can also discuss there. Happy to also follow up
> on zoom with interested developers. Happy to suit any timezone.
>
> Luis
prev parent reply other threads:[~2024-03-19 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 15:44 Automation with 0-day & kdevops Luis Chamberlain
2024-02-25 11:28 ` Philip Li
2024-03-15 18:25 ` Luis Chamberlain
2024-03-19 1:38 ` Philip Li [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=ZfjsijETQPJOzyBl@rli9-mobl \
--to=philip.li@intel.com \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@kernel.org \
--cc=oliver.sang@intel.com \
/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