stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: kernelci@groups.io, kernel-build-reports@lists.linaro.org,
	automated-testing@lists.yoctoproject.org,
	linux-next@vger.kernel.org, stable@vger.kernel.org,
	Ard Biesheuvel <ardb@kernel.org>,
	agross@kernel.org, qcomlt-patches@lists.linaro.org,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	Tony Lindgren <tony@atomide.com>,
	ulf.hansson@linaro.org,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	linux-pm@vger.kernel.org, vireshk@kernel.org,
	Krzysztof Kozlowski <krzk@kernel.org>,
	kernel@collabora.com, kernelci@baylibre.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: kernelci.org transitioning to functional testing
Date: Wed, 13 May 2020 14:51:50 +0200	[thread overview]
Message-ID: <20200513125150.GA1084253@kroah.com> (raw)
In-Reply-To: <66aae710-1ee9-fb67-1a1b-997eeb70dc04@collabora.com>

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

      reply	other threads:[~2020-05-13 12:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 11:13 kernelci.org transitioning to functional testing Guillaume Tucker
2020-05-13 12:51 ` Greg KH [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=20200513125150.GA1084253@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=agross@kernel.org \
    --cc=ardb@kernel.org \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=kernel@collabora.com \
    --cc=kernelci@baylibre.com \
    --cc=kernelci@groups.io \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=qcomlt-patches@lists.linaro.org \
    --cc=stable@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=ulf.hansson@linaro.org \
    --cc=vireshk@kernel.org \
    /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 NNTP newsgroup(s).