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

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)

" 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? 

Regards,
Zhaoyan Chen

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, June 23, 2020 3:08 PM
> To: Chen, Zhaoyan <zhaoyan.chen@intel.com>
> Cc: ci@dpdk.org; sys_stv <sys_stv@intel.com>
> Subject: Failures reported by Intel CI for series 10551
> 
> Hello,
> 
> (It looks like I have no luck with CI those days... :-)).
> 
> All patches of a series of mine
> (https://patchwork.dpdk.org/project/dpdk/list/?series=10551) are marked
> as failing all compilation in Intel CI.
> 
> - Is it normal to see all patches with the exact same test report?
> Patch 1: http://mails.dpdk.org/archives/test-report/2020-
> June/137872.html
> Patch 9: http://mails.dpdk.org/archives/test-report/2020-
> June/137880.html
> 
> UNH and ovsrobot only report once when testing a full series.
> It makes more sense if Intel CI only tests full series.
> 
> 
> - Putting the first point aside, and focusing on patch 9 error:
> http://mails.dpdk.org/archives/test-report/2020-June/137880.html
> 
> ../drivers/mempool/bucket/rte_mempool_bucket.c: In function
> ‘bucket_get_count’:
> ../drivers/mempool/bucket/rte_mempool_bucket.c:400:2: error: implicit
> declaration of function ‘rte_lcore_iterate’; did you mean
> ‘rte_lcore_is_enabled’? [-Werror=implicit-function-declaration]
>   rte_lcore_iterate(count_per_lcore, &ctx);
>   ^~~~~~~~~~~~~~~~~
>   rte_lcore_is_enabled
> ../drivers/mempool/bucket/rte_mempool_bucket.c:400:2: error: nested
> extern declaration of ‘rte_lcore_iterate’ [-Werror=nested-externs]
> cc1: all warnings being treated as errors
> 
> 
> This function is defined in rte_lcore.h which does seem to be included,
> seeing how the compiler suggests another rte_lcore_is_enabled function.
> The v2 revision passed fine
> (http://mails.dpdk.org/archives/test-report/2020-June/137552.html) and I
> see no change in v3 that would break like this.
> 
> I am a bit puzzled...
> One thing that comes to mind, do we have dpdk headers installed system-
> wide on the Intel CI server(s)?
> 
> 
> --
> David Marchand


  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 [this message]
2020-06-26  7:43   ` David Marchand
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=BYAPR11MB33172895885B80FA2B1B67068B930@BYAPR11MB3317.namprd11.prod.outlook.com \
    --to=zhaoyan.chen@intel.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=sys_stv@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