DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: ci@dpdk.org, sys_stv <sys_stv@intel.com>,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-ci] Failures reported by Intel CI for series 10551
Date: Fri, 26 Jun 2020 12:23:59 +0200	[thread overview]
Message-ID: <6471530.9lzsYzkM2H@thomas> (raw)
In-Reply-To: <CAJFAV8wWfbPQxsw0pR4TAqGio0poROo22KkvPEawVFLByXRKMg@mail.gmail.com>

26/06/2020 09:43, David Marchand:
> On Fri, Jun 26, 2020 at 5:03 AM Chen, Zhaoyan <zhaoyan.chen@intel.com> wrote:
> >
> > Hi, David,
> >
> > For your question, "Is it normal to see all patches with the exact same test report?"
> > Yes, we always test a series, rather than a single patch. You can see the exact same report
> > on any patch in a series. (it's convenient, you don't need backward to search
> > the header of the series, then check result)
> 
> Convenience is subject to interpretation :-).
> Other CI systems send a single report which is more sane for me.

I think these tests have 2 purposes:
	- sending quick error feedback to the author
	- check that all is green before merging
In both cases we don't need to have the same report duplicated,
because we check for failures in all patches anyway.

I suggest sending the series report only on the last patch of the series.



  reply	other threads:[~2020-06-26 10:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  7:07 David Marchand
2020-06-24 14:19 ` Lincoln Lavoie
2020-06-25 14:20   ` David Marchand
2020-06-26  3:03 ` Chen, Zhaoyan
2020-06-26  7:43   ` David Marchand
2020-06-26 10:23     ` Thomas Monjalon [this message]
2020-06-30  5:59       ` Chen, Zhaoyan
2020-06-30  7:13         ` Thomas Monjalon

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=6471530.9lzsYzkM2H@thomas \
    --to=thomas@monjalon.net \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --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).