public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: "Kevin Hilman" <khilman@baylibre.com>
To: kernelci@groups.io, guillaume.tucker@gmail.com, kernelci@groups.io
Subject: Re: Tests view in kernelci-frontend
Date: Thu, 24 Jan 2019 02:53:27 -0800	[thread overview]
Message-ID: <7h7eeuz5qw.fsf@baylibre.com> (raw)
In-Reply-To: <ea54a553-c76a-7c8d-7247-a0fd0bdfff88@collabora.com>

"Guillaume Tucker" <guillaume.tucker@gmail.com> writes:

> The Tests view in kernelci-frontend is currently a bit behind:
>
>     https://kernelci.org/test/
>
> As discussed previously, while it was interesting to try a new
> design, it turns out to be somewhat confusing to have results
> sorted by platforms instead of kernel revisions like for builds
> and boots.  Also, since we've introduced recursive sub-groups in
> the backend, the views haven't been updated to properly show the
> results.  All the groups are shown in a flat list regardless of
> their hierarchy.
>
> While alternatives are being investigated using Elasticsearch and
> Kibana, we should probably do something about the current
> frontend as that's what's currently online.  It doesn't seem like
> anyone is actively working on fixing it right now, so I would
> suggest to remove the link from the navigation bar so visitors
> are not encouraged to see this page until it's in a better shape.
> Others agreed during this Monday's meeting.
>
> If you need the Tests link to remain visible, or if you know
> someone will have a fix for it in the coming days, then please
> let us know.  Otherwise I think we could hide the link next week.

Removing the link from the navigation bar is fine, but I assume this
means leaving the /test route and code in place so we can use it
manually if needed?

When working on email reporting, even though the views aren't terribly
useful, it's useful at least to see that (new) data has arrived.

Kevin

      reply	other threads:[~2019-01-24 10:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23  8:05 Tests view in kernelci-frontend Guillaume Tucker
2019-01-24 10:53 ` Kevin Hilman [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=7h7eeuz5qw.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=guillaume.tucker@gmail.com \
    --cc=kernelci@groups.io \
    /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