Good to know - I do still see a failure in the IOL job (even from a few
hours ago). I suppose the lab side might need some adjustment, too?
The builds performed for latest SPDK and SPDK LTS, against dpdk-main branch seem to be
passing. Would love to hear if
this is what you are seeing on your end too.
From: Lincoln Lavoie <lylavoie(a)iol.unh.edu>
Sent: Monday, February 8, 2021 5:21 PM
To: Zawadzki, Tomasz <tomasz.zawadzki(a)intel.com>
Cc: Aaron Conole <aconole(a)redhat.com>; Brandon Lo <blo(a)iol.unh.edu>;
Subject: Re: [dpdk-ci] [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
Can you let us know when the merge happens and we'll make sure the next set of builds
pass or see what the next failure
On Mon, Feb 8, 2021 at 11:03 AM Zawadzki, Tomasz <tomasz.zawadzki(a)intel.com>
Thank you for reporting this !
This is an issue with rte_power now depending on rte_ethdev, which was resolved on
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:
The fix has been backported to that branch and should be merged shortly:
> -----Original Message-----
> From: dev <dev-bounces(a)dpdk.org> On Behalf Of Aaron Conole
> Sent: Monday, February 8, 2021 4:21 PM
> To: Brandon Lo <blo(a)iol.unh.edu>
> Cc: dpdklab(a)iol.unh.edu; ci(a)dpdk.org; dev(a)dpdk.org; spdk(a)lists.01.org
> Subject: [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab
> 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
> available when linking.
> Job details (for example):
> 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?