Dear all,
after quick look at the logs,
it looks like the issue is caused by vpp-dpdk-dev-17.02-vpp1_amd64.pom deploy
failure.
As a consequence hc2vpp integration jobs are not triggered, which causes
honeycomb packages
being out of synch much more often.
The issue was also reported by our team
Current hc2vpp jobs expect vpp jobs to be successful (vpp jobs are triggers).
Ed: would it be possible to ignore vpp-dpdk-dev deploy failure?
If not - this is something we can live with (perhaps hc2vpp jobs need some
hardening).
Found one more issue (looks like it might be related):
Most curren
+ Ed
-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
Sent: 1 marca 2017 08:07
To: fdio-helpd...@rt.linuxfoundation.org; dwallac...@gmail.com
Cc: Peter Lapos -X (plapos - PAN
Vanessa,
does it apply to all fd.io projects or only VPP?
Regards,
Marek
-Original Message-
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Vanessa
Valderrama via RT
Sent: 31 lipca 2018 20:16
To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco)
Cc: csit-...@
