FYI, I've seen this particular failure signature previously when the
download from packagecloud for vpp-ext-deps install fails. At that
point, the vpp-ext-deps package gets built by the executor and the
subsequent push to packagecloud fails because the package actually exists.
If the script(s) verified that the package exists on packagecloud prior
to download, then it could know enough to skip the upload at the end. I
didn't find a simple way to implement this fix at that time and it
happens infrequently, thus it never got fixed.
Thanks,
-daw-
On 5/16/2020 5:42 AM, Andrew Yourtchenko wrote:
1) “jobs are broken” is a bit of a strong assessment for this case -
it would be more precise to say “sporadic failures” - there are plenty
of blue bullets after and before that job:
https://jenkins.fd.io/view/vpp/job/vpp-merge-master-centos7/
(the trend overall is not stellar -
https://jenkins.fd.io/view/vpp/job/vpp-merge-master-centos7/buildTimeTrend -
but you see the big red dip when we had been debugging the issue last
weekend and that was rather broken :-)
2) About the nature of the failure: this is what I see in
https://jenkins.fd.io/view/vpp/job/vpp-merge-master-centos7/9496/console:
**
*05:14:22* *******************************************************************
*05:14:22* + echo '* VPP BUILD SUCCESSFULLY COMPLETED'
*05:14:22* * VPP BUILD SUCCESSFULLY COMPLETED
*05:14:22* + echo
'*******************************************************************'
*05:14:22* *******************************************************************
...
*05:15:22* Pushing
./build-root/vpp-selinux-policy-20.09-rc0~22_gf3a522f~b9496.x86_64.rpm...
success!
*05:15:22* Pushing ./build/external/vpp-ext-deps-20.09-0.x86_64.rpm... error:
*05:15:22*
*05:15:22* filename: has already been taken
*05:15:22*
*05:15:22* Build step 'Execute shell' marked build as failure
*05:15:22* $ ssh-agent -k
*05:15:22* unset SSH_AUTH_SOCK;
*05:15:22* unset SSH_AGENT_PID;
*05:15:22* echo Agent pid 72 killed;
*05:15:22* [ssh-agent] Stopped.
It means that the job had expected to push the VPP-ext-deps (which is
updated every once in a while only), but found that the file with that
name is already there in the repo. If the file is right content, it’s
not the end of the world at all. Though odd that it happens only once
in a while, I will try to look at it - probably after the 20.05
release is done.
In the memif issues you mention, there are some *warnings* that don’t
affect the state of the job.
worth having a person who is the expert in that area looking at them
and seeing if they are real or bogus.. I suppose got blame will tell
who that is - probably Damjan ?
--a
On 16 May 2020, at 06:14, Paul Vinciguerra
<pvi...@vinciconsulting.com> wrote:
I'm not sure who this should go to, nor the impact, so I'm posting
it here.
vpp-merge-master-centos7 is failing due to libmemif and
[-Wstringop-overflow=] see [0].
[0]
https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-merge-master-centos7/9496/console.log.gz
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16439): https://lists.fd.io/g/vpp-dev/message/16439
Mute This Topic: https://lists.fd.io/mt/74243105/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
