DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick MacArthur <pmacarth@iol.unh.edu>
To: ci@dpdk.org
Cc: dpdklab@iol.unh.edu
Subject: [dpdk-ci] agenda item for 2018-06-05 meeting: dashboard
Date: Mon, 4 Jun 2018 17:56:28 -0400	[thread overview]
Message-ID: <CABj6NQz7SLKkP+P4siz=p1gwnRyh7-kOs5KLYs=_VzOvY1uQHw@mail.gmail.com> (raw)

Hi, all,

I have done some work on the dashboard and would like to discuss it
and demonstrate it if there is time.

What I have currently implemented is a table showing all of the
patchsets currently active in Patchwork, and when you click on a
patchset, it shows the list of patches, and, for a logged in vendor,
the results for that vendor's hardware.

In particular, I would like to discuss the differences between what an
anonymous user can see versus what a logged-in vendor user can see,
particularly when a patch causes a regression on a single vendor's
hardware. In my present implementation, if a patch causes a regression
on least one vendor's hardware, the patch will show on the dashboard
as "Possible Regression" for all users. However, the actual results
for a given piece of hardware are only visible for that specific
vendor. This could create an "odd" situation where a logged-in vendor
will see a result labeled "Possible Regression" but will see only
passing results.

Input from vendors on what they would like to see would be helpful.

Thanks,
Patrick

-- 
Patrick MacArthur
Research and Development, High Performance Networking and Storage
UNH InterOperability Laboratory

                 reply	other threads:[~2018-06-04 21:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CABj6NQz7SLKkP+P4siz=p1gwnRyh7-kOs5KLYs=_VzOvY1uQHw@mail.gmail.com' \
    --to=pmacarth@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    /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).