DPDK CI discussions
 help / color / mirror / Atom feed
From: Jeremy Plsek <jplsek@iol.unh.edu>
To: "Tu, Lijuan" <lijuan.tu@intel.com>
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] missing patch results in dashboard
Date: Tue, 20 Nov 2018 08:40:22 -0500	[thread overview]
Message-ID: <CA+xUZB4kFJtztAvQg3iCbUj8ZKKcNa6K8cH888hPHxOvezLkQA@mail.gmail.com> (raw)
In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0B9BE9FB@SHSMSX101.ccr.corp.intel.com>

Hi Lijuan,

The Dashboard overview only shows 'new', 'under-review', and
'awaiting-upstream', (which are also not RFC) patches from Patchwork.
Since that patch is 'accepted', it does not show up on the Dashboard
overview.

Here is the detailed result:
https://lab.dpdk.org/results/dashboard/patchsets/3617/

There's been a feature request in our backlog for some time now in
order to allow users to filter on patch status, but it has not been
made a priority.

Thanks.
On Tue, Nov 20, 2018 at 4:35 AM Tu, Lijuan <lijuan.tu@intel.com> wrote:
>
> Hi all,
>
>
>
> I found some patch series missing test results in dashboard, although they were tested.
>
> For instance, patch id: 48157, patch link: https://patches.dpdk.org/patch/48157/
>
>          Test results are found in patchwork, but not in dashboard: https://lab.dpdk.org/results/dashboard/
>
> In my mind, they should be shown both in patchwork and dashboard.
>
>
>
> Thanks
>
> Lijuan.
>
>



--
Jeremy Plsek
UNH InterOperability Laboratory

      reply	other threads:[~2018-11-20 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-20  9:35 Tu, Lijuan
2018-11-20 13:40 ` Jeremy Plsek [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=CA+xUZB4kFJtztAvQg3iCbUj8ZKKcNa6K8cH888hPHxOvezLkQA@mail.gmail.com \
    --to=jplsek@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=lijuan.tu@intel.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 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).