Atin Mukherjee amukh...@redhat.com wrote:
Is this reproducible in netbsd everytime, if yes I would need a VM to
further debug it.
nbslave78.cloud.gluster.org
Note that it failed a lot of jobs yesterday, I do not know why, but I am
not sure the system is the culprit: nbslave7a exhibited the
On 05/02/2015 10:14 AM, Krishnan Parthasarathi wrote:
If glusterd itself fails to come up, of course the test will fail :-). Is it
still happening?
Pranith,
Did you get a chance to see glusterd logs and find why glusterd didn't come up?
Please paste the relevant logs in this thread.
No :-(.
On 05/02/2015 09:08 AM, Atin Mukherjee wrote:
On 05/02/2015 08:54 AM, Emmanuel Dreyfus wrote:
Pranith Kumar Karampuri pkara...@redhat.com wrote:
Seems like glusterd failure from the looks of it: +glusterd folks.
Running tests in file ./tests/basic/cdc.t
volume delete: patchy: failed:
Emmanuel Dreyfus m...@netbsd.org wrote:
Note that it failed a lot of jobs yesterday, I do not know why, but I am
not sure the system is the culprit: nbslave7a exhibited the same
behavior and is now fine while I did nothing for it.
I think it is git.gluster.org that misbehaved: I started
On 05/02/2015 11:59 AM, Atin Mukherjee wrote:
On 05/02/2015 09:08 AM, Atin Mukherjee wrote:
On 05/02/2015 08:54 AM, Emmanuel Dreyfus wrote:
Pranith Kumar Karampuri pkara...@redhat.com wrote:
Seems like glusterd failure from the looks of it: +glusterd folks.
Running tests in file
Atin Mukherjee amukh...@redhat.com wrote:
it hangs on gverify.sh
While there, for the sake of portability it should not depend on bash.
While it is reasonable to expect bash to be installed for running the
test suite, IMO the non test stuff should try to lower dependencies, and
bash is easy to
