From: LABBE Corentin <clabbe@baylibre.com>
To: kernelci@groups.io, khilman@baylibre.com
Cc: automated-testing@lists.yoctoproject.org, tools@linux.kernel.org
Subject: Re: RFC: dashboards, visualization and analytics for test results
Date: Wed, 21 Oct 2020 08:39:14 +0200 [thread overview]
Message-ID: <20201021063914.GC21391@Red> (raw)
In-Reply-To: <7hk0w2c4i3.fsf@baylibre.com>
On Wed, Oct 07, 2020 at 10:47:32AM -0700, Kevin Hilman wrote:
> Hello folks interested in kernel testing/automation,
>
> The KernelCI project is starting to look at what's next for dashboards,
> visualization and analytics for the various Linux focused testing
> projects.
>
> At Linux Plumbers, we launched some discussions[1] around common ways to
> collect test results, logs and metadata into a public, shared dataset,
> and we've already started collecting data from several different
> sources.
>
> So the next question is... how do we best use all of this data?
>
> We're beginning to brainstorm how to visualize, analyze and learn from
> this data in useful ways.
>
> To that end, we're starting to collect a set of user stories to help us
> brainstorm a new design for web based dashboard and analytics, and we'd
> like to hear from you.
>
> Below is the start of a list of user stories[2], but we want to grow
> this list with your ideas, so please share them on this thread.
>
> We're also very interested in talking with any big data people and data
> scientists who might be willing to look at this growing set of data and
> help us better plan for the future full of lots of test data.
>
> We appreciate your ideas and feedback,
>
> Kevin (on behalf of the KernelCI team)
>
>
> [1] c.f. Unifying Test Reporting with KernelCI from the testing/fuzzing
> micro-conference:
> https://linuxplumbersconf.org/event/7/sessions/80/#20200826
>
>
>
> [2] Example user stories
>
> A kernel developer has sent a patch which caused a regression
> - Find the details, how to reproduce, check when it’s fixed
>
> A maintainer is getting a branch ready for the next merge window
> - Compare results against mainline, ensure all tests were run correctly
>
> An OEM or SoC vendor needs to upgrade their kernel or move to upstream
> - See all results for a particular platform on various stable releases
>
> Regular visitors who want to know how the kernel is doing
> - Highlight new regressions, show trends for pass/fail and performance
> - Does kernel X work on my hardware?
>
> Distro vendor wants to know
> - Is the latest kernel stable enough for my distro?
> - Why does this test fail on my distro kernel but not stable kernel?
>
> Stable kernel maintainer wants to know
> - Is this kernel stable enough to release?
>
> Kernel / subsystem maintainer wants to know
> - Is my code/subsystem being tested? How much coverage?
> - Is the kernel size growing? Why? Which subsystems
> - Is boot time / test execution time increasing/decreasing? What are the historical trends?
>
Hello
As a maintainer, viewing all boot including a specific hardware/driver.
Does my xxxx driver works everywhere ?
Recent example:
- I have added support for PRNG/hash on sun8i-ce, I want to check all boots with this driver.
More complex recent example:
- since commit bbc4d71d6354 ("net: phy: realtek: fix rtl8211e rx/tx delay config") many board could loose network, I want to see all boots including this patch with this PHY.
Regards
next prev parent reply other threads:[~2020-10-21 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 17:47 RFC: dashboards, visualization and analytics for test results Kevin Hilman
2020-10-21 6:39 ` LABBE Corentin [this message]
2020-12-10 10:38 ` [Automated-testing] " Nikolai Kondrashov
2020-12-22 15:37 ` Chris Paterson
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=20201021063914.GC21391@Red \
--to=clabbe@baylibre.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=kernelci@groups.io \
--cc=khilman@baylibre.com \
--cc=tools@linux.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).