On 2 August 2018 at 05:46, Shyam Ranganathan wrote:
> Below is a summary of failures over the last 7 days on the nightly
> health check jobs. This is one test per line, sorted in descending order
> of occurrence (IOW, most frequent failure is on top).
>
> The list includes spurious failures as
On 6 August 2018 at 18:03, Nithya Balachandran wrote:
>
>
> On 2 August 2018 at 05:46, Shyam Ranganathan wrote:
>
>> Below is a summary of failures over the last 7 days on the nightly
>> health check jobs. This is one test per line, sorted in descending order
>> of occurrence (IOW, most
On 2 August 2018 at 05:46, Shyam Ranganathan wrote:
> Below is a summary of failures over the last 7 days on the nightly
> health check jobs. This is one test per line, sorted in descending order
> of occurrence (IOW, most frequent failure is on top).
>
> The list includes spurious failures as
On Mon, 6 Aug 2018 at 06:09, Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:
> On Mon, Aug 6, 2018 at 5:17 AM, Amye Scavarda wrote:
> >
> >
> > On Sun, Aug 5, 2018 at 3:24 PM Shyam Ranganathan
> > wrote:
> >>
> >> On 07/31/2018 07:16 AM, Shyam Ranganathan wrote:
> >> > On
On Mon, Aug 6, 2018 at 5:17 AM, Amye Scavarda wrote:
>
>
> On Sun, Aug 5, 2018 at 3:24 PM Shyam Ranganathan
> wrote:
>>
>> On 07/31/2018 07:16 AM, Shyam Ranganathan wrote:
>> > On 07/30/2018 03:21 PM, Shyam Ranganathan wrote:
>> >> On 07/24/2018 03:12 PM, Shyam Ranganathan wrote:
>> >>> 1)
On Sun, Aug 5, 2018 at 3:24 PM Shyam Ranganathan
wrote:
> On 07/31/2018 07:16 AM, Shyam Ranganathan wrote:
> > On 07/30/2018 03:21 PM, Shyam Ranganathan wrote:
> >> On 07/24/2018 03:12 PM, Shyam Ranganathan wrote:
> >>> 1) master branch health checks (weekly, till branching)
> >>> - Expect
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 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
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
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.
>
>
>
>
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.
>>
>>
>>
On Thu, Aug 2, 2018 at 10:03 PM Pranith Kumar Karampuri
wrote:
>
>
> On Thu, Aug 2, 2018 at 7:19 PM Atin Mukherjee wrote:
>
>> New addition - tests/basic/volume.t - failed twice atleast with shd core.
>>
>> One such ref -
>> https://build.gluster.org/job/centos7-regression/2058/console
>>
>
> I
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.
>
>
>
Have attached in the Bug https://bugzilla.redhat.com/show_bug.cgi?id=1611635
On Thu, 2 Aug 2018, 22:21 Raghavendra Gowdappa, wrote:
>
>
> On Thu, Aug 2, 2018 at 5:48 PM, Kotresh Hiremath Ravishankar <
> khire...@redhat.com> wrote:
>
>> I am facing different issue in softserve machines. The
On Thu, Aug 2, 2018 at 5:48 PM, Kotresh Hiremath Ravishankar <
khire...@redhat.com> wrote:
> I am facing different issue in softserve machines. The fuse mount itself
> is failing.
> I tried day before yesterday to debug geo-rep failures. I discussed with
> Raghu,
> but could not root cause it.
>
On Thu, Aug 2, 2018 at 7:19 PM Atin Mukherjee wrote:
> New addition - tests/basic/volume.t - failed twice atleast with shd core.
>
> One such ref -
> https://build.gluster.org/job/centos7-regression/2058/console
>
I will take a look.
>
>
> On Thu, Aug 2, 2018 at 6:28 PM Sankarshan
New addition - tests/basic/volume.t - failed twice atleast with shd core.
One such ref - https://build.gluster.org/job/centos7-regression/2058/console
On Thu, Aug 2, 2018 at 6:28 PM Sankarshan Mukhopadhyay <
sankarshan.mukhopadh...@gmail.com> wrote:
> On Thu, Aug 2, 2018 at 5:48 PM, Kotresh
On Thu, Aug 2, 2018 at 5:48 PM, Kotresh Hiremath Ravishankar
wrote:
> I am facing different issue in softserve machines. The fuse mount itself is
> failing.
> I tried day before yesterday to debug geo-rep failures. I discussed with
> Raghu,
> but could not root cause it. So none of the tests were
On Thu, Aug 2, 2018 at 1:42 PM Kotresh Hiremath Ravishankar <
khire...@redhat.com> wrote:
>
>
> On Thu, Aug 2, 2018 at 5:05 PM, Atin Mukherjee > wrote:
>
>>
>>
>> On Thu, Aug 2, 2018 at 4:37 PM Kotresh Hiremath Ravishankar <
>> khire...@redhat.com> wrote:
>>
>>>
>>>
>>> On Thu, Aug 2, 2018 at
I am facing different issue in softserve machines. The fuse mount itself is
failing.
I tried day before yesterday to debug geo-rep failures. I discussed with
Raghu,
but could not root cause it. So none of the tests were passing. It happened
on
both machine instances I tried.
On Thu, Aug 2, 2018 at 5:12 PM Kotresh Hiremath Ravishankar <
khire...@redhat.com> wrote:
> Don't know, something to do with perf xlators I suppose. It's not
> repdroduced on my local system with brick-mux enabled as well. But it's
> happening on Xavis' system.
>
> Xavi,
> Could you try with the
On Thu, Aug 2, 2018 at 5:05 PM, Atin Mukherjee
wrote:
>
>
> On Thu, Aug 2, 2018 at 4:37 PM Kotresh Hiremath Ravishankar <
> khire...@redhat.com> wrote:
>
>>
>>
>> On Thu, Aug 2, 2018 at 3:49 PM, Xavi Hernandez
>> wrote:
>>
>>> On Thu, Aug 2, 2018 at 6:14 AM Atin Mukherjee
>>> wrote:
>>>
On Thu, Aug 2, 2018 at 4:37 PM Kotresh Hiremath Ravishankar <
khire...@redhat.com> wrote:
>
>
> On Thu, Aug 2, 2018 at 3:49 PM, Xavi Hernandez
> wrote:
>
>> On Thu, Aug 2, 2018 at 6:14 AM Atin Mukherjee
>> wrote:
>>
>>>
>>>
>>> On Tue, Jul 31, 2018 at 10:11 PM Atin Mukherjee
>>> wrote:
>>>
On Thu, Aug 2, 2018 at 4:50 PM, Amar Tumballi wrote:
>
>
> On Thu, Aug 2, 2018 at 4:37 PM, Kotresh Hiremath Ravishankar <
> khire...@redhat.com> wrote:
>
>>
>>
>> On Thu, Aug 2, 2018 at 3:49 PM, Xavi Hernandez
>> wrote:
>>
>>> On Thu, Aug 2, 2018 at 6:14 AM Atin Mukherjee
>>> wrote:
>>>
On Thu, Aug 2, 2018 at 4:37 PM, Kotresh Hiremath Ravishankar <
khire...@redhat.com> wrote:
>
>
> On Thu, Aug 2, 2018 at 3:49 PM, Xavi Hernandez
> wrote:
>
>> On Thu, Aug 2, 2018 at 6:14 AM Atin Mukherjee
>> wrote:
>>
>>>
>>>
>>> On Tue, Jul 31, 2018 at 10:11 PM Atin Mukherjee
>>> wrote:
>>>
On Thu, Aug 2, 2018 at 11:43 AM, Xavi Hernandez
wrote:
> On Thu, Aug 2, 2018 at 6:14 AM Atin Mukherjee wrote:
>
>>
>>
>> On Tue, Jul 31, 2018 at 10:11 PM Atin Mukherjee
>> wrote:
>>
>>> I just went through the nightly regression report of brick mux runs and
>>> here's what I can summarize.
>>>
On Thu, Aug 2, 2018 at 6:14 AM Atin Mukherjee wrote:
>
>
> On Tue, Jul 31, 2018 at 10:11 PM Atin Mukherjee
> wrote:
>
>> I just went through the nightly regression report of brick mux runs and
>> here's what I can summarize.
>>
>>
>>
On Tue, Jul 31, 2018 at 10:11 PM Atin Mukherjee wrote:
> I just went through the nightly regression report of brick mux runs and
> here's what I can summarize.
>
>
>
On Thu, Aug 2, 2018 at 12:19 AM, Shyam Ranganathan wrote:
> On 07/31/2018 12:41 PM, Atin Mukherjee wrote:
>> tests/bugs/core/bug-1432542-mpx-restart-crash.t - Times out even after
>> 400 secs. Refer
>> https://fstat.gluster.org/failure/209?state=2_date=2018-06-30_date=2018-07-31=all,
>>
On 07/31/2018 12:41 PM, Atin Mukherjee wrote:
> tests/bugs/core/bug-1432542-mpx-restart-crash.t - Times out even after
> 400 secs. Refer
> https://fstat.gluster.org/failure/209?state=2_date=2018-06-30_date=2018-07-31=all,
> specifically the latest report
>
On 08/01/2018 12:13 AM, Sankarshan Mukhopadhyay wrote:
>> Thinking aloud, we may have to stop merges to master to get these test
>> failures addressed at the earliest and to continue maintaining them
>> GREEN for the health of the branch.
>>
>> I would give the above a week, before we lockdown the
On Tue, Jul 31, 2018 at 4:46 PM, Shyam Ranganathan wrote:
> On 07/30/2018 03:21 PM, Shyam Ranganathan wrote:
>> On 07/24/2018 03:12 PM, Shyam Ranganathan wrote:
>>> 1) master branch health checks (weekly, till branching)
>>> - Expect every Monday a status update on various tests runs
>>
>> See
I just went through the nightly regression report of brick mux runs and
here's what I can summarize.
=
Fails only with brick-mux
36 matches
Mail list logo
