[vpp-dev] About dpdk tx failure

[yu scott]

Hi all

I run vpp in kvm vm,and the software nic is vhost-user.
I test the vpp route performance with Tester, vm connect Tester with dpdk
ovs datapath
I exec the cli "show error"
it show  item has so many packet.


I know vpp forward packets via vector,which is a set of packet.In my
experience，If
vpp have no cpu to forward packets, it will lose packet in dpdk rx, not tx.

If lose packet in tx, I think the reason is tx corresponding to the card in
ovs dpdk datapath not
timely get the packet away. But in my test environment ,dpdk ovs datapath
get packet rate is
10mpps，vpp forward rate is 800kpps.

So I confuse about the dpdk tx drop so many packets.
May be some config about vpp I mistake ?

Hope to you reply :-)
Thx
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Queries regarding test cases for "vppinfra"

[Ayush Singhal]

I tried the test cases on a 64 bit machine and they passed alright. I tried
the same on a 32 bit machine, expecting positive results straight away!

Well, I don't know if i missed anything because my compilation on a 32 bit
machine was successful. Was planning on unit testing each of the vpp components
but if I am not wrong the unit test cases are available only for vppinfra
and vnet.

Any pointers on that?

Thanks,
Ayush

On Thu, Oct 13, 2016 at 6:17 PM, Dave Barach (dbarach) 
wrote:

> Before I answer: from 100,000 feet, what are you trying to do? Run vpp on
> a CPU architecture other than x86_64?
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Ayush Singhal
> *Sent:* Thursday, October 13, 2016 8:34 AM
> *To:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] Queries regarding test cases for "vppinfra"
>
>
>
> Hi Team,
>
> I ran a few test cases related to vppinfra and noticed that some of them
> returned the value as '0' while some returns a non-zero value.
>
> Looking into the code it looks like, the return value is 0 when the test
> case is a success and is non-zero for a failure.
>
> I have observed that the below test cases return a non-zero output -
> 1. test_bihash_template
> 2. test_random fails with the following output
> test_random_main:72: known sequence check passes
> test_random_main:92: 1000 iterations, seed 7147
> 0x iterations 0 repeats
> Aborted (core dumped)
>
> Also, there are some test cases which pass (returns 0) with some warnings,
> for example:
> 1. test_phash passes with the following output
> 8-byte key 8 byte value test
> test_pfhash_main:121: key 0 bucket 1 lookup FAIL
> test_pfhash_main:121: key 1 bucket 1 lookup FAIL
> test_pfhash_main:121: key 2 bucket 1 lookup FAIL
> test_pfhash_main:121: key 3 bucket 1 lookup FAIL
> test_pfhash_main:139: key 0 bucket 1 lookup FAIL
> test_pfhash_main:139: key 1 bucket 1 lookup FAIL
> test_pfhash_main:139: key 2 bucket 1 lookup FAIL
> test_pfhash_main:139: key 3 bucket 1 lookup FAIL
> 16-byte key test
> 8-byte key test
> 4-byte key test
>
> 2. test_timing_wheel passes with the following output
> test_timing_wheel_main:161: iter 10, events 100, seed 1, level
> 0: 3.4483e-10 - 8.8276e-8 secs, 2^0 - 2^8 clocks
> test_timing_wheel_main:308: 20 iter done 276 expired; ave.
> error 2.3738e-11 +- 8.7304e-11, range 0.e0 3.4483e-10
> Error max  Fraction  Total  Count
> 0.e0   93.1159%  93.1159%   257
> 3.4483e-10 6.8841%   100.%  19
> test_timing_wheel_main:339: level 0: 3.4483e-10 - 8.8276e-8
> secs, 2^0 - 2^8 clocks
> time base advances 0, every 7.4051e-1 secs
> level 0: refills 0
>
> All I wanted to confirm is whether these test cases are sufficient
> evidence for the functional testing of the "vppinfra" component.
>
> Do I need to look further?
>
> All your comments are more than welcome.
>
> Thanks,
> Ayush
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Problems with sub-interfaces

[Tibor Frank -X (tifrank - PANTHEON TECHNOLOGIES at Cisco)]

Hi
I found two issues:

1.   It is not possible to create a sub-interface using VAT - 
https://jira.fd.io/browse/VPP-506

2.   It is not possible to set MAC address for a sub-interface - 
https://jira.fd.io/browse/VPP-507

Can someone look at it, please.

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

Re: [vpp-dev] Problems with sub-interfaces

[Dave Barach (dbarach)]

Both Jira tickets now in "request information" state, please update...

Thanks... Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Tibor Frank -X (tifrank - PANTHEON TECHNOLOGIES at Cisco)
Sent: Thursday, October 20, 2016 9:59 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Problems with sub-interfaces

Hi
I found two issues:

1.  It is not possible to create a sub-interface using VAT - 
https://jira.fd.io/browse/VPP-506

2.  It is not possible to set MAC address for a sub-interface - 
https://jira.fd.io/browse/VPP-507

Can someone look at it, please.

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

Re: [vpp-dev] Problems with sub-interfaces

[John Lo (loj)]

Since MAC on a sub-interface is the same as that of the main interface, does it 
make sense to set MAC on a sub-interface? If so, wouldn't MAC also be changed 
for the main interface and other sub-interfaces on the same port? I doubt NICs 
can use separate MACs for sub-interfaces as it is transparent to them. I think 
it make sense to allow setting MAC on the main interface only and the crash as 
shown in the log while setting MAC on a sub-interface should be fixed.   -John

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Dave Barach (dbarach)
Sent: Thursday, October 20, 2016 10:13 AM
To: Tibor Frank -X (tifrank - PANTHEON TECHNOLOGIES at Cisco); 
vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] Problems with sub-interfaces

Both Jira tickets now in "request information" state, please update...

Thanks... Dave

From: vpp-dev-boun...@lists.fd.io 
[mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Tibor Frank -X (tifrank - 
PANTHEON TECHNOLOGIES at Cisco)
Sent: Thursday, October 20, 2016 9:59 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Problems with sub-interfaces

Hi
I found two issues:

1.  It is not possible to create a sub-interface using VAT - 
https://jira.fd.io/browse/VPP-506

2.  It is not possible to set MAC address for a sub-interface - 
https://jira.fd.io/browse/VPP-507

Can someone look at it, please.

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

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Dave Wallace]

Maciek,

This looks like a race condition in the build for JVPP. All of the 
failures contain the following error:


   09:32:35 make[5]: Entering directory
   
'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
   09:32:35   CC jvpp-common/libjvpp_common_la-jvpp_common.lo
   09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
   09:32:35   CC jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
   09:32:39   CCLD libjvpp_common.la
   09:32:39   CCLD libjvpp_registry.la
   09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
   09:32:40 /usr/bin/ld: cannot find -ljvpp_common
   09:32:40 collect2: error: ld returned 1 exit status
   09:32:40 Makefile:551: recipe for target 'libjvpp_registry.la' failed

It appears that the output of "CCLD libjvpp_common.la" is an input to 
"CCLD libjvpp_registry.la" and in the error case it is not found.


I had thought that Maros or Marek had provided a fix for this issue a 
couple of weeks ago.  When I get the chance investigate further.


Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:

Hi,

Anybody with time and willingness to look at below jobs and see why 
they pass 1st time and fail 2nd time,

ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:

https://gerrit.fd.io/r/#/c/3499/
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE

Seem to be vpp build related, as the standalone ubuntu1604 build jobs 
for this patch are also yielding not repeatable results:

https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS


-Maciek

from 
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/consoleFull
10:52:23 make[1]: Entering directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'

10:52:23 dh clean --with dkms --with systemd
10:52:24 dh: error: cannot read debian/changelog: No such file or 
directory

10:52:24 debian/rules:21: recipe for target 'clean' failed
10:52:24 make[1]: *** [clean] Error 2
10:52:24 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'

10:52:24 Makefile:1159: recipe for target 'distclean' failed
10:52:24 make: *** [distclean] Error 2

10:59:49 collect2: error: ld returned 1 exit status
10:59:49 Makefile:551: recipe for target 'libjvpp_registry.la' failed
10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
10:59:49 make[5]: *** Waiting for unfinished jobs
11:00:00 make[5]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'

11:00:00 Makefile:445: recipe for target 'all' failed
11:00:00 make[4]: *** [all] Error 2
11:00:00 make[4]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'

11:00:00 Makefile:377: recipe for target 'all-recursive' failed
11:00:00 make[3]: *** [all-recursive] Error 1
11:00:00 make[3]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api'

11:00:00 Makefile:699: recipe for target 'vpp-api-build' failed
11:00:00 make[2]: *** [vpp-api-build] Error 2
11:00:00 make[2]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root'
11:00:00 
/w/workspace/vpp-csit-verify-virl-master/build-data/platforms.mk:20: 
recipe for target 'install-deb' failed

11:00:00 make[1]: *** [install-deb] Error 1
11:00:00 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root'

11:00:00 Makefile:264: recipe for target 'pkg-deb' failed
11:00:00 make: *** [pkg-deb] Error 2


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


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

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Edward Warnicke]

This change:

https://gerrit.fd.io/r/#/c/3486/

Was touching that part of the world... *if* it is a race condition, is it
possible that this patch got lucky, and the ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace  wrote:

> Maciek,
>
> This looks like a race condition in the build for JVPP.  All of the
> failures contain the following error:
>
> 09:32:35 make[5]: Entering directory '/w/workspace/vpp-verify-
> master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
> 09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
> 09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
> 09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
> 09:32:39   CCLD libjvpp_common.la
> 09:32:39   CCLD libjvpp_registry.la
> 09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
> 09:32:40 /usr/bin/ld: cannot find -ljvpp_common
> 09:32:40 collect2: error: ld returned 1 exit status
> 09:32:40 Makefile:551: recipe for target 'libjvpp_registry.la' failed
>
> It appears that the output of "CCLD libjvpp_common.la" is an input to
> "CCLD libjvpp_registry.la" and in the error case it is not found.
>
> I had thought that Maros or Marek had provided a fix for this issue a
> couple of weeks ago.  When I get the chance investigate further.
>
> Thanks,
> -daw-
>
>
> On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
>
> Hi,
>
> Anybody with time and willingness to look at below jobs and see why they
> pass 1st time and fail 2nd time,
> ie not repeatable..
>
> All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:
>
> https://gerrit.fd.io/r/#/c/3499/
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE
>
> Seem to be vpp build related, as the standalone ubuntu1604 build jobs for
> this patch are also yielding not repeatable results:
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS
>
>
> -Maciek
>
> from https://jenkins.fd.io/job/vpp-csit-verify-virl-
> master/1841/consoleFull
> 10:52:23 make[1]: Entering directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:23 dh clean --with dkms --with systemd
> 10:52:24 dh: error: cannot read debian/changelog: No such file or directory
> 10:52:24 debian/rules:21: recipe for target 'clean' failed
> 10:52:24 make[1]: *** [clean] Error 2
> 10:52:24 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:24 Makefile:1159: recipe for target 'distclean' failed
> 10:52:24 make: *** [distclean] Error 2
>
> 10:59:49 collect2: error: ld returned 1 exit status
> 10:59:49 Makefile:551: recipe for target 'libjvpp_registry.la' failed
> 10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
> 10:59:49 make[5]: *** Waiting for unfinished jobs
> 11:00:00 make[5]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:445: recipe for target 'all' failed
> 11:00:00 make[4]: *** [all] Error 2
> 11:00:00 make[4]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:377: recipe for target 'all-recursive' failed
> 11:00:00 make[3]: *** [all-recursive] Error 1
> 11:00:00 make[3]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api'
> 11:00:00 Makefile:699: recipe for target 'vpp-api-build' failed
> 11:00:00 make[2]: *** [vpp-api-build] Error 2
> 11:00:00 make[2]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root'
> 11:00:00 /w/workspace/vpp-csit-verify-virl-master/build-data/platfor
> ms.mk:20: recipe for target 'install-deb' failed
> 11:00:00 make[1]: *** [install-deb] Error 1
> 11:00:00 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root'
> 11:00:00 Makefile:264: recipe for target 'pkg-deb' failed
> 11:00:00 make: *** [pkg-deb] Error 2
>
>
> ___
> csit-dev mailing 
> listcsit-...@lists.fd.iohttps://lists.fd.io/mailman/listinfo/csit-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] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)]

It's quite possible, I've made multiple builds and rebuilds to make sure I 
didn't break anything, but I apparently did. Feel free to revert the patch and 
I'll take a look at it again. That java build stuff is a real mess...

Klement

On Oct 20, 2016 6:22 PM, Edward Warnicke  wrote:
This change:

https://gerrit.fd.io/r/#/c/3486/

Was touching that part of the world... *if* it is a race condition, is it 
possible that this patch got lucky, and the ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace 
mailto:dwallac...@gmail.com>> wrote:
Maciek,

This looks like a race condition in the build for JVPP.  All of the failures 
contain the following error:
09:32:35 make[5]: Entering directory 
'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
09:32:39   CCLD libjvpp_common.la
09:32:39   CCLD libjvpp_registry.la
09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target 
'libjvpp_registry.la' failed
It appears that the output of "CCLD 
libjvpp_common.la" is an input to "CCLD 
libjvpp_registry.la" and in the error case it is 
not found.

I had thought that Maros or Marek had provided a fix for this issue a couple of 
weeks ago.  When I get the chance investigate further.

Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
Hi,

Anybody with time and willingness to look at below jobs and see why they pass 
1st time and fail 2nd time,
ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:

https://gerrit.fd.io/r/#/c/3499/
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE

Seem to be vpp build related, as the standalone ubuntu1604 build jobs for this 
patch are also yielding not repeatable results:
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS


-Maciek

from https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/consoleFull
10:52:23 make[1]: Entering directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:23 dh clean --with dkms --with systemd
10:52:24 dh: error: cannot read debian/changelog: No such file or directory
10:52:24 debian/rules:21: recipe for target 'clean' failed
10:52:24 make[1]: *** [clean] Error 2
10:52:24 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:24 Makefile:1159: recipe for target 'distclean' failed
10:52:24 make: *** [distclean] Error 2

10:59:49 collect2: error: ld returned 1 exit status
10:59:49 Makefile:551: recipe for target 
'libjvpp_registry.la' failed
10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
10:59:49 make[5]: *** Waiting for unfinished jobs
11:00:00 make[5]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'
11:00:00 Makefile:445: recipe for target 'all' failed
11:00:00 make[4]: *** [all] Error 2
11:00:00 make[4]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'
11:00:00 Makefile:377: recipe for target 'all-recursive' failed
11:00:00 make[3]: *** [all-recursive] Error 1
11:00:00 make[3]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api'
11:00:00 Makefile:699: recipe for target 'vpp-api-build' failed
11:00:00 make[2]: *** [vpp-api-build] Error 2
11:00:00 make[2]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root'
11:00:00 
/w/workspace/vpp-csit-verify-virl-master/build-data/platforms.mk:20:
 recipe for target 'install-deb' failed
11:00:00 make[1]: *** [install-deb] Error 1
11:00:00 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root'
11:00:00 Makefile:264: recipe for target 'pkg-deb' failed
11:00:00 make: *** [pkg-deb] Error 2



___
csit-dev mailing list
csit-...@lists.fd.io
https://lists.fd.io/mailman/listinfo/csit-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] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Edward Warnicke]

Klement,

I'm not quite ready to point the finger strongly at that patch yet... I
appreciate you trying to improve the java build system :)

On Thu, Oct 20, 2016 at 9:24 AM, Klement Sekera -X (ksekera - PANTHEON
TECHNOLOGIES at Cisco)  wrote:

> It's quite possible, I've made multiple builds and rebuilds to make sure I
> didn't break anything, but I apparently did. Feel free to revert the patch
> and I'll take a look at it again. That java build stuff is a real mess...
>
> Klement
>
> On Oct 20, 2016 6:22 PM, Edward Warnicke  wrote:
>
> This change:
>
> https://gerrit.fd.io/r/#/c/3486/
>
> Was touching that part of the world... *if* it is a race condition, is it
> possible that this patch got lucky, and the ones that followed did not?
>
> Ed
>
> On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace 
> wrote:
>
> Maciek,
>
> This looks like a race condition in the build for JVPP.  All of the
> failures contain the following error:
>
> 09:32:35 make[5]: Entering directory '/w/workspace/vpp-verify-maste
> r-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
> 09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
> 09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
> 09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
> 09:32:39   CCLD libjvpp_common.la
> 09:32:39   CCLD libjvpp_registry.la
> 09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
> 09:32:40 /usr/bin/ld: cannot find -ljvpp_common
> 09:32:40 collect2: error: ld returned 1 exit status
> 09:32:40 Makefile:551: recipe for target 'libjvpp_registry.la' failed
>
> It appears that the output of "CCLD libjvpp_common.la" is an input to
> "CCLD libjvpp_registry.la" and in the error case it is not found.
>
> I had thought that Maros or Marek had provided a fix for this issue a
> couple of weeks ago.  When I get the chance investigate further.
>
> Thanks,
> -daw-
>
>
> On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
>
> Hi,
>
> Anybody with time and willingness to look at below jobs and see why they
> pass 1st time and fail 2nd time,
> ie not repeatable..
>
> All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:
>
> https://gerrit.fd.io/r/#/c/3499/
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE
>
> Seem to be vpp build related, as the standalone ubuntu1604 build jobs for
> this patch are also yielding not repeatable results:
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS
>
>
> -Maciek
>
> from https://jenkins.fd.io/job/vpp-csit-verify-virl-master/
> 1841/consoleFull
> 10:52:23 make[1]: Entering directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:23 dh clean --with dkms --with systemd
> 10:52:24 dh: error: cannot read debian/changelog: No such file or directory
> 10:52:24 debian/rules:21: recipe for target 'clean' failed
> 10:52:24 make[1]: *** [clean] Error 2
> 10:52:24 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:24 Makefile:1159: recipe for target 'distclean' failed
> 10:52:24 make: *** [distclean] Error 2
>
> 10:59:49 collect2: error: ld returned 1 exit status
> 10:59:49 Makefile:551: recipe for target 'libjvpp_registry.la' failed
> 10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
> 10:59:49 make[5]: *** Waiting for unfinished jobs
> 11:00:00 make[5]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:445: recipe for target 'all' failed
> 11:00:00 make[4]: *** [all] Error 2
> 11:00:00 make[4]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:377: recipe for target 'all-recursive' failed
> 11:00:00 make[3]: *** [all-recursive] Error 1
> 11:00:00 make[3]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api'
> 11:00:00 Makefile:699: recipe for target 'vpp-api-build' failed
> 11:00:00 make[2]: *** [vpp-api-build] Error 2
> 11:00:00 make[2]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root'
> 11:00:00 /w/workspace/vpp-csit-verify-virl-master/build-data/platform
> s.mk:20: recipe for target 'install-deb' failed
> 11:00:00 make[1]: *** [install-deb] Error 1
> 11:00:00 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root'
> 11:00:00 Makefile:264: recipe for target 'pkg-deb' failed
> 11:00:00 make: *** [pkg-deb] Error 2
>
>
> ___
> csit-dev mailing 
> listcsit-...@lists.fd.iohttps://lists.fd.io/mailman/listinfo/csit-dev
>
>
>
> ___
> vpp-dev mailing list
> vpp-dev@lists.fd.io
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
>
__

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Dave Barach (dbarach)]

Makefile.am bug.

Try -l:libjvpp_common.la in libjvpp_registry_la_LIBADD instead of 
-ljvpp_common. Worst case, add an explicit dependency.

Thanks... Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Dave Wallace
Sent: Thursday, October 20, 2016 12:16 PM
To: Maciek Konstantynowicz (mkonstan) ; 
csit-...@lists.fd.io; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build 
failures

Maciek,

This looks like a race condition in the build for JVPP.  All of the failures 
contain the following error:
09:32:35 make[5]: Entering directory 
'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
09:32:39   CCLD libjvpp_common.la
09:32:39   CCLD libjvpp_registry.la
09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target 'libjvpp_registry.la' failed
It appears that the output of "CCLD libjvpp_common.la" is an input to "CCLD 
libjvpp_registry.la" and in the error case it is not found.

I had thought that Maros or Marek had provided a fix for this issue a couple of 
weeks ago.  When I get the chance investigate further.

Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
Hi,

Anybody with time and willingness to look at below jobs and see why they pass 
1st time and fail 2nd time,
ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:

https://gerrit.fd.io/r/#/c/3499/
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE

Seem to be vpp build related, as the standalone ubuntu1604 build jobs for this 
patch are also yielding not repeatable results:
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS


-Maciek

from https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/consoleFull
10:52:23 make[1]: Entering directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:23 dh clean --with dkms --with systemd
10:52:24 dh: error: cannot read debian/changelog: No such file or directory
10:52:24 debian/rules:21: recipe for target 'clean' failed
10:52:24 make[1]: *** [clean] Error 2
10:52:24 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:24 Makefile:1159: recipe for target 'distclean' failed
10:52:24 make: *** [distclean] Error 2

10:59:49 collect2: error: ld returned 1 exit status
10:59:49 Makefile:551: recipe for target 'libjvpp_registry.la' failed
10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
10:59:49 make[5]: *** Waiting for unfinished jobs
11:00:00 make[5]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'
11:00:00 Makefile:445: recipe for target 'all' failed
11:00:00 make[4]: *** [all] Error 2
11:00:00 make[4]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'
11:00:00 Makefile:377: recipe for target 'all-recursive' failed
11:00:00 make[3]: *** [all-recursive] Error 1
11:00:00 make[3]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api'
11:00:00 Makefile:699: recipe for target 'vpp-api-build' failed
11:00:00 make[2]: *** [vpp-api-build] Error 2
11:00:00 make[2]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root'
11:00:00 /w/workspace/vpp-csit-verify-virl-master/build-data/platforms.mk:20: 
recipe for target 'install-deb' failed
11:00:00 make[1]: *** [install-deb] Error 1
11:00:00 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root'
11:00:00 Makefile:264: recipe for target 'pkg-deb' failed
11:00:00 make: *** [pkg-deb] Error 2




___

csit-dev mailing list

csit-...@lists.fd.io

https://lists.fd.io/mailman/listinfo/csit-dev

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

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Dave Barach (dbarach)]

+1 on the “real mess” comment.

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
Sent: Thursday, October 20, 2016 12:24 PM
To: Edward Warnicke 
Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build 
failures


It's quite possible, I've made multiple builds and rebuilds to make sure I 
didn't break anything, but I apparently did. Feel free to revert the patch and 
I'll take a look at it again. That java build stuff is a real mess...

Klement

On Oct 20, 2016 6:22 PM, Edward Warnicke 
mailto:hagb...@gmail.com>> wrote:
This change:

https://gerrit.fd.io/r/#/c/3486/

Was touching that part of the world... *if* it is a race condition, is it 
possible that this patch got lucky, and the ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace 
mailto:dwallac...@gmail.com>> wrote:
Maciek,

This looks like a race condition in the build for JVPP.  All of the failures 
contain the following error:
09:32:35 make[5]: Entering directory 
'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
09:32:39   CCLD libjvpp_common.la
09:32:39   CCLD libjvpp_registry.la
09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target 
'libjvpp_registry.la' failed
It appears that the output of "CCLD 
libjvpp_common.la" is an input to "CCLD 
libjvpp_registry.la" and in the error case it is 
not found.

I had thought that Maros or Marek had provided a fix for this issue a couple of 
weeks ago.  When I get the chance investigate further.

Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
Hi,

Anybody with time and willingness to look at below jobs and see why they pass 
1st time and fail 2nd time,
ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:

https://gerrit.fd.io/r/#/c/3499/
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE

Seem to be vpp build related, as the standalone ubuntu1604 build jobs for this 
patch are also yielding not repeatable results:
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS


-Maciek

from https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/consoleFull
10:52:23 make[1]: Entering directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:23 dh clean --with dkms --with systemd
10:52:24 dh: error: cannot read debian/changelog: No such file or directory
10:52:24 debian/rules:21: recipe for target 'clean' failed
10:52:24 make[1]: *** [clean] Error 2
10:52:24 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:24 Makefile:1159: recipe for target 'distclean' failed
10:52:24 make: *** [distclean] Error 2

10:59:49 collect2: error: ld returned 1 exit status
10:59:49 Makefile:551: recipe for target 
'libjvpp_registry.la' failed
10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
10:59:49 make[5]: *** Waiting for unfinished jobs
11:00:00 make[5]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'
11:00:00 Makefile:445: recipe for target 'all' failed
11:00:00 make[4]: *** [all] Error 2
11:00:00 make[4]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'
11:00:00 Makefile:377: recipe for target 'all-recursive' failed
11:00:00 make[3]: *** [all-recursive] Error 1
11:00:00 make[3]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api'
11:00:00 Makefile:699: recipe for target 'vpp-api-build' failed
11:00:00 make[2]: *** [vpp-api-build] Error 2
11:00:00 make[2]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root'
11:00:00 
/w/workspace/vpp-csit-verify-virl-master/build-data/platforms.mk:20:
 recipe for target 'install-deb' failed
11:00:00 make[1]: *** [install-deb] Error 1
11:00:00 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root'
11:00:00 Makefile:264: recipe for target 'pkg-deb' failed
11:00:00 make: *** [pkg-deb] Error 2



___

csit-dev mailing list

csit-...@lists.fd.io

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Dave Wallace]

Klement,

Thanks for helping improve the java build infrastructure.

I think that you may find that the execution of the build system is very 
different on the LF cloud infrastructure then on a typical development 
platform.  IIRC, this is not the first time we've been bitten by that 
particular bug.


Here is Marek's patch which fixed this issue earlier: 
https://gerrit.fd.io/r/#/c/3131


Looking at your patch, I think this deletion may be the primary culprit 
in opening up the race condition:


   -EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la

I think it would be worth pushing a patch with that dependency restored 
before reverting the entire patch.


Thanks,
-daw-

On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera - PANTHEON 
TECHNOLOGIES at Cisco) wrote:


It's quite possible, I've made multiple builds and rebuilds to make 
sure I didn't break anything, but I apparently did. Feel free to 
revert the patch and I'll take a look at it again. That java build 
stuff is a real mess...


Klement


On Oct 20, 2016 6:22 PM, Edward Warnicke  wrote:

This change:

https://gerrit.fd.io/r/#/c/3486/

Was touching that part of the world... *if* it is a race
condition, is it possible that this patch got lucky, and the ones
that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace
mailto:dwallac...@gmail.com>> wrote:

Maciek,

This looks like a race condition in the build for JVPP.  All
of the failures contain the following error:

09:32:35 make[5]: Entering directory

'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35   CC jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35   CC jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35   CC  
jvpp-registry/libjvpp_registry_la-jvpp_registry.lo

09:32:39   CCLD libjvpp_common.la 
09:32:39   CCLD libjvpp_registry.la

09:32:40 ar: `u' modifier ignored since `D' is the default
(see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target
'libjvpp_registry.la ' failed

It appears that the output of "CCLD libjvpp_common.la
" is an input to "CCLD
libjvpp_registry.la " and in the
error case it is not found.

I had thought that Maros or Marek had provided a fix for this
issue a couple of weeks ago. When I get the chance investigate
further.

Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:

Hi,

Anybody with time and willingness to look at below jobs
and see why they pass 1st time and fail 2nd time,
ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL. Related to
two vpp patches:

https://gerrit.fd.io/r/#/c/3499/

https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ 

: SUCCESS
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ 

: FAILURE

Seem to be vpp build related, as the standalone ubuntu1604
build jobs for this patch are also yielding not repeatable
results:
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/
 :
FAILURE
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/
 :
SUCCESS


-Maciek

from

https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/consoleFull


10:52:23 make[1]: Entering directory
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:23 dh clean --with dkms --with systemd
10:52:24 dh: error: cannot read debian/changelog: No such
file or directory
10:52:24 debian/rules:21: recipe for target 'clean' failed
10:52:24 make[1]: *** [clean] Error 2
10:52:24 make[1]: Leaving directory
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:24 Makefile:1159: recipe for target 'distclean' failed
10:52:24 make: *** [distclean] Error 2

10:59:49 collect2: error: ld returned 1 exit s

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Edward Warnicke]

You mean like this:
https://gerrit.fd.io/r/#/c/3511/1/vpp-api/java/Makefile.am :)

Ed

On Thu, Oct 20, 2016 at 9:50 AM, Dave Wallace  wrote:

> Klement,
>
> Thanks for helping improve the java build infrastructure.
>
> I think that you may find that the execution of the build system is very
> different on the LF cloud infrastructure then on a typical development
> platform.  IIRC, this is not the first time we've been bitten by that
> particular bug.
>
> Here is Marek's patch which fixed this issue earlier:
> https://gerrit.fd.io/r/#/c/3131
>
> Looking at your patch, I think this deletion may be the primary culprit in
> opening up the race condition:
>
> -EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la
>
> I think it would be worth pushing a patch with that dependency restored
> before reverting the entire patch.
>
> Thanks,
> -daw-
>
>
> On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES
> at Cisco) wrote:
>
> It's quite possible, I've made multiple builds and rebuilds to make sure I
> didn't break anything, but I apparently did. Feel free to revert the patch
> and I'll take a look at it again. That java build stuff is a real mess...
>
> Klement
>
> On Oct 20, 2016 6:22 PM, Edward Warnicke 
>  wrote:
>
> This change:
>
> https://gerrit.fd.io/r/#/c/3486/
>
> Was touching that part of the world... *if* it is a race condition, is it
> possible that this patch got lucky, and the ones that followed did not?
>
> Ed
>
> On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace 
> wrote:
>
> Maciek,
>
> This looks like a race condition in the build for JVPP.  All of the
> failures contain the following error:
>
> 09:32:35 make[5]: Entering directory '/w/workspace/vpp-verify-maste
> r-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
> 09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
> 09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
> 09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
> 09:32:39   CCLD libjvpp_common.la
> 09:32:39   CCLD libjvpp_registry.la
> 09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
> 09:32:40 /usr/bin/ld: cannot find -ljvpp_common
> 09:32:40 collect2: error: ld returned 1 exit status
> 09:32:40 Makefile:551: recipe for target 'libjvpp_registry.la' failed
>
> It appears that the output of "CCLD libjvpp_common.la" is an input to
> "CCLD libjvpp_registry.la" and in the error case it is not found.
>
> I had thought that Maros or Marek had provided a fix for this issue a
> couple of weeks ago.  When I get the chance investigate further.
>
> Thanks,
> -daw-
>
>
> On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
>
> Hi,
>
> Anybody with time and willingness to look at below jobs and see why they
> pass 1st time and fail 2nd time,
> ie not repeatable..
>
> All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:
>
> https://gerrit.fd.io/r/#/c/3499/
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE
>
> Seem to be vpp build related, as the standalone ubuntu1604 build jobs for
> this patch are also yielding not repeatable results:
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS
>
>
> -Maciek
>
> from https://jenkins.fd.io/job/vpp-csit-verify-virl-master/
> 1841/consoleFull
> 10:52:23 make[1]: Entering directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:23 dh clean --with dkms --with systemd
> 10:52:24 dh: error: cannot read debian/changelog: No such file or directory
> 10:52:24 debian/rules:21: recipe for target 'clean' failed
> 10:52:24 make[1]: *** [clean] Error 2
> 10:52:24 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/deb'
> 10:52:24 Makefile:1159: recipe for target 'distclean' failed
> 10:52:24 make: *** [distclean] Error 2
>
> 10:59:49 collect2: error: ld returned 1 exit status
> 10:59:49 Makefile:551: recipe for target 'libjvpp_registry.la' failed
> 10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
> 10:59:49 make[5]: *** Waiting for unfinished jobs
> 11:00:00 make[5]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:445: recipe for target 'all' failed
> 11:00:00 make[4]: *** [all] Error 2
> 11:00:00 make[4]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api/java'
> 11:00:00 Makefile:377: recipe for target 'all-recursive' failed
> 11:00:00 make[3]: *** [all-recursive] Error 1
> 11:00:00 make[3]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-master/build-root/build-vpp-native/vpp-api'
> 11:00:00 Makefile:699: recipe for target 'vpp-api-build' failed
> 11:00:00 make[2]: *** [vpp-api-build] Error 2
> 11:00:00 make[2]: Leaving directory '/w/workspace/vpp-csit-verify-
> virl-ma

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Luke, Chris]

It passed the first time round; do we want to exercise it a bit before merging?

Chris

From: csit-dev-boun...@lists.fd.io [mailto:csit-dev-boun...@lists.fd.io] On 
Behalf Of Edward Warnicke
Sent: Thursday, October 20, 2016 13:01
To: Dave Wallace 
Cc: csit-...@lists.fd.io; Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at 
Cisco) ; vpp-dev@lists.fd.io
Subject: Re: [csit-dev] [vpp-dev] vpp-csit-verify-virl-master - some more build 
failures

You mean like this: https://gerrit.fd.io/r/#/c/3511/1/vpp-api/java/Makefile.am 
:)

Ed

On Thu, Oct 20, 2016 at 9:50 AM, Dave Wallace 
mailto:dwallac...@gmail.com>> wrote:
Klement,

Thanks for helping improve the java build infrastructure.

I think that you may find that the execution of the build system is very 
different on the LF cloud infrastructure then on a typical development 
platform.  IIRC, this is not the first time we've been bitten by that 
particular bug.

Here is Marek's patch which fixed this issue earlier:  
https://gerrit.fd.io/r/#/c/3131

Looking at your patch, I think this deletion may be the primary culprit in 
opening up the race condition:
-EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la
I think it would be worth pushing a patch with that dependency restored before 
reverting the entire patch.

Thanks,
-daw-


On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at 
Cisco) wrote:

It's quite possible, I've made multiple builds and rebuilds to make sure I 
didn't break anything, but I apparently did. Feel free to revert the patch and 
I'll take a look at it again. That java build stuff is a real mess...

Klement

On Oct 20, 2016 6:22 PM, Edward Warnicke 
 wrote:
This change:

https://gerrit.fd.io/r/#/c/3486/

Was touching that part of the world... *if* it is a race condition, is it 
possible that this patch got lucky, and the ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace 
mailto:dwallac...@gmail.com>> wrote:
Maciek,

This looks like a race condition in the build for JVPP.  All of the failures 
contain the following error:
09:32:35 make[5]: Entering directory 
'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
09:32:39   CCLD libjvpp_common.la
09:32:39   CCLD libjvpp_registry.la
09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target 
'libjvpp_registry.la' failed
It appears that the output of "CCLD 
libjvpp_common.la" is an input to "CCLD 
libjvpp_registry.la" and in the error case it is 
not found.

I had thought that Maros or Marek had provided a fix for this issue a couple of 
weeks ago.  When I get the chance investigate further.

Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
Hi,

Anybody with time and willingness to look at below jobs and see why they pass 
1st time and fail 2nd time,
ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:

https://gerrit.fd.io/r/#/c/3499/
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE

Seem to be vpp build related, as the standalone ubuntu1604 build jobs for this 
patch are also yielding not repeatable results:
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS


-Maciek

from https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/consoleFull
10:52:23 make[1]: Entering directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:23 dh clean --with dkms --with systemd
10:52:24 dh: error: cannot read debian/changelog: No such file or directory
10:52:24 debian/rules:21: recipe for target 'clean' failed
10:52:24 make[1]: *** [clean] Error 2
10:52:24 make[1]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/deb'
10:52:24 Makefile:1159: recipe for target 'distclean' failed
10:52:24 make: *** [distclean] Error 2

10:59:49 collect2: error: ld returned 1 exit status
10:59:49 Makefile:551: recipe for target 
'libjvpp_registry.la' failed
10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
10:59:49 make[5]: *** Waiting for unfinished jobs
11:00:00 make[5]: Leaving directory 
'/w/workspace/vpp-csit-verify-virl-master/build-root/build-vpp-native/vpp-api/java'
11:00:00 Makefile:445: recipe for target 'all' failed
11:00:00 make[4]: *** [a

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Dave Wallace]

Yes, please.  Let's run it 5 times and then I'll be willing to merge it.

Thanks,
-daw-

On 10/20/2016 02:03 PM, Luke, Chris wrote:


It passed the first time round; do we want to exercise it a bit before 
merging?


Chris

*From:*csit-dev-boun...@lists.fd.io 
[mailto:csit-dev-boun...@lists.fd.io] *On Behalf Of *Edward Warnicke

*Sent:* Thursday, October 20, 2016 13:01
*To:* Dave Wallace 
*Cc:* csit-...@lists.fd.io; Klement Sekera -X (ksekera - PANTHEON 
TECHNOLOGIES at Cisco) ; vpp-dev@lists.fd.io
*Subject:* Re: [csit-dev] [vpp-dev] vpp-csit-verify-virl-master - some 
more build failures


You mean like this: 
https://gerrit.fd.io/r/#/c/3511/1/vpp-api/java/Makefile.am :)


Ed

On Thu, Oct 20, 2016 at 9:50 AM, Dave Wallace > wrote:


Klement,

Thanks for helping improve the java build infrastructure.

I think that you may find that the execution of the build system
is very different on the LF cloud infrastructure then on a typical
development platform.  IIRC, this is not the first time we've been
bitten by that particular bug.

Here is Marek's patch which fixed this issue earlier:
https://gerrit.fd.io/r/#/c/3131 

Looking at your patch, I think this deletion may be the primary
culprit in opening up the race condition:

-EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la


I think it would be worth pushing a patch with that dependency
restored before reverting the entire patch.

Thanks,
-daw-



On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera - PANTHEON
TECHNOLOGIES at Cisco) wrote:

It's quite possible, I've made multiple builds and rebuilds to
make sure I didn't break anything, but I apparently did. Feel
free to revert the patch and I'll take a look at it again.
That java build stuff is a real mess...

Klement

On Oct 20, 2016 6:22 PM, Edward Warnicke 
 wrote:

This change:

https://gerrit.fd.io/r/#/c/3486/

Was touching that part of the world... *if* it is a race
condition, is it possible that this patch got lucky, and
the ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace
mailto:dwallac...@gmail.com>> wrote:

Maciek,

This looks like a race condition in the build for
JVPP.  All of the failures contain the following error:

09:32:35 make[5]: Entering directory

'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35 CC
jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35 CC jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35 CC
jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
09:32:39 CCLD libjvpp_common.la

09:32:39 CCLD libjvpp_registry.la

09:32:40 ar: `u' modifier ignored since `D' is the
default (see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target
'libjvpp_registry.la '
failed

It appears that the output of "CCLD libjvpp_common.la
" is an input to "CCLD
libjvpp_registry.la " and
in the error case it is not found.

I had thought that Maros or Marek had provided a fix
for this issue a couple of weeks ago.  When I get the
chance investigate further.

Thanks,
-daw-



On 10/20/2016 10:31 AM, Maciek Konstantynowicz
(mkonstan) wrote:

Hi,

Anybody with time and willingness to look at below
jobs and see why they pass 1st time and fail 2nd time,

ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL.
Related to two vpp patches:

https://gerrit.fd.io/r/#/c/3499/

https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ 
:
SUCCESS

https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ 
:
FAILURE

Seem to be vpp build related, as the standalone
ubuntu1604 build jobs for this patch are also
yielding 

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Dave Wallace]

Thanks Ed!
-daw-

On 10/20/2016 01:01 PM, Edward Warnicke wrote:
You mean like this: 
https://gerrit.fd.io/r/#/c/3511/1/vpp-api/java/Makefile.am :)


Ed

On Thu, Oct 20, 2016 at 9:50 AM, Dave Wallace > wrote:


Klement,

Thanks for helping improve the java build infrastructure.

I think that you may find that the execution of the build system
is very different on the LF cloud infrastructure then on a typical
development platform. IIRC, this is not the first time we've been
bitten by that particular bug.

Here is Marek's patch which fixed this issue earlier:
https://gerrit.fd.io/r/#/c/3131 

Looking at your patch, I think this deletion may be the primary
culprit in opening up the race condition:

-EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la


I think it would be worth pushing a patch with that dependency
restored before reverting the entire patch.

Thanks,
-daw-


On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera - PANTHEON
TECHNOLOGIES at Cisco) wrote:


It's quite possible, I've made multiple builds and rebuilds to
make sure I didn't break anything, but I apparently did. Feel
free to revert the patch and I'll take a look at it again. That
java build stuff is a real mess...

Klement


On Oct 20, 2016 6:22 PM, Edward Warnicke 
 wrote:

This change:

https://gerrit.fd.io/r/#/c/3486/


Was touching that part of the world... *if* it is a race
condition, is it possible that this patch got lucky, and the
ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace
mailto:dwallac...@gmail.com>> wrote:

Maciek,

This looks like a race condition in the build for JVPP. 
All of the failures contain the following error:


09:32:35 make[5]: Entering directory

'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35   CC
jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35   CC jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35   CC
jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
09:32:39   CCLD libjvpp_common.la

09:32:39   CCLD libjvpp_registry.la

09:32:40 ar: `u' modifier ignored since `D' is the
default (see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target
'libjvpp_registry.la ' failed

It appears that the output of "CCLD libjvpp_common.la
" is an input to "CCLD
libjvpp_registry.la " and in
the error case it is not found.

I had thought that Maros or Marek had provided a fix for
this issue a couple of weeks ago.  When I get the chance
investigate further.

Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan)
wrote:

Hi,

Anybody with time and willingness to look at below
jobs and see why they pass 1st time and fail 2nd time,
ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL.
Related to two vpp patches:

https://gerrit.fd.io/r/#/c/3499/

https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/

: SUCCESS
https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/

: FAILURE

Seem to be vpp build related, as the standalone
ubuntu1604 build jobs for this patch are also
yielding not repeatable results:
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/
 :
FAILURE
https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/
 :
SUCCESS


-Maciek

from

https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/consoleFull
  

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Edward Warnicke]

So the first run of https://gerrit.fd.io/r/#/c/3511/ succeeded, the second
failed (see:

https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/console ) which
looks like test failures unrelated to the
build failures we were seeing before.

CSIT folks, thoughts?

Ed

On Thu, Oct 20, 2016 at 11:20 AM, Dave Wallace  wrote:

> Thanks Ed!
> -daw-
>
>
> On 10/20/2016 01:01 PM, Edward Warnicke wrote:
>
> You mean like this: https://gerrit.fd.io/r/#/c/3511/1/vpp-api/java/
> Makefile.am :)
>
> Ed
>
> On Thu, Oct 20, 2016 at 9:50 AM, Dave Wallace 
> wrote:
>
>> Klement,
>>
>> Thanks for helping improve the java build infrastructure.
>>
>> I think that you may find that the execution of the build system is very
>> different on the LF cloud infrastructure then on a typical development
>> platform.  IIRC, this is not the first time we've been bitten by that
>> particular bug.
>>
>> Here is Marek's patch which fixed this issue earlier:
>> https://gerrit.fd.io/r/#/c/3131
>>
>> Looking at your patch, I think this deletion may be the primary culprit
>> in opening up the race condition:
>>
>> -EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la
>>
>> I think it would be worth pushing a patch with that dependency restored
>> before reverting the entire patch.
>>
>> Thanks,
>> -daw-
>>
>>
>> On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera - PANTHEON
>> TECHNOLOGIES at Cisco) wrote:
>>
>> It's quite possible, I've made multiple builds and rebuilds to make sure
>> I didn't break anything, but I apparently did. Feel free to revert the
>> patch and I'll take a look at it again. That java build stuff is a real
>> mess...
>>
>> Klement
>>
>> On Oct 20, 2016 6:22 PM, Edward Warnicke 
>>  wrote:
>>
>> This change:
>>
>> https://gerrit.fd.io/r/#/c/3486/
>>
>> Was touching that part of the world... *if* it is a race condition, is it
>> possible that this patch got lucky, and the ones that followed did not?
>>
>> Ed
>>
>> On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace < 
>> dwallac...@gmail.com> wrote:
>>
>> Maciek,
>>
>> This looks like a race condition in the build for JVPP.  All of the
>> failures contain the following error:
>>
>> 09:32:35 make[5]: Entering directory '/w/workspace/vpp-verify-maste
>> r-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
>> 09:32:35   CC   jvpp-common/libjvpp_common_la-jvpp_common.lo
>> 09:32:35   CC   jvpp-core/libjvpp_core_la-jvpp_core.lo
>> 09:32:35   CC   jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
>> 09:32:39   CCLD libjvpp_common.la
>> 09:32:39   CCLD libjvpp_registry.la
>> 09:32:40 ar: `u' modifier ignored since `D' is the default (see `U')
>> 09:32:40 /usr/bin/ld: cannot find -ljvpp_common
>> 09:32:40 collect2: error: ld returned 1 exit status
>> 09:32:40 Makefile:551: recipe for target 'libjvpp_registry.la' failed
>>
>> It appears that the output of "CCLD libjvpp_common.la" is an input to
>> "CCLD libjvpp_registry.la" and in the error case it is not found.
>>
>> I had thought that Maros or Marek had provided a fix for this issue a
>> couple of weeks ago.  When I get the chance investigate further.
>>
>> Thanks,
>> -daw-
>>
>>
>> On 10/20/2016 10:31 AM, Maciek Konstantynowicz (mkonstan) wrote:
>>
>> Hi,
>>
>> Anybody with time and willingness to look at below jobs and see why they
>> pass 1st time and fail 2nd time,
>> ie not repeatable..
>>
>> All running on the new ubuntu1604 VMs in VIRL. Related to two vpp patches:
>>
>> https://gerrit.fd.io/r/#/c/3499/
>> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1838/ : SUCCESS
>> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/ : FAILURE
>>
>> Seem to be vpp build related, as the standalone ubuntu1604 build jobs for
>> this patch are also yielding not repeatable results:
>> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/ : FAILURE
>> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1836/ : SUCCESS
>>
>>
>> -Maciek
>>
>> from
>> 
>> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1841/consoleFull
>> 10:52:23 make[1]: Entering directory '/w/workspace/vpp-csit-verify-
>> virl-master/build-root/deb'
>> 10:52:23 dh clean --with dkms --with systemd
>> 10:52:24 dh: error: cannot read debian/changelog: No such file or
>> directory
>> 10:52:24 debian/rules:21: recipe for target 'clean' failed
>> 10:52:24 make[1]: *** [clean] Error 2
>> 10:52:24 make[1]: Leaving directory '/w/workspace/vpp-csit-verify-
>> virl-master/build-root/deb'
>> 10:52:24 Makefile:1159: recipe for target 'distclean' failed
>> 10:52:24 make: *** [distclean] Error 2
>>
>> 10:59:49 collect2: error: ld returned 1 exit status
>> 10:59:49 Makefile:551: recipe for target 'libjvpp_registry.la' failed
>> 10:59:49 make[5]: *** [libjvpp_registry.la] Error 1
>> 10:59:49 make[5]: *** Waiting for unfinished jobs
>> 11:00:00 make[5]: Leaving directory '/w/workspace/vpp-csit-verify-
>> virl-master/build-root/bui

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Dave Wallace]

I started to +2 this, because the build failures appear to be fixed.  
Then decided not to merge it, but managed to hit the submit button 
anyways.  So it has been merged.


I'll investigate the random CSIT test failures tomorrow.

Thanks,
-daw-

On 10/20/16 3:31 PM, Edward Warnicke wrote:
So the first run of https://gerrit.fd.io/r/#/c/3511/ succeeded, the 
second failed (see:


https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/console ) 
which looks like test failures unrelated to the

build failures we were seeing before.

CSIT folks, thoughts?

Ed

On Thu, Oct 20, 2016 at 11:20 AM, Dave Wallace > wrote:


Thanks Ed!
-daw-


On 10/20/2016 01:01 PM, Edward Warnicke wrote:

You mean like this:
https://gerrit.fd.io/r/#/c/3511/1/vpp-api/java/Makefile.am
 :)

Ed

On Thu, Oct 20, 2016 at 9:50 AM, Dave Wallace
mailto:dwallac...@gmail.com>> wrote:

Klement,

Thanks for helping improve the java build infrastructure.

I think that you may find that the execution of the build
system is very different on the LF cloud infrastructure then
on a typical development platform. IIRC, this is not the
first time we've been bitten by that particular bug.

Here is Marek's patch which fixed this issue earlier:
https://gerrit.fd.io/r/#/c/3131

Looking at your patch, I think this deletion may be the
primary culprit in opening up the race condition:

-EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la


I think it would be worth pushing a patch with that
dependency restored before reverting the entire patch.

Thanks,
-daw-


On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera - PANTHEON
TECHNOLOGIES at Cisco) wrote:


It's quite possible, I've made multiple builds and rebuilds
to make sure I didn't break anything, but I apparently did.
Feel free to revert the patch and I'll take a look at it
again. That java build stuff is a real mess...

Klement


On Oct 20, 2016 6:22 PM, Edward Warnicke 
 wrote:

This change:

https://gerrit.fd.io/r/#/c/3486/


Was touching that part of the world... *if* it is a race
condition, is it possible that this patch got lucky, and
the ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace
mailto:dwallac...@gmail.com>> wrote:

Maciek,

This looks like a race condition in the build for
JVPP. All of the failures contain the following error:

09:32:35 make[5]: Entering directory

'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35 CC
jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35 CC jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35 CC
jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
09:32:39 CCLD libjvpp_common.la

09:32:39 CCLD libjvpp_registry.la

09:32:40 ar: `u' modifier ignored since `D' is
the default (see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target
'libjvpp_registry.la
' failed

It appears that the output of "CCLD
libjvpp_common.la " is an
input to "CCLD libjvpp_registry.la
" and in the error case
it is not found.

I had thought that Maros or Marek had provided a fix
for this issue a couple of weeks ago.  When I get
the chance investigate further.

Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz
(mkonstan) wrote:

Hi,

Anybody with time and willingness to look at
below jobs and see why they pass 1st time and
fail 2nd time,
ie not repeatable..

All running on the new ubuntu1604 VMs in VIRL.
Related to two vpp patches:

https://gerrit.fd.io/r/#/c/3499/

Re: [vpp-dev] [csit-dev] vpp-csit-verify-virl-master - some more build failures

[Dave Wallace]

I rebased https://jenkins.fd.io/job/vpp-csit-verify-virl-master/1855 
which had also been failing due to the jvpp build failure and the build 
has completed.  We'll see if the CSIT tests pass or not in the AM.


Thanks,
-daw-

On 10/21/16 12:01 AM, Dave Wallace wrote:
I started to +2 this, because the build failures appear to be fixed.  
Then decided not to merge it, but managed to hit the submit button 
anyways.  So it has been merged.


I'll investigate the random CSIT test failures tomorrow.

Thanks,
-daw-

On 10/20/16 3:31 PM, Edward Warnicke wrote:
So the first run of https://gerrit.fd.io/r/#/c/3511/ succeeded, the 
second failed (see:


https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/1833/console ) 
which looks like test failures unrelated to the

build failures we were seeing before.

CSIT folks, thoughts?

Ed

On Thu, Oct 20, 2016 at 11:20 AM, Dave Wallace > wrote:


Thanks Ed!
-daw-


On 10/20/2016 01:01 PM, Edward Warnicke wrote:

You mean like this:
https://gerrit.fd.io/r/#/c/3511/1/vpp-api/java/Makefile.am
 :)

Ed

On Thu, Oct 20, 2016 at 9:50 AM, Dave Wallace
mailto:dwallac...@gmail.com>> wrote:

Klement,

Thanks for helping improve the java build infrastructure.

I think that you may find that the execution of the build
system is very different on the LF cloud infrastructure then
on a typical development platform. IIRC, this is not the
first time we've been bitten by that particular bug.

Here is Marek's patch which fixed this issue earlier:
https://gerrit.fd.io/r/#/c/3131

Looking at your patch, I think this deletion may be the
primary culprit in opening up the race condition:

-EXTRA_libjvpp_registry_la_DEPENDENCIES=libjvpp_common.la


I think it would be worth pushing a patch with that
dependency restored before reverting the entire patch.

Thanks,
-daw-


On 10/20/2016 12:24 PM, Klement Sekera -X (ksekera -
PANTHEON TECHNOLOGIES at Cisco) wrote:


It's quite possible, I've made multiple builds and rebuilds
to make sure I didn't break anything, but I apparently did.
Feel free to revert the patch and I'll take a look at it
again. That java build stuff is a real mess...

Klement


On Oct 20, 2016 6:22 PM, Edward Warnicke
  wrote:

This change:

https://gerrit.fd.io/r/#/c/3486/


Was touching that part of the world... *if* it is a
race condition, is it possible that this patch got
lucky, and the ones that followed did not?

Ed

On Thu, Oct 20, 2016 at 9:15 AM, Dave Wallace
mailto:dwallac...@gmail.com>> wrote:

Maciek,

This looks like a race condition in the build for
JVPP.  All of the failures contain the following error:

09:32:35 make[5]: Entering directory

'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp-api/java'
09:32:35 CC
jvpp-common/libjvpp_common_la-jvpp_common.lo
09:32:35 CC jvpp-core/libjvpp_core_la-jvpp_core.lo
09:32:35 CC
jvpp-registry/libjvpp_registry_la-jvpp_registry.lo
09:32:39 CCLD libjvpp_common.la

09:32:39 CCLD libjvpp_registry.la

09:32:40 ar: `u' modifier ignored since `D' is
the default (see `U')
09:32:40 /usr/bin/ld: cannot find -ljvpp_common
09:32:40 collect2: error: ld returned 1 exit status
09:32:40 Makefile:551: recipe for target
'libjvpp_registry.la
' failed

It appears that the output of "CCLD
libjvpp_common.la " is an
input to "CCLD libjvpp_registry.la
" and in the error case
it is not found.

I had thought that Maros or Marek had provided a
fix for this issue a couple of weeks ago.  When I
get the chance investigate further.

Thanks,
-daw-


On 10/20/2016 10:31 AM, Maciek Konstantynowicz
(mkonstan) wrote:

Hi,

Anybody with time and willingness to look at
below jobs and see why they pass 1st time and
fail 2nd