On 07/21/2015 09:20 AM, Atin Mukherjee wrote:
On 07/20/2015 06:23 PM, Avra Sengupta wrote:
Got access to the slave machine. Had a look at the BT. The test-case
that keeps failing spuriously is kill_glusterd in cluster.rc, and the bt
looks like the following. Looks like the volinfo is
http://build.gluster.org/job/rackspace-regression-2GB-triggered/12541/consoleFull
http://build.gluster.org/job/rackspace-regression-2GB-triggered/12499/consoleFull
Please advise.
--
Milind
___
Gluster-devel mailing list
Gluster-devel@gluster.org
One more core for volume-snapshot.t:
https://build.gluster.org/job/rackspace-regression-2GB-triggered/12605/consoleFull
On 07/20/2015 03:00 PM, Raghavendra Talur wrote:
Adding Susant and Avra for dht and snapshot test cases respectively.
On Mon, Jul 20, 2015 at 11:45 AM, Milind Changire
Adding Susant and Avra for dht and snapshot test cases respectively.
On Mon, Jul 20, 2015 at 11:45 AM, Milind Changire milindchang...@gmail.com
wrote:
http://build.gluster.org/job/rackspace-regression-2GB-triggered/12541/consoleFull
The particular slave (slave21) containing the cores is down. I however
have access to slave0, so trying to recreate it on that slave and will
analyze the core when I get it.
Regards,
Avra
On 07/20/2015 03:19 PM, Ravishankar N wrote:
One more core for volume-snapshot.t:
Got access to the slave machine. Had a look at the BT. The test-case
that keeps failing spuriously is kill_glusterd in cluster.rc, and the bt
looks like the following. Looks like the volinfo is corrupted. Is looks
like it was trying to access peer data after cleanup_and _exit was called.
On 07/20/2015 06:23 PM, Avra Sengupta wrote:
Got access to the slave machine. Had a look at the BT. The test-case
that keeps failing spuriously is kill_glusterd in cluster.rc, and the bt
looks like the following. Looks like the volinfo is corrupted. Is looks
like it was trying to access peer
