[vpp-dev] [FD.io Helpdesk #47942] Re: Merge jobs faiing

2017-11-08 Thread Vanessa Valderrama via RT 
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 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 via RT <
> fdio-helpd...@rt.linuxfoundation.org> wrote:
> 
> > 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 wrote:
> > > 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:2.7:deploy-file
> > > (default-
> > > cli)
> > > on project standalone-pom: Failed to deploy artifacts: Could not
> > > transfer
> > > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > > fd.io.master.ubuntu.xenial.main (
> > > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> > ):
> > > Failed to transfer file:
> > >
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > > 13:07:08 [ERROR]
> > > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > > Maven
> > > with the -e switch.
> > > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full
> > > debug
> > > logging.
> > > 13:07:08 [ERROR]
> > > 13:07:08 [ERROR] For more information about the errors and possible
> > > solutions, please read the following articles:
> > > 13:07:08 [ERROR] [Help 1]
> > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > > 13:07:08 Build step 'Execute shell' marked build as failure
> > >
> > >
> > > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > > 
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > Any update on this? We can't get the latest patches via the
> > > > Ubuntu
> > > > package
> > > > manager and that hurts certain test scenarios.
> > > >
> > > > -Lori
> > > >
> > > >
> > > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke 
> > > > wrote:
> > > >
> > > >> This looks like we are hitting the limit on storage at
> > > >> packagecloud.
> > > >>
> > > >> I've manually trimmed some old packages, but we really really
> > > >> need
> > > >> to get
> > > >> the script going that autotrims for us.
> > > >>
> > > >> Vanessa,
> > > >>
> > > >> How are we doing on that?
> > > >>
> > > >> Ed
> > > >>
> > > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris
> > > >> 
> > > >> wrote:
> > > >>
> > > >>> The post-merge jobs are failing with errors like this:
> > > >>>
> > > >>>
> > > >>>
> > > >>> *16:04:05* [ERROR] Failed to execute goal
> > > >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > > >>> (default-cli) on project standalone-pom: Failed to deploy
> > > >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> > > >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> > > >>> fd.io.master.ubuntu.xenial.main
> > > >>> (
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> > > >>> Failed to transfer file:
> > > >>>
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > > >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-
> > > >>> deb.deb.
> > > >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > > >>>
> > > >>>
> > > >>>
> > > >>> (from
> > > >>> https://jenkins.fd.io/job/vpp-merge-master-
> > > >>> ubuntu1604/3148/consoleFull)
> > > >>>
> > > >>>
> > > >>>
> > > >>> This is sufficiently voodoo for me to not know how to proceed.
> > > >>> (The
> > > >>> Nexus stuff consistently annoys and baffles me, not least the
> > > >>> overly-verbose chatter in build logs)
> > > >>>
> > > >>>
> > > >>>
> > > >>> Could someone take a look, please?
> > > >>>
> > > >>>
> > > >>>
> > > >>> Net result: No packages are being stored from master, and docs
> > > >>> are
> > > >>> not
> > > >>> getting generated. It has been doing for thia a few days as
> > > >>> best I
> > > >>> can tell.
> > > >>>
> > > >>>
> > > >>>
> > > >>> Thanks,
> > > >>>
> > > >>> Chris.
> > > >>> ___
> > > >>> vpp-dev mailing list
> > > >>> vpp-dev@lists.fd.io
> > > >>> https://lists.fd.io/mailman/listinfo/vpp-dev
> >

[vpp-dev] [FD.io Helpdesk #47850] Packages for master not published

2017-11-08 Thread Vanessa Valderrama via RT 
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 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 it bad enough, would be a fine hack) but the next merge build
> will
> refail for the same reasons.
> 
> Ed
> 
> On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama via RT <
> fdio-helpd...@rt.linuxfoundation.org> wrote:
> 
> > 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 wrote:
> > > 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:2.7:deploy-file
> > > (default-
> > > cli)
> > > on project standalone-pom: Failed to deploy artifacts: Could not
> > > transfer
> > > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > > fd.io.master.ubuntu.xenial.main (
> > > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> > ):
> > > Failed to transfer file:
> > >
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > > 13:07:08 [ERROR]
> > > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > > Maven
> > > with the -e switch.
> > > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full
> > > debug
> > > logging.
> > > 13:07:08 [ERROR]
> > > 13:07:08 [ERROR] For more information about the errors and possible
> > > solutions, please read the following articles:
> > > 13:07:08 [ERROR] [Help 1]
> > > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > > 13:07:08 Build step 'Execute shell' marked build as failure
> > >
> > >
> > > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > > 
> > > wrote:
> > >
> > > > Hello,
> > > >
> > > > Any update on this? We can't get the latest patches via the
> > > > Ubuntu
> > > > package
> > > > manager and that hurts certain test scenarios.
> > > >
> > > > -Lori
> > > >
> > > >
> > > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke 
> > > > wrote:
> > > >
> > > >> This looks like we are hitting the limit on storage at
> > > >> packagecloud.
> > > >>
> > > >> I've manually trimmed some old packages, but we really really
> > > >> need
> > > >> to get
> > > >> the script going that autotrims for us.
> > > >>
> > > >> Vanessa,
> > > >>
> > > >> How are we doing on that?
> > > >>
> > > >> Ed
> > > >>
> > > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris
> > > >> 
> > > >> wrote:
> > > >>
> > > >>> The post-merge jobs are failing with errors like this:
> > > >>>
> > > >>>
> > > >>>
> > > >>> *16:04:05* [ERROR] Failed to execute goal
> > > >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > > >>> (default-cli) on project standalone-pom: Failed to deploy
> > > >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> > > >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> > > >>> fd.io.master.ubuntu.xenial.main
> > > >>> (
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> > > >>> Failed to transfer file:
> > > >>>
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > > >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-
> > > >>> deb.deb.
> > > >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > > >>>
> > > >>>
> > > >>>
> > > >>> (from
> > > >>> https://jenkins.fd.io/job/vpp-merge-master-
> > > >>> ubuntu1604/3148/consoleFull)
> > > >>>
> > > >>>
> > > >>>
> > > >>> This is sufficiently voodoo for me to not know how to proceed.
> > > >>> (The
> > > >>> Nexus stuff consistently annoys and baffles me, not least the
> > > >>> overly-verbose chatter in build logs)
> > > >>>
> > > >>>
> > > >>>
> > > >>> Could someone take a look, please?
> > > >>>
> > > >>>
> > > >>>
> > > >>> Net result: No packages are being stored from master, and docs
> > > >>> are
> > > >>> not
> > > >>> getting generated. It has been doing for thia a few days as
> > > >>> best I
> > > >>> can tell.
> > > >>>
> > > >>>
> > > >>>
> > > >>> Thanks,
> > > >>>
> > > >>> Chris.
> > > >>> ___
> > > >>> vp

Re: [vpp-dev] And Boost Log too?

2017-11-08 Thread Jon Loeliger 
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/listinfo/vpp-dev

Re: [vpp-dev] And Boost Log too?

2017-11-08 Thread Neale Ranns (nranns) 
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
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/workspace/vpp/src 
-I/home/jdl/workspace/vpp/build-root/install-vpp-native//vpp/include 
-I/home/jdl/workspace/vpp/build-root/vapi_test/ -DBOOST_LOG_DYN_LINK -O0 -g 
vom_test.cpp 
/home/jdl/workspace/vpp/build-root/build-vpp-native/vpp/vpp-api/vom/.libs/libvom.so
 -lboost_log -lboost_thread -lboost_system -lboost_filesystem 
-lboost_unit_test_framework 
-L/home/jdl/workspace/vpp/build-root/build-vpp-native/vpp/.libs/ 
-L/home/jdl/workspace/vpp/build-root/build-vpp-native/vpp/vpp-api/vapi/.libs/ 
-lvppinfra -lvlibmemoryclient -lsvm -lpthread -lcheck -lrt -lm -lvapiclient 
-lsubunit
/usr/bin/ld: cannot find -lboost_log
collect2: error: ld returned 1 exit status
make[2]: *** [/home/jdl/workspace/vpp/build-root/vom_test/vom_test] Error 1
make[2]: Leaving directory `/home/jdl/workspace/vpp/test/ext'
make[1]: *** [ext] Error 2
make[1]: Leaving directory `/home/jdl/workspace/vpp/test'
make: *** [test] Error 2


# make install-dep -n
sudo -E yum groupinstall  'Development Tools'
sudo -E yum install  redhat-lsb glibc-static java-1.8.0-openjdk-devel yum-utils 
apr-devel numactl-devel check check-devel boost boost-devel openssl-devel 
python-devel python-virtualenv chrpath libffi-devel rpm-build

$ sudo yum install boost-log
Loaded plugins: auto-update-debuginfo, fastestmirror
Loading mirror speeds from cached hostfile
 * base: repo1.dal.innoscale.net
 * epel: kdeforge2.unl.edu
 * epel-debuginfo: mirror.steadfast.net
 * extras: repo1.dal.innoscale.net
 * updates: repo1.dal.innoscale.net
No package boost-log available.


___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] And Boost Log too?

2017-11-08 Thread Jon Loeliger 
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/workspace/vpp/src
-I/home/jdl/workspace/vpp/build-root/install-vpp-native//vpp/include
-I/home/jdl/workspace/vpp/build-root/vapi_test/ -DBOOST_LOG_DYN_LINK -O0 -g
vom_test.cpp
/home/jdl/workspace/vpp/build-root/build-vpp-native/vpp/vpp-api/vom/.libs/libvom.so
-lboost_log -lboost_thread -lboost_system -lboost_filesystem
-lboost_unit_test_framework
-L/home/jdl/workspace/vpp/build-root/build-vpp-native/vpp/.libs/
-L/home/jdl/workspace/vpp/build-root/build-vpp-native/vpp/vpp-api/vapi/.libs/
-lvppinfra -lvlibmemoryclient -lsvm -lpthread -lcheck -lrt -lm -lvapiclient
-lsubunit
/usr/bin/ld: cannot find -lboost_log
collect2: error: ld returned 1 exit status
make[2]: *** [/home/jdl/workspace/vpp/build-root/vom_test/vom_test] Error 1
make[2]: Leaving directory `/home/jdl/workspace/vpp/test/ext'
make[1]: *** [ext] Error 2
make[1]: Leaving directory `/home/jdl/workspace/vpp/test'
make: *** [test] Error 2


# make install-dep -n
sudo -E yum groupinstall  'Development Tools'
sudo -E yum install  redhat-lsb glibc-static java-1.8.0-openjdk-devel
yum-utils apr-devel numactl-devel check check-devel boost boost-devel
openssl-devel python-devel python-virtualenv chrpath libffi-devel rpm-build

$ sudo yum install boost-log
Loaded plugins: auto-update-debuginfo, fastestmirror
Loading mirror speeds from cached hostfile
 * base: repo1.dal.innoscale.net
 * epel: kdeforge2.unl.edu
 * epel-debuginfo: mirror.steadfast.net
 * extras: repo1.dal.innoscale.net
 * updates: repo1.dal.innoscale.net
No package boost-log available.
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Neighbor DUMP Takes Forever

2017-11-08 Thread Jon Loeliger 
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_interface_details responses (if any)
> 4.) once control-ping reply is received, you know that there will be no
> more
> responses to the sw_interface_dump call.
>

Yep.  I get it.  I just botched it.  Sorry.


> HTH,
> Klement
>

Thanks,
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Neighbor DUMP Takes Forever

2017-11-08 Thread Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco) 
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
responses to the sw_interface_dump call.

This approach is used by all the existing API bindings, python, C VAPI,
C++ VAPI...

There have been proposals to have this logic built-in, but it doesn't
seem to have happened so far..

HTH,
Klement

Quoting Jon Loeliger (2017-11-08 19:25:03)
>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 one iterates over them one at a time asking for an 
>IP_NEIGHBOR_DUMP of each sw_if_index and AF combination.
>That's all fine.  The problem is that the DUMP response DETAILS never come
>for
>interfaces that have NO entries.  So the message handling times-out
>instead.  With
>a one-second timeout on each (interface, AF) pair, it takes 2 seconds per
>IF.
>It makes for a very slow process to determine the ARP/Neighbor tables.
>This used to be a problem in the NAT DUMP as well, but that was fixed.  I
>don't
>recall how off-hand, but at least one solution would be to always reply,
>and if a
>bogus entry is needed, do that.  Use a detail with a sw_if_index = ~0 if
>necessary.
>(Yeah, the ip_neighbor_t detail should be returning the sw_if_index too
>anyway.)
>Maybe something like that?
>Oh, the reason that you never see this problem with vppctl is that it
>doesn't
>use the API. It goes straight to internal data structures instead.
>Thanks,
>jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Neighbor DUMP Takes Forever

2017-11-08 Thread Jon Loeliger 
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
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Neighbor DUMP Takes Forever

2017-11-08 Thread Jon Loeliger 
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 one iterates over them one at a time asking for an
IP_NEIGHBOR_DUMP of each sw_if_index and AF combination.

That's all fine.  The problem is that the DUMP response DETAILS never come
for
interfaces that have NO entries.  So the message handling times-out
instead.  With
a one-second timeout on each (interface, AF) pair, it takes 2 seconds per
IF.

It makes for a very slow process to determine the ARP/Neighbor tables.

This used to be a problem in the NAT DUMP as well, but that was fixed.  I
don't
recall how off-hand, but at least one solution would be to always reply,
and if a
bogus entry is needed, do that.  Use a detail with a sw_if_index = ~0 if
necessary.
(Yeah, the ip_neighbor_t detail should be returning the sw_if_index too
anyway.)

Maybe something like that?

Oh, the reason that you never see this problem with vppctl is that it
doesn't
use the API. It goes straight to internal data structures instead.

Thanks,
jdl
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] SEGSEGV in acl using 2 core configuration

2017-11-08 Thread Andrew Yourtchenko 
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. Then we can track if the 
latest commit fixed or merely masked it...

--a

> On 8 Nov 2017, at 08:40, khers  wrote:
> 
> Dear Andrew
> 
> Sorry for my delay, I get last revision of master  (commit : 
> e695cb4dbdb6f9424ac5a567799e67f791fad328 ), and 
> segfault did not occur with the same environment and test scenario. I will 
> try to reproduce the potential bug
> with running test with longer duration and more aggressive scenario. 
> 
> Regards,
> Khers
> 
>> On Wed, Oct 25, 2017 at 1:45 PM, Andrew 👽 Yourtchenko  
>> wrote:
>> Dear Khers,
>> 
>> okay, cool! When testing the debug image, you could save the full dump
>> and the .debs for all the artefacts so just in case I could grab the
>> entire set of info and was able to look at it in my environment.
>> 
>> Meantime, I had an idea for another potential failure mode, whereby
>> the session would get checked while there is a session being freed,
>> potentially resulting in a reallocation of the free bitmap in the
>> pool.
>> 
>> So before the reproduction in the debug build, give a shot to this
>> one-line change
>>  in the release build and see if you still can reproduce the crash with it:
>> 
>> --- a/src/plugins/acl/fa_node.c
>> +++ b/src/plugins/acl/fa_node.c
>> @@ -609,6 +609,8 @@ acl_fa_verify_init_sessions (acl_main_t * am)
>>  for (wk = 0; wk < vec_len (am->per_worker_data); wk++) {
>>acl_fa_per_worker_data_t *pw = &am->per_worker_data[wk];
>>pool_alloc_aligned(pw->fa_sessions_pool,
>> am->fa_conn_table_max_entries, CLIB_CACHE_LINE_BYTES);
>> +  /* preallocate the free bitmap */
>> +  clib_bitmap_validate(pool_header(pw->fa_sessions_pool)->free_bitmap,
>> am->fa_conn_table_max_entries);
>>  }
>> 
>> --a
>> 
>> On 10/24/17, khers  wrote:
>> > Dear Andrew
>> >
>> > I used latest version of master branch, I will replay the test with debug
>> > build to make more debug info ASAP.
>> > Vpp is running on Xeon E5-2600  series.
>> > I did the tanother tests with two rx-queue and two worker, also with 4
>> > rx-queue and 4 worker, I got segmentation fault on the same function.
>> >
>> > I will send more info in few days.
>> >
>> > Regards,
>> > Khers
>> >
>> > On Oct 24, 2017 6:43 PM, "Andrew 👽 Yourtchenko" 
>> > wrote:
>> >
>> >> Dear Khers,
>> >>
>> >> Thanks for the info!
>> >>
>> >> I tried with these configs in my local setup (I tried even to increase
>> >> the multi-cpu contention by specifying 4 rx-queues instead of 2), but
>> >> it works ok for me on the master. What is the version you are testing
>> >> with ? I presume it is also the master, but just wanted to verify.
>> >>
>> >> To try to get more info about this happening: could you give a shot at
>> >> reproducing this on the debug build ? There are a few asserts that
>> >> would be handy to verify that they do hold true during your tests -
>> >> the location of the crash points to either the pool header being
>> >> corrupted by something (the asserts should catch that) or the pool
>> >> itself reallocated and memory used by something else (which should not
>> >> happen because the memory is preallocated during the initialisation
>> >> time - unless you change the max number of sessions after
>> >> initialisation).
>> >>
>> >> Also, could you tell a bit more about the hardware you are testing
>> >> with ? (cat /proc/cpuinfo)
>> >>
>> >> --a
>> >>
>> >> On 10/24/17, khers  wrote:
>> >> > Dear Andrew
>> >> >
>> >> > Thanks for your attention.
>> >> > Trex config file 
>> >> > Trex scenario is default sfr.yaml.
>> >> > vpp: startup.conf 
>> >> > I changed size of acl_mheap to '(uword)2<<32' in acl.c
>> >> > vpp config:
>> >> > vppctl set interface l2 bridge TenGigabitEthernet86/0/0 1
>> >> > vppctl set interface l2 bridge TenGigabitEthernet86/0/1 1
>> >> >
>> >> > vppctl set int state TenGigabitEthernet86/0/0 up
>> >> > vppctl set int state TenGigabitEthernet86/0/1 up
>> >> >
>> >> > vppctl set acl-plugin session table hash-table-buckets 100
>> >> > vppctl set acl-plugin session table hash-table-memory 2147483648
>> >> >
>> >> > vppctl set acl-plugin session timeout udp idle 5
>> >> > vppctl set acl-plugin session timeout tcp idle 10
>> >> > vppctl set acl-plugin session timeout tcp transient 5
>> >> >
>> >> > Regards,
>> >> > Khers
>> >> >
>> >> >
>> >> > On Mon, Oct 23, 2017 at 7:52 PM, Andrew 👽 Yourtchenko <
>> >> ayour...@gmail.com>
>> >> > wrote:
>> >> >
>> >> >> Hi,
>> >> >>
>> >> >> could you share the exact TRex and VPP config files, so I could
>> >> >> recreate it locally to investigate further ?
>> >> >>
>> >> >> Thanks a lot!
>> >> >>
>> >> >> --a
>> >> >>
>> >> >> On 10/23/17, khers

Re: [vpp-dev] [FD.io Helpdesk #47850] Packages for master not published

2017-11-08 Thread Ed Warnicke via RT 
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 it bad enough, would be a fine hack) but the next merge build will
refail for the same reasons.

Ed

On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> 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 wrote:
> > 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:2.7:deploy-file (default-
> > cli)
> > on project standalone-pom: Failed to deploy artifacts: Could not
> > transfer
> > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > fd.io.master.ubuntu.xenial.main (
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> ):
> > Failed to transfer file:
> >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > Maven
> > with the -e switch.
> > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
> > logging.
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] For more information about the errors and possible
> > solutions, please read the following articles:
> > 13:07:08 [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > 13:07:08 Build step 'Execute shell' marked build as failure
> >
> >
> > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > 
> > wrote:
> >
> > > Hello,
> > >
> > > Any update on this? We can't get the latest patches via the Ubuntu
> > > package
> > > manager and that hurts certain test scenarios.
> > >
> > > -Lori
> > >
> > >
> > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke 
> > > wrote:
> > >
> > >> This looks like we are hitting the limit on storage at packagecloud.
> > >>
> > >> I've manually trimmed some old packages, but we really really need
> > >> to get
> > >> the script going that autotrims for us.
> > >>
> > >> Vanessa,
> > >>
> > >> How are we doing on that?
> > >>
> > >> Ed
> > >>
> > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris 
> > >> wrote:
> > >>
> > >>> The post-merge jobs are failing with errors like this:
> > >>>
> > >>>
> > >>>
> > >>> *16:04:05* [ERROR] Failed to execute goal
> > >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > >>> (default-cli) on project standalone-pom: Failed to deploy
> > >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> > >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> > >>> fd.io.master.ubuntu.xenial.main
> > >>> (
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> > >>> Failed to transfer file:
> > >>>
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > >>>
> > >>>
> > >>>
> > >>> (from
> > >>> https://jenkins.fd.io/job/vpp-merge-master-
> > >>> ubuntu1604/3148/consoleFull)
> > >>>
> > >>>
> > >>>
> > >>> This is sufficiently voodoo for me to not know how to proceed. (The
> > >>> Nexus stuff consistently annoys and baffles me, not least the
> > >>> overly-verbose chatter in build logs)
> > >>>
> > >>>
> > >>>
> > >>> Could someone take a look, please?
> > >>>
> > >>>
> > >>>
> > >>> Net result: No packages are being stored from master, and docs are
> > >>> not
> > >>> getting generated. It has been doing for thia a few days as best I
> > >>> can tell.
> > >>>
> > >>>
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Chris.
> > >>> ___
> > >>> 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
>

___
vpp-dev mailing

Re: [vpp-dev] [FD.io Helpdesk #47850] Packages for master not published

2017-11-08 Thread Ed Warnicke 
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 it bad enough, would be a fine hack) but the next merge build will
refail for the same reasons.

Ed

On Wed, Nov 8, 2017 at 7:52 AM Vanessa Valderrama via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> 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 wrote:
> > 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:2.7:deploy-file (default-
> > cli)
> > on project standalone-pom: Failed to deploy artifacts: Could not
> > transfer
> > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > fd.io.master.ubuntu.xenial.main (
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> ):
> > Failed to transfer file:
> >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > Maven
> > with the -e switch.
> > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
> > logging.
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] For more information about the errors and possible
> > solutions, please read the following articles:
> > 13:07:08 [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > 13:07:08 Build step 'Execute shell' marked build as failure
> >
> >
> > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > 
> > wrote:
> >
> > > Hello,
> > >
> > > Any update on this? We can't get the latest patches via the Ubuntu
> > > package
> > > manager and that hurts certain test scenarios.
> > >
> > > -Lori
> > >
> > >
> > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke 
> > > wrote:
> > >
> > >> This looks like we are hitting the limit on storage at packagecloud.
> > >>
> > >> I've manually trimmed some old packages, but we really really need
> > >> to get
> > >> the script going that autotrims for us.
> > >>
> > >> Vanessa,
> > >>
> > >> How are we doing on that?
> > >>
> > >> Ed
> > >>
> > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris 
> > >> wrote:
> > >>
> > >>> The post-merge jobs are failing with errors like this:
> > >>>
> > >>>
> > >>>
> > >>> *16:04:05* [ERROR] Failed to execute goal
> > >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > >>> (default-cli) on project standalone-pom: Failed to deploy
> > >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> > >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> > >>> fd.io.master.ubuntu.xenial.main
> > >>> (
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> > >>> Failed to transfer file:
> > >>>
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > >>>
> > >>>
> > >>>
> > >>> (from
> > >>> https://jenkins.fd.io/job/vpp-merge-master-
> > >>> ubuntu1604/3148/consoleFull)
> > >>>
> > >>>
> > >>>
> > >>> This is sufficiently voodoo for me to not know how to proceed. (The
> > >>> Nexus stuff consistently annoys and baffles me, not least the
> > >>> overly-verbose chatter in build logs)
> > >>>
> > >>>
> > >>>
> > >>> Could someone take a look, please?
> > >>>
> > >>>
> > >>>
> > >>> Net result: No packages are being stored from master, and docs are
> > >>> not
> > >>> getting generated. It has been doing for thia a few days as best I
> > >>> can tell.
> > >>>
> > >>>
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Chris.
> > >>> ___
> > >>> 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
>
___
vpp-dev mailing l

Re: [vpp-dev] [FD.io Helpdesk #47942] Re: Merge jobs faiing

2017-11-08 Thread Ed Warnicke 
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 via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> 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 wrote:
> > 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:2.7:deploy-file (default-
> > cli)
> > on project standalone-pom: Failed to deploy artifacts: Could not
> > transfer
> > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > fd.io.master.ubuntu.xenial.main (
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> ):
> > Failed to transfer file:
> >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > Maven
> > with the -e switch.
> > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
> > logging.
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] For more information about the errors and possible
> > solutions, please read the following articles:
> > 13:07:08 [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > 13:07:08 Build step 'Execute shell' marked build as failure
> >
> >
> > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > 
> > wrote:
> >
> > > Hello,
> > >
> > > Any update on this? We can't get the latest patches via the Ubuntu
> > > package
> > > manager and that hurts certain test scenarios.
> > >
> > > -Lori
> > >
> > >
> > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke 
> > > wrote:
> > >
> > >> This looks like we are hitting the limit on storage at packagecloud.
> > >>
> > >> I've manually trimmed some old packages, but we really really need
> > >> to get
> > >> the script going that autotrims for us.
> > >>
> > >> Vanessa,
> > >>
> > >> How are we doing on that?
> > >>
> > >> Ed
> > >>
> > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris 
> > >> wrote:
> > >>
> > >>> The post-merge jobs are failing with errors like this:
> > >>>
> > >>>
> > >>>
> > >>> *16:04:05* [ERROR] Failed to execute goal
> > >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > >>> (default-cli) on project standalone-pom: Failed to deploy
> > >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> > >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> > >>> fd.io.master.ubuntu.xenial.main
> > >>> (
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> > >>> Failed to transfer file:
> > >>>
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > >>>
> > >>>
> > >>>
> > >>> (from
> > >>> https://jenkins.fd.io/job/vpp-merge-master-
> > >>> ubuntu1604/3148/consoleFull)
> > >>>
> > >>>
> > >>>
> > >>> This is sufficiently voodoo for me to not know how to proceed. (The
> > >>> Nexus stuff consistently annoys and baffles me, not least the
> > >>> overly-verbose chatter in build logs)
> > >>>
> > >>>
> > >>>
> > >>> Could someone take a look, please?
> > >>>
> > >>>
> > >>>
> > >>> Net result: No packages are being stored from master, and docs are
> > >>> not
> > >>> getting generated. It has been doing for thia a few days as best I
> > >>> can tell.
> > >>>
> > >>>
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Chris.
> > >>> ___
> > >>> 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

Re: [vpp-dev] [FD.io Helpdesk #47942] Re: Merge jobs faiing

2017-11-08 Thread Ed Warnicke via RT 
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 via RT <
fdio-helpd...@rt.linuxfoundation.org> wrote:

> 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 wrote:
> > 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:2.7:deploy-file (default-
> > cli)
> > on project standalone-pom: Failed to deploy artifacts: Could not
> > transfer
> > artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> > fd.io.master.ubuntu.xenial.main (
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main
> ):
> > Failed to transfer file:
> >
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> > Maven
> > with the -e switch.
> > 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
> > logging.
> > 13:07:08 [ERROR]
> > 13:07:08 [ERROR] For more information about the errors and possible
> > solutions, please read the following articles:
> > 13:07:08 [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > 13:07:08 Build step 'Execute shell' marked build as failure
> >
> >
> > On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> > 
> > wrote:
> >
> > > Hello,
> > >
> > > Any update on this? We can't get the latest patches via the Ubuntu
> > > package
> > > manager and that hurts certain test scenarios.
> > >
> > > -Lori
> > >
> > >
> > > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke 
> > > wrote:
> > >
> > >> This looks like we are hitting the limit on storage at packagecloud.
> > >>
> > >> I've manually trimmed some old packages, but we really really need
> > >> to get
> > >> the script going that autotrims for us.
> > >>
> > >> Vanessa,
> > >>
> > >> How are we doing on that?
> > >>
> > >> Ed
> > >>
> > >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris 
> > >> wrote:
> > >>
> > >>> The post-merge jobs are failing with errors like this:
> > >>>
> > >>>
> > >>>
> > >>> *16:04:05* [ERROR] Failed to execute goal
> > >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> > >>> (default-cli) on project standalone-pom: Failed to deploy
> > >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> > >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> > >>> fd.io.master.ubuntu.xenial.main
> > >>> (
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> > >>> Failed to transfer file:
> > >>>
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> > >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> > >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> > >>>
> > >>>
> > >>>
> > >>> (from
> > >>> https://jenkins.fd.io/job/vpp-merge-master-
> > >>> ubuntu1604/3148/consoleFull)
> > >>>
> > >>>
> > >>>
> > >>> This is sufficiently voodoo for me to not know how to proceed. (The
> > >>> Nexus stuff consistently annoys and baffles me, not least the
> > >>> overly-verbose chatter in build logs)
> > >>>
> > >>>
> > >>>
> > >>> Could someone take a look, please?
> > >>>
> > >>>
> > >>>
> > >>> Net result: No packages are being stored from master, and docs are
> > >>> not
> > >>> getting generated. It has been doing for thia a few days as best I
> > >>> can tell.
> > >>>
> > >>>
> > >>>
> > >>> Thanks,
> > >>>
> > >>> Chris.
> > >>> ___
> > >>> 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

[vpp-dev] [FD.io Helpdesk #47850] Packages for master not published

2017-11-08 Thread Vanessa Valderrama via RT 
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 wrote:
> 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:2.7:deploy-file (default-
> cli)
> on project standalone-pom: Failed to deploy artifacts: Could not
> transfer
> artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> fd.io.master.ubuntu.xenial.main (
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> Failed to transfer file:
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> 13:07:08 [ERROR]
> 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> Maven
> with the -e switch.
> 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> 13:07:08 [ERROR]
> 13:07:08 [ERROR] For more information about the errors and possible
> solutions, please read the following articles:
> 13:07:08 [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 13:07:08 Build step 'Execute shell' marked build as failure
> 
> 
> On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> 
> wrote:
> 
> > Hello,
> >
> > Any update on this? We can't get the latest patches via the Ubuntu
> > package
> > manager and that hurts certain test scenarios.
> >
> > -Lori
> >
> >
> > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke 
> > wrote:
> >
> >> This looks like we are hitting the limit on storage at packagecloud.
> >>
> >> I've manually trimmed some old packages, but we really really need
> >> to get
> >> the script going that autotrims for us.
> >>
> >> Vanessa,
> >>
> >> How are we doing on that?
> >>
> >> Ed
> >>
> >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris 
> >> wrote:
> >>
> >>> The post-merge jobs are failing with errors like this:
> >>>
> >>>
> >>>
> >>> *16:04:05* [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> >>> (default-cli) on project standalone-pom: Failed to deploy
> >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> >>> fd.io.master.ubuntu.xenial.main
> >>> (https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> >>> Failed to transfer file:
> >>> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> >>>
> >>>
> >>>
> >>> (from
> >>> https://jenkins.fd.io/job/vpp-merge-master-
> >>> ubuntu1604/3148/consoleFull)
> >>>
> >>>
> >>>
> >>> This is sufficiently voodoo for me to not know how to proceed. (The
> >>> Nexus stuff consistently annoys and baffles me, not least the
> >>> overly-verbose chatter in build logs)
> >>>
> >>>
> >>>
> >>> Could someone take a look, please?
> >>>
> >>>
> >>>
> >>> Net result: No packages are being stored from master, and docs are
> >>> not
> >>> getting generated. It has been doing for thia a few days as best I
> >>> can tell.
> >>>
> >>>
> >>>
> >>> Thanks,
> >>>
> >>> Chris.
> >>> ___
> >>> 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

[vpp-dev] [FD.io Helpdesk #47942] Re: Merge jobs faiing

2017-11-08 Thread Vanessa Valderrama via RT 
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 wrote:
> 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:2.7:deploy-file (default-
> cli)
> on project standalone-pom: Failed to deploy artifacts: Could not
> transfer
> artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
> fd.io.master.ubuntu.xenial.main (
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> Failed to transfer file:
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> 13:07:08 [ERROR]
> 13:07:08 [ERROR] To see the full stack trace of the errors, re-run
> Maven
> with the -e switch.
> 13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> 13:07:08 [ERROR]
> 13:07:08 [ERROR] For more information about the errors and possible
> solutions, please read the following articles:
> 13:07:08 [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 13:07:08 Build step 'Execute shell' marked build as failure
> 
> 
> On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab
> 
> wrote:
> 
> > Hello,
> >
> > Any update on this? We can't get the latest patches via the Ubuntu
> > package
> > manager and that hurts certain test scenarios.
> >
> > -Lori
> >
> >
> > On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke 
> > wrote:
> >
> >> This looks like we are hitting the limit on storage at packagecloud.
> >>
> >> I've manually trimmed some old packages, but we really really need
> >> to get
> >> the script going that autotrims for us.
> >>
> >> Vanessa,
> >>
> >> How are we doing on that?
> >>
> >> Ed
> >>
> >> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris 
> >> wrote:
> >>
> >>> The post-merge jobs are failing with errors like this:
> >>>
> >>>
> >>>
> >>> *16:04:05* [ERROR] Failed to execute goal
> >>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file
> >>> (default-cli) on project standalone-pom: Failed to deploy
> >>> artifacts: Could not transfer artifact io.fd.vpp:vpp-dpdk-
> >>> dev:deb:deb:17.08-vpp2_amd64 from/to
> >>> fd.io.master.ubuntu.xenial.main
> >>> (https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
> >>> Failed to transfer file:
> >>> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-
> >>> dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
> >>> Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
> >>>
> >>>
> >>>
> >>> (from
> >>> https://jenkins.fd.io/job/vpp-merge-master-
> >>> ubuntu1604/3148/consoleFull)
> >>>
> >>>
> >>>
> >>> This is sufficiently voodoo for me to not know how to proceed. (The
> >>> Nexus stuff consistently annoys and baffles me, not least the
> >>> overly-verbose chatter in build logs)
> >>>
> >>>
> >>>
> >>> Could someone take a look, please?
> >>>
> >>>
> >>>
> >>> Net result: No packages are being stored from master, and docs are
> >>> not
> >>> getting generated. It has been doing for thia a few days as best I
> >>> can tell.
> >>>
> >>>
> >>>
> >>> Thanks,
> >>>
> >>> Chris.
> >>> ___
> >>> 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

Re: [vpp-dev] Merge jobs faiing

2017-11-08 Thread Ed Warnicke 
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:2.7:deploy-file (default-cli)
on project standalone-pom: Failed to deploy artifacts: Could not transfer
artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to
fd.io.master.ubuntu.xenial.main (
https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main):
Failed to transfer file:
https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
13:07:08 [ERROR]
13:07:08 [ERROR] To see the full stack trace of the errors, re-run Maven
with the -e switch.
13:07:08 [ERROR] Re-run Maven using the -X switch to enable full debug
logging.
13:07:08 [ERROR]
13:07:08 [ERROR] For more information about the errors and possible
solutions, please read the following articles:
13:07:08 [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
13:07:08 Build step 'Execute shell' marked build as failure


On Tue, Nov 7, 2017 at 11:50 PM Lori Jakab 
wrote:

> Hello,
>
> Any update on this? We can't get the latest patches via the Ubuntu package
> manager and that hurts certain test scenarios.
>
> -Lori
>
>
> On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke  wrote:
>
>> This looks like we are hitting the limit on storage at packagecloud.
>>
>> I've manually trimmed some old packages, but we really really need to get
>> the script going that autotrims for us.
>>
>> Vanessa,
>>
>> How are we doing on that?
>>
>> Ed
>>
>> On Mon, Nov 6, 2017 at 9:17 AM Luke, Chris 
>> wrote:
>>
>>> The post-merge jobs are failing with errors like this:
>>>
>>>
>>>
>>> *16:04:05* [ERROR] Failed to execute goal 
>>> org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy-file (default-cli) 
>>> on project standalone-pom: Failed to deploy artifacts: Could not transfer 
>>> artifact io.fd.vpp:vpp-dpdk-dev:deb:deb:17.08-vpp2_amd64 from/to 
>>> fd.io.master.ubuntu.xenial.main 
>>> (https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main): 
>>> Failed to transfer file: 
>>> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp-dpdk-dev/17.08-vpp2_amd64/vpp-dpdk-dev-17.08-vpp2_amd64-deb.deb.
>>>  Return code is: 400, ReasonPhrase: Bad Request. -> [Help 1]
>>>
>>>
>>>
>>> (from
>>> https://jenkins.fd.io/job/vpp-merge-master-ubuntu1604/3148/consoleFull)
>>>
>>>
>>>
>>> This is sufficiently voodoo for me to not know how to proceed. (The
>>> Nexus stuff consistently annoys and baffles me, not least the
>>> overly-verbose chatter in build logs)
>>>
>>>
>>>
>>> Could someone take a look, please?
>>>
>>>
>>>
>>> Net result: No packages are being stored from master, and docs are not
>>> getting generated. It has been doing for thia a few days as best I can tell.
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Chris.
>>> ___
>>> 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

Re: [vpp-dev] multi-core multi-threading performance

2017-11-08 Thread Dave Barach (dbarach) 
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: Re: multi-core multi-threading performance

Hi all,

Any help/ideas on how we can have a better performance using multi-cores is 
appreciated.

Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3...@rit.edu
ph : 585 764 4662


On Mon, Nov 6, 2017 at 8:10 AM, Pragash Vijayaragavan 
mailto:pxv3...@g.rit.edu>> wrote:
Ok now i provisioned 4 rx queues for 4 worker threads and yea all workers
are processing traffic, but the lookup rate has dropped, i am getting low 
packets than when it was 2 workers.

I tried configuring 4 tx queues as well, still same problem (low packets 
received compared to 2 workers).



Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3...@rit.edu
ph : 585 764 4662


On Mon, Nov 6, 2017 at 8:00 AM, Pragash Vijayaragavan 
mailto:pxv3...@g.rit.edu>> wrote:
Just 1, let me change it to 2 may be 3 and get back to you.

Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3...@rit.edu
ph : 585 764 4662


On Mon, Nov 6, 2017 at 7:48 AM, Dave Barach (dbarach) 
mailto:dbar...@cisco.com>> wrote:
How many RX queues did you provision? One per worker, or no supper...

Thanks… Dave

From: Pragash Vijayaragavan [mailto:pxv3...@rit.edu]
Sent: Monday, November 6, 2017 7:36 AM

To: Dave Barach (dbarach) mailto:dbar...@cisco.com>>
Cc: vpp-dev@lists.fd.io; John Marshall (jwm) 
mailto:j...@cisco.com>>; Neale Ranns (nranns) 
mailto:nra...@cisco.com>>; Minseok Kwon 
mailto:mxk...@rit.edu>>
Subject: Re: multi-core multi-threading performance

Hi Dave,

As per your suggestion i tried sending different traffic and i could notice 
that, 1 worker acts per port (hardware NIC)

Is it true that multiple workers cannot work on same port at the same time?





Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3...@rit.edu
ph : 585 764 4662


On Mon, Nov 6, 2017 at 7:13 AM, Pragash Vijayaragavan 
mailto:pxv3...@g.rit.edu>> wrote:
Thanks Dave,

let me try it out real quick and get back to you.

Thanks,

Pragash Vijayaragavan
Grad Student at Rochester Institute of Technology
email : pxv3...@rit.edu
ph : 585 764 4662


On Mon, Nov 6, 2017 at 7:11 AM, Dave Barach (dbarach) 
mailto:dbar...@cisco.com>> wrote:
Incrementing / random src/dst addr/port

Thanks… Dave

From: Pragash Vijayaragavan [mailto:pxv3...@rit.edu]
Sent: Monday, November 6, 2017 7:06 AM
To: Dave Barach (dbarach) mailto:dbar...@cisco.com>>
Cc: vpp-dev@lists.fd.io; John Marshall (jwm) 
mailto:j...@cisco.com>>; Neale Ranns (nranns) 
mailto:nra...@cisco.com>>; Minseok Kwon 
mailto:mxk...@rit.edu>>
Subject: Re: multi-core multi-threading performance

Hi Dave,

Thanks for the mail

a "show run" command shows dpdk-input process on 2 of the workers but the 
ip6-lookup process is running only on 1 worker.

What config should be done to make all threads process traffic.

This is for 4 workers and 1 main core.

Pasted output :


vpp# sh run
Thread 0 vpp_main (lcore 1)
Time 7.5, average vectors/node 0.00, last 128 main loops 0.00 per node 0.00
  vector rates in 0.e0, out 0.e0, drop 0.e0, punt 0.e0
 Name State Calls  Vectors
Suspends Clocks   Vectors/Call
acl-plugin-fa-cleaner-process   any wait 0   0  
15  4.97e30.00
api-rx-from-ring active  0   0  
79  1.07e50.00
cdp-process any wait 0   0  
 3  2.65e30.00
dpdk-processany wait 0   0  
 2  6.77e70.00
fib-walkany wait 0   0  
  7474  6.74e20.00
gmon-processtime wait0   0  
 1  4.24e30.00
ikev2-manager-process   any wait 0   0  
 7  7.04e30.00
ip6-icmp-neighbor-discovery-ev  any wait 0   0  
 7  4.67e30.00
lisp-retry-service  any wait 0   0  
 3  7.21e30.00
unix-epoll-input polling  21655148