Re: [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab

["Zawadzki, Tomasz" <tomasz.zawadzki@intel.com>]

Hi Aaron,

Thank you for reporting this !

This is an issue with rte_power now depending on rte_ethdev, which was resolved on latest SPDK.

I believe that UNH lab verifies DPDK patches against SPDK branch for latest release. Which after the very recent SPDK release, would be v21.01.x:
https://github.com/spdk/spdk/tree/v21.01.x

The fix has been backported to that branch and should be merged shortly:
https://review.spdk.io/gerrit/c/spdk/spdk/+/6320

Thanks,
Tomek

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Aaron Conole
> Sent: Monday, February 8, 2021 4:21 PM
> To: Brandon Lo <blo@iol.unh.edu>
> Cc: dpdklab@iol.unh.edu; ci@dpdk.org; dev@dpdk.org; spdk@lists.01.org
> Subject: [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
> 
> Greetings,
> 
> I've noticed that recently SPDK compilation in the UNH community lab seems
> to be failing, and I don't see an obvious reason for the failure.
> The logs haven't been too helpful - it appears that there is a symbol that isn't
> available when linking.
> 
> Job details (for example):
> https://lab.dpdk.org/results/dashboard/results/results-
> uploads/test_runs/2363efb43157465db3228c34c00ebd57/log_upload_file/20
> 21/2/dpdk_f6f2d2240153_15524_2021-02-04_22-59-59_NA.zip
> 
> Is it possible to turn on more verbose logging during the compilation of
> SPDK?  Maybe show the arguments to the compiler for the specific object?
> Maybe the SPDK folks can see something obviously wrong?
> 
> Thanks,
> -Aaron