Re: [vpp-dev] Test failing

rds, Jan -Original Message- From: Marco Varlese [mailto:marco.varl...@suse.com] Sent: Wednesday, October 11, 2017 10:49 To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <jgel...@cisco.com>; Ed Kern (ejk) <e...@cisco.com> Cc: vpp-dev@lists.fd.io; csit-...@list

Re: [vpp-dev] Test failing

, October 09, 2017 09:04 To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <jgel...@cisco.com>; Ed Kern (ejk) <e...@cisco.com> Cc: vpp-dev@lists.fd.io; csit-...@lists.fd.io Subject: Re: [vpp-dev] Test failing Please, take a look at this logs: https://jenkins.fd.io/job/vpp-csit

Re: [vpp-dev] Test failing

+ csit-dev Hello Marco, The mentioned test case is not responsible for -1 in verification as this test case is marked as non-critical. Please, provide links to affected jobs to find which TC is really failing. Thanks, Jan -Original Message- From: vpp-dev-boun...@lists.fd.io

Re: [vpp-dev] 17.07 CIST Failures : FW: Change in vpp[stable/1704]: DHCP complete event includes the subnet mask

Hello Neale, If I am correct, it is necessary to move/copy vagrant directory from build-root/vagrant/ to extras/vagrant/ in stable/1704 branch. Probably it should be done for all stable vpp branches. Regards, Jan -Original Message- From: vpp-dev-boun...@lists.fd.io

Re: [vpp-dev] [FD.io Helpdesk #41921] connection interruptiones between jenkins executor and VIRL servers

30.52.0/24, > 10.30.53.0/24 and also for 10.30.54.0/24 (that is planned for vilr3 > when it will be upgraded)? > > Thank you very much. > > Regards, > Jan > > -Original Message- > From: Vanessa Valderrama via RT [mailto:fdio- > helpd...@rt.linuxfoundatio

Re: [vpp-dev] [FD.io Helpdesk #41921] connection interruptiones between jenkins executor and VIRL servers

> Unfortunately we are still having issues with ssh connection > > > timeouts during tests on virl. Could you, please, have a look on > > > it? > > > > > > Thank you very much. > > > Regards, > > > Jan > > > > > > -Original Message- >

Re: [vpp-dev] [FD.io Helpdesk #41921] connection interruptiones between jenkins executor and VIRL servers

, June 14, 2017 15:45 To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <jgel...@cisco.com> Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io Subject: [FD.io Helpdesk #41921] connection interruptiones between jenkins executor and VIRL servers Jan: On my side I currently don't s

[vpp-dev] FW: [FD.io Helpdesk #41921] AutoReply: connection interruptiones between jenkins executor and VIRL servers

FYI -Original Message- From: FD.io Helpdesk via RT [mailto:fdio-helpd...@rt.linuxfoundation.org] Sent: Wednesday, June 14, 2017 14:13 To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <jgel...@cisco.com> Subject: [FD.io Helpdesk #41921] AutoReply: connection interrup

[vpp-dev] connection interruptiones between jenkins executor and VIRL servers

Dear held...@fd.io We are observing connection issues between Jenkins executors and VIRL servers that leads to failures of verify jobs (https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-virl-master/,

[vpp-dev] VPP unit test failures on Ubuntu16.04

Hello, We observed vpp unit test failures during verification of patch https://gerrit.fd.io/r/#/c/7015/ where the csit operational branch has been updated - it has no impact to vpp unit test execution. Failures have occurred on containerised PoC builds as well as on official fd.io JJB builds:

Re: [vpp-dev] [FD.io Helpdesk #41298] Jobs are not triggered from gerrit

Hello Anton, Do you know, please, what was the root cause and how we can avoid such situation in the future? Thanks, Jan -Original Message- From: Anton Baranov via RT [mailto:fdio-helpd...@rt.linuxfoundation.org] Sent: Wednesday, May 31, 2017 16:03 To: Jan Gelety -X (jgelety

Re: [vpp-dev] [csit-dev] VIRL build failure

Hello Ole, The problem is that requested CSIT operational branch (oper-170313) is not available anymore (it has already been deleted). I created patch to use CSIT release branch in vpp stable/1704: https://gerrit.fd.io/r/#/c/6818/ When this patch is merged, please, rebase your patch to use

Re: [vpp-dev] Fwd: Change in vpp[master]: make test: python interpreter customization

Hello Klement, Unfortunately, the VIRL simulation has not been started successfully. I did some cleaning action on VIRL servers and forced recheck in your commit. I will keep my eyes on the started virl verify job https://jenkins.fd.io/job/vpp-csit-verify-virl-master/4910/ Thanks, Jan PS:

[vpp-dev] Centos OS reported on ubuntu jenkins executor

Hello Vanessa, We observed strange behaviour during one of vpp-csit-verify-virl-master jobs - the job has been started on ubuntu1604 executor: Building remotely on ubuntu1604-basebuild-4c-4g-5409 (ubuntu1604-basebuild-4c-4g) in workspace /w/workspace/vpp-csit-verify-virl-master However

[vpp-dev] installation issue of release rpm packages from Nexus on centos7 system

Hello vpp developers, We are facing following issue during installation of release vpp rpm packages downloaded from Nexus on VIRL: DEBUG: Running with topology double-ring-nested.centos7 DEBUG: Checking if file /tmp/vpp-17.04-rc0~359_g077d6ae~b1983.x86_64.rpm exists DEBUG: Checking if file

Re: [vpp-dev] vpp make test is not working

Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco) <ksek...@cisco.com> Cc: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <jgel...@cisco.com>; vpp-dev@lists.fd.io Subject: Re: [vpp-dev] vpp make test is not working Jan, Could you try with master again? For reference, the p

Re: [vpp-dev] [csit-dev] reset_fib API issue in case of IPv6 FIB

Hello Neale, Thank you very much for the fix and info. I will have a look on test cases. Regards, Jan From: Neale Ranns (nranns) Sent: Monday, February 20, 2017 18:35 To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <jgel...@cisco.com>; vpp-dev@lists.fd.io Cc: csit-...@lists

Re: [vpp-dev] [csit-dev] reset_fib API issue in case of IPv6 FIB

Hello Neale, It’s in review: https://gerrit.fd.io/r/#/c/4433/ Affected tests are skipped there at the moment. Regards, Jan From: Neale Ranns (nranns) Sent: Monday, February 20, 2017 12:49 To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <jgel...@cisco.com>; vpp-dev@lists.fd

[vpp-dev] Jenkins jobs are not started

Hello, No new Jenkins job was not started in the last our and the build queue is increasing. Could you, please, have a look on it? Thanks, Jan ___ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Fix for vpp-verify-master-ubuntu1604 build failures

Wallace [mailto:dwallac...@gmail.com] Sent: Thursday, February 02, 2017 06:14 To: vpp-dev <vpp-dev@lists.fd.io>; csit-...@lists.fd.io; Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco) <jgel...@cisco.com> Subject: Re: Fix for vpp-verify-master-ubuntu1604 build failures J

[vpp-dev] CSIT for 17.01 release

Hello, I had a look on current status of CSIT related jobs. When the vpp stable/17.01 branch is created then Jenkins jobs vpp-csit-verify-virl-1701 and vpp-csit-verify-hw-perf-1701-{type} (already created) will use CSIT tests from CSIT master branch. When the CSIT release branch rls1701 and

[vpp-dev] VIRL servers back in operation

Hello, Issue with VIRL servers is fixed (and small correction that should avoid such issue in the future applied) and vpp-csit-verify job can be run now. Recheck was applied on following affected patches: https://gerrit.fd.io/r/#/c/4267/1 https://gerrit.fd.io/r/#/c/4197/2

[vpp-dev] possible network issues?

Hello, We are experiencing occasional issues with access to https://gerrit.fd.io/r/csit from Jenkins since last Friday. https://jenkins.fd.io/view/vpp/job/vpp-csit-verify-virl-master/2193/console : 10:55:38 + echo '***'

[vpp-dev] L2BD test failing during MAC learning - VPP-518

Dear vpp developers, We found out that VPP crashes during the MAC learning when run L2BD test that is part of the test framework. The issue is reported here: https://jira.fd.io/browse/VPP-518 Regards, Jan ___ vpp-dev mailing list vpp-dev@lists.fd.io

[vpp-dev] Workaround for VPP restart issue on VIRL

Dear VPP developers, As it was discussed and proposed on the VPP weekly call this Tuesday we implemented workaround (as a short-term solution until we find and fix the root cause) to try another restart of VPP when it failed (max. three tries are allowed). This workaround has been