From: "Theodore Ts'o" <tytso@mit.edu>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Steve French <smfrench@gmail.com>,
Amir Goldstein <amir73il@gmail.com>,
Luis Chamberlain <mcgrof@kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"kdevops@lists.linux.dev" <kdevops@lists.linux.dev>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
Jan Kara <jack@suse.cz>
Subject: Re: kdevops BoF at LSFMM
Date: Mon, 13 May 2024 07:17:53 -0600 [thread overview]
Message-ID: <20240513131753.GA520598@mit.edu> (raw)
In-Reply-To: <E2589F86-7582-488C-9DBB-8022D481AFB3@oracle.com>
On Wed, May 08, 2024 at 05:54:50PM +0000, Chuck Lever III wrote:
>
> In my experience, these require the addition of a CI
> apparatus like BuildBot or Jenkins -- they are not
> directly part of kdevops' mission. Scott Mayhew and
> I have been playing with BuildBot, and there are some
> areas where integration between kdevops and BuildBot
> could be improved (and could be discussed next week).
This is support which gce-xfstests has. You can either have it watch
a particular branch on a git repo, and whenever it changes it will
kick off a tests:
gce-xfstests ltm [-c <cfg>] [-g <group>]|[<tests>] ... [--repo <url>] \
--watch <branch>
As an example:
gce-xfstests ltm -c ext4/all -g auto --repo ext4 --watch dev
Or you can specify a specific commit that you want to run tests on:
gce-xfstests ltm -c ext4/all -g auto --repo ext4 --commit dev
In the two examples above ext4 is an abbrevation so you don't have to
type the full URL; you can define additional abbrevs in your config
file.
> > 3) make it easier to auto-bisect what commit regressed when a failing test
> > is spotted
>
> Jeff Layton has mentioned this as well. I don't think
> it would be impossible to get kdevops to orchestrate
> a bisect, as long as it has an automatic way to decide
> when to use "git bisect {good|bad}"
gce-xfstests has this as well:
gce-xfstests ltm [-c <cfg>] [-g <group>]|[<tests>] ... [--repo <url>] \
--bisect-bad <bad_rev> --bisect-good <good_rev> \
[--bisect-good <good_rev1> ...]
So yeah, not that hard --- we had intern learn how to program in Go
and to implement the base lightweight test manager, and a team of
undergraduates who implemented the build server, test spinner, and
auto-bisector as part of their software engineering classes's project. :-)
The code is up on github at github.com/tytso/xfstests-bld if anyone
wants to repurpose it.
- Ted
prev parent reply other threads:[~2024-05-13 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 18:44 kdevops BoF at LSFMM Luis Chamberlain
2024-05-07 18:56 ` Chuck Lever III
2024-05-08 7:45 ` Amir Goldstein
2024-05-08 15:57 ` Luis Chamberlain
2024-05-13 1:58 ` Matthew Wilcox
2024-05-08 17:45 ` Steve French
2024-05-08 17:54 ` Chuck Lever III
2024-05-12 20:20 ` Luis Chamberlain
2024-05-13 13:17 ` Theodore Ts'o [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=20240513131753.GA520598@mit.edu \
--to=tytso@mit.edu \
--cc=amir73il@gmail.com \
--cc=chuck.lever@oracle.com \
--cc=jack@suse.cz \
--cc=kdevops@lists.linux.dev \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=smfrench@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).