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 091DAA0549; Tue, 9 Feb 2021 16:13:15 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8C53A4014E; Tue, 9 Feb 2021 16:13:15 +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 9BCEB40147 for ; Tue, 9 Feb 2021 16:13:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1612883592; 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=Z1PrvDhrsabUn4/mzcATLLuj/qyt8yg9oS1gX8hFw4c=; b=F5MrAbSCEOqaANJm96aVED0i+ZVc953aG4YLcQBkCb2gh+Wnk81LKQI8ElW5/lMUbXJFD0 tkmAIO2aBSqXnyb8XLm8O2qML5N2OlaCwKWhq5SgG1azxYfly0WJOPe7n5+lET32btEJn4 xL6iPLmUiAeBVLIHQaCS5hJOFesT/fs= 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-518-SltCYOrXMdenskuK8zR2nw-1; Tue, 09 Feb 2021 10:13:08 -0500 X-MC-Unique: SltCYOrXMdenskuK8zR2nw-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 35482100CA83; Tue, 9 Feb 2021 15:13:07 +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 B54E51820E; Tue, 9 Feb 2021 15:13:04 +0000 (UTC) From: Aaron Conole To: "Zawadzki\, Tomasz" Cc: Lincoln Lavoie , Brandon Lo , "dpdklab\@iol.unh.edu" , "ci\@dpdk.org" , "dev\@dpdk.org" , "spdk\@lists.01.org" References: Date: Tue, 09 Feb 2021 10:13:03 -0500 In-Reply-To: (Tomasz Zawadzki's message of "Mon, 8 Feb 2021 17:17:34 +0000") Message-ID: 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.16 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] [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" "Zawadzki, Tomasz" 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 > Sent: Monday, February 8, 2021 5:21 PM > To: Zawadzki, Tomasz > Cc: Aaron Conole ; Brandon Lo ; 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 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