On Tue, Nov 22, 2016 at 6:48 AM, Poornima Gurusiddaiah
wrote:
> Hi,
>
> Have posted a fix for hang in read : http://review.gluster.org/15901
> I think, it will fix the issue reported here. Please check the commit
> message of the patch
> for more details.
>
Thank you for the
la...@redhat.com>
> To: "Raghavendra Gowdappa" <rgowd...@redhat.com>
> Cc: "Gluster Devel" <gluster-devel@gluster.org>
> Sent: Tuesday, November 22, 2016 3:23:59 AM
> Subject: Re: [Gluster-devel] Upstream smoke test failures
> On 22 November 2
- Original Message -
> From: "Vijay Bellur" <vbel...@redhat.com>
> To: "Nithya Balachandran" <nbala...@redhat.com>
> Cc: "Gluster Devel" <gluster-devel@gluster.org>
> Sent: Wednesday, November 16, 2016 9:41:12 AM
> Subjec
On Tue, Nov 15, 2016 at 8:40 AM, Nithya Balachandran
wrote:
>
>
> On 15 November 2016 at 18:55, Vijay Bellur wrote:
>>
>> On Mon, Nov 14, 2016 at 10:34 PM, Nithya Balachandran
>> wrote:
>> >
>> >
>> > On 14 November 2016 at 21:38,
On 15 November 2016 at 18:55, Vijay Bellur wrote:
> On Mon, Nov 14, 2016 at 10:34 PM, Nithya Balachandran
> wrote:
> >
> >
> > On 14 November 2016 at 21:38, Vijay Bellur wrote:
> >>
> >> I would prefer that we disable dbench only if
On Mon, Nov 14, 2016 at 10:34 PM, Nithya Balachandran
wrote:
>
>
> On 14 November 2016 at 21:38, Vijay Bellur wrote:
>>
>> I would prefer that we disable dbench only if we have an owner for
>> fixing the problem and re-enabling it as part of smoke tests.
On Tue, Nov 15, 2016 at 9:04 AM, Nithya Balachandran
wrote:
>
>
> On 14 November 2016 at 21:38, Vijay Bellur wrote:
>
>> I would prefer that we disable dbench only if we have an owner for
>> fixing the problem and re-enabling it as part of smoke tests.
I would prefer that we disable dbench only if we have an owner for
fixing the problem and re-enabling it as part of smoke tests. Running
dbench seamlessly on gluster has worked for a long while and if it is
failing today, we need to address this regression asap.
Does anybody have more context or
Does this mean race conditions are in master and are just being retried until
they're not hit?
On November 13, 2016 9:33:51 PM PST, Nithya Balachandran
wrote:
>Hi,
>
>Our smoke tests have been failing quite frequently of late. While
>re-triggering smoke several times in
On Mon, Nov 14, 2016 at 11:09 AM, Nigel Babu wrote:
> On Mon, Nov 14, 2016 at 11:03:51AM +0530, Nithya Balachandran wrote:
> > Hi,
> >
> > Our smoke tests have been failing quite frequently of late. While
> > re-triggering smoke several times in order to get a +1 works
On Mon, Nov 14, 2016 at 11:03:51AM +0530, Nithya Balachandran wrote:
> Hi,
>
> Our smoke tests have been failing quite frequently of late. While
> re-triggering smoke several times in order to get a +1 works eventually,
> this does not really help anything IMO.
>
> I believe Jeff has already
Hi,
Our smoke tests have been failing quite frequently of late. While
re-triggering smoke several times in order to get a +1 works eventually,
this does not really help anything IMO.
I believe Jeff has already proposed this earlier but can we remove the
failing dbench tests from smoke until we
12 matches
Mail list logo