From: David Marchand <david.marchand@redhat.com>
To: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Cc: ci@dpdk.org, sys_stv@intel.com
Subject: [dpdk-ci] Failures reported by Intel CI for series 10551
Date: Tue, 23 Jun 2020 09:07:31 +0200 [thread overview]
Message-ID: <CAJFAV8wzbt1GjeepRe4jHADOG-WBVRspwVwA5A-qZyXvLNxQ5A@mail.gmail.com> (raw)
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
next reply other threads:[~2020-06-23 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 7:07 David Marchand [this message]
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
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=CAJFAV8wzbt1GjeepRe4jHADOG-WBVRspwVwA5A-qZyXvLNxQ5A@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
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).