From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 21DD9A0548 for ; Mon, 8 Feb 2021 17:23:30 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 164B11606F3; Mon, 8 Feb 2021 17:23:30 +0100 (CET) Received: from mail-ej1-f50.google.com (mail-ej1-f50.google.com [209.85.218.50]) by mails.dpdk.org (Postfix) with ESMTP id 7E9D51606E3 for ; Mon, 8 Feb 2021 17:23:27 +0100 (CET) Received: by mail-ej1-f50.google.com with SMTP id f14so25758379ejc.8 for ; Mon, 08 Feb 2021 08:23:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PwtoFDHftasjirSK0xRjhbdbYrVILmKwtk1Wv9UWktc=; b=F7sHhN64C7i1pnCITeGCuNgG9mk4PByEuWyos6goMToj3rMypHOansU7puZQaa+7+8 +D+NBw2hleN1cnAR5bIAfK66HuVauqi6CcTyRx1zNGTt8saDSXrAN62U6LQHzRJLjTce wVtuqtnUegXEDdlXABGCGob15eOUXdIJTDcqM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PwtoFDHftasjirSK0xRjhbdbYrVILmKwtk1Wv9UWktc=; b=Vpmn0rSITUGlnxGaRkHcQjiBMN0ehBMtzyGV4btjBTT5G6GjjBWGMJD3ql2tySoKGz QMSprqAIazz72QBZdEVAZGuHokoz/ebbp+5kXZJftFJkjg1FndjvTkn+AhWkqvycl02n Dlz2eH8UiKKq8Sffu+21JE+9h36fCPdVrVXBQonidp5h2QtKNUgKvw3jDLF9y3dMR5zD Ocvpl4KpHzc5nz8bohrvySCmNiPDeCXE+LtFoc2Jfai+XVh42ubjGVx6iwouEup6Aj4N wgKsLIFrYOH0nhbAouGPCbviFklAdzDFNXaNRry4D2O99WpX8/HJ8h5o03qDsxeFYG3e kh+g== X-Gm-Message-State: AOAM530n3FmnONJ+1FF+0EoymHNmhMPj3oMAtfcMFwdlD1qB7v1eeTm2 xLMev+P1AFOYYeKbyOaoG4y/C0woP9Ubzw1SMgQlTA== X-Google-Smtp-Source: ABdhPJyzcvq4Kt/5G2nZKDlYW7GJp6YV0bzQ1BGAXm4ohX2hYAaHvixETAgVRQ/EUTNj8hFb/KfJ+NodFIur4Noyh3A= X-Received: by 2002:a17:906:cb83:: with SMTP id mf3mr8896796ejb.155.1612801406938; Mon, 08 Feb 2021 08:23:26 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Lincoln Lavoie Date: Mon, 8 Feb 2021 11:21:08 -0500 Message-ID: To: "Zawadzki, Tomasz" Cc: Aaron Conole , Brandon Lo , "dpdklab@iol.unh.edu" , "ci@dpdk.org" , "dev@dpdk.org" , "spdk@lists.01.org" Content-Type: multipart/alternative; boundary="000000000000f444f605bad5960d" Subject: Re: [dpdk-ci] [dpdk-dev] [CI] SPDK compilation failures @ DPDK community lab X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" --000000000000f444f605bad5960d Content-Type: text/plain; charset="UTF-8" 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 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 On Behalf Of Aaron Conole > > Sent: Monday, February 8, 2021 4:21 PM > > To: Brandon Lo > > 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 > > -- *Lincoln Lavoie* Principal Engineer, Broadband Technologies 21 Madbury Rd., Ste. 100, Durham, NH 03824 lylavoie@iol.unh.edu https://www.iol.unh.edu +1-603-674-2755 (m) --000000000000f444f605bad5960d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Tha= nks 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 Z= awadzki, Tomasz <tomasz.zaw= adzki@intel.com> wrote:
Hi Aaron,

Thank you for reporting this !

This is an issue with rte_power now depending on rte_ethdev, which was reso= lved 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@i= ol.unh.edu; ci@dpdk.or= g; dev@dpdk.org; = spdk@lists.01.org
> Subject: [dpdk-dev] [CI] SPDK compilation failures @ DPDK community la= b
>
> Greetings,
>
> I've noticed that recently SPDK compilation in the UNH community l= ab seems
> to be failing, and I don't see an obvious reason for the failure.<= br> > The logs haven't been too helpful - it appears that there is a sym= bol that isn't
> available when linking.
>
> Job details (for example):
> https://lab.dpdk.org/results/dashboard/r= esults/results-
> uploads/test_runs/2363efb43157465db3228c34c00ebd57/log_upload_file/20<= br> > 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?=C2=A0 Maybe show the arguments to the compiler for the specific = object?
> Maybe the SPDK folks can see something obviously wrong?
>
> Thanks,
> -Aaron



--
Lincoln Lavoie
Prin= cipal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, = Durham, NH 03824
+1-603-674-= 2755 (m)

--000000000000f444f605bad5960d--