All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: Nick Desaulniers <ndesaulniers@google.com>, kernelci@groups.io
Subject: Re: RFC: dashboards, visualization and analytics for test results
Date: Tue, 20 Oct 2020 14:39:13 -0700	[thread overview]
Message-ID: <7h8sc0k266.fsf@baylibre.com> (raw)
In-Reply-To: <CAKwvOdks7ih0yaVKPtnUzCRNs=VE6uRNtjRt9beH=tWbVpu8gw@mail.gmail.com>

Nick Desaulniers <ndesaulniers@google.com> writes:

> On Wed, Oct 7, 2020 at 10:47 AM Kevin Hilman <khilman@baylibre.com> 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
>
> additional user story:
>
> A developer wants to slice and dice warnings by toolchain and
> toolchain version to see what errors or warnings are compiler
> specific/need to be fixed.

Excellent, thanks!

Kevin

  reply	other threads:[~2020-10-20 21:39 UTC|newest]

Thread overview: 10+ 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-13 14:16 ` [cip-dev] FW: [Automated-testing] " Chris Paterson
2020-10-19 22:10 ` Nick Desaulniers
2020-10-20 21:39   ` Kevin Hilman [this message]
2020-10-21  6:39 ` Corentin Labbe
2020-10-21  6:39   ` LABBE Corentin
2020-12-07 11:26 ` Chris Fiege
2020-12-10 10:38 ` [Automated-testing] " Nikolai Kondrashov
2020-12-22 15:37 ` Chris Paterson
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=7h8sc0k266.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=kernelci@groups.io \
    --cc=ndesaulniers@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.