Is this happening every time the test runs? I've seen this happening few
times when the test is running with a very small heap or the test is
running on VMs and the Java VM or the local file system are unstable due
load on the virtualized environment. Have you looked into increasing the
heap or the the load of the environment where you are running this test?
On Fri, Jul 11, 2014 at 3:40 AM, Reinis Vicups <[EMAIL PROTECTED]> wrote: