From: Guillaume Tucker <guillaume.tucker@collabora•com>
To: 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: kernelci.org transitioning to functional testing
Date: Wed, 13 May 2020 12:13:24 +0100 [thread overview]
Message-ID: <66aae710-1ee9-fb67-1a1b-997eeb70dc04@collabora.com> (raw)
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].
Please let us know if you have any questions, comments or
concerns either in this thread, on kernelci@groups•io or IRC
#kernelci on Freenode.
Stay tuned!
Thanks,
Guillaume
[1] bootrr: https://github.com/kernelci/bootrr
[2] schedule: https://github.com/kernelci/kernelci-backend/issues/238
next reply other threads:[~2020-05-13 11:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 11:13 Guillaume Tucker [this message]
2020-05-13 12:51 ` kernelci.org transitioning to functional testing Greg KH
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=66aae710-1ee9-fb67-1a1b-997eeb70dc04@collabora.com \
--to=guillaume.tucker@collabora$(echo .)com \
--cc=agross@kernel$(echo .)org \
--cc=ardb@kernel$(echo .)org \
--cc=automated-testing@lists$(echo .)yoctoproject.org \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=kernel@collabora$(echo .)com \
--cc=kernelci@baylibre$(echo .)com \
--cc=kernelci@groups$(echo .)io \
--cc=krzk@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-gpio@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=qcomlt-patches@lists$(echo .)linaro.org \
--cc=stable@vger$(echo .)kernel.org \
--cc=tony@atomide$(echo .)com \
--cc=ulf.hansson@linaro$(echo .)org \
--cc=vireshk@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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