Justin Clift wrote:
> This kind of error message at the end of a failure log indicates
> the VM has self-disconnected from Jenkins and needs rebooting.
> Haven't found any other way to fix it. :/
If the connexion is dropped, this means there is something that sends a
TCP RST. Perhaps we could ru
On 5 May 2015, at 03:40, Jeff Darcy wrote:
Jeff's patch failed again with same problem:
>> http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/4531/console
>
> Wouldn't have expected anything different. This one looks like a
> problem in the Jenkins/Gerrit infrastructure.
This k
On 05/05/2015 08:13 AM, Pranith Kumar Karampuri wrote:
On 05/05/2015 08:10 AM, Jeff Darcy wrote:
Jeff's patch failed again with same problem:
http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/4531/console
Wouldn't have expected anything different. This one looks like a
prob
On 05/05/2015 08:10 AM, Jeff Darcy wrote:
Jeff's patch failed again with same problem:
http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/4531/console
Wouldn't have expected anything different. This one looks like a
problem in the Jenkins/Gerrit infrastructure.
Sorry for the
> Jeff's patch failed again with same problem:
> http://build.gluster.org/job/rackspace-netbsd7-regression-triggered/4531/console
Wouldn't have expected anything different. This one looks like a
problem in the Jenkins/Gerrit infrastructure.
___
Gluster-
Just saw two more failures in the same place for netbsd regressions. I
am ignoring NetBSD status for the test fixes for now. I am not sure how
this needs to be fixed. Please help!
Pranith
On 05/05/2015 07:17 AM, Pranith Kumar Karampuri wrote:
On 05/05/2015 06:12 AM, Pranith Kumar Karampuri wr
On 05/05/2015 06:12 AM, Pranith Kumar Karampuri wrote:
On 05/05/2015 12:58 AM, Justin Clift wrote:
On 4 May 2015, at 08:06, Vijay Bellur wrote:
Hi All,
There has been a spate of regression test failures (due to broken
tests or race conditions showing up) in the recent past [1] and I am
in
On 05/05/2015 12:58 AM, Justin Clift wrote:
On 4 May 2015, at 08:06, Vijay Bellur wrote:
Hi All,
There has been a spate of regression test failures (due to broken tests or race
conditions showing up) in the recent past [1] and I am inclined to block 3.7.0
GA along with acceptance of patches
> Also, one of us should
> go through the last however-many failures and determine the relative
> frequency of failures caused by each test, so we can prioritize.
I started doing this, and very quickly found a runaway "winner" -
data-self-heal.t, which also happens to be the very first test we
run
> There has been a spate of regression test failures (due to broken tests
> or race conditions showing up) in the recent past [1] and I am inclined
> to block 3.7.0 GA along with acceptance of patches until we fix *all*
> regression test failures. We seem to have reached a point where this
> seems
On 4 May 2015, at 08:06, Vijay Bellur wrote:
> Hi All,
>
> There has been a spate of regression test failures (due to broken tests or
> race conditions showing up) in the recent past [1] and I am inclined to block
> 3.7.0 GA along with acceptance of patches until we fix *all* regression test
>
Hi All,
There has been a spate of regression test failures (due to broken tests
or race conditions showing up) in the recent past [1] and I am inclined
to block 3.7.0 GA along with acceptance of patches until we fix *all*
regression test failures. We seem to have reached a point where this
se
12 matches
Mail list logo
