[vpp-dev] [FD.io Helpdesk #75515] fd.io vpp jenkins queue stuck

[Vanessa Valderrama via RT]

This issue is resolved. We will send an email to the community detailing the 
cause for the issues this morning.

Thank you,
Vanessa

On Tue May 14 10:48:27 2019, dbarach wrote:
> "executor starvation"... Something is seriously wrong...
> 
> Thanks... Dave
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13082): https://lists.fd.io/g/vpp-dev/message/13082
Mute This Topic: https://lists.fd.io/mt/31665116/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #68790] gerrit - unable to login

[Vanessa Valderrama via RT]

We are aware of users experiencing authentication issues when trying to
log into gerrit.fd.io. We have identified the cause and are working to
resolve it as quickly as possible. I have requested an ETA but have not
been provided one at this time.

Thank you,
Vanessa



On Tue Feb 19 09:57:19 2019, dmar...@me.com wrote:
> 
> Folks,
> 
> Myself and at least one more person is not able to login to
> gerrit.fd.io .
> 
> Error message is:
> 
> Authentication unavailable at this time.
> 
> Please take a a look,



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12285): https://lists.fd.io/g/vpp-dev/message/12285
Mute This Topic: https://lists.fd.io/mt/29918333/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #68790] gerrit - unable to login

[Vanessa Valderrama via RT]

The issue should be resolved now.

On Tue Feb 19 10:11:16 2019, valderrv wrote:
> We are aware of users experiencing authentication issues when trying to
> log into gerrit.fd.io. We have identified the cause and are working to
> resolve it as quickly as possible. I have requested an ETA but have not
> been provided one at this time.
> 
> Thank you,
> Vanessa
> 
> 
> 
> On Tue Feb 19 09:57:19 2019, dmar...@me.com wrote:
> > 
> > Folks,
> > 
> > Myself and at least one more person is not able to login to
> > gerrit.fd.io .
> > 
> > Error message is:
> > 
> > Authentication unavailable at this time.
> > 
> > Please take a a look,
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#12284): https://lists.fd.io/g/vpp-dev/message/12284
Mute This Topic: https://lists.fd.io/mt/29918319/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #63805] FD.io compute infra down -

[Vanessa Valderrama via RT]

The hardware has been replace and services have been restored. Thank you for 
your patience. Please open an RT ticket is you are experiencing any issues.  
helpd...@fd.io
Thank you,
Vanessa

On Fri Nov 16 10:26:44 2018, valderrv wrote:
> Apparently, we have an issue with an upstream network provider which
> is impacting some of our CI services.
> 
> We're working on getting more information including an ETA if
> possible. I'll send a notification to the community as well.
> 
> Thank you,
> Vanessa
> 
> 
> On Fri Nov 16 10:18:59 2018, valderrv wrote:
> > Maciek,
> >
> > We're looking into this now.
> >
> > On Fri Nov 16 09:02:19 2018, mackonstan wrote:
> > > Nexus(?) backend to nginx is reporting down.
> > > Resolution time?
> > >
> > > Cheers,
> > > -Maciek
> > >
> > > [cid:876751CF-C733-46B9-9A07-8298C0A0A0C8@cisco.com]
> >
> >



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11295): https://lists.fd.io/g/vpp-dev/message/11295
Mute This Topic: https://lists.fd.io/mt/28171040/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #63805] FD.io compute infra down -

[Vanessa Valderrama via RT]

Maciek,

We're looking into this now. 

On Fri Nov 16 09:02:19 2018, mackonstan wrote:
> Nexus(?) backend to nginx is reporting down.
> Resolution time?
> 
> Cheers,
> -Maciek
> 
> [cid:876751CF-C733-46B9-9A07-8298C0A0A0C8@cisco.com]



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11292): https://lists.fd.io/g/vpp-dev/message/11292
Mute This Topic: https://lists.fd.io/mt/28168082/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #63805] FD.io compute infra down -

[Vanessa Valderrama via RT]

Apparently, we have an issue with an upstream network provider which is 
impacting some of our CI services.

We're working on getting more information including an ETA if possible. I'll 
send a notification to the community as well.

Thank you,
Vanessa


On Fri Nov 16 10:18:59 2018, valderrv wrote:
> Maciek,
> 
> We're looking into this now. 
> 
> On Fri Nov 16 09:02:19 2018, mackonstan wrote:
> > Nexus(?) backend to nginx is reporting down.
> > Resolution time?
> > 
> > Cheers,
> > -Maciek
> > 
> > [cid:876751CF-C733-46B9-9A07-8298C0A0A0C8@cisco.com]
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11293): https://lists.fd.io/g/vpp-dev/message/11293
Mute This Topic: https://lists.fd.io/mt/28168083/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #62777] All VPP builds are currently failing

[Vanessa Valderrama via RT]

The patch was tested on the sandbox and merged but because ci-management 
verify/merge jobs weren't running successfully the patch didn't update the jobs.

A patch was merged to resolve the issue with the ci-management verify/merge 
jobs.

I've run recheck on all VPP jobs that were unstable are passing now.

Thank you,
Vanessa

On Fri Oct 26 17:37:38 2018, dmar...@me.com wrote:
> 
> Looks like it is not resolved. I just rebased or rechecked dozen of patches,
> and they are failing again with unstable error
> 
> i..e.
> 
> https://gerrit.fd.io/r/#/c/15549/ 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11008): https://lists.fd.io/g/vpp-dev/message/11008
Mute This Topic: https://lists.fd.io/mt/27742023/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #62777] All VPP builds are currently failing

[Vanessa Valderrama via RT]

The issue has been resolved.  The root cause was a change to the 
global-macros.yaml file postbuildscript.  This doesn't work on the VPP 
containers because it uses the lf-infra-ship-logs builder which can't run on 
the VPP containers at this time.

We didn't anticipate this being an issue prior to merging the change if we did 
I would have made sure the community was notified in advance.  I apologize for 
the inconvenience. I'll be working closely with Ed Kern before any other 
changes in preparation for global-jjb are merged.

Thank you,
Vanessa

 

On Fri Oct 26 06:00:05 2018, mvarl...@suse.de wrote:
> All VPP builds are currently failing.
> 
> Reported error in gerrit is "UNSTABLE"
> 
> In the logs I can see this:
> 
> 11:44:47 [vpp-checkstyle-verify-master] $ /bin/bash -l
> /tmp/jenkins5258297763900395189.sh
> 11:44:47 mesg: ttyname failed: Inappropriate ioctl for device
> 
> 
> Cheers,



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#11002): https://lists.fd.io/g/vpp-dev/message/11002
Mute This Topic: https://lists.fd.io/mt/27742023/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP artifacts

[Vanessa Valderrama via RT]

Ed developed a script that will allow us to keep/remove artifacts based on the 
number of days. So we will remove artifacts older than 30 days.  Please let me 
know if this meets your requirements.

Thank you,
Vanessa


On Fri Aug 10 09:14:10 2018, jgel...@cisco.com wrote:
> 
> Hello,
> 
> Could you, please, let us know if the solution proposed by Peter below
> is possible to implement
> or we need to start thinking about another (non-optimal) solution,
> e.g.
> 
> - compile vpp artefacts for every csit-vpp-functional job (time and
> resource wasting)
> 
> - copy vpp artefacts needed for csit-vpp-functional jobs to one of
> VIRL servers and use nfs/rsync/apache2 (just temporary solution as
> VIRL servers are planned to be re-used when CSIT VIRL tests migration
> to VPP_path and VPP_device tests is finished)
> 
> - copy vpp artefacts needed for csit-vpp-functional jobs to another
> location on Nexus that is used to store csit reports (here we would
> need solution for deleting obsolete artefacts)
> 
> Thanks,
> Jan
> 
> Jan Gelety
> Engineer - Software
> Cisco Systems, Inc.
> 
> -Original Message-
> From: csit-...@lists.fd.io  On Behalf Of Peter
> Mikus via Lists.Fd.Io
> Sent: Wednesday, August 8, 2018 5:29 PM
> To: fdio-helpd...@rt.linuxfoundation.org
> Cc: csit-...@lists.fd.io
> Subject: Re: [csit-dev] [FD.io Helpdesk #56625] Nexus
> fd.io.master.centos7 VPP artifacts
> 
> Hello,
> 
> We are creating branches on weekly basis and CSIT being verified in
> weekly job. So the question is if there is option to set "date" or
> "number" when limiting repo.
> 
> Counting the cadence of up to 10 merges per day (artifacts posted on
> Nexus) then means that safe value is around 100-120 artifacts.
> This I am talking about master branch of VPP. Stable branches we
> should be ok with just 10-15 artifacts.
> 
> Peter Mikus
> Engineer – Software
> Cisco Systems Limited
> 
> -Original Message-
> From: Vanessa Valderrama via RT [mailto:fdio-
> helpd...@rt.linuxfoundation.org]
> Sent: Wednesday, August 08, 2018 5:22 PM
> To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco)
> 
> Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp-
> d...@lists.fd.io
> Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP
> artifacts
> 
> Peter,
> 
> How many artifacts do you need us to retain for your testing?
> 
> Thank you,
> Vanessa
> 
> 
> On Mon Aug 06 04:53:29 2018, pmi...@cisco.com wrote:
> > Hello Vanessa,
> >
> > For CSIT it is not about release or not. We would need to increase
> > cadence on our weekly jobs to daily. Currently CSIT jobs are all
> > failing as VPP has more than 10-15 artifacts in week.
> > Our defined stable versions of VPP (updated once a week) are not in
> > repo anymore or are obsoleting faster than we are updating. This is
> > impacting everything.
> >
> > Right now we are *blocked* and we need to work new solution do adopt.
> >
> > One of the option is that we will have to start building VPP from
> > scratch for every job as we cannot use artifacts anymore. This will
> > cause huge overhead on infrastructure and execution times will extend
> > as nexus acted as optimization for us.
> > Right now Nexus is not an option for us anymore. This also means that
> > Nexus artifacts will not be tested by CSIT.
> >
> > Peter Mikus
> > Engineer – Software
> > Cisco Systems Limited
> >
> > -Original Message-
> >   From: Vanessa Valderrama via RT [mailto:fdio-
> > helpd...@rt.linuxfoundation.org]
> > Sent: Tuesday, July 31, 2018 8:16 PM
> >  To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco)
> > 
> >  Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp-
> > d...@lists.fd.io
> >  Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP
> > artifacts
> >
> > Peter,
> >
> > We need to make a decision on the number of artifacts to keep. I'd
> > like to propose the following
> >
> > previous release repos - 10 packages per subproject master - 10 to 15
> > packages per subproject
> >
> > Thank you,
> > Vanessa
> >
> > On Tue Jun 05 00:51:02 2018, pmi...@cisco.com wrote:
> > > Hello Vanessa,
> > >
> > > Thank you for an explanation. Indeed this will impact certain
> > > things
> > > that are planned like "automatic bisecting" (downloading and
> > > testing
> > > range of artifacts). Let me analyze current situation with CSIT
> > > team
> > > and get back to you.

[vpp-dev] [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP artifacts

[Vanessa Valderrama via RT]

Peter,

How many artifacts do you need us to retain for your testing?

Thank you,
Vanessa


On Mon Aug 06 04:53:29 2018, pmi...@cisco.com wrote:
> Hello Vanessa,
> 
> For CSIT it is not about release or not. We would need to increase
> cadence on our weekly jobs to daily. Currently CSIT jobs are all
> failing as VPP has more than 10-15 artifacts in week.
> Our defined stable versions of VPP (updated once a week) are not in
> repo anymore or are obsoleting faster than we are updating. This is
> impacting everything.
> 
> Right now we are *blocked* and we need to work new solution do adopt.
> 
> One of the option is that we will have to start building VPP from
> scratch for every job as we cannot use artifacts anymore. This will
> cause huge overhead on infrastructure and execution times will extend
> as nexus acted as optimization for us.
> Right now Nexus is not an option for us anymore. This also means that
> Nexus artifacts will not be tested by CSIT.
> 
> Peter Mikus
> Engineer – Software
> Cisco Systems Limited
> 
> -Original Message-
>  From: Vanessa Valderrama via RT [mailto:fdio-
> helpd...@rt.linuxfoundation.org]
> Sent: Tuesday, July 31, 2018 8:16 PM
> To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco)
> 
> Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp-
> d...@lists.fd.io
> Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP
> artifacts
> 
> Peter,
> 
> We need to make a decision on the number of artifacts to keep. I'd
> like to propose the following
> 
> previous release repos - 10 packages per subproject master - 10 to 15
> packages per subproject
> 
> Thank you,
> Vanessa
> 
> On Tue Jun 05 00:51:02 2018, pmi...@cisco.com wrote:
> > Hello Vanessa,
> >
> > Thank you for an explanation. Indeed this will impact certain things
> > that are planned like "automatic bisecting" (downloading and testing
> > range of artifacts). Let me analyze current situation with CSIT team
> > and get back to you.
> >
> > Peter Mikus
> > Engineer – Software
> > Cisco Systems Limited
> >
> >
> > -Original Message-
> >   From: Vanessa Valderrama via RT [mailto:fdio-
> > helpd...@rt.linuxfoundation.org]
> > Sent: Monday, June 04, 2018 9:47 PM
> >  To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco)
> > 
> >  Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp-
> > d...@lists.fd.io
> >  Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP
> > artifacts
> >
> > Peter,
> >
> > The fd.io.master.centos7 repo had to be cleaned up significantly to
> > eliminate Jenkins build timeout errors.  This was discussed in the
> > TSC. Going forward we'll only be keeping an average of 10 of the
> > current release candidate artifacts in the repository.  Please let me
> > know if this retention policy causes an issue for you.
> >
> > We do need to clean up the other repositories as well.  Please let me
> > know if you'd like to discuss retention policies.  I'll hold off on
> > cleaning up other repositories for now.
> >
> > Thank you,
> > Vanessa
> >
> > On Wed May 30 10:20:21 2018, pmi...@cisco.com wrote:
> > > Hello,
> > >
> > > I have recently spotted that CentOS repo got reduced and old
> > > binaries are missing [1].
> > >
> > > Is this expected?
> > > Will the similar be done for Ubuntu repos?
> > >
> > > Was this announced somewhere?
> > >
> > > Thank you.
> > >
> > > [1]
> > > https://nexus.fd.io/content/repositories/fd.io.master.centos7/io/fd/
> > > vp
> > > p/vpp/
> > >
> > > Peter Mikus
> > > Engineer - Software
> > > Cisco Systems Limited
> > > [http://www.cisco.com/web/europe/images/email/signature/logo05.jpg]
> > > Think before you print.
> > >This email may contain confidential and privileged material for
> > > the
> > >   sole use of the intended recipient. Any review, use, distribution
> > > or
> > >   disclosure by others is strictly prohibited. If you are not the
> > >   intended recipient (or authorized to receive for the recipient),
> > >  please contact the sender by reply email and delete all copies of
> > > this message.
> > > For corporate legal information go to:
> > > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> >
> >
> >
> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#10068): https://lists.fd.io/g/vpp-dev/message/10068
Mute This Topic: https://lists.fd.io/mt/21275985/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP artifacts

[Vanessa Valderrama via RT]

Peter,

We need to make a decision on the number of artifacts to keep. I'd like to 
propose the following

previous release repos - 10 packages per subproject
master - 10 to 15 packages per subproject

Thank you,
Vanessa

On Tue Jun 05 00:51:02 2018, pmi...@cisco.com wrote:
> Hello Vanessa,
> 
> Thank you for an explanation. Indeed this will impact certain things
> that are planned like "automatic bisecting" (downloading and testing
> range of artifacts). Let me analyze current situation with CSIT team
> and get back to you.
> 
> Peter Mikus
> Engineer – Software
> Cisco Systems Limited
> 
> 
> -Original Message-
>  From: Vanessa Valderrama via RT [mailto:fdio-
> helpd...@rt.linuxfoundation.org]
> Sent: Monday, June 04, 2018 9:47 PM
> To: Peter Mikus -X (pmikus - PANTHEON TECHNOLOGIES at Cisco)
> 
> Cc: csit-...@lists.fd.io; infra-steer...@lists.fd.io; vpp-
> d...@lists.fd.io
> Subject: [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP
> artifacts
> 
> Peter,
> 
> The fd.io.master.centos7 repo had to be cleaned up significantly to
> eliminate Jenkins build timeout errors.  This was discussed in the
> TSC. Going forward we'll only be keeping an average of 10 of the
> current release candidate artifacts in the repository.  Please let me
> know if this retention policy causes an issue for you.
> 
> We do need to clean up the other repositories as well.  Please let me
> know if you'd like to discuss retention policies.  I'll hold off on
> cleaning up other repositories for now.
> 
> Thank you,
> Vanessa
> 
> On Wed May 30 10:20:21 2018, pmi...@cisco.com wrote:
> > Hello,
> >
> > I have recently spotted that CentOS repo got reduced and old binaries
> > are missing [1].
> >
> > Is this expected?
> > Will the similar be done for Ubuntu repos?
> >
> > Was this announced somewhere?
> >
> > Thank you.
> >
> > [1]
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/io/fd/vp
> > p/vpp/
> >
> > Peter Mikus
> > Engineer - Software
> > Cisco Systems Limited
> > [http://www.cisco.com/web/europe/images/email/signature/logo05.jpg]
> > Think before you print.
> >  This email may contain confidential and privileged material for the
> >  sole use of the intended recipient. Any review, use, distribution or
> >  disclosure by others is strictly prohibited. If you are not the
> >  intended recipient (or authorized to receive for the recipient),
> >  please contact the sender by reply email and delete all copies of
> > this
> > message.
> > For corporate legal information go to:
> > http://www.cisco.com/web/about/doing_business/legal/cri/index.html
> 
> 
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#9992): https://lists.fd.io/g/vpp-dev/message/9992
Mute This Topic: https://lists.fd.io/mt/21275985/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #56625] Nexus fd.io.master.centos7 VPP artifacts

[Vanessa Valderrama via RT]

Peter,

The fd.io.master.centos7 repo had to be cleaned up significantly to eliminate 
Jenkins build timeout errors.  This was discussed in the TSC. Going forward 
we'll only be keeping an average of 10 of the current release candidate 
artifacts in the repository.  Please let me know if this retention policy 
causes an issue for you.

We do need to clean up the other repositories as well.  Please let me know if 
you'd like to discuss retention policies.  I'll hold off on cleaning up other 
repositories for now.

Thank you,
Vanessa

On Wed May 30 10:20:21 2018, pmi...@cisco.com wrote:
> Hello,
> 
> I have recently spotted that CentOS repo got reduced and old binaries
> are missing [1].
> 
> Is this expected?
> Will the similar be done for Ubuntu repos?
> 
> Was this announced somewhere?
> 
> Thank you.
> 
> [1]
> https://nexus.fd.io/content/repositories/fd.io.master.centos7/io/fd/vpp/vpp/
> 
> Peter Mikus
> Engineer - Software
> Cisco Systems Limited
> [http://www.cisco.com/web/europe/images/email/signature/logo05.jpg]
> Think before you print.
> This email may contain confidential and privileged material for the
> sole use of the intended recipient. Any review, use, distribution or
> disclosure by others is strictly prohibited. If you are not the
> intended recipient (or authorized to receive for the recipient),
> please contact the sender by reply email and delete all copies of this
> message.
> For corporate legal information go to:
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html




-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9521): https://lists.fd.io/g/vpp-dev/message/9521
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/21275985
Mute This Topic: https://lists.fd.io/mt/21275985/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
Email sent to: arch...@mail-archive.com
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #56282] git.fd.io not updating

[Vanessa Valderrama via RT]

Anton actually resolved this issue for us.

On Tue May 22 14:56:02 2018, fcoras.li...@gmail.com wrote:
> It is! Thank you, Vanessa!
> 
> Florin
> 
> > On May 22, 2018, at 11:41 AM, Vanessa Valderrama via RT  > helpd...@rt.linuxfoundation.org> wrote:
> >
> > This issue should be resolved.
> >
> > Thank you,
> > Vanessa
> >
> > On Tue May 22 02:59:02 2018, mvarl...@suse.de wrote:
> >> Roughly a week ago, I noticed there was a DNS/IP change when cloning
> >> a
> >> new VPP
> >> repo... I wonder if what I saw is somehow connected to this issue.
> >> On Mon, 2018-05-21 at 16:34 -0700, Florin Coras wrote:
> >>> Hi,
> >>> It would seem that git.fd.io [1] thinks that we last committed a
> >>> patch to vpp
> >>> almost 1 week ago. Any idea what might’ve triggered this?
> >>> Thanks, Florin
> >>> [1] https://git.fd.io/vpp/log/
> >>>
> >>> 
> >>>
> >
> >
> >




-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9359): https://lists.fd.io/g/vpp-dev/message/9359
View All Messages In Topic (3): https://lists.fd.io/g/vpp-dev/topic/19743812
Mute This Topic: https://lists.fd.io/mt/19743812/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #56282] git.fd.io not updating

[Vanessa Valderrama via RT]

This issue should be resolved.

Thank you,
Vanessa

On Tue May 22 02:59:02 2018, mvarl...@suse.de wrote:
> Roughly a week ago, I noticed there was a DNS/IP change when cloning a
> new VPP
> repo... I wonder if what I saw is somehow connected to this issue.
> On Mon, 2018-05-21 at 16:34 -0700, Florin Coras wrote:
> > Hi,
> > It would seem that git.fd.io [1] thinks that we last committed a
> > patch to vpp
> > almost 1 week ago. Any idea what might’ve triggered this?
> > Thanks, Florin
> > [1] https://git.fd.io/vpp/log/
> >
> > 
> >




-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#9358): https://lists.fd.io/g/vpp-dev/message/9358
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/19743865
Mute This Topic: https://lists.fd.io/mt/19743865/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #53548] issues with opensuse and centos verify job for stable/1801

[Vanessa Valderrama via RT]

Matus,

I believe the vpp-dpdk-devel package error can be resolved by doing a rebase.

Thank you,
Vanessa

On Tue Mar 13 11:13:13 2018, matfa...@cisco.com wrote:
> Hi,
> 
> I see issues with opensuse and centos verify jobs for stable/1801
> branch.
> The error is same for both jobs:
> 11:39:26 
> 11:39:27 package vpp-dpdk-devel-18.02-vpp1.x86_64 (which is newer
> than vpp-dpdk-devel-17.11-vpp1.x86_64) is already installed
> 11:39:27 make[1]: *** [install-rpm] Error 2
> 11:39:27 make[1]: Leaving directory `/w/workspace/vpp-verify-1801-
> centos7/dpdk'
> 11:39:27 make: *** [dpdk-install-dev] Error 2
> 11:39:27 Build step 'Execute shell' marked build as failure
> 
> See following patches:
> https://gerrit.fd.io/r/#/c/11079/
> https://gerrit.fd.io/r/#/c/11058/
> https://gerrit.fd.io/r/#/c/11056/
> https://gerrit.fd.io/r/#/c/11059/
> https://gerrit.fd.io/r/#/c/11060/
> 
> Regards,
> Matus Fabian




-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8645): https://lists.fd.io/g/vpp-dev/message/8645
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/16062993
Mute This Topic: https://lists.fd.io/mt/16062993/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #52672] Issues with CentOS jenkins job

[Vanessa Valderrama via RT]

Marco,

The error is due to trying to install a package older than the one already 
installed.  It appears this issue has been resolved as the centos7 builds are 
no longer failing due to this issue.

Thank you,
Vanessa



On Tue Feb 20 07:09:27 2018, mvarl...@suse.de wrote:
> Hi,
> 
> This morning I see another issue affecting the CentOS jenkins job. All
> others
> are fine.
> 
> The error marking the build as "Verified-1" can be found below.
> 
> 10:59:17 make[2]: Leaving directory `/w/workspace/vpp-verify-master-
> centos7/dpdk'
> 10:59:17 sudo rpm -Uih vpp-dpdk-devel-17.11-vpp1.x86_64.rpm
> 10:59:17 
> 10:59:17package vpp-dpdk-devel-18.02-vpp1.x86_64 (which is
> newer than
> vpp-dpdk-devel-17.11-vpp1.x86_64) is already installed
> 10:59:17 make[1]: *** [install-rpm] Error 2
> 10:59:17 make[1]: Leaving directory `/w/workspace/vpp-verify-master-
> centos7/dpdk'
> 10:59:17 make: *** [dpdk-install-dev] Error 2
> 10:59:17 Build step 'Execute shell' marked build as failure
> 10:59:17 $ ssh-agent -k
> 
> Full logs are here:
> https://jenkins.fd.io/job/vpp-verify-master-centos7/9519/consoleFull
> 
> 
> Cheers,




-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8288): https://lists.fd.io/g/vpp-dev/message/8288
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/12333790
Mute This Topic: https://lists.fd.io/mt/12333790/21656
New Topic: https://lists.fd.io/g/vpp-dev/post

Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656
Group Home: https://lists.fd.io/g/vpp-dev
Contact Group Owner: vpp-dev+ow...@lists.fd.io
Terms of Service: https://lists.fd.io/static/tos
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] [FD.io Helpdesk #48422] Gerrit and git out of sync?

[Vanessa Valderrama via RT]

Can you point me to specific changes that aren't in sync.  The branches appear 
to be in sync.


On Mon Nov 20 21:45:46 2017, fcoras.li...@gmail.com wrote:
> Hi,
> 
> It seems that git master head points at a gerrit patch merged 10h
> ago[1]. There have been several recent merges and none show up [2].
> Any idea what may be causing this?
> 
> Thanks,
> Florin
> 
> [1] https://git.fd.io/vpp/log/ 
> [2] https://gerrit.fd.io/r/#/q/project:vpp
> 




___
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

[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
> > > <lorand.jakab+f...@gmail.com>
> > > 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 <hagb...@gmail.com>
> > > > 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
> > > >> <chris_l...@comcast.com>
> > > >> 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):
> > > >>> F

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

[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
> > > <lorand.jakab+f...@gmail.com>
> > > 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 <hagb...@gmail.com>
> > > > 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
> > > >> <chris_l...@comcast.com>
> > > >> 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
&

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

[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

[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 #47101] No joy: ping6 gerrit.fd.io

[Vanessa Valderrama via RT]

Anton and I worked with Dave to troubleshoot this issue.  It appears to be 
isolated.  He's going to contact Cisco IT and approved this ticket being closed.

On Thu Oct 26 13:45:06 2017, valderrv wrote:
> When Dave returns from his conference we'll scheudle time to
> troubleshoot this issue with him.
> 
> On Thu Oct 19 16:46:42 2017, valderrv wrote:
> >
> >
> > $ ssh -6 -v -p29418 gerrit.fd.io
> > OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g  1 Mar 2016
> > debug1: Reading configuration data /users/dbarach/.ssh/config
> > debug1: /users/dbarach/.ssh/config line 5: Applying options for
> > gerrit.fd.io
> > debug1: Reading configuration data /etc/ssh/ssh_config
> > debug1: /etc/ssh/ssh_config line 19: Applying options for *
> > debug1: Connecting to gerrit.fd.io
> > [2604:e100:1:0:f816:3eff:fe7e:8731]
> > port 29418.
> > debug1: Connection established.
> > debug1: identity file /users/dbarach/.ssh/id_rsa type 1
> > debug1: key_load_public: No such file or directory
> > debug1: identity file /users/dbarach/.ssh/id_rsa-cert type -1
> > debug1: key_load_public: No such file or directory
> > debug1: identity file /users/dbarach/.ssh/id_dsa type -1
> > debug1: key_load_public: No such file or directory
> > debug1: identity file /users/dbarach/.ssh/id_dsa-cert type -1
> > debug1: key_load_public: No such file or directory
> > debug1: identity file /users/dbarach/.ssh/id_ecdsa type -1
> > debug1: key_load_public: No such file or directory
> > debug1: identity file /users/dbarach/.ssh/id_ecdsa-cert type -1
> > debug1: key_load_public: No such file or directory
> > debug1: identity file /users/dbarach/.ssh/id_ed25519 type -1
> > debug1: key_load_public: No such file or directory
> > debug1: identity file /users/dbarach/.ssh/id_ed25519-cert type -1
> > debug1: Enabling compatibility mode for protocol 2.0
> > debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
> > debug1: Remote protocol version 2.0, remote software version
> > GerritCodeReview_2.14.4 (SSHD-CORE-1.4.0)
> > debug1: no match: GerritCodeReview_2.14.4 (SSHD-CORE-1.4.0)
> > debug1: Authenticating to gerrit.fd.io:29418 as 'dbarach'
> > debug1: SSH2_MSG_KEXINIT sent
> > debug1: SSH2_MSG_KEXINIT received
> > debug1: kex: algorithm: ecdh-sha2-nistp256
> > debug1: kex: host key algorithm: ssh-rsa
> > debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256
> > compression: none
> > debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256
> > compression: none
> > debug1: sending SSH2_MSG_KEX_ECDH_INIT
> > debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
> > 
> >
> > $ nc -6 -nv 2604:e100:1:0:f816:3eff:fe7e:8731 29418
> > Connection to 2604:e100:1:0:f816:3eff:fe7e:8731 29418 port [tcp/*]
> > succeeded!
> > SSH-2.0-GerritCodeReview_2.14.4 (SSHD-CORE-1.4.0)
> > 
> >
> > $ traceroute6 gerrit.fd.io
> > traceroute to dev.fd.io (2604:e100:1:0:f816:3eff:fe7e:8731) from
> > 2001:420:2c50:2014:66f6:9dff:fe7a:118, 30 hops max, 24 byte packets
> >  1  2001:420:2c50:2014::1 (2001:420:2c50:2014::1)  0.732 ms  0.351 ms
> > 0.305 ms
> >  2  2001:420:2c50:2000::1 (2001:420:2c50:2000::1)  0.95 ms  0.573 ms
> > 0.46 ms
> >  3  bxb22-cibb-gw1-ten1-5.cisco.com (2001:420:2c40:f::)  0.897 ms
> > 0.813 ms  0.747 ms
> >  4  bxb23-sbb-gw1-ten1-7.cisco.com (2001:420:2c40:33::)  0.881 ms
> > 0.847 ms  0.708 ms
> >  5  bxb22-rbb-gw1-ten1-7.cisco.com (2001:420:2c40:b::1)  0.832 ms
> > 0.754 ms  0.707 ms
> >  6  2001:420:c000:454:: (2001:420:c000:454::)  0.56 ms  0.577 ms
> > 0.526 ms
> >  7  capnet-rtp10-bxb25-10ge.cisco.com (2001:420:c000:135::1)  21.136
> > ms  21.182 ms  21.061 ms
> >  8  rtp10-cd-rbb-gw1-por20.cisco.com (2001:420:c000:401::1)  21.016
> > ms
> > 21.026 ms  20.999 ms
> >  9  rpt10-corp-gw1-ten0-1-0.cisco.com (2001:420:2001:11e::)  21.107
> > ms
> > 21.109 ms  21.051 ms
> > 10  rtp10-cd-dmzbb-gw1-vla777.cisco.com (2001:420:2040:d::6)  21.575
> > ms  21.331 ms  21.244 ms
> > 11  rtp10-cd-isp-gw1-ten0-0-0.cisco.com (2001:420:2040:5::)  66.238
> > ms
> > 47.285 ms  48.875 ms
> > 12  2001:1890:c00:7401::ee6e:5239 (2001:1890:c00:7401::ee6e:5239)
> > 22.615 ms  22.196 ms  22.176 ms
> > 13  rlgnc22crs.ipv6.att.net (2001:1890:ff::12:123:138:162)
> > 33.943
> > ms  34.681 ms  31.996 ms
> > 14  wswdc21crs.ipv6.att.net (2001:1890:ff::12:122:2:190)  34.221
> > ms  31.865 ms  31.968 ms
> > 15  wswdc401igs.ipv6.att.net (2001:1890:ff::12:122:113:37)
> > 32.893
> > ms  34.639 ms  31.971 ms
> > 16  att-gw.wswdc.tinet.net (2001:1890:1fff:20f:192:205:37:194)
> > 30.417
> > ms  32.166 ms  30.514 ms
> > 17  xe-7-3-0.cr0-mtl1.ip6.gtt.net (2001:668:0:2::1:4452)  48.912 ms
> > 48.865 ms  48.824 ms
> > 18  2001:668:0:3::0:adcd:2f2e (2001:668:0:3::0:adcd:2f2e)
> > 48.897 ms  48.851 ms  48.757 ms
> > 19  2605:9000:0:f3f::3 (2605:9000:0:f3f::3)  48.861 ms  51.709 ms
> > 48.73 ms
> > 20  2605:9000:0:100::1 (2605:9000:0:100::1)  50.773 ms  48.931 ms
> > 51.24 ms
> > 21  2605:9000:400:107::c (2605:9000:400:107::c)  48.992 ms  48.933 ms
> > 48.864 ms
> > 

[vpp-dev] [FD.io Helpdesk #47101] No joy: ping6 gerrit.fd.io

[Vanessa Valderrama via RT]

$ ssh -6 -v -p29418 gerrit.fd.io
OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /users/dbarach/.ssh/config
debug1: /users/dbarach/.ssh/config line 5: Applying options for gerrit.fd.io
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to gerrit.fd.io [2604:e100:1:0:f816:3eff:fe7e:8731] port 
29418.
debug1: Connection established.
debug1: identity file /users/dbarach/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /users/dbarach/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /users/dbarach/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /users/dbarach/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /users/dbarach/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /users/dbarach/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /users/dbarach/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /users/dbarach/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
debug1: Remote protocol version 2.0, remote software version 
GerritCodeReview_2.14.4 (SSHD-CORE-1.4.0)
debug1: no match: GerritCodeReview_2.14.4 (SSHD-CORE-1.4.0)
debug1: Authenticating to gerrit.fd.io:29418 as 'dbarach'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: ecdh-sha2-nistp256
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: 
none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: 
none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY


$ nc -6 -nv 2604:e100:1:0:f816:3eff:fe7e:8731 29418
Connection to 2604:e100:1:0:f816:3eff:fe7e:8731 29418 port [tcp/*] succeeded!
SSH-2.0-GerritCodeReview_2.14.4 (SSHD-CORE-1.4.0)


$ traceroute6 gerrit.fd.io
traceroute to dev.fd.io (2604:e100:1:0:f816:3eff:fe7e:8731) from 
2001:420:2c50:2014:66f6:9dff:fe7a:118, 30 hops max, 24 byte packets
 1  2001:420:2c50:2014::1 (2001:420:2c50:2014::1)  0.732 ms  0.351 ms  0.305 ms
 2  2001:420:2c50:2000::1 (2001:420:2c50:2000::1)  0.95 ms  0.573 ms  0.46 ms
 3  bxb22-cibb-gw1-ten1-5.cisco.com (2001:420:2c40:f::)  0.897 ms  0.813 ms  
0.747 ms
 4  bxb23-sbb-gw1-ten1-7.cisco.com (2001:420:2c40:33::)  0.881 ms  0.847 ms  
0.708 ms
 5  bxb22-rbb-gw1-ten1-7.cisco.com (2001:420:2c40:b::1)  0.832 ms  0.754 ms  
0.707 ms
 6  2001:420:c000:454:: (2001:420:c000:454::)  0.56 ms  0.577 ms  0.526 ms
 7  capnet-rtp10-bxb25-10ge.cisco.com (2001:420:c000:135::1)  21.136 ms  21.182 
ms  21.061 ms
 8  rtp10-cd-rbb-gw1-por20.cisco.com (2001:420:c000:401::1)  21.016 ms  21.026 
ms  20.999 ms
 9  rpt10-corp-gw1-ten0-1-0.cisco.com (2001:420:2001:11e::)  21.107 ms  21.109 
ms  21.051 ms
10  rtp10-cd-dmzbb-gw1-vla777.cisco.com (2001:420:2040:d::6)  21.575 ms  21.331 
ms  21.244 ms
11  rtp10-cd-isp-gw1-ten0-0-0.cisco.com (2001:420:2040:5::)  66.238 ms  47.285 
ms  48.875 ms
12  2001:1890:c00:7401::ee6e:5239 (2001:1890:c00:7401::ee6e:5239)  22.615 ms  
22.196 ms  22.176 ms
13  rlgnc22crs.ipv6.att.net (2001:1890:ff::12:123:138:162)  33.943 ms  
34.681 ms  31.996 ms
14  wswdc21crs.ipv6.att.net (2001:1890:ff::12:122:2:190)  34.221 ms  31.865 
ms  31.968 ms
15  wswdc401igs.ipv6.att.net (2001:1890:ff::12:122:113:37)  32.893 ms  
34.639 ms  31.971 ms
16  att-gw.wswdc.tinet.net (2001:1890:1fff:20f:192:205:37:194)  30.417 ms  
32.166 ms  30.514 ms
17  xe-7-3-0.cr0-mtl1.ip6.gtt.net (2001:668:0:2::1:4452)  48.912 ms  48.865 ms  
48.824 ms
18  2001:668:0:3::0:adcd:2f2e (2001:668:0:3::0:adcd:2f2e)  48.897 ms  
48.851 ms  48.757 ms
19  2605:9000:0:f3f::3 (2605:9000:0:f3f::3)  48.861 ms  51.709 ms  48.73 ms
20  2605:9000:0:100::1 (2605:9000:0:100::1)  50.773 ms  48.931 ms  51.24 ms
21  2605:9000:400:107::c (2605:9000:400:107::c)  48.992 ms  48.933 ms  48.864 ms
22  * * *
^C

Thanks… Dave

-Original Message-
From: Vanessa Valderrama [mailto:vvalderr...@linuxfoundation.org] 
Sent: Thursday, October 19, 2017 1:37 PM
To: Dave Barach (dbarach) 
Subject: Re: TSC meeting

Dave can you please try the following and send the output?

ssh -6 -v -p29418 gerrit.fd.io
nc -6 -nv 2604:e100:1:0:f816:3eff:fe7e:8731 29418
traceroute6 gerrit.fd.io


On 10/19/2017 10:38 AM, Dave Barach (dbarach) wrote:
> $ git clone ssh://gerrit.fd.io:29418/vpp foo
> Cloning into 'foo'...
> 
>
> ssh never connects. Sshd is probably not listening on AF_INET6, port 22. 
> Suggest "netstat -ln" or similar...
>
> Ip6 connectivity is OK: 
>
> $ ping6 gerrit.fd.io
> PING 

[vpp-dev] [FD.io Helpdesk #46540] Growing build queue

[Vanessa Valderrama via RT]

On Mon Oct 02 16:02:06 2017, fcoras.li...@gmail.com wrote:
> Queue is back down to 1.
> 
> Thanks a lot Vanessa!
> 
> Florin
> 
> > On Oct 2, 2017, at 11:59 AM, Vanessa Valderrama
> >  wrote:
> >
> > Florin,
> >
> > I'm looking into the issue now.
> >
> > Thank you,
> > Vanessa
> >
> > On 10/02/2017 11:49 AM, Florin Coras wrote:
> >> Hi Vanessa,
> >>
> >> It would seem we’re running out of executors and the build queue
> >> keeps on growing. Could you take a look at it?
> >>
> >> Thanks,
> >> Florin
> >



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

[vpp-dev] [FD.io Helpdesk #46540] [linuxfoundation.org #46540] Re: Growing build queue

[Vanessa Valderrama via RT]

Florin,

I'm looking into the issue now.

Thank you,
Vanessa

On 10/02/2017 11:49 AM, Florin Coras wrote:
> Hi Vanessa, 
>
> It would seem we’re running out of executors and the build queue keeps on 
> growing. Could you take a look at it?
>
> Thanks,
> Florin


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

[vpp-dev] [FD.io Helpdesk #45750] Spurious patch verification failure (gerrit 8400)

[Vanessa Valderrama via RT]

Switching to the new flavors appears to have resolved this issue.

Thank you,
Vanessa

On Wed Sep 13 15:09:49 2017, valderrv wrote:
> We do see intermittent slow response times from Nexus.  We are
> investigating the cause.
> 
> On Wed Sep 13 09:56:20 2017, dbarach wrote:
> > See gerrit https://gerrit.fd.io/r/#/c/8400,
> > https://jenkins.fd.io/job/vpp-verify-master-centos7/7070/console
> >
> >
> > 12:29:12 make[1]: Leaving directory `/w/workspace/vpp-verify-master-
> > centos7/test'
> > 12:29:12 [vpp-verify-master-centos7] $ /bin/bash
> > /tmp/hudson3100921859131279854.sh
> > 12:29:12 Loaded plugins: fastestmirror, langpacks
> > 12:29:12 Repodata is over 2 weeks old. Install yum-cron? Or run: yum
> > makecache fast
> > 12:29:17 Determining fastest mirrors
> > 12:29:18  * base: centos.mirror.ca.planethoster.net
> > 12:29:18  * epel: ftp.cse.buffalo.edu
> > 12:29:18  * extras: centos.mirror.iweb.ca
> > 12:29:18  * updates: centos.mirror.netelligent.ca
> > 12:29:21 Package redhat-lsb-4.1-27.el7.centos.1.x86_64 already
> > installed and latest version
> > 12:29:21 Nothing to do
> > 12:29:21 DISTRIB_ID: CentOS
> > 12:29:21 DISTRIB_RELEASE: 7.3.1611
> > 12:29:21 DISTRIB_CODENAME: Core
> > 12:29:21 DISTRIB_DESCRIPTION: "CentOS Linux release 7.3.1611 (Core) "
> > 12:29:21 INSTALLING VPP-DPKG-DEV from apt/yum repo
> > 12:29:21 REPO_URL:
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7
> > 12:29:21 Loaded plugins: fastestmirror, langpacks
> > 12:29:52
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:29:52 Trying other mirror.
> > 12:30:22
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:30:22 Trying other mirror.
> > 12:30:52
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:30:52 Trying other mirror.
> > 12:31:22
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:31:22 Trying other mirror.
> > 12:31:52
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:31:52 Trying other mirror.
> > 12:32:22
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:32:22 Trying other mirror.
> > 12:32:52
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:32:52 Trying other mirror.
> > 12:33:22
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:33:22 Trying other mirror.
> > 12:33:52
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:33:52 Trying other mirror.
> > 12:34:22
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > [Errno 12] Timeout on
> > https://nexus.fd.io/content/repositories/fd.io.master.centos7/repodata/repomd.xml:
> > (28, 'Operation too slow. Less than 1000 bytes/sec transferred the
> > last 30 seconds')
> > 12:34:22 Trying other mirror.
> > 12:34:22
> > 12:34:22
> > 12:34:22  One of the configured repositories failed (fd.io master
> > branch latest merge),
> > 

[vpp-dev] [FD.io Helpdesk #45822] [linuxfoundation.org #45822] Re: Jenkins ubuntu 1604 failures

[Vanessa Valderrama via RT]

Florin,

It doesn't appear the  failures are related to the new instances.  We
will be switching to a new performance (4c/8GB) instance when it's
available. I've submitted a request to the vendor and will follow up
tomorrow morning.  Adding the additional CPU resources may
improve/resolve the failure in build 7108.  Please let me know if there
are additional failures you are concerned about that I haven't
addressed.  Also please feel free to ping me via IRC fdio-infra
(valderrv) if you'd like to work together to debug these issues quickly.

*https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7108/console
17:34:21* ACL IPv4 routed -> bridged, L2 ACL
permit+reflect17:44:47,177 Timeout while waiting for child test runner
process (last test running was `MACIP 2 ACLs each with 100+ entries' in
`/tmp/vpp-unittest-TestMACIP-py7viS')!

*
*This failure is not a timeout and appears to be related to code*
   
https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7109/console*   

*16:48:11* * Test framework PEP8 compliance check FAILED
*16:48:11*
***
*16:48:11* Makefile:172: recipe for target 'checkstyle' failed
*16:48:11* make[1]: *** [checkstyle]
Error 1 *16:48:11* make[1]: Leaving directory
'/w/workspace/vpp-verify-master-ubuntu1604/test' *16:48:11*
Makefile:376: recipe for target 'test-checkstyle' failed *16:48:11*
make: *** [test-checkstyle] Error 2 *16:48:11* Build step
'Execute shell' marked build as failure


The cause of these two failures appear to be related to package(s) not
installing?
*   
https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7111/console
   
https://jenkins.fd.io/view/vpp/job/vpp-verify-master-ubuntu1604/7112/console
**19:05:38* cc1: all warnings being treated as errors *19:05:38*
Makefile:6164: recipe for target 'vppinfra/linux/mem.lo' failed
*19:05:38* make[3]: *** [vppinfra/linux/mem.lo] Error 1 *19:05:38*
make[3]: *** Waiting for unfinished jobs *   
19:05:40* make[3]: Leaving directory
'/w/workspace/vpp-verify-master-ubuntu1604/build-root/build-vpp-native/vpp'*19:05:40*
Makefile:698: recipe for target 'vpp-build' failed *19:05:40* make[2]:
*** [vpp-build] Error 2 *19:05:40* make[2]:
Leaving directory
'/w/workspace/vpp-verify-master-ubuntu1604/build-root' *19:05:40*
Makefile:934: recipe for target 'install-packages' failed *19:05:40*
make[1]: *** [install-packages] Error 1 *19:05:40* make[1]: Leaving
directory '/w/workspace
/vpp-verify-master-ubuntu1604/build-root' *19:05:40* Makefile:487:
recipe for target 'verify' failed *19:05:40* make: *** [verify] Error 2
*19:05:40* Build step 'Execute shell' marked build as failure

Thank you,
Vanessa

On 09/14/2017 02:27 PM, Florin Coras wrote:
> Hi Vanessa, 
>
> We’re seeing lots of vpp-verify-master-ubuntu1604 failures that seem to be 
> timeouts related. Could they be related to the recent switch to the new 
> instances?
>
> Thanks, 
> Florin
>


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

[vpp-dev] [FD.io Helpdesk #44785] Another 6 hour build timeout

[Vanessa Valderrama via RT]

This issue appears to be resolved with the switch to the new instances.

On Fri Aug 25 12:16:52 2017, valderrv wrote:
> It appears build times have recovered.  I opened a ticket with the
> vendor to determine the root cause of the timeouts and will update the
> ticket when I receive a response.
> 
> Thank you,
> Vanessa
> 
> On Thu Aug 24 13:57:31 2017, dwallacelf wrote:
> > Dear helpdesk,
> >
> > Please investigate this build failure
> > https://jenkins.fd.io/job/vpp-verify-master-centos7/6757/
> >
> > The build output has that has indications of something seriously
> > wrong
> > with the minion's os:
> >
> > [From
> > https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify-
> > master-
> > centos7/6757/console-timestamp.log.gz]
> >
> > 08:37:27  /usr/bin/tar: vpp-17.10/.gitignore: time stamp 2017-08-24
> > 16:44:25 is 29217.570024474 s in the future
> > 08:37:27  /usr/bin/tar: vpp-17.10/.gitreview: time stamp 2017-08-24
> > 16:44:25 is 29217.569892077 s in the future
> > 08:37:27  /usr/bin/tar: vpp-17.10/LICENSE: time stamp 2017-08-24
> > 16:44:25 is 29217.569781399 s in the future
> > 08:37:27  /usr/bin/tar: vpp-17.10/MAINTAINERS: time stamp 2017-08-24
> > 16:44:25 is 29217.569661502 s in the future
> > 08:37:27  /usr/bin/tar: vpp-17.10/Makefile: time stamp 2017-08-24
> > 16:44:25 is 29217.569547964 s in the future
> >
> >
> > I don't see any reason for the build timeout to be 6 hours.  Can this
> > be
> > changed to something closer to 2 hours.  It is a waste of resources
> > to
> > continue to allow the minions to spend hours producing nothing of
> > value.
> >
> > Thanks,
> > -daw-



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

[vpp-dev] [FD.io Helpdesk #45343] More build timeouts for vpp-verify-master-ubuntu1604

[Vanessa Valderrama via RT]

This issue appears to be resolved with the switch to the new instances.


On Wed Sep 06 15:48:23 2017, valderrv wrote:
> We are in the process of switching to dedicated instances that should
> resolve this issue.  We hope to have this complete tomorrow around
> 9:00am PDT
> 
> 
> On 09/06/2017 02:40 PM, Florin Coras wrote:
> > Hi, 
> >
> > Any news regarding this? We are 1 week away from API freeze and the
> > infra makes it almost impossible to merge patches! 
> >
> > Thanks, 
> > Florin
> >
> >> On Sep 4, 2017, at 9:44 PM, Dave Wallace  >> > wrote:
> >>
> >> Dear helpd...@fd.io,
> >>
> >> There has been another string of build timeouts for
> >> vpp-verify-master-ubuntu1604:
> >>
> >> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/buildTimeTrend
> >>
> >> Please change the timeout for build failures from 360 minutes to 120
> >> minutes in addition to addressing the slow minion issue.
> >>
> >> Thanks,
> >> -daw-
> >> ___
> >> 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 #45343] [linuxfoundation.org #45343] Re: More build timeouts for vpp-verify-master-ubuntu1604

[Vanessa Valderrama via RT]

We are in the process of switching to dedicated instances that should
resolve this issue.  We hope to have this complete tomorrow around
9:00am PDT


On 09/06/2017 02:40 PM, Florin Coras wrote:
> Hi, 
>
> Any news regarding this? We are 1 week away from API freeze and the
> infra makes it almost impossible to merge patches! 
>
> Thanks, 
> Florin
>
>> On Sep 4, 2017, at 9:44 PM, Dave Wallace > > wrote:
>>
>> Dear helpd...@fd.io,
>>
>> There has been another string of build timeouts for
>> vpp-verify-master-ubuntu1604:
>>
>> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/buildTimeTrend
>>
>> Please change the timeout for build failures from 360 minutes to 120
>> minutes in addition to addressing the slow minion issue.
>>
>> Thanks,
>> -daw-
>> ___
>> 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 #44785] Another 6 hour build timeout

[Vanessa Valderrama via RT]

It appears build times have recovered.  I opened a ticket with the vendor to 
determine the root cause of the timeouts and will update the ticket when I 
receive a response.

Thank you,
Vanessa

On Thu Aug 24 13:57:31 2017, dwallacelf wrote:
> Dear helpdesk,
> 
> Please investigate this build failure
> https://jenkins.fd.io/job/vpp-verify-master-centos7/6757/
> 
> The build output has that has indications of something seriously wrong
> with the minion's os:
> 
> [From
> https://logs.fd.io/production/vex-yul-rot-jenkins-1/vpp-verify-master-
> centos7/6757/console-timestamp.log.gz]
> 
> 08:37:27  /usr/bin/tar: vpp-17.10/.gitignore: time stamp 2017-08-24
> 16:44:25 is 29217.570024474 s in the future
> 08:37:27  /usr/bin/tar: vpp-17.10/.gitreview: time stamp 2017-08-24
> 16:44:25 is 29217.569892077 s in the future
> 08:37:27  /usr/bin/tar: vpp-17.10/LICENSE: time stamp 2017-08-24
> 16:44:25 is 29217.569781399 s in the future
> 08:37:27  /usr/bin/tar: vpp-17.10/MAINTAINERS: time stamp 2017-08-24
> 16:44:25 is 29217.569661502 s in the future
> 08:37:27  /usr/bin/tar: vpp-17.10/Makefile: time stamp 2017-08-24
> 16:44:25 is 29217.569547964 s in the future
> 
> 
> I don't see any reason for the build timeout to be 6 hours.  Can this
> be
> changed to something closer to 2 hours.  It is a waste of resources to
> continue to allow the minions to spend hours producing nothing of
> value.
> 
> Thanks,
> -daw-



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

[vpp-dev] [FD.io Helpdesk #44395] jenkins build timeout

[Vanessa Valderrama via RT]

Root cause:
There was a misconfigured flavor type which did not have proper shares/limits 
so it was consuming significantly more CPU power than it should be (unfairly).  
When the VMs landed on Hypervisor the CPU was severely limited


On Wed Aug 16 17:50:49 2017, valderrv wrote:
> I spoke with the vendor.  They are implenting a fix at this time.
> They are also adding monitoring so they can proactively alert and
> resolve this issue in the future.
> On Wed Aug 16 11:03:24 2017, ksek...@cisco.com wrote:
> > Hi helpd...@fd.io,
> >
> > I just noticed a 360 minute build timeout in jenkins..
> >
> > https://jenkins.fd.io/job/vpp-verify-master-centos7/6639/console
> >
> > timestamps for the build commands look unreal...
> >
> > 09:21:11   CC   svm/svm.lo
> > 09:21:11   CC   svm/ssvm.lo
> > 09:21:11   CC   svm/svm_fifo.lo
> > 09:21:11   CC   svm/svm_fifo_segment.lo
> > 09:21:12   CC   svm/svmdb.lo
> > 09:21:16   CC   vlib/buffer.lo
> > 09:21:54   CC   vlib/buffer_serialize.lo
> > ...
> > 11:34:28   CC   vnet/tcp/builtin_client.lo
> > 11:35:22   CC   vnet/tcp/builtin_server.lo
> > 11:36:41   CC   vnet/tcp/builtin_http_server.lo
> > 11:36:51   CC   vnet/tcp/builtin_proxy.lo
> > 11:38:17   CC   vnet/tcp/tcp_test.lo
> > 11:38:19   CC   vnet/tcp/tcp.lo
> > 11:40:07   CC   vnet/udp/udp.lo
> > ...
> > 14:15:29 copying selected object files to avoid basename conflicts...
> > 14:15:32   CCLD test_svm_fifo1
> > 14:15:38   CCLD libsvmdb.la
> > 14:15:51   CCLD libvlibmemory.la
> > 14:15:54   CCLD libvlibmemoryclient.la
> > 14:16:11   CCLD vlib_unix
> > 14:16:16   CCLD libvppapiclient.la
> > 14:16:25   CCLD svmdbtool
> > 14:16:50   CCLD bin/vpp_get_metrics
> > 14:16:55   CCLD vpp_api_test
> > 14:17:05   CCLD vpp_restart
> > 14:17:20   CCLD bin/summary_stats_client
> > 14:17:36   CCLD uri_udp_test
> > 14:17:39   CCLD uri_tcp_test
> > 14:17:55   CCLD libvlibsocket.la
> > 14:18:10   CCLD libvppcom.la
> > 14:19:12   CCLD vcl_test_server
> > 14:19:12   CCLD vcl_test_client
> > 14:49:28 Build timed out (after 360 minutes). Marking the build as
> > failed.
> >
> > Any idea what causes this huge slowdowns?
> >
> > Thanks,
> > Klement




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

[vpp-dev] [FD.io Helpdesk #44397] Poor VPP Build Time

[Vanessa Valderrama via RT]

I spoke with the vendor.  They are implenting a fix at this time.  They are 
also adding monitoring so they can proactively alert and resolve this issue in 
the future.

On Wed Aug 16 11:29:10 2017, dwallacelf wrote:
> Resend without graphics... See link for details.
> 
> On 8/16/17 11:27 AM, Dave Wallace wrote:
> > Dear FIDO Helpdesk,
> >
> > Several VPP verify jobs are running so slow that they are timing out 
> > after 6 hours without having completed compiling the codebase!
> >
> > https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/buildTimeTrend
> >
> > Run times are varying quite widely.  Please feed the minions more 
> > spinach... ;^)
> >
> > Thanks,
> > -daw-
> >
> 



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

[vpp-dev] [FD.io Helpdesk #44395] jenkins build timeout

[Vanessa Valderrama via RT]

I spoke with the vendor.  They are implenting a fix at this time.  They are 
also adding monitoring so they can proactively alert and resolve this issue in 
the future.
On Wed Aug 16 11:03:24 2017, ksek...@cisco.com wrote:
> Hi helpd...@fd.io,
> 
> I just noticed a 360 minute build timeout in jenkins..
> 
> https://jenkins.fd.io/job/vpp-verify-master-centos7/6639/console
> 
> timestamps for the build commands look unreal...
> 
> 09:21:11   CC   svm/svm.lo
> 09:21:11   CC   svm/ssvm.lo
> 09:21:11   CC   svm/svm_fifo.lo
> 09:21:11   CC   svm/svm_fifo_segment.lo
> 09:21:12   CC   svm/svmdb.lo
> 09:21:16   CC   vlib/buffer.lo
> 09:21:54   CC   vlib/buffer_serialize.lo
> ...
> 11:34:28   CC   vnet/tcp/builtin_client.lo
> 11:35:22   CC   vnet/tcp/builtin_server.lo
> 11:36:41   CC   vnet/tcp/builtin_http_server.lo
> 11:36:51   CC   vnet/tcp/builtin_proxy.lo
> 11:38:17   CC   vnet/tcp/tcp_test.lo
> 11:38:19   CC   vnet/tcp/tcp.lo
> 11:40:07   CC   vnet/udp/udp.lo
> ...
> 14:15:29 copying selected object files to avoid basename conflicts...
> 14:15:32   CCLD test_svm_fifo1
> 14:15:38   CCLD libsvmdb.la
> 14:15:51   CCLD libvlibmemory.la
> 14:15:54   CCLD libvlibmemoryclient.la
> 14:16:11   CCLD vlib_unix
> 14:16:16   CCLD libvppapiclient.la
> 14:16:25   CCLD svmdbtool
> 14:16:50   CCLD bin/vpp_get_metrics
> 14:16:55   CCLD vpp_api_test
> 14:17:05   CCLD vpp_restart
> 14:17:20   CCLD bin/summary_stats_client
> 14:17:36   CCLD uri_udp_test
> 14:17:39   CCLD uri_tcp_test
> 14:17:55   CCLD libvlibsocket.la
> 14:18:10   CCLD libvppcom.la
> 14:19:12   CCLD vcl_test_server
> 14:19:12   CCLD vcl_test_client
> 14:49:28 Build timed out (after 360 minutes). Marking the build as
> failed.
> 
> Any idea what causes this huge slowdowns?
> 
> Thanks,
> Klement




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

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

[Vanessa Valderrama via RT]

Jan,

We are looking into this issue.

Thank you,
Vanessa

On Fri Jun 16 09:12:55 2017, jgel...@cisco.com wrote:
> Hello Anton,
> 
> 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-
>  From: Anton Baranov via RT [mailto:fdio-
> helpd...@rt.linuxfoundation.org]
> Sent: Wednesday, June 14, 2017 15:45
> To: Jan Gelety -X (jgelety - PANTHEON TECHNOLOGIES at Cisco)
> 
> 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 see any connectivity problems between
> jenkins and VIRL servers. Please let me know if you're still having
> that issue. I'll keep an eye on that problem and if it reapears I'll
> report that to our cloud provider to check further.
> 
> Thanks,
> --
> Anton Baranov
> Systems and Network Administrator
> The Linux Foundation
> 
> On Wed Jun 14 08:12:45 2017, jgel...@cisco.com wrote:
> > 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/,
> > https://jenkins.fd.io/view/csit/job/csit-vpp-functional-master-
> > ubuntu1604-virl/, https://jenkins.fd.io/view/csit/job/csit-vpp-
> > functional-master-centos7-virl/) because of ssh connection timeouts.
> >
> > Could you, please, have a look on it?
> >
> > Thank you very much.
> >
> > Regards,
> > Jan
> 
> 
> 



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

[vpp-dev] [FD.io Helpdesk #41698] Test failure due to resource unavailable

[Vanessa Valderrama via RT]

This appears to be an isolated incident caused by an intermittent 
infrastructure issue.  All jobs since 5805 have passed.  I've added this issue 
to the Jenkins failure cause management.

Thank you,
Vanessa

On Wed Jun 07 19:07:18 2017, dwallacelf wrote:
> Dear held...@fd.io
> 
> Please investigate the root cause of this resource failure during build 
> phase of vpp-csit-verify-virl-master job:
> 
> https://jenkins.fd.io/job/vpp-csit-verify-virl-master/5805/console
> 
> - %< -
> 21:37:41   CC   vnet/map/ip6_map.lo
> 21:37:44   CC   vnet/map/ip4_map_t.lo
> 21:37:45   CC   vnet/map/ip6_map_t.lo
> 21:37:47 ./libtool: fork: retry: Resource temporarily unavailable
> 21:37:47 ./libtool: fork: retry: No child processes
> 21:37:48 ./libtool: fork: retry: No child processes
> 21:37:48 ./libtool: fork: retry: No child processes
> 21:37:50 ./libtool: fork: retry: No child processes
> 21:37:50 ./libtool: fork: retry: No child processes
> 21:37:54 ./libtool: fork: retry: No child processes
> 21:37:54 ./libtool: fork: retry: No child processes
> 21:38:02 ./libtool: fork: Resource temporarily unavailable
> 21:38:02 ./libtool: fork: retry: No child processes
> 21:38:02 ./libtool: fork: Resource temporarily unavailable
> 21:38:02 ./libtool: line 1: wait_for: No record of process 25401
> 21:38:02 ./libtool: fork: retry: No child processes
> 21:38:02 ./libtool: fork: retry: No child processes
> 21:38:03 ./libtool: fork: retry: No child processes
> 21:38:03 ./libtool: fork: retry: No child processes
> 21:38:03 ./libtool: fork: retry: No child processes
> 21:38:03 gcc: error: vfork: Resource temporarily unavailable
> - %< -



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

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

[Vanessa Valderrama via RT]

Restarting the plugin appears to have resolved this issue.  I've run several 
rechecks that all triggered properly.  Since this issue appeared to be resolved 
earlier we'll leave this ticket open for now.  Please let us know if this 
happens again.

Thank you,
Vanessa

On Wed May 31 13:15:14 2017, valderrv wrote:
> Still looking into this issue.  
> 
> On Wed May 31 11:37:54 2017, hagbard wrote:
> > Anton,
> >   We are getting patches not triggering again:
> > 
> > https://gerrit.fd.io/r/#/c/6959/
> > 
> > Ed
> > 
> > On Wed, May 31, 2017 at 7:49 AM, Anton Baranov via RT <
> > fdio-helpd...@rt.linuxfoundation.org> wrote:
> > 
> > > Jan:
> > >
> > > Unfortunately there is nothing in the logs that indicates the root cause
> > > of the problem. Our guess is that Gerrit Trigger plugin just crushed and
> > > caused jobs not being triggered properly
> > >
> > > --
> > > Anton Baranov
> > > Systems and Network Administrator
> > > The Linux Foundation
> > >
> > >
> > > On Wed May 31 10:10:04 2017, jgel...@cisco.com wrote:
> > > > 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 - PANTHEON TECHNOLOGIES at Cisco)
> > > > 
> > > > Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io
> > > > Subject: [FD.io Helpdesk #41298] Jobs are not triggered from gerrit
> > > >
> > > > We triggered rechecks for two gerrit changes:
> > > > - https://gerrit.fd.io/r/#/c/6806/2
> > > > - https://gerrit.fd.io/r/#/c/6912/2
> > > >
> > > > Regards,
> > > >
> > > > On Wed May 31 09:58:32 2017, hagbard wrote:
> > > > > What did you do to confirm triggers are now happening?
> > > > >
> > > > > Ed
> > > > >
> > > > > On Wed, May 31, 2017 at 6:55 AM, Anton Baranov via RT <
> > > > > fdio-helpd...@rt.linuxfoundation.org> wrote:
> > > > >
> > > > > > Hello,
> > > > > >
> > > > > > We restarted jenkins service and that fixed jobs triggering.
> > > > > >
> > > > > > Best regards,
> > > > > > --
> > > > > > Anton Baranov
> > > > > > Systems and Network Administrator
> > > > > > The Linux Foundation
> > > > > >
> > > > > >
> > > > > > On Wed May 31 09:20:26 2017, abaranov wrote:
> > > > > > > Hello,
> > > > > > >
> > > > > > > We're checking that issue right now  and will keep you updated
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > ___
> > > > > > vpp-dev mailing list
> > > > > > vpp-dev@lists.fd.io
> > > > > > https://lists.fd.io/mailman/listinfo/vpp-dev
> > > > > >
> > > >
> > > >
> > > > --
> > > > Anton Baranov
> > > > Systems and Network Administrator
> > > > The Linux Foundation
> > >
> > >
> > >
> > > ___
> > > 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] [FD.io Helpdesk #41298] Jobs are not triggered from gerrit

[Vanessa Valderrama via RT]

Still looking into this issue.  

On Wed May 31 11:37:54 2017, hagbard wrote:
> Anton,
>   We are getting patches not triggering again:
> 
> https://gerrit.fd.io/r/#/c/6959/
> 
> Ed
> 
> On Wed, May 31, 2017 at 7:49 AM, Anton Baranov via RT <
> fdio-helpd...@rt.linuxfoundation.org> wrote:
> 
> > Jan:
> >
> > Unfortunately there is nothing in the logs that indicates the root cause
> > of the problem. Our guess is that Gerrit Trigger plugin just crushed and
> > caused jobs not being triggered properly
> >
> > --
> > Anton Baranov
> > Systems and Network Administrator
> > The Linux Foundation
> >
> >
> > On Wed May 31 10:10:04 2017, jgel...@cisco.com wrote:
> > > 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 - PANTHEON TECHNOLOGIES at Cisco)
> > > 
> > > Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io
> > > Subject: [FD.io Helpdesk #41298] Jobs are not triggered from gerrit
> > >
> > > We triggered rechecks for two gerrit changes:
> > > - https://gerrit.fd.io/r/#/c/6806/2
> > > - https://gerrit.fd.io/r/#/c/6912/2
> > >
> > > Regards,
> > >
> > > On Wed May 31 09:58:32 2017, hagbard wrote:
> > > > What did you do to confirm triggers are now happening?
> > > >
> > > > Ed
> > > >
> > > > On Wed, May 31, 2017 at 6:55 AM, Anton Baranov via RT <
> > > > fdio-helpd...@rt.linuxfoundation.org> wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > We restarted jenkins service and that fixed jobs triggering.
> > > > >
> > > > > Best regards,
> > > > > --
> > > > > Anton Baranov
> > > > > Systems and Network Administrator
> > > > > The Linux Foundation
> > > > >
> > > > >
> > > > > On Wed May 31 09:20:26 2017, abaranov wrote:
> > > > > > Hello,
> > > > > >
> > > > > > We're checking that issue right now  and will keep you updated
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > ___
> > > > > vpp-dev mailing list
> > > > > vpp-dev@lists.fd.io
> > > > > https://lists.fd.io/mailman/listinfo/vpp-dev
> > > > >
> > >
> > >
> > > --
> > > Anton Baranov
> > > Systems and Network Administrator
> > > The Linux Foundation
> >
> >
> >
> > ___
> > 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] [FD.io Helpdesk #39405] "Jenkins is going to shut down" bar in jenkins webpage

[Vanessa Valderrama via RT]

This change is complete.  Jenkins builds have started.  Please report any 
issues to valderrv via fdio-infra on IRC.
Thank you,
We had intermittent builds failing that required Jenkins maintenance.  
Notifications were sent to t...@lists.fd.io, disc...@lists.fd.io, and 
infra-steer...@lists.fd.io.  The maintenance is complete and builds are running 
again.

Thank you,
Vanessa

On 04/04/2017 12:35 PM, Vanessa Valderrama wrote:
>
> This change is a bit delayed. There is one build that needs to finish before 
> starting the change.
>
> Thank you,
>
> Vanessa
>
>
> On 04/04/2017 11:59 AM, Vanessa Valderrama wrote:
>>
>> What:
>>
>> LF will be uninstalling the Jenkins JClouds plugin in production
>>
>> When:
>>
>> 2016-04-04 @ 0530 UTC (10:30am PDT)
>>
>>
>> Impact:
>> Jenkins is currently in shutdown mode.  This change requires a Jenkins 
>> restart.
>>
>> Why:
>> Intermittent build failures related to the plugins lead us to believe the 
>> JClouds plugin is conflicting with the OpenStack plugin. 
>



On Tue Apr 04 13:33:08 2017, therb...@redhat.com wrote:
> Does anyone know what is meant by the Red Bar in jenkins that says 
> "Jenkins is going to shut down"
> 
> --Tom
> 



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

[vpp-dev] [FD.io Helpdesk #39399] Spurious patch validation failure

[Vanessa Valderrama via RT]

Dave,

We're seeing intermittent errors related to plugins.  We still have the JClouds 
plugin installed even though we are using OpenStack. The JClouds plugin isn't 
installed on the sandbox so I think it's a low risk change to remove the 
JClouds plugin in production.  After I remove the plugin I'll closely monitor 
the builds.  I've put Jenkins in shutdown and will be sending a notification to 
the lists shortly.

Apr 04, 2017 1:00:45 PM jenkins.plugins.openstack.compute.JCloudsCleanupThread 
terminatesNodesWithoutServers
WARNING: No server running for computer ubuntu1404-basebuild-4c-4g-9647. 
Terminating

Thanks,
Vanessa

On Tue Apr 04 11:13:49 2017, valderrv wrote:
> Dave,
> 
> Looking into this issue.
> 
> On Tue Apr 04 10:42:43 2017, dbarach wrote:
> > Any idea what could have cause this failure?
> > https://jenkins.fd.io/job/vpp-verify-master-ubuntu1404/4739/
> > 
> > Thanks... Dave
> 
> 



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

[vpp-dev] [FD.io Helpdesk #37770] Latest Linux x86_64 google-chrome hates gerrit.fd.io

[Vanessa Valderrama via RT]

All FD.io certs have been updated except for Nexus which will be updated next 
week.



On Fri Mar 10 11:51:51 2017, emsearcy wrote:
> Update: https://fd.io, https://wiki.fd.io, and https://lists.fd.io
> have had their certs updated.  Other sites including Gerrit are still
> in progress; will send updates as we have them.
> 
> -Eric



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

[vpp-dev] [FD.io Helpdesk #36808] vpp-merge-master-{os} Jenkins Jobs are failing

[Vanessa Valderrama via RT]

The jobs are now passing.

https://jenkins.fd.io/view/vpp/job/vpp-merge-master-centos7/
https://jenkins.fd.io/view/vpp/job/vpp-merge-master-ubuntu1404/
https://jenkins.fd.io/view/vpp/job/vpp-merge-master-ubuntu1604/

On Fri Mar 03 18:37:27 2017, hagbard wrote:
> The vpp merge jobs appear to be fixed now:
> 
> https://gerrit.fd.io/r/#/c/5619/
> 
> On Wed Mar 01 02:11:35 2017, mgrad...@cisco.com wrote:
> > + Ed
> >
> > -Original Message-
> > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-
> > boun...@lists.fd.io]
> > On Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at
> > Cisco)
> > Sent: 1 marca 2017 08:07
> > To: fdio-helpd...@rt.linuxfoundation.org; dwallac...@gmail.com
> > Cc: Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco)
> > <pla...@cisco.com>; csit-...@lists.fd.io; vpp-dev@lists.fd.io
> > Subject: Re: [vpp-dev] [FD.io Helpdesk #36808] vpp-merge-master-{os}
> > Jenkins Jobs are failing
> >
> > Current hc2vpp jobs expect vpp jobs to be successful (vpp jobs are
> > triggers).
> >
> > Ed: would it be possible to ignore vpp-dpdk-dev deploy failure?
> >
> > If not - this is something we can live with (perhaps hc2vpp jobs need
> > some hardening).
> >
> > Found one more issue (looks like it might be related):
> > Most current vpp ub16 package is 12days old:
> > https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main/io/fd/vpp/vpp/
> >
> > Ub14 and centos7 are ok. Any idea why is that happening?
> >
> > This is a bigger problem for our integration jobs (we are discussing
> > workaround now).
> >
> > Regards,
> > Marek
> >
> > -Original Message-
> > From: Vanessa Valderrama via RT [mailto:fdio-
> > helpd...@rt.linuxfoundation.org]
> > Sent: 28 lutego 2017 20:49
> > To: dwallac...@gmail.com
> > Cc: csit-...@lists.fd.io; hagb...@gmail.com; Jan Srnicek -X (jsrnicek
> > - PANTHEON TECHNOLOGIES at Cisco) <jsrni...@cisco.com>; Marek Gradzki
> > -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgrad...@cisco.com>;
> > Peter Lapos -X (plapos - PANTHEON TECHNOLOGIES at Cisco)
> > <pla...@cisco.com>; vpp-dev@lists.fd.io
> > Subject: [FD.io Helpdesk #36808] vpp-merge-master-{os} Jenkins Jobs
> > are failing
> >
> > Review this issue with Ed.  This is caused by repeatedly pushing vpp-
> > dpdk-dev with the same version.  Please let me know if any other
> > action is needed on this ticket.
> >
> > Thank you,
> > Vanessa
> >
> > On Tue Feb 28 06:29:30 2017, mgrad...@cisco.com wrote:
> > > Dear all,
> > >
> > > after quick look at the logs,
> > >  it looks like the issue is caused by vpp-dpdk-dev-17.02-
> > > vpp1_amd64.pom
> > > deploy failure.
> > >
> > > As a consequence hc2vpp integration jobs are not triggered, which
> > > causes honeycomb packages being out of synch much more often.
> > >
> > > The issue was also reported by our team as #37115 some time ago...
> > >
> > > Regards,
> > > Marek
> > >
> > > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-
> > > boun...@lists.fd.io]
> > > On Behalf Of Dave Wallace
> > > Sent: 16 lutego 2017 04:17
> > > To: helpd...@fd.io; Ed Warnicke <hagb...@gmail.com>
> > > Cc: csit-...@lists.fd.io; vpp-dev@lists.fd.io
> > > Subject: [vpp-dev] vpp-merge-master-{os} Jenkins Jobs are failing
> > >
> > > Dear helpd...@fd.io<mailto:helpd...@fd.io>,
> > >
> > > All of the vpp-merge-master-{os} jobs have been returning 'failure'
> > > for the past 8 days:
> > >
> > > [cid:image001.png@01D291BC.8904FB90]
> > >
> > > This is causing the downstream vpp-docs-merge-master and vpp-make-
> > > test-docs-merge-master to NOT be scheduled.
> > >
> > > Why are the docs merge jobs triggered off of the successful
> > > completion
> > > of 'vpp-merge-master-ubuntu1404' instead of being triggered by
> > > 'gerrit-trigger-patch-merged' and run in parallel with the other
> > > merge
> > > jobs?
> > >
> > > Also, why are the docs merge jobs being triggered off of the vpp
> > >  ubuntu1404 merge job when the os-parameter is being set to
> > > 'ubuntu1604'?
> > >
> > > Thanks,
> > > -daw-
> >
> >
> >
> > ___
> > 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 #36114] Verify job failures due to external IP address lookup

[Vanessa Valderrama via RT]

The last 4 builds for each job have passed.  The patches did require a rebase 
to pick up change https://gerrit.fd.io/r/#/c/4992/.

Please open a new RT if you have further issues.

Thank you,
Vanessa

On Fri Feb 03 12:41:59 2017, valderrv wrote:
> Andrew,
> 
> I am looking into this failure now.
> 
> Thank you,
> Vanessa
> 
> On Fri Feb 03 12:09:01 2017, ayour...@gmail.com wrote:
> > Vanessa,
> >
> > I had a failure just less than an hour ago, though it seems like a
> > different issue, on a patch set that had verified yesterday
> > successfully, after a comment-only change:
> >
> > https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/3696/console
> >
> > 16:23:28 Reading package lists...
> > 16:23:28 Building dependency tree...
> > 16:23:28 Reading state information...
> > 16:23:28 Package pkg-config is not available, but is referred to by
> > another package.
> > 16:23:28 This may mean that the package is missing, has been
> > obsoleted, or
> > 16:23:28 is only available from another source
> > 16:23:28
> > 16:23:28 E: Package 'pkg-config' has no installation candidate
> > 16:23:28 E: Unable to locate package chrpath
> > 16:23:28 E: Unable to locate package default-jdk-headless
> > 16:23:28 Makefile:167: recipe for target 'install-dep' failed
> > 16:23:28 make: *** [install-dep] Error 100
> > 16:23:28 Build step 'Execute shell' marked build as failure
> > 16:23:28 [ssh-agent] Stopped.
> > 16:23:29 Skipped archiving because build is not successful
> > 16:23:29 [PostBuildScript] - Execution post build scripts.
> >
> > And https://jenkins.fd.io/job/vpp-csit-verify-virl-master/3700/:
> >
> > 16:24:28 Reading state information...
> > 16:24:28 Package pkg-config is not available, but is referred to by
> > another package.
> > 16:24:28 This may mean that the package is missing, has been
> > obsoleted, or
> > 16:24:28 is only available from another source
> > 16:24:28
> > 16:24:28 E: Package 'pkg-config' has no installation candidate
> > 16:24:28 E: Unable to locate package chrpath
> > 16:24:28 E: Unable to locate package default-jdk-headless
> > 16:24:28 Makefile:167: recipe for target 'install-dep' failed
> > 16:24:28 make: *** [install-dep] Error 100
> > 16:24:28 rm -f /w/workspace/vpp-csit-verify-virl-master/build-
> > root/scripts/.version
> > /w/workspace/vpp-csit-verify-virl-master/build-root/rpm/*.tar.gz
> > 16:24:28 E: Package 'pkg-config' has no installation candidate
> > 16:24:28 E: Unable to locate package chrpath
> > 16:24:28 E: Unable to locate package default-jdk-headless
> >
> > Anything I need to do on my side ?
> >
> > --a
> >
> >
> > On 2/2/17, Vanessa Valderrama via RT
> > <fdio-helpd...@rt.linuxfoundation.org> wrote:
> > > The following changes have resolved this issue:
> > > https://gerrit.fd.io/r/#/c/4990/
> > > https://gerrit.fd.io/r/#/c/4993/
> > >
> > > Builds are passing
> > > vpp-verify-master-ubuntu1604
> > > vpp-csit-verify-virl-master
> > >
> > > Thank you,
> > > Vanessa
> > >
> > >
> > > On Wed Feb 01 11:28:33 2017, valderrv wrote:
> > >> We have opened a ticket with our vendor to investigate this issue.
> > >>
> > >> Thank you,
> > >> Vanessa
> > >>
> > >> On Wed Feb 01 01:55:15 2017, matfa...@cisco.com wrote:
> > >> > Hi,
> > >> >
> > >> > same issue https://gerrit.fd.io/r/#/c/4966/
> > >> >
> > >> > Regards,
> > >> >
> > >> >
> > >> >
> > >> >
> > >> > Matus Fabian
> > >> > Engineer - Software
> > >> > matfa...@cisco.com<mailto:matfa...@cisco.com>
> > >> > Tel:
> > >> >
> > >> > Cisco Systems, Inc.
> > >> >
> > >> >
> > >> >
> > >> > Slovakia
> > >> > cisco.com
> > >> >
> > >> >
> > >> > [http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> > >> > before you print.
> > >> >
> > >> > This email may contain confidential and privileged material for
> > >> > the
> > >> > sole use of the intended recipient. Any review, use,
> > >> > distribution
> > >> > or
> > >> > disclosure by others is strictly prohibited. If you are not the
> > >> > intended r

[vpp-dev] [FD.io Helpdesk #36114] Verify job failures due to external IP address lookup

[Vanessa Valderrama via RT]

Andrew,

I am looking into this failure now.

Thank you,
Vanessa

On Fri Feb 03 12:09:01 2017, ayour...@gmail.com wrote:
> Vanessa,
> 
> I had a failure just less than an hour ago, though it seems like a
> different issue, on a patch set that had verified yesterday
> successfully, after a comment-only change:
> 
> https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/3696/console
> 
> 16:23:28 Reading package lists...
> 16:23:28 Building dependency tree...
> 16:23:28 Reading state information...
> 16:23:28 Package pkg-config is not available, but is referred to by
> another package.
> 16:23:28 This may mean that the package is missing, has been
> obsoleted, or
> 16:23:28 is only available from another source
> 16:23:28
> 16:23:28 E: Package 'pkg-config' has no installation candidate
> 16:23:28 E: Unable to locate package chrpath
> 16:23:28 E: Unable to locate package default-jdk-headless
> 16:23:28 Makefile:167: recipe for target 'install-dep' failed
> 16:23:28 make: *** [install-dep] Error 100
> 16:23:28 Build step 'Execute shell' marked build as failure
> 16:23:28 [ssh-agent] Stopped.
> 16:23:29 Skipped archiving because build is not successful
> 16:23:29 [PostBuildScript] - Execution post build scripts.
> 
> And https://jenkins.fd.io/job/vpp-csit-verify-virl-master/3700/:
> 
> 16:24:28 Reading state information...
> 16:24:28 Package pkg-config is not available, but is referred to by
> another package.
> 16:24:28 This may mean that the package is missing, has been
> obsoleted, or
> 16:24:28 is only available from another source
> 16:24:28
> 16:24:28 E: Package 'pkg-config' has no installation candidate
> 16:24:28 E: Unable to locate package chrpath
> 16:24:28 E: Unable to locate package default-jdk-headless
> 16:24:28 Makefile:167: recipe for target 'install-dep' failed
> 16:24:28 make: *** [install-dep] Error 100
> 16:24:28 rm -f /w/workspace/vpp-csit-verify-virl-master/build-
> root/scripts/.version
> /w/workspace/vpp-csit-verify-virl-master/build-root/rpm/*.tar.gz
> 16:24:28 E: Package 'pkg-config' has no installation candidate
> 16:24:28 E: Unable to locate package chrpath
> 16:24:28 E: Unable to locate package default-jdk-headless
> 
> Anything I need to do on my side ?
> 
> --a
> 
> 
> On 2/2/17, Vanessa Valderrama via RT
> <fdio-helpd...@rt.linuxfoundation.org> wrote:
> > The following changes have resolved this issue:
> > https://gerrit.fd.io/r/#/c/4990/
> > https://gerrit.fd.io/r/#/c/4993/
> >
> > Builds are passing
> > vpp-verify-master-ubuntu1604
> > vpp-csit-verify-virl-master
> >
> > Thank you,
> > Vanessa
> >
> >
> > On Wed Feb 01 11:28:33 2017, valderrv wrote:
> >> We have opened a ticket with our vendor to investigate this issue.
> >>
> >> Thank you,
> >> Vanessa
> >>
> >> On Wed Feb 01 01:55:15 2017, matfa...@cisco.com wrote:
> >> > Hi,
> >> >
> >> > same issue https://gerrit.fd.io/r/#/c/4966/
> >> >
> >> > Regards,
> >> >
> >> >
> >> >
> >> >
> >> > Matus Fabian
> >> > Engineer - Software
> >> > matfa...@cisco.com<mailto:matfa...@cisco.com>
> >> > Tel:
> >> >
> >> > Cisco Systems, Inc.
> >> >
> >> >
> >> >
> >> > Slovakia
> >> > cisco.com
> >> >
> >> >
> >> > [http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> >> > before you print.
> >> >
> >> > This email may contain confidential and privileged material for
> >> > the
> >> > sole use of the intended recipient. Any review, use, distribution
> >> > or
> >> > disclosure by others is strictly prohibited. If you are not the
> >> > intended recipient (or authorized to receive for the recipient),
> >> > please contact the sender by reply email and delete all copies of
> >> > this
> >> > message.
> >> > Please click
> >> > here<http://www.cisco.com/web/about/doing_business/legal/cri/index.html>
> >> > for Company Registration Information.
> >> >
> >> >
> >> >
> >> > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-
> >> > boun...@lists.fd.io]
> >> > On Behalf Of Dave Wallace
> >> > Sent: Wednesday, February 1, 2017 4:25 AM
> >> > To: helpd...@fd.io
> >> > Cc: vpp-dev@lists.fd.io
> >> > Subject: [vpp-dev] Verify job failures due to ext

[vpp-dev] [FD.io Helpdesk #36114] Verify job failures due to external IP address lookup

[Vanessa Valderrama via RT]

The following changes have resolved this issue:
https://gerrit.fd.io/r/#/c/4990/
https://gerrit.fd.io/r/#/c/4993/

Builds are passing
vpp-verify-master-ubuntu1604
vpp-csit-verify-virl-master

Thank you,
Vanessa


On Wed Feb 01 11:28:33 2017, valderrv wrote:
> We have opened a ticket with our vendor to investigate this issue.
> 
> Thank you,
> Vanessa
> 
> On Wed Feb 01 01:55:15 2017, matfa...@cisco.com wrote:
> > Hi,
> >
> > same issue https://gerrit.fd.io/r/#/c/4966/
> >
> > Regards,
> >
> >
> >
> >
> > Matus Fabian
> > Engineer - Software
> > matfa...@cisco.com
> > Tel:
> >
> > Cisco Systems, Inc.
> >
> >
> >
> > Slovakia
> > cisco.com
> >
> >
> > [http://www.cisco.com/assets/swa/img/thinkbeforeyouprint.gif]Think
> > before you print.
> >
> > This email may contain confidential and privileged material for the
> > sole use of the intended recipient. Any review, use, distribution or
> > disclosure by others is strictly prohibited. If you are not the
> > intended recipient (or authorized to receive for the recipient),
> > please contact the sender by reply email and delete all copies of
> > this
> > message.
> > Please click
> > here
> > for Company Registration Information.
> >
> >
> >
> > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-
> > boun...@lists.fd.io]
> > On Behalf Of Dave Wallace
> > Sent: Wednesday, February 1, 2017 4:25 AM
> > To: helpd...@fd.io
> > Cc: vpp-dev@lists.fd.io
> > Subject: [vpp-dev] Verify job failures due to external IP address
> > lookup
> >
> > The following verify jobs are failing for
> > https://gerrit.fd.io/r/#/c/4897:
> >
> > https://jenkins.fd.io/job/vpp-verify-master-ubuntu1604/3568
> > https://jenkins.fd.io/job/vpp-csit-verify-virl-master/3572
> >
> > Both have the same error signature ("make install-dep" fails):
> >
> > 01:36:21 Err:1 http://ubuntu.mirror.vexxhost.com/ubuntu xenial-
> > security/main amd64 libssl-dev amd64 1.0.2g-1ubuntu4.6
> > 01:36:21   404  Not Found [IP: 162.253.53.24 80]
> > 01:36:21 Err:2 http://ubuntu.mirror.vexxhost.com/ubuntu xenial-
> > security/main amd64 libssl1.0.0 amd64 1.0.2g-1ubuntu4.6
> > 01:36:21   404  Not Found [IP: 162.253.53.24 80]
> > 01:36:21 Get:3 http://ubuntu.mirror.vexxhost.com/ubuntu
> > xenial/universe amd64 chrpath amd64 0.16-1 [12.9 kB]
> > 01:36:21 Get:4 http://ubuntu.mirror.vexxhost.com/ubuntu xenial/main
> > amd64 default-jre-headless amd64 2:1.8-56ubuntu2 [4,380 B]
> > 01:36:21 Get:5 http://ubuntu.mirror.vexxhost.com/ubuntu xenial/main
> > amd64 default-jdk-headless amd64 2:1.8-56ubuntu2 [986 B]
> > 01:36:21 Get:6 http://ubuntu.mirror.vexxhost.com/ubuntu xenial/main
> > amd64 pkg-config amd64 0.29.1-0ubuntu1 [45.0 kB]
> > 01:36:21 Fetched 63.3 kB in 0s (314 kB/s)
> > 01:36:21 W: --force-yes is deprecated, use one of the options
> > starting
> > with --allow instead.
> > 01:36:21 E: Failed to fetch
> > http://ubuntu.mirror.vexxhost.com/ubuntu/pool/main/o/openssl/libssl-
> > dev_1.0.2g-1ubuntu4.6_amd64.deb  404  Not Found [IP: 162.253.53.24
> > 80]
> > 01:36:21
> > 01:36:21 E: Failed to fetch
> > http://ubuntu.mirror.vexxhost.com/ubuntu/pool/main/o/openssl/libssl1.0.0_1.0.2g-
> > 1ubuntu4.6_amd64.deb  404  Not Found [IP: 162.253.53.24 80]
> > 01:36:21
> > 01:36:21 E: Unable to fetch some archives, maybe run apt-get update
> > or
> > try with --fix-missing?
> > 01:36:21 Makefile:166: recipe for target 'install-dep' failed
> > 01:36:21 make: *** [install-dep] Error 100
> >
> > "make verify" works fine with this patch set on a bare-metal Ubuntu
> > 16.10 desktop machine in my home network.
> >
> > Thanks,
> > -daw-



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

[vpp-dev] [FD.io Helpdesk #35627] 13:52:42 wget: unable to resolve host address ‘nexus.fd.io’

[Vanessa Valderrama via RT]

https://gerrit.fd.io/r/#/c/4754/1 unable to resolve jenkins.fd.io and 
nexus.fd.io in one build.  This is not an ongoing issue.

Logging https://gerrit.fd.io/r/#/c/4758/ in another RT since these are not 
related.

Thank you,
Vanessa

On Wed Jan 18 11:40:17 2017, alaga...@gmail.com wrote:
> https://gerrit.fd.io/r/#/c/4754/1
> 
> Also https://gerrit.fd.io/r/#/c/4758/ failed for some spurious reason.



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

[vpp-dev] [FD.io Helpdesk #31154] RE: [discuss] Complete - FD.io Maintenance

[Vanessa Valderrama via RT]

Peter,

Please let us know if you are still having these issues.

Thank you,
Vanessa

On Mon Oct 10 10:44:46 2016, valderrv wrote:
> Peter,
> 
> This issue is resolved.  This was a result of a vendor issue and the
> new version of Gerrit actively rejects the status messages that
> Jenkins is passing in because it always tries to set votes, which it
> can't do because the
> change is already merged / closed and so votes aren't accepted.
> 
> Thank you,
> Vanessa
> 
> 
> On Thu Oct 06 02:54:43 2016, pmi...@cisco.com wrote:
> > Hello,
> >
> > Currently we are not able to run any jobs (from gerrit) and also
> > there
> > are some job in queue without available slaves (pending)
> >
> > Can you please take a look?
> >
> > Thank you.
> >
> > Peter Mikus
> > Engineer – Software
> > Cisco Systems Limited
> >
> > From: discuss-boun...@lists.fd.io [mailto:discuss-
> > boun...@lists.fd.io]
> > On Behalf Of Vanessa Valderrama
> > Sent: Thursday, October 06, 2016 6:16 AM
> > To: it-infrastructure-ale...@linuxfoundation.org; infra-
> > steer...@lists.fd.io; disc...@lists.fd.io
> > Subject: [discuss] Complete - FD.io Maintenance
> >
> > Maintenance is complete.  Upgrades complete and services are now
> > available.
> >
> > Nexus Pro version 2.14.0-01
> > Gerrit version 2.13.1
> > Jenkins version 2.19.1
> >
> > Thank you,
> > Vanessa
> >
> >
> >
> > What:
> >
> > The Linux Foundation will be performing maintenance on the following
> > services: Nexus, Gerrit, and Jenkins
> >
> >
> > When:
> >
> > 2016-10-05 @ 18:00 - 21:00 PDT
> >
> >
> > Where:
> >
> > #fdio-infra at the start and end of the maintenance
> >
> >
> > Who:
> >
> > Vanessa Valderrama
> > 
> >
> > Andrew Grimeberg
> > 
> >
> >
> > Impact:
> >
> > The following systems will experience brief to semi-extended outages
> > depending on the service
> >
> > ·Nexus:https://nexus.fd.io
> >
> > ·Gerrit:  https://gerrit.fd.io
> >
> > ·Jenkins:  https://jenkins.fd.io
> >
> >
> > Why:
> >
> > 1. Nexus will be upgraded to Nexus Pro v2.13
> >
> > 2. Gerrit will be upgraded to v2.12
> >
> > 3. Jenkins will be upgraded to series 2.x



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