On Tue, Apr 5, 2016 at 4:24 PM, Kaushal M wrote:
>
> On 5 Apr 2016 3:43 p.m., "Kaushal M" wrote:
>>
>> So gerrit voting seems to be working again. It required all the jobs
>> to have the same trigger configuration.
>>
>> Smoke vote was given for [1] a
Hi all,
The minutes of today's meeting:
Meeting summary
---
* agenda: https://public.pad.fsfe.org/p/gluster-bug-triage (hgowtham,
12:00:24)
* Roll Call (hgowtham, 12:00:30)
* ndevos need to decide on how to provide/use debug builds (hgowtham,
12:03:44)
* ACTION: msvbhat
Hi all,
The weekly bug triage is about to take place in ~50 minutes.
Meeting details:
- location: #gluster-meeting on Freenode IRC
( https://webchat.freenode.net/?channels=gluster-meeting )
- date: every Tuesday
- time: 12:00 UTC
(in your terminal, run: date -d "12:00 UTC")
On 5 Apr 2016 3:43 p.m., "Kaushal M" wrote:
>
> So gerrit voting seems to be working again. It required all the jobs
> to have the same trigger configuration.
>
> Smoke vote was given for [1] a test change that I posted for review.
> Now just need to check if it works for
So gerrit voting seems to be working again. It required all the jobs
to have the same trigger configuration.
Smoke vote was given for [1] a test change that I posted for review.
Now just need to check if it works for changes which already have
regressions run on them.
I'll be following [2] to see
Hi,
Gluster Snapshots and Geo-replication are not well integrated, lot of
steps to be performed to take snapshot of Gluster Volume which is
Geo-replicated. Proposed enhancement for Geo-replication to understand
Snapshot better and automatically handle Slave side snapshot.
Proposed Solution:
On 04/05/2016 01:04 PM, ABHISHEK PALIWAL wrote:
> Hi Team,
>
> We are using Gluster 3.7.6 and facing one problem in which brick is not
> comming online after restart the board.
>
> To understand our setup, please look the following steps:
> 1. We have two boards A and B on which Gluster volume
Hi Team,
We are using Gluster 3.7.6 and facing one problem in which brick is not
comming online after restart the board.
To understand our setup, please look the following steps:
1. We have two boards A and B on which Gluster volume is running in
replicated mode having one brick on each board.
On Tue, Apr 5, 2016 at 12:39 PM, Kaushal M wrote:
> On Tue, Apr 5, 2016 at 11:26 AM, Kaushal M wrote:
>> On Tue, Apr 5, 2016 at 11:10 AM, Atin Mukherjee wrote:
>>>
>>>
>>> On 04/05/2016 11:06 AM, Kaushal M wrote:
I did some
On Tue, Apr 5, 2016 at 11:26 AM, Kaushal M wrote:
> On Tue, Apr 5, 2016 at 11:10 AM, Atin Mukherjee wrote:
>>
>>
>> On 04/05/2016 11:06 AM, Kaushal M wrote:
>>> I did some changes so that all smoke jobs (linux, *bsd smoke jobs,
>>> devrpm jobs etc) are
Test Summary Report
---
./tests/bugs/replicate/bug-1297695.t (Wstat: 0 Tests: 22 Failed: 1)
Failed test: 22
Files=1, Tests=22, 18 wallclock secs ( 0.03 usr 0.00 sys + 2.47 cusr 1.61
csys = 4.11 CPU)
Result: FAIL
End of test ./tests/bugs/replicate/bug-1297695.t
Can someone
Hi Pranith,
We are not aware of this crash. I will look into the crash.
Rafi KC
On 04/05/2016 11:45 AM, Pranith Kumar Karampuri wrote:
> I meant *Do* we. Sorry for the typo!
>
> On 04/05/2016 11:33 AM, Pranith Kumar Karampuri wrote:
>> On tests/bugs/tier/bug-1286974.t, I see the following crash
I meant *Do* we. Sorry for the typo!
On 04/05/2016 11:33 AM, Pranith Kumar Karampuri wrote:
On tests/bugs/tier/bug-1286974.t, I see the following crash for the
run:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/19421/consoleFull
#1 0x7f41e15ad2bb in syncenv_task
On tests/bugs/tier/bug-1286974.t, I see the following crash for the run:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/19421/consoleFull
#1 0x7f41e15ad2bb in syncenv_task (proc=0xca5540) at
14 matches
Mail list logo