On 2014-07-09 19:18, Vijay Bellur wrote:
> On 07/09/2014 09:56 PM, Anders Blomdell wrote:
>
>>
>> BTW: doc/hacker-guide/en-US/markdown/unittest.md seems to lack info on how
>> to write tests/bugs/bug-*.t files.
>>
>
> unittest.md is for writing code unit tests using cmockery.
>
> some details ab
I thought "pkg-version" in build-aux should have fixed this properly?
On Wed, Jul 9, 2014 at 1:33 PM, Justin Clift wrote:
> That v3.5qa2 tag name on master is annoying, due to the RPM
> naming it causes when building on master.
>
> Did we figure out a solution?
>
> Maybe we should do a v3.6 tag a
That v3.5qa2 tag name on master is annoying, due to the RPM
naming it causes when building on master.
Did we figure out a solution?
Maybe we should do a v3.6 tag at feature freeze
time or something?
+ Justin
--
GlusterFS - http://www.gluster.org
An open source, distributed file system scaling
On Wed, Jul 9, 2014 at 12:36 PM, John Mark Walker
wrote:
> Greetings,
>
> One of the things I wanted to do with the forge, was use it as the basis
> for creating a software distribution of tools related to GlusterFS.
> GlusterFS would remain the centerpiece, and we would add all some tools
> into
On 07/09/2014 09:56 PM, Anders Blomdell wrote:
BTW: doc/hacker-guide/en-US/markdown/unittest.md seems to lack info on how
to write tests/bugs/bug-*.t files.
unittest.md is for writing code unit tests using cmockery.
some details about writing tests/bugs/bug-*.t files is available at [1].
C
Greetings,
One of the things I wanted to do with the forge, was use it as the basis for
creating a software distribution of tools related to GlusterFS. GlusterFS would
remain the centerpiece, and we would add all some tools into the mix that would
be helpful for admins and developers. Some of t
On 2014-07-09 15:02, Niels de Vos wrote:
> On Tue, Jul 08, 2014 at 11:40:35AM +0100, Justin Clift wrote:
>> On 08/07/2014, at 9:53 AM, Anders Blomdell wrote:
>>
>>> 2. What are the rules for marking a bug as blocking the trackers (can't
>>> find one for
>>> 3.6.0 yet, so currently a moot point)
On 09/07/2014, at 3:54 PM, Justin Clift wrote:
> Reminder!!!
>
> The weekly Gluster Community meeting is in 5 mins, in
> #gluster-meeting on IRC.
Thanks to everyone for attending. Wasn't a long meeting
today. :)
* GlusterFS 3.4.5 _beta 2_ RPMs are being created now
Humble will announce wh
Reminder!!!
The weekly Gluster Community meeting is in 5 mins, in
#gluster-meeting on IRC.
This is a completely public meeting, everyone is encouraged
to attend and be a part of it. :)
To add Agenda items
***
Just add them to the main text of the Etherpad, and be at
the meeting.
Thanks for the info/links and the quickness :)
v
On Wed 09 Jul 2014 10:32:30, Humble Devassy Chirammal wrote:
> some more bits about libgfapi can be fetched from
> https://github.com/gluster/glusterfs/blob/master/doc/features/libgfapi.md
>
> --Humble
>
>
> On Wed, Jul 9, 2014 at 10:27 AM, Vij
On Tue, Jul 08, 2014 at 11:40:35AM +0100, Justin Clift wrote:
> On 08/07/2014, at 9:53 AM, Anders Blomdell wrote:
>
> > 2. What are the rules for marking a bug as blocking the trackers (can't
> > find one for
> > 3.6.0 yet, so currently a moot point).
>
> We should probably create an alias thi
Is the current behavior in master, where file-system operations on the fuse-fs
fails with 'Transport endpoint is not connected' for approximately 3.2 seconds
after an add-brick is done, or would it make sense to add something like NFS's
{soft/hard}/retrans/timeo logic, and if so, could somebody gi
hi,
I sent the following patch to change the output of EXPECT_WITHIN:
http://review.gluster.org/8263
Patch got one +1 and regressions passed. Merge it please :-).
Test:
#!/bin/bash
. $(dirname $0)/../include.rc
EXPECT_WITHIN 10 "abc" echo "def"
EXPECT_WITHIN 10 "def" echo "def"
EXPECT_WITHIN 1
13 matches
Mail list logo
