/#/c/37131/, add a
comment recheck bug 1197476 which will basically re-run the jenkins
tests and update the rechecks page with your review number.
See here for more info -
https://wiki.openstack.org/wiki/GerritJenkinsGit#Test_Failures
-- dims
On Mon, Sep 9, 2013 at 6:40 PM, Baldwin, Carl (HPCS
Hi all,
https://review.openstack.org/#/c/37131/
This review has been consistently marked as fail for the last three patch
sets. I'm scratching my head over how the failure is related to the
patch. Can anyone lend some insight? Is this a known failure that is not
caused by my patch or is this
Hi all,
This bug was marked as fix released for H-3. However, the fix that was
merged was reverted due to gate breakage. The patch was resubmitted as
https://review.openstack.org/#/c/42412/ and fixes the gate breakage but
this new patch has not been merged. So, the bug state of Yix released
is
#Test_Failures
-- dims
On Mon, Sep 9, 2013 at 6:40 PM, Baldwin, Carl (HPCS Neutron)
carl.bald...@hp.commailto:carl.bald...@hp.com wrote:
Hi all,
https://review.openstack.org/#/c/37131/
This review has been consistently marked as fail for the last three patch
sets. I'm scratching my head over how
2013/9/5 Baldwin, Carl (HPCS Neutron) carl.bald...@hp.com:
Brian,
As far as I know, no consensus was reached.
A problem was discovered that happens when spawning multiple processes.
The mysql connection seems to go away after between 10-60 seconds in my
testing causing a seemingly random API
in db/api.py.
在 2013年9月6日星期五，Nachi Ueno 写道：
Hi Folks
We choose https://review.openstack.org/#/c/37131/ -- This patch to go on.
We are also discussing in this patch.
Best
Nachi
2013/9/5 Baldwin, Carl (HPCS Neutron) carl.bald...@hp.com:
Brian,
As far as I know, no consensus was reached
, it seemed).
Is it realistically looking like this patch will be cut for h3?
--
Brian Cline
Software Engineer III, Product Innovation
SoftLayer, an IBM Company
4849 Alpha Rd, Dallas, TX 75244
214.782.7876 direct | bcl...@softlayer.com
-Original Message-
From: Baldwin, Carl (HPCS Neutron
On 8/28/13 11:28 AM, Vishvananda Ishaya vishvana...@gmail.com wrote:
On Aug 26, 2013, at 6:14 PM, Maru Newby ma...@redhat.com wrote:
On Aug 26, 2013, at 4:06 PM, Edgar Magana emag...@plumgrid.com wrote:
Hi Developers,
Let me explain my point of view on this topic and please share your
Salvatore,
Two problems have been found that were caused by calling empty_chain and
then failing to restore some rule in the chain that was just emptied. The
first problem found was mine in my fix to this bug.
https://bugs.launchpad.net/neutron/+bug/1209011
I filed a bug on the second
All,
We've known for a while now that some duplication of work happened with
respect to adding multiple worker processes to the neutron-server. There
were a few mistakes made which led to three patches being done
independently of each other.
Can we settle on one and accept it?
I have changed
10 matches
Mail list logo
