From: Thomas Monjalon <firstname.lastname@example.org> To: "Chen, Zhaoyan" <email@example.com> Cc: firstname.lastname@example.org, sys_stv <email@example.com>, David Marchand <firstname.lastname@example.org> Subject: Re: [dpdk-ci] Failures reported by Intel CI for series 10551 Date: Fri, 26 Jun 2020 12:23:59 +0200 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 <email@example.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.
next prev parent reply index 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 publically 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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /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
DPDK CI discussions Archives are clonable: git clone --mirror http://inbox.dpdk.org/ci/0 ci/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ci ci/ http://inbox.dpdk.org/ci \ email@example.com public-inbox-index ci Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.ci AGPL code for this site: git clone https://public-inbox.org/ public-inbox