[dpdk-ci] Failures reported by Intel CI for series 10551

[David Marchand]

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