On 31 July 2018 at 22:11, Atin Mukherjee wrote:
> I just went through the nightly regression report of brick mux runs and
> here's what I can summarize.
>
>
>
>
On Fri, Aug 3, 2018 at 5:58 PM, Yaniv Kaul wrote:
> Why not revert, fix and resubmit (unless you can quickly fix it)?
> Y.
>
https://review.gluster.org/20634
>
> On Fri, Aug 3, 2018, 5:04 PM Raghavendra Gowdappa
> wrote:
>
>> Will take a look.
>>
>> On Fri, Aug 3, 2018 at 3:08 PM, Krutika
GlusterFS Coverity covscan results for the master branch are available from
http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-08-03-93d7f3f2/
Coverity covscan results for other active branches are also available at
Why not revert, fix and resubmit (unless you can quickly fix it)?
Y.
On Fri, Aug 3, 2018, 5:04 PM Raghavendra Gowdappa
wrote:
> Will take a look.
>
> On Fri, Aug 3, 2018 at 3:08 PM, Krutika Dhananjay
> wrote:
>
>> Adding Raghavendra G who actually restored and reworked on this after it
>> was
On Fri, Aug 3, 2018 at 11:04 AM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
> On Thu, Aug 2, 2018 at 10:03 PM Pranith Kumar Karampuri <
> pkara...@redhat.com> wrote:
>
>> On Thu, Aug 2, 2018 at 7:19 PM Atin Mukherjee
>> wrote:
>>
>>> New addition - tests/basic/volume.t - failed twice
On Fri, Aug 3, 2018 at 4:01 PM, Kotresh Hiremath Ravishankar <
khire...@redhat.com> wrote:
> Hi Du/Poornima,
>
> I was analysing bitrot and geo-rep failures and I suspect there is a bug
> in some perf xlator
> that was one of the cause. I was seeing following behaviour in few runs.
>
> 1. Geo-rep
On Fri, Aug 3, 2018 at 3:07 PM Karthik Subrahmanya
wrote:
>
>
> On Fri, Aug 3, 2018 at 2:12 PM Karthik Subrahmanya
> wrote:
>
>>
>>
>> On Thu, Aug 2, 2018 at 11:00 PM Karthik Subrahmanya
>> wrote:
>>
>>>
>>>
>>> On Tue 31 Jul, 2018, 10:17 PM Atin Mukherjee,
>>> wrote:
>>>
I just went
Will take a look.
On Fri, Aug 3, 2018 at 3:08 PM, Krutika Dhananjay
wrote:
> Adding Raghavendra G who actually restored and reworked on this after it
> was abandoned.
>
> -Krutika
>
> On Fri, Aug 3, 2018 at 2:38 PM, Nithya Balachandran
> wrote:
>
>> Using git bisect, the patch that introduced
Hi Du/Poornima,
I was analysing bitrot and geo-rep failures and I suspect there is a bug in
some perf xlator
that was one of the cause. I was seeing following behaviour in few runs.
1. Geo-rep synced data to slave. It creats empty file and then rsync syncs
data.
But test does "stat --format
Adding Raghavendra G who actually restored and reworked on this after it
was abandoned.
-Krutika
On Fri, Aug 3, 2018 at 2:38 PM, Nithya Balachandran
wrote:
> Using git bisect, the patch that introduced this behaviour is :
>
> commit 7131de81f72dda0ef685ed60d0887c6e14289b8c
> Author: Krutika
On Fri, Aug 3, 2018 at 2:12 PM Karthik Subrahmanya
wrote:
>
>
> On Thu, Aug 2, 2018 at 11:00 PM Karthik Subrahmanya
> wrote:
>
>>
>>
>> On Tue 31 Jul, 2018, 10:17 PM Atin Mukherjee,
>> wrote:
>>
>>> I just went through the nightly regression report of brick mux runs and
>>> here's what I can
On 31 July 2018 at 22:11, Atin Mukherjee wrote:
> I just went through the nightly regression report of brick mux runs and
> here's what I can summarize.
>
>
>
>
Using git bisect, the patch that introduced this behaviour is :
commit 7131de81f72dda0ef685ed60d0887c6e14289b8c
Author: Krutika Dhananjay
Date: Tue Jan 17 16:40:04 2017 +0530
performance/readdir-ahead: Invalidate cached dentries if they're
modified while in cache
Krutika, can you take a
This is a new issue - the test uses ls -l to get some information. With the
latest master, ls -l returns strange results the first time it is called on
the mount point causing the test to fail:
With the latest master, I created a single brick volume and some files
inside it.
[root@rhgs313-6 ~]#
On Thu, Aug 2, 2018 at 11:00 PM Karthik Subrahmanya
wrote:
>
>
> On Tue 31 Jul, 2018, 10:17 PM Atin Mukherjee, wrote:
>
>> I just went through the nightly regression report of brick mux runs and
>> here's what I can summarize.
>>
>>
>>
15 matches
Mail list logo
