DPDK CI discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Aaron Conole <aconole@redhat.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	David Marchand <david.marchand@redhat.com>,
	sys_stv@intel.com,  "Chen, Zhaoyan" <zhaoyan.chen@intel.com>,
	Lincoln Lavoie <lylavoie@iol.unh.edu>,
	"ci@dpdk.org" <ci@dpdk.org>
Subject: Re: [dpdk-ci] Understanding results of patchwork
Date: Wed, 15 Apr 2020 10:24:36 -0700	[thread overview]
Message-ID: <CACZ4nhvD-zQUf9D=qX0d3YZnRmCsBgt_SJfXGjDCXoNSJ_MtRQ@mail.gmail.com> (raw)
In-Reply-To: <f7two6g4qt1.fsf@dhcp-25.97.bos.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2311 bytes --]

On Wed, Apr 15, 2020 at 10:11 AM Aaron Conole <aconole@redhat.com> wrote:

> Ferruh Yigit <ferruh.yigit@intel.com> writes:
>
> > On 4/15/2020 5:42 PM, David Marchand wrote:
> >> On Wed, Apr 15, 2020 at 6:34 PM Ferruh Yigit <ferruh.yigit@intel.com>
> wrote:
> >>>
> >>> On 4/15/2020 3:40 PM, Ajit Khaparde wrote:
> >>>> Ferruh,
> >>>> I am trying to apply this patchset.
> >>>> https://patchwork.dpdk.org/project/dpdk/list/?series=9386
> >>>>
> >>>> So I am trying to check if the patches passed all the checks.
> >>>> I can see only the checkpatch for individual patches and the
> >>>> travis result - presumably for the complete set.
> >>>>
> >>>> https://travis-ci.com/ovsrobot/dpdk/builds/160349438
> >>>>
> >>>> For previous versions, I had seen results for individual patches and
> performance
> >>>> results also. Is it enough to apply the patches based on just the
> travis and
> >>>> checkpatch results?
> >>>>
> >>>
> >>> Hi Ajit,
> >>>
> >>> We expect other checks, cc'ed David too.
> >>
> >> Better to Cc: ci@dpdk.org from my pov.
> >
> > Agree, cc'ed now.
> >
> >>
> >>
> >>>
> >>> Intel-compilation seems not sending the reports for a day, last one is
> from
> >>> yesterday, it may be stuck in some set, etc.. @Zhaoyan, can you please
> check it?
> >>>
> >>> The community lab one is still on pending state, it may be because it
> is a big
> >>> patchset.
> >>> https://lab.dpdk.org/results/dashboard/patchsets/10445/
> >>>
> >>>
> >>> And @David, @Aaron, does travis checks patchset only or does it checks
> each
> >>> patch in set?
> >>
> >> Travis checks the whole patchset at the last patch.
> >
> > Thanks, so we are missing patch by patch checks in our CI checks, since
> as far
> > as I know Intel check is also for patchset.
>
> For now, we only check the series as a whole in travis to save on
> time.  It's expected that someone / something else would do
> patch-at-a-time for the series, to preserve the ability to bisect
> through series.
>
Ok, thanks for the clarification.
We went through the exercise. Since this was a big patchset,
I was trying to be extra careful. So I wanted to make sure reports for all
automated checks are in. That's when I started digging into the reports
and the process.

Thanks


> >> The dpdk.org server sends checkpatch reports for each patch.
> >>
>
>

[-- Attachment #2: Type: text/html, Size: 4454 bytes --]

      reply	other threads:[~2020-04-15 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACZ4nhvvNPB71Gs3DnpLmUDBPmkyOCmBL8qf9-_ynKRXc9itcA@mail.gmail.com>
     [not found] ` <d463e85b-83aa-300c-b89e-7f9138d18ff3@intel.com>
     [not found]   ` <CAJFAV8xmLOdY3uoi1wD8jpdMRTYtAbgq8zXxhXqWETYBNA+7qw@mail.gmail.com>
2020-04-15 16:45     ` Ferruh Yigit
2020-04-15 17:11       ` Aaron Conole
2020-04-15 17:24         ` Ajit Khaparde [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='CACZ4nhvD-zQUf9D=qX0d3YZnRmCsBgt_SJfXGjDCXoNSJ_MtRQ@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=aconole@redhat.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=ferruh.yigit@intel.com \
    --cc=lylavoie@iol.unh.edu \
    --cc=sys_stv@intel.com \
    --cc=zhaoyan.chen@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).