DPDK CI discussions
 help / color / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: "ci@dpdk.org" <ci@dpdk.org>, sys_stv <sys_stv@intel.com>
Subject: Re: [dpdk-ci] Failures reported by Intel CI for series 10551
Date: Fri, 26 Jun 2020 09:43:48 +0200
Message-ID: <CAJFAV8wWfbPQxsw0pR4TAqGio0poROo22KkvPEawVFLByXRKMg@mail.gmail.com> (raw)
In-Reply-To: <BYAPR11MB33172895885B80FA2B1B67068B930@BYAPR11MB3317.namprd11.prod.outlook.com>

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.


>
> " One thing that comes to mind, do we have dpdk headers installed system-
> > wide on the Intel CI server(s)?"
>
> Sure, we do. We don't see any problem on other patch compilation, so far. but it's strange
> that your V2 and V3 is same, but v3 test is failed. (code base is same). So I will try to re-run
> your series(v3), and check what's changed on CI system between the 2 days. Is that helpful?

Just to be sure.
By this, you mean that you have some dpdk headers installed on the CI
system in /usr?

Having those headers most likely exacerbates races with dpdk headers
copy in the building directory.
This could be where my series failed.


-- 
David Marchand


  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 [this message]
2020-06-26 10:23     ` Thomas Monjalon
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=CAJFAV8wWfbPQxsw0pR4TAqGio0poROo22KkvPEawVFLByXRKMg@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=ci@dpdk.org \
    --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

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 \
		ci@dpdk.org
	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