From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 84433A054A;
	Thu, 11 Feb 2021 15:03:01 +0100 (CET)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 3BADB1CC3CE;
	Thu, 11 Feb 2021 15:03:01 +0100 (CET)
Received: from us-smtp-delivery-124.mimecast.com
 (us-smtp-delivery-124.mimecast.com [63.128.21.124])
 by mails.dpdk.org (Postfix) with ESMTP id B3D891CC344
 for <dev@dpdk.org>; Thu, 11 Feb 2021 15:02:59 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;
 s=mimecast20190719; t=1613052178;
 h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
 in-reply-to:in-reply-to:references:references;
 bh=n09UWRX4icbVRGXGCjmwZ1exE1LuwxN8BjCIXYOO07g=;
 b=BRSdyn2Wa0BOPr34zr800cKTQcFIwGWVStCRt0SZqRX+70aevCJb0t6Z5YYeNYaNIqdSOZ
 1YsraYIC3qycatX6zLwFumCQQngeR5MfBu664+a2JUNxF4kS5JxsawCHGuWSyS88QN41L9
 3XH4Wkoz/BUXadAMOjZ4KW3JCltnyPw=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id
 us-mta-392-e8Z8pH6mOeaFBSAH6jQ6nA-1; Thu, 11 Feb 2021 09:02:46 -0500
X-MC-Unique: e8Z8pH6mOeaFBSAH6jQ6nA-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com
 [10.5.11.11])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EF6A2801965;
 Thu, 11 Feb 2021 14:02:31 +0000 (UTC)
Received: from dhcp-25.97.bos.redhat.com (ovpn-114-243.rdu2.redhat.com
 [10.10.114.243])
 by smtp.corp.redhat.com (Postfix) with ESMTPS id 0CAE860657;
 Thu, 11 Feb 2021 14:02:30 +0000 (UTC)
From: Aaron Conole <aconole@redhat.com>
To: Brandon Lo <blo@iol.unh.edu>
Cc: "Zawadzki\, Tomasz" <tomasz.zawadzki@intel.com>,
 Lincoln Lavoie <lylavoie@iol.unh.edu>,
 "dpdklab\@iol.unh.edu" <dpdklab@iol.unh.edu>, "ci\@dpdk.org" <ci@dpdk.org>,
 "dev\@dpdk.org" <dev@dpdk.org>, "spdk\@lists.01.org" <spdk@lists.01.org>
References: <f7ta6se7fh7.fsf@dhcp-25.97.bos.redhat.com>
 <DM6PR11MB4220733693776AA1B8BE91A9EE8F9@DM6PR11MB4220.namprd11.prod.outlook.com>
 <CAOE1vsPC-D-5Rnc08fJDqrpcjeK1oYbaPsp1B72h2Pueyby0TA@mail.gmail.com>
 <DM6PR11MB422097059AB558056B97BEC5EE8F9@DM6PR11MB4220.namprd11.prod.outlook.com>
 <f7th7ml5l6o.fsf@dhcp-25.97.bos.redhat.com>
 <CAOeXdva_KdVOqmVTWaECKTRRgWpXjX+_RuT6d5vFB5FGy3DhCw@mail.gmail.com>
 <CAOeXdvZrTJu0bCoe8hXEGqDRDwJ-PBZcrbjg723M6TxSB1mw1w@mail.gmail.com>
Date: Thu, 11 Feb 2021 09:02:29 -0500
In-Reply-To: <CAOeXdvZrTJu0bCoe8hXEGqDRDwJ-PBZcrbjg723M6TxSB1mw1w@mail.gmail.com>
 (Brandon Lo's message of "Tue, 9 Feb 2021 12:54:36 -0500")
Message-ID: <f7tk0re1z4a.fsf@dhcp-25.97.bos.redhat.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
Authentication-Results: relay.mimecast.com;
 auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=aconole@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain
Subject: Re: [dpdk-dev] [dpdklab] Re: [dpdk-ci] [CI] SPDK compilation
 failures @ DPDK community lab
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Brandon Lo <blo@iol.unh.edu> writes:

> Hi again everyone,
>
> I have checked the pipelines with SPDK branch v21.01.x on the main DPDK branch.
> It still seems to have an issue with compilation, and I have attached
> a log of a Fedora SPDK compilation.
> There are some undefined references to "rte_ether_unformat_addr"
> I will continue to look into this. If you have any ideas on how to fix
> this, please let me know.

Looks like rte_ethdev depends on rte_net - maybe I missed something.

Brandon, can we disable this test for the time being since it's been
failing for a while now?  Can you also send me the container image /
definitions you're using so that I can help work on this?

> Thanks,
> Brandon
>
> On Tue, Feb 9, 2021 at 11:07 AM Brandon Lo <blo@iol.unh.edu> wrote:
>>
>> 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 <aconole@redhat.com> wrote:
>> >
>> > "Zawadzki, Tomasz" <tomasz.zawadzki@intel.com> writes:
>> >
>> > > 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?
>> >
>> > >
>> > > 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 <lylavoie@iol.unh.edu>
>> > > Sent: Monday, February 8, 2021 5:21 PM
>> > > To: Zawadzki, Tomasz <tomasz.zawadzki@intel.com>
>> > > Cc: Aaron Conole <aconole@redhat.com>; Brandon Lo
>> > > <blo@iol.unh.edu>; 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 <tomasz.zawadzki@intel.com> 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 <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
>> >
>>
>>
>> --
>>
>> Brandon Lo
>>
>> UNH InterOperability Laboratory
>>
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>
>> blo@iol.unh.edu
>>
>> www.iol.unh.edu