Hi,
I also have this issue on my machine, and I see on http://static.dpdk.org/rel/ that dpdk-17.08.tar.xz was written yesterday (27-Nov-2017 13:00) Wouldn't it be possible that the archive was overwritten ? In which case, the hash would need to be updated. 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 ? 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
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
