On 01/11/2016 01:00 PM, Pranith Kumar Karampuri wrote:
On 01/09/2016 12:34 AM, Vijay Bellur wrote:
On 01/08/2016 08:18 AM, Jeff Darcy wrote:
I think we just need to come up with rules for considering a
platform to have voting ability before merging the patch.
I totally agree,
On 01/09/2016 12:34 AM, Vijay Bellur wrote:
On 01/08/2016 08:18 AM, Jeff Darcy wrote:
I think we just need to come up with rules for considering a
platform to have voting ability before merging the patch.
I totally agree, except for the "just" part. ;) IMO a platform is much
> On 01/07/2016 02:39 PM, Emmanuel Dreyfus wrote:
> > On Wed, Jan 06, 2016 at 05:49:04PM +0530, Ravishankar N wrote:
> >> I re triggered NetBSD regressions for
> >> http://review.gluster.org/#/c/13041/3
> >> but they are being run in silent mode and are not completing. Can some one
> >> from the
On 01/08/2016 09:57 AM, Emmanuel Dreyfus wrote:
I am a bit disturbed by the fact that people raise the
"NetBSD regression ruins my life" issue without doing the work of
listing the actual issues encountered.
I already did earlier- the lack of infrastructure to even find out what
caused the
Emmanuel Dreyfus wrote:
> While trying to reproduce the problem in
> ./tests/basic/afr/arbiter-statfs.t, I came to many failures here:
>
> [03:53:07] ./tests/basic/afr/split-brain-resolution.t
I was running tests from wrong directory :-/
This one is fine with HEAD.
--
On Fri, Jan 08, 2016 at 11:45:20AM +0530, Pranith Kumar Karampuri wrote:
> 1) How to set up NetBSD VMs on my laptop which is of exact version as the
> ones that are run on build systems.
Well, the easier way is to pick the VM image we run at rackspace, which
relies on Xen. If you use an hardware
On Fri, Jan 08, 2016 at 12:42:36PM +0530, Sachidananda URS wrote:
> I have a NetBSD 7.0 installation which I can share with you, to get
> started.
> Once manu@ gets back on a specific version, I can set that up too.
NetBSD 7.0 is fine and has everything required in GENERIC kernel.
--
Emmanuel
On 01/08/2016 03:25 PM, Emmanuel Dreyfus wrote:
On Fri, Jan 08, 2016 at 03:18:02PM +0530, Pranith Kumar Karampuri wrote:
Should the cleanup script needs to be manually executed on the NetBSD
machine?
You can run the script manually, but if the goal is to restore a
misbehaving machine,
Emmanuel Dreyfus wrote:
> > With your support I think we can make things better. To avoid duplication of
> > work, did you take any tests that you are already investigating? If not that
> > is the first thing I will try to find out.
>
> I will look at the
Pranith Kumar Karampuri wrote:
> With your support I think we can make things better. To avoid
> duplication of work, did you take any tests that you are already
> investigating? If not that is the first thing I will try to find out.
While trying to reproduce the problem
On 01/08/2016 02:08 PM, Emmanuel Dreyfus wrote:
On Fri, Jan 08, 2016 at 11:45:20AM +0530, Pranith Kumar Karampuri wrote:
1) How to set up NetBSD VMs on my laptop which is of exact version as the
ones that are run on build systems.
Well, the easier way is to pick the VM image we run at
On Fri, Jan 08, 2016 at 03:18:02PM +0530, Pranith Kumar Karampuri wrote:
> Should the cleanup script needs to be manually executed on the NetBSD
> machine?
You can run the script manually, but if the goal is to restore a
misbehaving machine, rebooting is probbaly the fastest way to sort
the
On 01/08/2016 03:57 PM, Emmanuel Dreyfus wrote:
On Fri, Jan 08, 2016 at 05:11:22AM -0500, Jeff Darcy wrote:
[08:45:57] ./tests/basic/afr/arbiter-statfs.t ..
[08:43:03] ./tests/basic/afr/arbiter-statfs.t ..
[08:40:06] ./tests/basic/afr/arbiter-statfs.t ..
[08:08:51]
- Original Message -
> On Fri, Jan 08, 2016 at 05:11:22AM -0500, Jeff Darcy wrote:
> > [08:45:57] ./tests/basic/afr/arbiter-statfs.t ..
> > [08:43:03] ./tests/basic/afr/arbiter-statfs.t ..
> > [08:40:06] ./tests/basic/afr/arbiter-statfs.t ..
> > [08:08:51]
> If you do not
> prevent integration of patches that break NetBSD regression, that will get
> in, and tests will break one by one over time.
On the other hand, if patch A starts blocking all merges because of
NetBSD
de...@gluster.org>, "gluster-infra"
> <gluster-infra@gluster.org>
> Sent: Thursday, January 7, 2016 1:53:47 PM
> Subject: Re: [Gluster-devel] [Gluster-infra] NetBSD tests not running to
> completion.
>
> I have been always with this approach right f
On 01/07/2016 03:15 PM, Jeff Darcy wrote:
If you do not
prevent integration of patches that break NetBSD regression, that will get
in, and tests will break one by one over time.
On the other hand, if patch A starts blocking all merges because of
NetBSD failures, then all platforms - including
On Thu, Jan 07, 2016 at 03:01:41PM +0530, Avra Sengupta wrote:
> Why is this a bad idea?
Because each week you will have multiple regressins introduced. Few
people will be willing to investigate wether they pushed a patch that
caused a regression, and that few people will have to deal the others
- Original Message -
> From: "Pranith Kumar Karampuri"
> To: "Emmanuel Dreyfus" , "Ravishankar N"
>
> Cc: "Gluster Devel" , "gluster-infra"
>
> Sent: Friday, January 8,
On 01/07/2016 02:39 PM, Emmanuel Dreyfus wrote:
On Wed, Jan 06, 2016 at 05:49:04PM +0530, Ravishankar N wrote:
I re triggered NetBSD regressions for http://review.gluster.org/#/c/13041/3
but they are being run in silent mode and are not completing. Can some one
from the infra-team take a
Avra Sengupta wrote:
> Agree with your point. If we are ready to make exceptions, then we might
> as well not block all the patches. As Jeff suggested, triaging the
> nightly/weekly results manually and making any serious issues a blocker
> should suffice.
How are you
21 matches
Mail list logo