[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZxaZIJh61cM3fI76@bombadil.infradead.org>
Date: Mon, 21 Oct 2024 11:10:40 -0700
From: Luis Chamberlain <mcgrof@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Bart Van Assche <bvanassche@....org>, torvalds@...ux-foundation.org,
ksummit@...ts.linux.dev, linux-kernel@...r.kernel.org,
Shin'ichiro Kawasaki <shinichiro.kawasaki@....com>
Subject: Re: linus-next: improving functional testing for to-be-merged pull
requests
On Mon, Oct 21, 2024 at 01:30:06PM -0400, Sasha Levin wrote:
> On Mon, Oct 21, 2024 at 10:24:53AM -0700, Bart Van Assche wrote:
> > On 10/21/24 9:07 AM, Sasha Levin wrote:
> > > Current testing:
> > > - LKFT: https://qa-reports.linaro.org/lkft/sashal-linus-next/
> > > - KernelCI: https://t.ly/KEW7F
> >
> > Hi Sasha,
> >
> > Is blktests included in any of the above? If not, please consider
> > including it. During the past few years we have noticed that the
> > test failures reported by this test suite are most of the time caused
> > by kernel bugs. Sometimes issues in the tests are discovered but this
> > is rare. See also https://github.com/osandov/blktests/.
>
> Hey Bart,
>
> I don't plan on doing any tests on my own, but rather have our existing
> CI infra (kernelci, LKFT, etc) deal with the actual testing part of
> things.
>
> AFAIK KernelCI if working on adding blktests support!
We can automate blktests with kdevops today, if that's desirable let
me know.
Luis
Powered by blists - more mailing lists