Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-05 Thread Vijay Bellur
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

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-05 Thread Justin Clift
On 5 May 2015, at 03:40, Jeff Darcy jda...@redhat.com 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

[Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Vijay Bellur
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

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Justin Clift
On 4 May 2015, at 08:06, Vijay Bellur vbel...@redhat.com 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*

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Pranith Kumar Karampuri
On 05/05/2015 12:58 AM, Justin Clift wrote: On 4 May 2015, at 08:06, Vijay Bellur vbel...@redhat.com 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

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Pranith Kumar Karampuri
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 vbel...@redhat.com wrote: Hi All, There has been a spate of regression test failures (due to broken tests or race conditions showing up) in the recent

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Pranith Kumar Karampuri
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

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Pranith Kumar Karampuri
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

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Jeff Darcy
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. ___

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Jeff Darcy
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.

Re: [Gluster-devel] Regression test failures - Call for Action

2015-05-04 Thread Jeff Darcy
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 to