[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200513125150.GA1084253@kroah.com>
Date: Wed, 13 May 2020 14:51:50 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: Guillaume Tucker <guillaume.tucker@...labora.com>
Cc: kernelci@...ups.io, kernel-build-reports@...ts.linaro.org,
automated-testing@...ts.yoctoproject.org,
linux-next@...r.kernel.org, stable@...r.kernel.org,
Ard Biesheuvel <ardb@...nel.org>, agross@...nel.org,
qcomlt-patches@...ts.linaro.org,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>, ulf.hansson@...aro.org,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, linux-pm@...r.kernel.org,
vireshk@...nel.org, Krzysztof Kozlowski <krzk@...nel.org>,
kernel@...labora.com, kernelci@...libre.com,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: kernelci.org transitioning to functional testing
On Wed, May 13, 2020 at 12:13:24PM +0100, Guillaume Tucker wrote:
> As kernelci.org is expanding its functional testing
> capabilities, the concept of boot testing is now being
> deprecated.
>
> Next Monday 18th May, the web dashboard on https://kernelci.org
> will be updated to primarily show functional test results
> rather than boot results. The Boots tab will still be
> available until 5th June to ease the transition.
>
> The new equivalent to boot testing is the *baseline* test suite
> which also runs sanity checks using dmesg and bootrr[1].
>
> Boot email reports will eventually be replaced with baseline
> reports. For those of you already familiar with the test email
> reports, they will be simplified to only show regressions with
> links to the dashboard for all the details.
>
> Some functional tests are already being run by kernelci.org,
> results have only been shared by email so far but they will
> become visible on the web dashboard next week. In particular:
> v4l2-compliance, i-g-t for DRM/KMS and Panfrost,
> suspend/resume...
>
> And of course, a lot of functional test suites are in the
> process of being added: kselftest, KUnit, LTP, xfstests,
> extended i-g-t coverage and many more.
>
> The detailed schedule is available on a GitHub issue[2].
Very cool stuff, thanks so much to everyone involved for making this
happen, it's really helpful.
greg k-h
Powered by blists - more mailing lists