Thread (13 messages) flat view 13 messages, 5 authors, 2021-02-18

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

From: Brandon Lo <hidden>
Date: 2021-02-09 16:07:49

Hi everyone,

I will adjust the branches and watch over the first few pipelines to
make sure everything goes smoothly.

Thanks for the update,
Brandon

On Tue, Feb 9, 2021 at 10:13 AM Aaron Conole [off-list ref] wrote:
"Zawadzki, Tomasz" [off-list ref] writes:
quoted
Hi Lincoln,



That patch in question is now merged to branch v21.01.x.
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?
quoted
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.



Thanks,

Tomek



From: Lincoln Lavoie <redacted>
Sent: Monday, February 8, 2021 5:21 PM
To: Zawadzki, Tomasz <redacted>
Cc: Aaron Conole <aconole@redhat.com>; Brandon Lo <redacted>; dpdklab@iol.unh.edu; ci@dpdk.org;
dev@dpdk.org; spdk@lists.01.org
Subject: Re: [dpdk-ci] [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab



Thanks Tomek,



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
is. :-P



Cheers,
Lincoln



On Mon, Feb 8, 2021 at 11:03 AM Zawadzki, Tomasz [off-list ref] wrote:

 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 [off-list ref] On Behalf Of Aaron Conole
 > Sent: Monday, February 8, 2021 4:21 PM
 > To: Brandon Lo [off-list ref]
 > 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

-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help