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 10 abc
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
On Tue, Jul 08, 2014 at 11:40:35AM +0100, Justin Clift wrote:
On 08/07/2014, at 9:53 AM, Anders Blomdell wrote:
snip
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 thing
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, Vijay
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
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:
snip
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
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].
On Wed, Jul 9, 2014 at 12:36 PM, John Mark Walker johnm...@gluster.org
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
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.6something tag at feature freeze
time or something?
+ Justin
--
GlusterFS - http://www.gluster.org
An open source, distributed file
I thought pkg-version in build-aux should have fixed this properly?
On Wed, Jul 9, 2014 at 1:33 PM, Justin Clift jus...@gluster.org 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
10 matches
Mail list logo
