On 05/08/2015 10:53 PM, Justin Clift wrote:
Seems like a new one, so it's been added to the Etherpad.
http://build.gluster.org/job/regression-test-burn-in/23/console
This looks a lot similar to the data-self-heal.t test where healing
fails to happen because both the threads end up not getting enough locks
to perform heal in self-heal domain. taking blocking locks seem like an
easy solution but that will decrease self-heal through put, so Ravi and
I are still thinking about best way to solve this problem. Will take
some time. I can add this and data-self-heal.t to badtests for now, if
that helps.
Pranith
It's on a new slave VM (slave1), which has been disconnected in
Jenkins so it can be investigated. It's using our standard
Jenkins auth.
+ Justin
--
GlusterFS - http://www.gluster.org
An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.
My personal twitter: twitter.com/realjustinclift
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel