From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id D204D324A for ; Wed, 29 Nov 2017 12:20:48 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 351DE20AFA; Wed, 29 Nov 2017 06:20:48 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 29 Nov 2017 06:20:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=bHRMsf89+wxSwVxX2Oh/C414hI 2FP8uPpUhcx6cehII=; b=UpC2xGh6huFwQ9ZD8+pouW1sU+bHRSGp1BxlUELR3O Ji2kxlb+DLE0KLv9d0Jk0V+3GodUVsG17IMekUgFoYLTimDluKsIuzoPLCOu+IHi V5U3hkWABVyP3Z28A8NR1BJmEHKFEbn43t4zZf1y0r6VuX8ZRGylle32DdhNaODC 4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=bHRMsf 89+wxSwVxX2Oh/C414hI2FP8uPpUhcx6cehII=; b=ZW396I8+B8ET2VhQADGyDw zmp0havRkjsnSkEZ+vNAGjsZrCDjrnC3rqM0CmcHj5bpQzDPZl06swHUZp7mkk85 DL+wIHhInSaygv5SMmkrmXM6ehNZYDZ726lAA4OF22yC4F0TsvPpQ+Zk5i4qPKzQ Dt49FIc/TIPwe/XnOWeAxltXGPnyGNl9NhDmIqgjcMp/+pFyA+araT8sowsbUMC+ CpLQ+QRtFujCdj5dv6yXb8JgbDDkA+mNkuI+oIOMhyk7X9y98oA+YxkOfd9ELAQe OwEj3iIgz70xn7m7e0quWaEAvhyKsKlsCbO3VieE6MwvYFWkrjujxoD4ZuC389LA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id CE8B7245A8; Wed, 29 Nov 2017 06:20:47 -0500 (EST) From: Thomas Monjalon To: Marco Varlese , Gabriel Ganne Cc: users@dpdk.org, Dave Wallace , "Gonzalez Monroy, Sergio" , "vpp-dev@lists.fd.io" , yliu@fridaylinux.org Date: Wed, 29 Nov 2017 12:20:46 +0100 Message-ID: <1618803.qeEmeQ9Ak4@xps> In-Reply-To: <1511868713.2292.12.camel@suse.de> References: <1511868713.2292.12.camel@suse.de> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-users] [vpp-dev] vpp-verify-master-opensuse build failure triage X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 11:20:49 -0000 Hi, It is an error on DPDK side. It seems the tarball for DPDK 17.08 has been overwritten by the stable rele= ase process. I have restored the original tarball and we are checking what went wrong. fast.dpdk.org is a CDN for static.dpdk.org. It may take time to get the restored tarball on all CDN nodes. Sorry for the noise 28/11/2017 12:31, Marco Varlese: > Hi Gabriel, >=20 > I just submitted a patch (https://gerrit.fd.io/r/#/c/9597/) to VPP to fix= thisissue.=20 > I've added you to the review so you can take a look. >=20 > In order to verify that the new patch fixes the issue, people should firs= t run: >=20 > $ rpm -e vpp-dpdk-devel && rm dpdk/dpdk-17.08.tar.xz >=20 > to trigger a rebuild and reinstall of the dpdk package... >=20 >=20 > Cheers, > Marco >=20 > On Tue, 2017-11-28 at 10:34 +0000, Gabriel Ganne wrote: > > Adding dpdk-user ML. > >=20 > > I had a look with an older dpdk archive I found. > > The folder archived has been renamed from *dpdk-17.08* to *dpdk-stable-= 17.08* > > This is the only difference, but it is enough to make the md5sum fail. > >=20 > > -- > > Gabriel Ganne > > From: Gabriel Ganne > > Sent: Tuesday, November 28, 2017 11:13:23 AM > > To: Marco Varlese; Dave Wallace; Gonzalez Monroy, Sergio > > Cc: vpp-dev@lists.fd.io > > Subject: Re: [vpp-dev] vpp-verify-master-opensuse build failure triage > > =20 > > Hi Marco, > >=20 > > I believe http://fast.dpdk.org/rel redirects to http://static.dpdk.org/= rel/ > >=20 > > I disagree on the md5 hashs. > > I have the following (NOK on 17.08, and OK on 17.11) : > >=20 > > $ wget http://static.dpdk.org/rel/dpdk-17.08.tar.xz > > $ openssl md5 dpdk-17.08.tar.xz # is 0641f59ea8ea98afefa7cfa2699f6241 in > > dpdk/Makefile > > MD5(dpdk-17.08.tar.xz)=3D 537ff038915fefd0f210905fafcadb4b=20 > >=20 > > $ wget http://static.dpdk.org/rel/dpdk-17.11.tar.xz > > $ openssl md5 dpdk-17.11.tar.xz > > MD5(dpdk-17.11.tar.xz)=3D 53ee9e054a8797c9e67ffa0eb5d0c701=20 > >=20 > > Though I agree that if the "recheck" button made the build pass, there = must be > > something wrong on my side. > > ... what did I miss ? > >=20 > > -- > > Gabriel Ganne > > From: Marco Varlese > > Sent: Tuesday, November 28, 2017 10:55:49 AM > > To: Gabriel Ganne; Dave Wallace; Gonzalez Monroy, Sergio > > Cc: vpp-dev@lists.fd.io > > Subject: Re: [vpp-dev] vpp-verify-master-opensuse build failure triage > > =20 > > Hi Gabriel, > >=20 > > On Tue, 2017-11-28 at 09:19 +0000, Gabriel Ganne wrote: > > > Hi, > > >=20 > > > I also have this issue on my machine, and I see on http://static.dpdk= =2Eorg/re > > > l/ that dpdk-17.08.tar.xz was written yesterday (27-Nov-2017 13:00) > > > Wouldn't it be possible that the archive was overwritten ? > >=20 > > The DPDK tarball in VPP is downloaded from http://fast.dpdk.org/rel > > According to http://dpdk.org/rel the MD5 used in VPP for the DPDK 17.08 > > release is correct. > > > In which case, the hash would need to be updated. > >=20 > > Right, if the tarball was a newer and different one then the MD5 hash s= hould > > be updated in VPP for the the checksum performed... > > However, in the case described by Dave below, a simple 'recheck' which > > triggers a new build (with the same code/scripts/etc. hence the same MD= 5 hash) > > solved it. > >=20 > > > Also, this would probably not be seen by people who had the dpdk-inst= all-dev=20 > > > package already installed. > > >=20 > > > Who should I ask to check this ? > >=20 > > I've added Sergio who might have further thoughts on this one. > >=20 > > > Best regards > > >=20 > > > -- > > > Gabriel Ganne > > > From: vpp-dev-bounces@lists.fd.io on be= half of > > > Marco Varlese > > > Sent: Tuesday, November 28, 2017 9:19:37 AM > > > To: Dave Wallace > > > Cc: vpp-dev@lists.fd.io > > > Subject: Re: [vpp-dev] vpp-verify-master-opensuse build failure triage > > > =20 > > > Dear Dave, > > >=20 > > > By the look of it is seemed to have been an hiccup with the download = or > > > that something spurious was left on the filesystem... > > > =3D=3D=3D > > > 12:08:13 Bad Checksum! Please remove /w/workspace/vpp-verify-master- > > > opensuse/dpdk/dpdk-17.08.tar.xz and retry > > > 12:08:13 Makefile:267: recipe for target '/w/workspace/vpp-verify- > > > master-opensuse/build-root/build-vpp-native/dpdk/.download.ok' failed > > > 12:08:13 make[3]: *** [/w/workspace/vpp-verify-master-opensuse/build- > > > root/build-vpp-native/dpdk/.download.ok] Error 1 > > > 12:08:13 make[3]: Leaving directory '/w/workspace/vpp-verify-master- > > > opensuse/dpdk' > > > 12:08:13 Makefile:460: recipe for target 'ebuild-build' failed > > > 12:08:13 make[2]: *** [ebuild-build] Error 2 > > > 12:08:13 make[2]: Leaving directory '/w/workspace/vpp-verify-master- > > > opensuse/dpdk' > > > 12:08:13 Makefile:682: recipe for target 'dpdk-build' failed > > > 12:08:13 make[1]: *** [dpdk-build] Error 2 > > > 12:08:13 make[1]: Leaving directory '/w/workspace/vpp-verify-master- > > > opensuse/build-root' > > > 12:08:13 Makefile:333: recipe for target 'build-release' failed > > > 12:08:13 make: *** [build-release] Error 2 > > > 12:08:13 Build step 'Execute shell' marked build as failure > > > =3D=3D=3D > > >=20 > > > Since the MD5 checksum on the DPDK tarball fails; to answer your > > > question, no, it has never happened to me to see this specific issue > > > before. > > >=20 > > > I don't think there's anything specific to the openSUSE setup and/or > > > scripts being executed. I'd rather feel is - as I said earlier - > > > something to do with an hiccup on the infrastructure side. The fact > > > that a 'recheck' made it passing I suppose it confirms my current > > > theory. > > >=20 > > > An idea: maybe, if it happens again, we might want to ask Vanessa to > > > see what's the status on the slave-node? Not sure if that could give = us > > > some more insight of what's going on. > > >=20 > > >=20 > > > Cheers, > > > Marco > > >=20 > > > On Mon, 2017-11-27 at 11:04 -0500, Dave Wallace wrote: > > > > Marco, > > > >=20 > > > > Can you please take a look at the build failure encountered with ht= tp > > > > s://gerrit.fd.io/r/#/c/9582/ on the vpp-verify-master-opensuse > > > > jenkins job: > > > >=20 > > > > ----- %< ----- > > > > fd.io JJB 7:56 AM > > > > Patch Set 2: Verified-1 > > > > Build Failed=20 > > > > https://jenkins.fd.io/job/vpp-verify-master-opensuse/459/ : FAILURE > > > > No problems were identified. If you know why this problem occurred, > > > > please add a suitable Cause for it. ( https://jenkins.fd.io/job/vpp= =2Dv > > > > erify-master-opensuse/459/ ) > > > > Logs: https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verif= y- > > > > master-opensuse/459 > > > > ----- %< ------ > > > >=20 > > > > From the logs, it appears that there is an issue related to building > > > > dpdk. Have you seen this issue before? If so, it this an > > > > infrastructure issue or something else? > > > >=20 > > > > Thanks, > > > > -daw- > > > > _______________________________________________ > > > > vpp-dev mailing list > > > > vpp-dev@lists.fd.io > > > > https://lists.fd.io/mailman/listinfo/vpp-dev > > > _______________________________________________ > > > vpp-dev mailing list > > > vpp-dev@lists.fd.io > > > https://lists.fd.io/mailman/listinfo/vpp-dev > >=20 > > Marco V > >=20 > > SUSE LINUX GmbH | GF: Felix Imend=F6rffer, Jane Smithard, Graham Norton > > HRB 21284 (AG N=FCrnberg) Maxfeldstr. 5, D-90409, N=FCrnberg >=20