DPDK CI discussions
 help / color / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>, ci@dpdk.org, sys_stv@intel.com
Subject: Re: [dpdk-ci] Failures reported by Intel CI for series 10551
Date: Wed, 24 Jun 2020 10:19:24 -0400
Message-ID: <CAOE1vsNmmnRaYF-zeogNX6QiQ=RujxQrFg9wKfjnVpoyoKm2=Q@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8wzbt1GjeepRe4jHADOG-WBVRspwVwA5A-qZyXvLNxQ5A@mail.gmail.com>

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

Hi David,

Did you get any response to this from the Intel folks?  Should we add a bug
to track this for discussion / review at our meeting next week?

Cheers,
Lincoln

On Tue, Jun 23, 2020 at 3:07 AM David Marchand <david.marchand@redhat.com>
wrote:

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

-- 
*Lincoln Lavoie*
Senior Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu/>

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

<div dir="ltr"><div class="gmail_default" style="font-size:small">Hi David,</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Did you get any response to this from the Intel folks?  Should we add a bug to track this for discussion / review at our meeting next week?</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Cheers,<br>Lincoln</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 23, 2020 at 3:07 AM David Marchand &lt;<a href="mailto:david.marchand@redhat.com">david.marchand@redhat.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello,<br>
<br>
(It looks like I have no luck with CI those days... :-)).<br>
<br>
All patches of a series of mine<br>
(<a href="https://patchwork.dpdk.org/project/dpdk/list/?series=10551" rel="noreferrer" target="_blank">https://patchwork.dpdk.org/project/dpdk/list/?series=10551</a>) are<br>
marked as failing all compilation in Intel CI.<br>
<br>
- Is it normal to see all patches with the exact same test report?<br>
Patch 1: <a href="http://mails.dpdk.org/archives/test-report/2020-June/137872.html" rel="noreferrer" target="_blank">http://mails.dpdk.org/archives/test-report/2020-June/137872.html</a><br>
Patch 9: <a href="http://mails.dpdk.org/archives/test-report/2020-June/137880.html" rel="noreferrer" target="_blank">http://mails.dpdk.org/archives/test-report/2020-June/137880.html</a><br>
<br>
UNH and ovsrobot only report once when testing a full series.<br>
It makes more sense if Intel CI only tests full series.<br>
<br>
<br>
- Putting the first point aside, and focusing on patch 9 error:<br>
<a href="http://mails.dpdk.org/archives/test-report/2020-June/137880.html" rel="noreferrer" target="_blank">http://mails.dpdk.org/archives/test-report/2020-June/137880.html</a><br>
<br>
../drivers/mempool/bucket/rte_mempool_bucket.c: In function ‘bucket_get_count’:<br>
../drivers/mempool/bucket/rte_mempool_bucket.c:400:2: error: implicit<br>
declaration of function ‘rte_lcore_iterate’; did you mean<br>
‘rte_lcore_is_enabled’? [-Werror=implicit-function-declaration]<br>
  rte_lcore_iterate(count_per_lcore, &amp;ctx);<br>
  ^~~~~~~~~~~~~~~~~<br>
  rte_lcore_is_enabled<br>
../drivers/mempool/bucket/rte_mempool_bucket.c:400:2: error: nested<br>
extern declaration of ‘rte_lcore_iterate’ [-Werror=nested-externs]<br>
cc1: all warnings being treated as errors<br>
<br>
<br>
This function is defined in rte_lcore.h which does seem to be<br>
included, seeing how the compiler suggests another<br>
rte_lcore_is_enabled function.<br>
The v2 revision passed fine<br>
(<a href="http://mails.dpdk.org/archives/test-report/2020-June/137552.html" rel="noreferrer" target="_blank">http://mails.dpdk.org/archives/test-report/2020-June/137552.html</a>) and<br>
I see no change in v3 that would break like this.<br>
<br>
I am a bit puzzled...<br>
One thing that comes to mind, do we have dpdk headers installed<br>
system-wide on the Intel CI server(s)?<br>
<br>
<br>
-- <br>
David Marchand<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b>Lincoln Lavoie</b><br></div><div>Senior Engineer, Broadband Technologies</div><div>21 Madbury Rd., Ste. 100, Durham, NH 03824</div><div><a href="mailto:lylavoie@iol.unh.edu" target="_blank">lylavoie@iol.unh.edu</a></div><div><a href="https://www.iol.unh.edu" target="_blank">https://www.iol.unh.edu</a></div><div>+1-603-674-2755 (m)<br></div><div><a href="https://www.iol.unh.edu/" target="_blank"><img src="http://homeautomation.lavoieholdings.com/_/rsrc/1390068882701/unh-iol-logo.png"></a></div></div></div></div></div></div></div></div></div></div></div></div>

  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 [this message]
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
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='CAOE1vsNmmnRaYF-zeogNX6QiQ=RujxQrFg9wKfjnVpoyoKm2=Q@mail.gmail.com' \
    --to=lylavoie@iol.unh.edu \
    --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

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