On 2016-05-13 12:53:36 + (+), Amrith Kumar wrote:
> The interwebs must've been in need of some pluming work ...
[...]
If this ran in rax-ord then it's a known long-standing issue for us.
I've had a support ticket open with them for weeks (since well
before the summit) trying to get to the
The interwebs must've been in need of some pluming work ...
2016-05-13 06:09:37.457 | git.exc.GitCommandError: 'git remote prune --dry-run
origin' returned with exit code 128
2016-05-13 06:09:37.457 | stderr: 'fatal: unable to connect to
git.openstack.org:
2016-05-13 06:09:37.457 | git.openstack
On Wed, Apr 06, 2016 at 10:08:44AM +, Amrith Kumar wrote:
> Stable team, the reason for this failure of py27 in kilo is
>
> https://bugs.launchpad.net/trove/+bug/1437179
>
> The bug was fixed in liberty in commit
> I92eaa1c98f5a58ce124210f2b6a2136dfc573a29 and therefore, at this time,
Stable team, the reason for this failure of py27 in kilo is
https://bugs.launchpad.net/trove/+bug/1437179
The bug was fixed in liberty in commit
I92eaa1c98f5a58ce124210f2b6a2136dfc573a29 and therefore, at this time, only
impacts Kilo.
The issue is that the flavors are coming back in a
Subject: Re: [openstack-dev] [Openstack-stable-maint] Stable check of
> openstack/trove failed
>
> On 2016-03-28 11:52:12 + (+), Amrith Kumar wrote:
> > I ran this manually on stable/mitaka and it succeeded. The errors
> > being reported are "database is locked".
On 2016-03-28 11:52:12 + (+), Amrith Kumar wrote:
> I ran this manually on stable/mitaka and it succeeded. The errors
> being reported are "database is locked". Is this something in the
> infrastructure or do you want me to investigate further?
It would probably be good to determine whethe
I ran this manually on stable/mitaka and it succeeded. The errors being
reported are "database is locked". Is this something in the infrastructure or
do you want me to investigate further?
-amrith
> -Original Message-
> From: A mailing list for the OpenStack Stable Branch test reports.
I just ran stable/liberty through these tests on a sandbox and they passed. I'm
not sure what caused this failure but if it persists, I'll take another look.
Some changes are coming soon on master and I'll backport them to mitaka and
liberty. They'll make debugging these tests a whole lot easier
Hi Amrith,
Thanks for keeping an eye on the periodic jobs :)
On Fri, Mar 18, 2016 at 01:01:10PM +, Amrith Kumar wrote:
> I just ran stable/liberty through these tests on a sandbox and they passed.
> I'm not sure what caused this failure but if it persists, I'll take another
> look.
Good
This (likely) relates to a change made on master. I'm looking into it.
-amrith
--
Amrith Kumar, CTO | amr...@tesora.com
Tesora, Inc | @amrithkumar
125 CambridgePark Drive, Suite 400 | http://www.tesora.com
Cambridge, MA. 02140| GPG: 0x5e4
10 matches
Mail list logo
