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/rel/<https://url10.mailanyone.net/v1/?m=1eJccQ-0000Nh-40&i=57e1b682&c=YXtwE6d2zZdJXheJMCdO_SuDEoEQrdHCdgK6mO-4uDZ2Bj4ObdPrE5Fn6cirFxtZy34K57yMEhszksJbrY2fvTBetWB77s_CJWkpQyyah6_rFbLQmG-dY-qWniIVsFMMRdRMvyqh0lqUak-Q_B9fQ1OiLTvnngJ7HyAk1jgaPeLkV0WU1HDSfBiGhal1ybeY3rdJxuTArJeYn2n4LUfPpkcz-j2_0PTyMVbDfGIpu8o>
 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<https://url10.mailanyone.net/v1/?m=1eJccQ-0000Nh-40&i=57e1b682&c=sI-Qn1OsaRXnxl6lIQOxUZGRD-xaVnPckQwB6CApx-aEpU2UjOwTOfDJA0lq7_Gt1VGQkE6h9MX8Bk9XrgJVo3hCjx0joHpm7zsqXSWsSRqfNFPpowBhGN6XywZqIk3LQZuUWd8ZzZ4GB3xv9bDSmK_j0r1RjBHuNRKrWVhBBEd_Ex_JIhXR3UfOngNNGAe6XmP6AtdokoxpJhyUHUq1pw>
According to 
http://dpdk.org/rel<https://url10.mailanyone.net/v1/?m=1eJccQ-0000Nh-40&i=57e1b682&c=sI-Qn1OsaRXnxl6lIQOxUZGRD-xaVnPckQwB6CApx-aEpU2UjOwTOfDJA0lq7_Gt1VGQkE6h9MX8Bk9XrgJVo3hCjx0joHpm7zsqXSWsSRqfNFPpowBhGN6XywZqIk3LQZuUWd8ZzZ4GB3xv9bDSmK_j0r1RjBHuNRKrWVhBBEd_Ex_JIhXR3UfOngNNGAe6XmP6AtdokoxpJhyUHUq1pw>
 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/<https://url10.mailanyone.net/v1/?m=1eJccQ-0000Nh-40&i=57e1b682&c=bSD_r9PFEyUeYK2sLQKAy2WL9BnY5kTrXCUuKUrPP9OQ7IBGKhjB5ocTORNFqDvxZSYlHbjt3iggbnpFxgM_Oybv6bXiZXxrK-lf_rZF8zGbD-WZXDzMK7PjFKj9mU8TJRgrL-Lh_HI4zy27A_UbQA7FiZ3rhkPs3CGLz57kaquUwiEfwfsIgfEbUbE2JNkyu1uT6zWxMqm05snDrIbcZI5pGcgFos0nhmVycif1cP3S5tp-prl2UPqAPqEn6oBBQGLcTn4UP-4dL7fSiTjm1g>
>  : 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<https://url10.mailanyone.net/v1/?m=1eJccQ-0000Nh-40&i=57e1b682&c=HPvq91kiezi7o40LB46GoU_VrbxtDBkQXU5NOJN_42q7wmrEnrwscRiZwyjmDXZOEmLd8JMBdpFe-7JiVzZkw4P2Ihs_YR6Sk9t1pjqzLuIudy-9VE0hgoBXW6H29wrv7L_K5Aqoyg78Nd5HU7OZO_asCpJAANWfs8j1RlQt4ZgVhZQ2MbpFnIS0JhjKATBUVrd-UJqu3fJ4NV72nr9EXIBKBo3TEwddeXt60-f6fY4>
> erify-master-opensuse/459/ )
> Logs: 
> https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify-<https://url10.mailanyone.net/v1/?m=1eJccQ-0000Nh-40&i=57e1b682&c=RTpZiGUHQDsP_NHKLHjL0vSodFxLttA5Axm0FF4Ba7Z_7XdX4q7ysiiijQ4SbYGfN4l8JkEWeWAQqcc6Embmgh6M0RYuRYKS56AaKXqb6hjUUMQMY55wxIWegV-oFHm4t1n9qPio_oM_07npfY6TAWw2UrFyU00Farp2o3CAJjNk4Lm-J4piiZkdu7FFCApKttRX190YxUS0tjKTz4c5TqKeV8umjOaEWX4jl9cshT_50M9ejJt2tEYt5eAglzbujgAy5y_LWjAa7ZqsJ-tOmQ>
> 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<https://url10.mailanyone.net/v1/?m=1eJccQ-0000Nh-40&i=57e1b682&c=x-0-WzGI6FM6bK_0y0wK-wa_kz5kTgJK0gAroY5hLIlDHyVofzSdxoUykmXKBcnKoIPJ8AerStHA272WfvwPTEfWez9UcPBjc6kB8arPadIKKH6TYBe8HjzfX8Hy08QqX01wl9RPNsq5OEaPRD7mDUak3_J5vjy5oimChKo1j47p83Tcn1zZ5KXEcIDfanVjw0WrJHG7vBBSGaoVvQKPK70sQ2NhCdAwIaMRCPzaJq_P-I3imaTGYdXc7R0xTP8s>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev<https://url10.mailanyone.net/v1/?m=1eJccQ-0000Nh-40&i=57e1b682&c=x-0-WzGI6FM6bK_0y0wK-wa_kz5kTgJK0gAroY5hLIlDHyVofzSdxoUykmXKBcnKoIPJ8AerStHA272WfvwPTEfWez9UcPBjc6kB8arPadIKKH6TYBe8HjzfX8Hy08QqX01wl9RPNsq5OEaPRD7mDUak3_J5vjy5oimChKo1j47p83Tcn1zZ5KXEcIDfanVjw0WrJHG7vBBSGaoVvQKPK70sQ2NhCdAwIaMRCPzaJq_P-I3imaTGYdXc7R0xTP8s>

--

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

Reply via email to