Hi, It is an error on DPDK side. It seems the tarball for DPDK 17.08 has been overwritten by the stable release 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, > > I just submitted a patch (https://gerrit.fd.io/r/#/c/9597/) to VPP to fix > thisissue. > I've added you to the review so you can take a look. > > In order to verify that the new patch fixes the issue, people should first > run: > > $ rpm -e vpp-dpdk-devel && rm dpdk/dpdk-17.08.tar.xz > > to trigger a rebuild and reinstall of the dpdk package... > > > Cheers, > Marco > > On Tue, 2017-11-28 at 10:34 +0000, Gabriel Ganne wrote: > > Adding dpdk-user ML. > > > > 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. > > > > -- > > 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 > > > > Hi Marco, > > > > I believe http://fast.dpdk.org/rel redirects to http://static.dpdk.org/rel/ > > > > I disagree on the md5 hashs. > > I have the following (NOK on 17.08, and OK on 17.11) : > > > > $ 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)= 537ff038915fefd0f210905fafcadb4b > > > > $ wget http://static.dpdk.org/rel/dpdk-17.11.tar.xz > > $ openssl md5 dpdk-17.11.tar.xz > > MD5(dpdk-17.11.tar.xz)= 53ee9e054a8797c9e67ffa0eb5d0c701 > > > > Though I agree that if the "recheck" button made the build pass, there must > > be > > something wrong on my side. > > ... what did I miss ? > > > > -- > > Gabriel Ganne > > From: Marco Varlese <mvarl...@suse.de> > > 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 > > > > Hi Gabriel, > > > > On Tue, 2017-11-28 at 09:19 +0000, Gabriel Ganne wrote: > > > Hi, > > > > > > I also have this issue on my machine, and I see on > > > http://static.dpdk.org/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 ? > > > > 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. > > > > Right, if the tarball was a newer and different one then the MD5 hash should > > 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 MD5 > > hash) > > solved it. > > > > > Also, this would probably not be seen by people who had the > > > dpdk-install-dev > > > package already installed. > > > > > > Who should I ask to check this ? > > > > I've added Sergio who might have further thoughts on this one. > > > > > Best regards > > > > > > -- > > > Gabriel Ganne > > > From: vpp-dev-boun...@lists.fd.io <vpp-dev-boun...@lists.fd.io> on behalf > > > of > > > Marco Varlese <mvarl...@suse.de> > > > 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 > > > > > > Dear Dave, > > > > > > By the look of it is seemed to have been an hiccup with the download or > > > that something spurious was left on the filesystem... > > > === > > > 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 > > > === > > > > > > 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. > > > > > > 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. > > > > > > 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. > > > > > > > > > Cheers, > > > Marco > > > > > > On Mon, 2017-11-27 at 11:04 -0500, Dave Wallace wrote: > > > > Marco, > > > > > > > > Can you please take a look at the build failure encountered with http > > > > s://gerrit.fd.io/r/#/c/9582/ on the vpp-verify-master-opensuse > > > > jenkins job: > > > > > > > > ----- %< ----- > > > > fd.io JJB 7:56 AM > > > > Patch Set 2: Verified-1 > > > > Build Failed > > > > 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-v > > > > erify-master-opensuse/459/ ) > > > > Logs: https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify- > > > > master-opensuse/459 > > > > ----- %< ------ > > > > > > > > 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? > > > > > > > > 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 > > > > Marco V > > > > SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton > > HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg > _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev