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]
http://lists.gluster.org/pipermail/gluster-devel/2017-February/
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 ma
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? There even is a "gluste
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):
>
> https://stackoverf
On 05/09/2017 10:51 AM, Pranith Kumar Karampuri wrote:
On Tue, May 9, 2017 at 7:27 PM, Sankarshan Mukhopadhyay
mailto:sankarshan.mukhopadh...@gmail.com>> wrote:
On Tue, May 9, 2017 at 7:21 PM, Pranith Kumar Karampuri
mailto:pkara...@redhat.com>> wrote:
>
>
> On Tue, May 9,
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, May 9, 2017 at 7:09 P
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 multiple
> responses on
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
> > wrote:
> >>
> >> On Tue, May 9, 2017 at 3:18 PM, Amar Tum
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):
https://meetbot.fedoraproject.org/gluster-meeting/2017-05-09/we
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 github questions than mailing list, because a valid
>> > question can later be
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 new feature. Also, as
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 make
> sure at least
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 for bugs, and
> questi
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
> wrote:
>
>> Hi Atin,
>>
>> Thanks for y
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 asap. Please try to
> review i
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 Muk
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
http://lists.gluster.org/mailman
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
>> system I have seen that the glusterd daemon is getting
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 you said, we
> > can 'as
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 g
+ 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 analyzing the logs from etc-g
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 make
> sure at least
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,
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
some
24 matches
Mail list logo