Re: [Gluster-devel] lock_revocation.t is hanging in regression tests

I think this should be disabled for now. See past context here [1] [2], I guess this not being reported as a failure is causing the attention lapse. [1] http://lists.gluster.org/pipermail/gluster-devel/2017-March/052287.html [2]

[Gluster-devel] lock_revocation.t is hanging in regression tests

After seeing this hang with multiplexing enabled yesterday, I saw it hang a test for a completely unrelated patch (https://review.gluster.org/17200) without multiplexing. Does anyone object to disabling this test while it's debugged? ___ Gluster-devel

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 9:01 PM, Sankarshan Mukhopadhyay < sankarshan.mukhopadh...@gmail.com> wrote: > On Tue, May 9, 2017 at 8:50 PM, Niels de Vos wrote: > > [much snipping] > > > A but related to this, but is Stack Overflow not *the* place to ask and > > answer questions?

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 8:50 PM, Niels de Vos wrote: [much snipping] > A but related to this, but is Stack Overflow not *the* place to ask and > answer questions? There even is a "glusterfs" tag, and questions and > answers can be marked even better than with GitHub (imho): >

Re: [Gluster-devel] Questions on github

On 05/09/2017 10:51 AM, Pranith Kumar Karampuri wrote: On Tue, May 9, 2017 at 7:27 PM, Sankarshan Mukhopadhyay > wrote: On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri

Re: [Gluster-devel] Questions on github

On Tue, May 09, 2017 at 08:21:54PM +0530, Pranith Kumar Karampuri wrote: > On Tue, May 9, 2017 at 7:27 PM, Sankarshan Mukhopadhyay < > sankarshan.mukhopadh...@gmail.com> wrote: > > > On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri > > wrote: > > > > > > > > > On Tue,

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 8:21 PM, Pranith Kumar Karampuri wrote: > People who respond on gluster-users do this already. Github issues is a > better tool to do this (Again IMHO). It is a bit easier to know what > questions are still open to be answered with github. Even after

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 7:27 PM, Sankarshan Mukhopadhyay < sankarshan.mukhopadh...@gmail.com> wrote: > On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri > wrote: > > > > > > On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay > >

[Gluster-devel] Meeting minutes for Gluster Bug Triage Meeting held on 9th May 2017

Hi All, The meeting minutes and logs for this weeks meeting are available at the links below.Minutes: Minutes: https://meetbot.fedoraproject.org/gluster-meeting/2017-05-09/weely_gluster_bug_triage.2017-05-09-12.01.html Minutes (text):

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri wrote: > > > On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay > wrote: >> >> On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi wrote: >> > I personally prefer

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 7:09 PM, Sankarshan Mukhopadhyay < sankarshan.mukhopadh...@gmail.com> wrote: > On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi wrote: > > I personally prefer github questions than mailing list, because a valid > > question can later become a reason for a

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi wrote: > I personally prefer github questions than mailing list, because a valid > question can later become a reason for a new feature. Also, as you said, we > can 'assignee' a question and if we start with bug triage we can also

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 4:43 PM, Shyam wrote: > Hi, > > I would first like to see the habit of developers filing github issues for > features that they are working on and are also thinking about in the near > future. > > When we have that practice in place, taking it forward

Re: [Gluster-devel] Empty info file preventing glusterd from starting

Actually it is very risky if it will reproduce in production thats is why I said it is on high priority as want to resolve it before production. On Tue, May 9, 2017 at 6:20 PM, Atin Mukherjee wrote: > > > On Tue, May 9, 2017 at 6:10 PM, ABHISHEK PALIWAL

Re: [Gluster-devel] Empty info file preventing glusterd from starting

On Tue, May 9, 2017 at 6:10 PM, ABHISHEK PALIWAL wrote: > Hi Atin, > > Thanks for your reply. > > > Its urgent because this error is very rarely reproducible we have seen > this 2 3 times in our system till now. > > We have delivery in near future so that we want it

Re: [Gluster-devel] Empty info file preventing glusterd from starting

Hi Atin, Thanks for your reply. Its urgent because this error is very rarely reproducible we have seen this 2 3 times in our system till now. We have delivery in near future so that we want it asap. Please try to review it internally. Regards, Abhishek On Tue, May 9, 2017 at 5:58 PM, Atin

[Gluster-devel] Coverity covscan for 2017-05-09-2ff39c5c (master branch)

GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2017-05-09-2ff39c5c ___ Gluster-devel mailing list Gluster-devel@gluster.org

Re: [Gluster-devel] Empty info file preventing glusterd from starting

On Tue, May 9, 2017 at 3:37 PM, ABHISHEK PALIWAL wrote: > + Muthu-vingeshwaran > > On Tue, May 9, 2017 at 11:30 AM, ABHISHEK PALIWAL > wrote: > >> Hi Atin/Team, >> >> We are using gluster-3.7.6 with setup of two brick and while restart of >>

Re: [Gluster-devel] Questions on github

On Tue, May 09, 2017 at 03:30:43PM +0530, Pranith Kumar Karampuri wrote: > On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi wrote: > > > I personally prefer github questions than mailing list, because a valid > > question can later become a reason for a new feature. Also, as

Re: [Gluster-devel] Questions on github

Hi, I would first like to see the habit of developers filing github issues for features that they are working on and are also thinking about in the near future. When we have that practice in place, taking it forward for bugs, and questions would work better. Currently we are still on the

Re: [Gluster-devel] Empty info file preventing glusterd from starting

+ Muthu-vingeshwaran On Tue, May 9, 2017 at 11:30 AM, ABHISHEK PALIWAL wrote: > Hi Atin/Team, > > We are using gluster-3.7.6 with setup of two brick and while restart of > system I have seen that the glusterd daemon is getting failed from start. > > > At the time of

Re: [Gluster-devel] Questions on github

On Tue, May 9, 2017 at 3:18 PM, Amar Tumballi wrote: > I personally prefer github questions than mailing list, because a valid > question can later become a reason for a new feature. Also, as you said, we > can 'assignee' a question and if we start with bug triage we can

Re: [Gluster-devel] Questions on github

I personally prefer github questions than mailing list, because a valid question can later become a reason for a new feature. Also, as you said, we can 'assignee' a question and if we start with bug triage we can also make sure at least we respond to questions which is pending. A note of caution,

[Gluster-devel] Questions on github

hi, Wanted to know what people feel about asking/answering questions on github.com, at the moment we are only using github for RFEs, I am wondering if it would be fine to open it for questions too. Main benefit I see is that it is easier to see open-questions at a glance and easy to direct

[Gluster-devel] Empty info file preventing glusterd from starting

Hi Atin/Team, We are using gluster-3.7.6 with setup of two brick and while restart of system I have seen that the glusterd daemon is getting failed from start. At the time of analyzing the logs from etc-glusterfs...log file I have received the below logs [2017-05-06 03:33:39.798087] I