Re: [vpp-dev] gerrit.fd.io very slow?

[Lori Jakab]

On Wed, Jun 20, 2018 at 5:22 PM Dave Barach via Lists.Fd.Io  wrote:

> Before I start bugging the LF: is anyone else noticing bad performance w/
> gerrit.fd.io?
>

Their status page shows an LDAP issue:

https://status.linuxfoundation.org

-Lori


>
>
> Thanks... Dave
>
>
> 
>
>

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

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

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

[Lori Jakab]

Thanks!

On Thu, Nov 9, 2017 at 3:48 PM, Ed Warnicke <hagb...@gmail.com> wrote:

> https://gerrit.fd.io/r/#/c/9329/ fixed it.
>
> Ed
>
> On Wed, Nov 8, 2017 at 3:39 PM Vanessa Valderrama via RT <
> fdio-helpd...@rt.linuxfoundation.org> wrote:
>
>> 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.
>> > > > >>

Re: [vpp-dev] Merge jobs faiing

[Lori Jakab]

Hello,

Any update on this? We can't get the latest patches via the Ubuntu package
manager and that hurts certain test scenarios.

-Lori

On Mon, Nov 6, 2017 at 6:31 PM, Ed Warnicke  wrote:

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

Re: [vpp-dev] syntax error near unexpected token `g2,'

[Lori Jakab]

On Mon, Nov 6, 2017 at 4:09 PM, Florin Coras <fcoras.li...@gmail.com> wrote:

> Hi Lori,
>
> backup
> git clean -fdx
> make bootstrap
> make build
>
> Any luck?
>

Yes, and that's weird... the fresh git clone should be the same as the
result of `git clean -dfx`. The only reasonable explanation I have is that
I tried the boostrap before installing all deps, so maybe that put the tree
into a weird state...?

Thanks for the help, I should have tried git clean it myself :)

-Lori


>
> Florin
>
> On Nov 6, 2017, at 4:17 AM, Lori Jakab <lorand.jakab+f...@gmail.com>
> wrote:
>
> Hi,
>
> I see the exact same issue that is reported in a previous thread [0],
> which didn't have a solution. I wonder if anyone has more insight now.
>
> I did not use Vagrant to set up a VM with the build environment. On an
> Ubuntu 16.04 VM I clone VPP latest master, do a `make install-dep` and then
> a `make bootstrap`. This is what I get:
>
> [...]
> checking for LIBRTE_PMD_AESNI_MB in rte_config.h... no
> checking for LIBRTE_PMD_AESNI_GCM in rte_config.h... no
> checking for RTE_VERSION 17.02/17.05 in rte_version.h... no
> checking for LIBRTE_MLX4_PMD in rte_config.h... no
> checking for LIBRTE_MLX5_PMD in rte_config.h... no
> /home/vagrant/vpp/build-root/../src/configure: line 18206: syntax error
> near unexpected token `g2,'
> /home/vagrant/vpp/build-root/../src/configure: line 18206: `
>  PKG_CHECK_MODULES(g2, gtk+-2.0)'
> Makefile:635: recipe for target 'tools-configure' failed
> make[1]: *** [tools-configure] Error 2
> make[1]: Leaving directory '/home/vagrant/vpp/build-root'
> Makefile:226: recipe for target '/home/vagrant/vpp/build-root/.bootstrap.ok'
> failed
> make: *** [/home/vagrant/vpp/build-root/.bootstrap.ok] Error 2
>
> No idea what package may I be missing.
>
> -Lori
>
> [0] https://lists.fd.io/pipermail/vpp-dev/2017-March/004543.html
> ___
> 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] syntax error near unexpected token `g2,'

[Lori Jakab]

Hi,

I see the exact same issue that is reported in a previous thread [0], which
didn't have a solution. I wonder if anyone has more insight now.

I did not use Vagrant to set up a VM with the build environment. On an
Ubuntu 16.04 VM I clone VPP latest master, do a `make install-dep` and then
a `make bootstrap`. This is what I get:

[...]
checking for LIBRTE_PMD_AESNI_MB in rte_config.h... no
checking for LIBRTE_PMD_AESNI_GCM in rte_config.h... no
checking for RTE_VERSION 17.02/17.05 in rte_version.h... no
checking for LIBRTE_MLX4_PMD in rte_config.h... no
checking for LIBRTE_MLX5_PMD in rte_config.h... no
/home/vagrant/vpp/build-root/../src/configure: line 18206: syntax error
near unexpected token `g2,'
/home/vagrant/vpp/build-root/../src/configure: line 18206: `
 PKG_CHECK_MODULES(g2, gtk+-2.0)'
Makefile:635: recipe for target 'tools-configure' failed
make[1]: *** [tools-configure] Error 2
make[1]: Leaving directory '/home/vagrant/vpp/build-root'
Makefile:226: recipe for target
'/home/vagrant/vpp/build-root/.bootstrap.ok' failed
make: *** [/home/vagrant/vpp/build-root/.bootstrap.ok] Error 2

No idea what package may I be missing.

-Lori

[0] https://lists.fd.io/pipermail/vpp-dev/2017-March/004543.html
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] Can't install honeycomb master package from nexus on xenial

[Lori Jakab]

On Tue, Aug 1, 2017 at 1:46 PM, Jan Srnicek -X (jsrnicek - PANTHEON
TECHNOLOGIES at Cisco) <jsrni...@cisco.com> wrote:

> Hi lori
>
>
>
> This is known issue with apt-get , as honeycomb packages have compatible
> vpp version defined ,but apt-get attempts to download the newest one.
>
>
>
> To solve this , you need to first install vpp like so:
>
>
>
> sudo apt-get install vpp=VERSION vpp-lib= VERSION vpp-plugins= VERSION
>
>
>
> and then install honeycomb
>

I have the installation as part of a script of a Vagrantfile, so I prefer
not to hardcode version numbers, but having seen the "Merge job failing"
thread you started confirms that this is an anomaly, and it will get fixed
eventually.

Thanks!

-Lori


>
>
> [image: banner11]
>
>
>
> *Jan Srnicek*
>
> Engineer - Software
>
> jsrni...@cisco.com
>
> Tel:
>
> *Cisco Systems, Inc.*
>
>
>
>
> Slovakia
> cisco.com
>
>
>
> [image: 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 *Lori Jakab
> *Sent:* Tuesday, August 1, 2017 10:08 AM
> *To:* vpp-dev@lists.fd.io; hc2vpp-...@lists.fd.io
> *Cc:* Florin Coras (fcoras) <fco...@cisco.com>
> *Subject:* [vpp-dev] Can't install honeycomb master package from nexus on
> xenial
>
>
>
> Hi,
>
>
>
> I'm trying to install honeycomb on Ubuntu Xenial, after having added '
> https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main'
> to the repository list. When installing honeycomb, I get the following
> error:
>
>
>
> The following packages have unmet dependencies:
>
>  honeycomb : Depends: vpp (= 17.10-rc0~95-g6881062~b2627) but
> 17.10-rc0~101-g5b31120~b2635 is to be installed
>
>  Depends: vpp-plugins (= 17.10-rc0~95-g6881062~b2627) but
> 17.10-rc0~101-g5b31120~b2635 is to be installed
>
>
>
> Is there an easy way to solve this? Maybe a honeycomb artifact publication
> job is failing?
>
>
>
> Thanks,
>
> -Lori
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Can't install honeycomb master package from nexus on xenial

[Lori Jakab]

Hi,

I'm trying to install honeycomb on Ubuntu Xenial, after having added '
https://nexus.fd.io/content/repositories/fd.io.master.ubuntu.xenial.main'
to the repository list. When installing honeycomb, I get the following
error:

The following packages have unmet dependencies:
 honeycomb : Depends: vpp (= 17.10-rc0~95-g6881062~b2627) but
17.10-rc0~101-g5b31120~b2635 is to be installed
 Depends: vpp-plugins (= 17.10-rc0~95-g6881062~b2627) but
17.10-rc0~101-g5b31120~b2635 is to be installed

Is there an easy way to solve this? Maybe a honeycomb artifact publication
job is failing?

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

Re: [vpp-dev] The Case Of the Missing API Definition

[Lori Jakab]

On Wed, May 24, 2017 at 6:21 PM, Jon Loeliger  wrote:

> On Wed, May 24, 2017 at 2:00 AM,   wrote:
> > Hi Jon,
>
> Hi Ole,
>
> > Thanks for the poetry! ;-)
>
> Most welcome.
>
> > This is me in 01384fe
> > Apologies for that. Next time I see you let me bring both band aid and
> whiskey.
>
> Apology accepted!
>
> > To my excuse, there has been this list of "broken" APIs maintained by the
> > Python and Java language binding implementors.
>
> See?  Java is bad for you. :-)
>
> > It's been on the todo list for a long time and I finally found some time
> to
> > deal with them. Obviously not everyone was aware of those planned
> > changes. I did include those I thought affected as code reviewers. #fail.
>
> It's OK, really.  I've been making a pretty systematic march
> through many of the VPP API areas, so there's no telling what
> or where I'll be poking next... :-)
>
> > I feel your pain. How can we make this better?
> > 1) Never change APIs, regardless the reason
> > 2) Announce and discuss changes a priori. Separate mailing list for
> > API changes?
> > {vpp-users, vpp-api-announce}
> > 3) ...
>
> This is a really good question.  I confess it is also a difficult one.
> We certainly can't abide by 1) Never change APIs.  That is just not
> a realistic approach.
>
> I follow the vpp-dev list pretty regularly these days, and I try
> to watch the upcoming Gerrit patches and reviews.  And I try
> to keep our VPP repo up-to-date WRT the fd.io Git repo; I pull
> maybe every couple days or so.
>
> So for me, I am willing to suffer a bit of tip-of-tree development
> pain and angst.  Even fixing this API call removal wasn't that
> difficult for our code.
>
> I think the thing that was most troubling for me was getting it
> pretty much without warning.  So I think at the very least, it
> would be good to make a statement on the vpp-dev list.
>
> But when?  Certainly it would be nice if it were in advance of
> the patch being committed.  I realize that may not always be
> possible.  But some indication on the list as it is being committed
> would also be nice.  Maybe even some indication from the patch
> author on list like "Hey, I have a patch in review that removes
> *this* API call.  If you are using it you will need to change your
> code like _this_."
>
> The process of adding API calls, and even changing an existing
> one is easier, of course.  But still, some advance notice would
> be appreciated.
>
> How hard would it be to have a Jenkins nightly build job that
> diff'ed yesterday's complete API list versus today's list and
> generated sent that diff mail?  Dunno.  Just an idea.
>

In the OpenDaylight community we have something called the "Weather" page
on the wiki [0], where information about potentially disruptive patches is
posted, then the link posted on one of the mailing list with "[WEATHER]" in
the subject so that it stands out and can be filtered. I would say it
worked reasonably well for us, maybe it's worth a try?

Then again, this approach was useful because we have many different
projects and tons of mailing lists, FD.io being more focused it may be
overkill.

HTH,
-Lori

[0] https://wiki.opendaylight.org/view/Weather


>
> > Do we reach everyone using vpp on  vpp-dev and a heads-up there
> > would suffice?
>
> Quite possibly.  I don't really have a feel for how many people
> use each of the various APIs for active development these days.
> It may very well justify a specific vpp-api-discussion list or so.
>
> > Cheers,
> > Ole
>
> HTH,
> jdl
> ___
> 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