On Sat, Apr 02, 2016 at 11:04:48AM -0400, Jeff Darcy wrote:
> > Please make sure that this change also gets included in the repository:
> >
> > https://github.com/gluster/glusterfs-patch-acceptance-tests
>
> Looks like we're getting a bit of a queue there. Who can merge some of
> these?
I nor
On Mon, Apr 04, 2016 at 12:36:56AM -0400, Luis Pabon wrote:
> Hi all,
> As you may know, Heketi (https://github.com/heketi/heketi) is a service
> that allows volumes to be created on demand from any number of GlusterFS
> clusters. The program heketi-cli was at first created as a sample
> appl
Hi,
If brick fails to become online then what is the solution to make it online?
Regards,
Abhishek
On Fri, Apr 1, 2016 at 4:23 PM, ABHISHEK PALIWAL
wrote:
> Please check the cmd-history file in attached logs of the Board A in which
> we are removing-brick at 11:56:48 because at this time after
Thanks Niels. I was explaining to another person offline that Heketi is like a
GlusterFS cloud volume manager. So maybe we should call it gcvm:
$ gcvm volume create ..?
What do you think?
- Original Message -
From: "Niels de Vos"
To: "Luis Pabon"
Cc: "Gluster Devel"
Sent: Monday, A
Le samedi 02 avril 2016 à 16:36 +0200, Niels de Vos a écrit :
> On Sat, Apr 02, 2016 at 07:53:32AM -0400, Jeff Darcy wrote:
> > > IIRC, this happens because in the build job use "--enable-bd-xlator"
> > > option while configure
> >
> > I came to the same conclusion, and set --enable-bd-xlator=no o
On Mon, Apr 04, 2016 at 07:37:07AM -0400, Luis Pabon wrote:
> Thanks Niels. I was explaining to another person offline that Heketi is like
> a GlusterFS cloud volume manager. So maybe we should call it gcvm:
>
> $ gcvm volume create ..?
I'm not sure if anyone would see a relation to Gluster wi
> Once this was done, I pushed to use the regular upstream change,
> something that was not done before since the local change broke
> automation to deploy test suite on Freebsd.
It looks like we have two options here:
(1) Fix configure so that it accurately detects whether the
system can/should
Le lundi 04 avril 2016 à 08:54 -0400, Jeff Darcy a écrit :
> > Once this was done, I pushed to use the regular upstream change,
> > something that was not done before since the local change broke
> > automation to deploy test suite on Freebsd.
>
> It looks like we have two options here:
>
> (1) F
Did anyone notice that for few of the patches smoke results are not voted
back?
http://review.gluster.org/#/c/13869 is one of them.
-Atin
Sent from one plus one
___
Gluster-devel mailing list
Gluster-devel@gluster.org
http://www.gluster.org/mailman/list
On Mon, Apr 4, 2016 at 9:58 PM, Atin Mukherjee
wrote:
> Did anyone notice that for few of the patches smoke results are not voted
> back?
>
> http://review.gluster.org/#/c/13869 is one of them.
+1
Here is another one http://review.gluster.org/#/c/11083/
I have also re-triggered it with "recheck
I did some changes so that all smoke jobs (linux, *bsd smoke jobs,
devrpm jobs etc) are triggered for `recheck smoke`.
The collated results are being reported back and the 'Smoke' flag is
being set. But sometimes, if regression jobs have been already run on
the patchset, jenkins is collating those
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 triggered for `recheck smoke`.
>
> The collated results are being reported back and the 'Smoke' flag is
> being set. But sometimes, if regression jobs have been al
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 triggered for `recheck smoke`.
>>
>> The collated results are being reported back and the 'Smoke' flag
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
/home/jenkins/root/workspace/rackspace-regression-2GB-triggered/libglusterfs/src/
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 (proc=
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
16 matches
Mail list logo
