Change https://gerrit.fd.io/r/#/c/9327/ was submitted and merged to resolve
this issue but the builds are still failing with the same error.
On Wed Nov 08 10:16:01 2017, hagbard wrote:
> So the more interesting question is... why are we building the vpp-
> dpdk-dev
> package at all given that the
Closing as a duplicate of
https://rt-sso.linuxfoundation.org/Ticket/Display.html?id=47942
On Wed Nov 08 10:19:43 2017, hagbard wrote:
> The problem is a little deeper. The build should install from nexus
> the
> package if its in nexus and the version in master hasn't increased.
> Its
> not doin
On Wed, Nov 8, 2017 at 2:29 PM, Neale Ranns (nranns)
wrote:
> Hi Jon,
>
>
>
> It doesn’t need it. I must have left that in by mistake. I’ll take it out.
>
Awesome. Thanks!
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/l
Hi Jon,
It doesn’t need it. I must have left that in by mistake. I’ll take it out.
Thanks,
neale
From: on behalf of Jon Loeliger
Date: Wednesday, 8 November 2017 at 20:56
To: vpp-dev
Subject: [vpp-dev] And Boost Log too?
Folks,
Looks like VPP top-of-tree needs boost_log now. And it isn't
i
Folks,
Looks like VPP top-of-tree needs boost_log now. And it isn't
in the install-deps. And my "yum install boost-log" goes MIA.
Hints?
Thanks,
jdl
g++ -o /home/jdl/workspace/vpp/build-root/vom_test/vom_test -I
/home/jdl/workspace/vpp/src/vpp-api/ -std=c++11 -g -Wall -pthread
-I/home/jdl/w
On Wed, Nov 8, 2017 at 12:37 PM, Klement Sekera -X (ksekera - PANTHEON
TECHNOLOGIES at Cisco) wrote:
> Hi Jon,
>
> the usual way to deal with possible-empty result sets is to wrap the
> call with a control-ping.
>
> 1.) send control-ping
> 2.) send e.g. sw_interface_dump
> 3.) start collecting sw
Hi Jon,
the usual way to deal with possible-empty result sets is to wrap the
call with a control-ping.
1.) send control-ping
2.) send e.g. sw_interface_dump
3.) start collecting sw_interface_details responses (if any)
4.) once control-ping reply is received, you know that there will be no more
re
On Wed, Nov 8, 2017 at 12:25 PM, Jon Loeliger wrote:
> Hi Folks,
>
> OK, maybe the Neighbor DUMP doesn't literally take forever.
> But it sure does take too long! Here is the problem:
>
The problem appears to be PEBCAK.
jdl
___
vpp-dev mailing list
v
Hi Folks,
OK, maybe the Neighbor DUMP doesn't literally take forever.
But it sure does take too long! Here is the problem:
When one goes to DUMP the Neighbor tables, one has no idea which interface
might have ARP/NDP entries on them. So one determines the total number of
interfaces, and then on
Dear Khers,
That is without applying the one liner change that I have proposed, right ?
I would suggest to retry the reproduction on the same commit where you were
previously able to reproduce it, and if it is reliably reproducible there - to
apply that change and see if it addresses the issue.
The problem is a little deeper. The build should install from nexus the
package if its in nexus and the version in master hasn't increased. Its
not doing that, which is the root of the problem. Removing the package
from nexus without fixing that will simply buy us *one* build (which if we
need
The problem is a little deeper. The build should install from nexus the
package if its in nexus and the version in master hasn't increased. Its
not doing that, which is the root of the problem. Removing the package
from nexus without fixing that will simply buy us *one* build (which if we
need
So the more interesting question is... why are we building the vpp-dpdk-dev
package at all given that the version in nexus matches the version in the
repo which means we should simply be installing it from the repo rather
than building it...
Ed
On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama vi
So the more interesting question is... why are we building the vpp-dpdk-dev
package at all given that the version in nexus matches the version in the
repo which means we should simply be installing it from the repo rather
than building it...
Ed
On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama vi
This error typically occurs when an artifact that already exists is trying to
be deployed. Would you like to remove the artifacts that were deployed on
10/10? I believe that will resolve this error.
vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb
Thank you,
Vanessa
On Wed Nov 08 08:49:28 2017, hagbard
This error typically occurs when an artifact that already exists is trying to
be deployed. Would you like to remove the artifacts that were deployed on
10/10? I believe that will resolve this error.
vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb
Thank you,
Vanessa
On Wed Nov 08 08:49:28 2017, hagbard
This appears to be something going wrong pushing to the nexus server... it
looks like the nexus server is rejecting the push, from:
https://jenkins.fd.io/view/vpp/job/vpp-merge-master-ubuntu1604/3174/consoleFull
13:07:08 [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:
Please write up what you’ve done, and provide a pointer to your code.
Thanks… Dave
From: Pragash Vijayaragavan [mailto:pxv3...@rit.edu]
Sent: Wednesday, November 8, 2017 1:19 AM
To: Dave Barach (dbarach)
Cc: vpp-dev@lists.fd.io; John Marshall (jwm) ; Neale Ranns
(nranns) ; Minseok Kwon
Subject
18 matches
Mail list logo
