[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z9_MaS4zWExJi9tJ@bombadil.infradead.org>
Date: Sun, 23 Mar 2025 01:55:05 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Masahiro Yamada <masahiroy@...nel.org>, kdevops@...ts.linux.dev
Cc: Jude Gyimah <Jude.Gyimah@...r-uni-bochum.de>,
Ole Schuerks <ole0811sch@...il.com>, linux-kbuild@...r.kernel.org,
jude.gyimah@....de, thorsten.berger@....de, deltaone@...ian.org,
jan.sollmann@....de, linux-kernel@...r.kernel.org,
nathan@...nel.org, nicolas@...sle.eu,
Brendan Jackman <jackmanb@...gle.com>,
Joel Granados <joel.granados@...nel.org>,
"Darrick J. Wong" <djwong@...nel.org>,
Carlos Maiolino <cem@...nel.org>,
Chuck Lever <chuck.lever@...cle.com>
Subject: Re: [PATCH v7 00/11] kconfig: Add support for conflict resolution
On Sun, Mar 23, 2025 at 01:40:37AM -0700, Luis Chamberlain wrote:
> Let me know if your team is interested in exploring these things.
Hrm, actually there's much more...
Given we support all cloud providers...
This can also be something like:
matrix:
providers: [aws, gcp]
storage: [ebs, nvme]
filesystems: [xfs, ext4]
testsuites: [fstests]
If we could gather data about price...
- cost_limit: $0.50/hr
We then just need a mapping of code to tests.
code_paths:
fs/xfs/: [fstests, ltp, gitr]
block/: [blktets]
Ie, code maps to Kconfig attributes, and so we know what tests to run
as code gets updated on each commit.
Luis
Powered by blists - more mailing lists