On 6/3/2013 1:12 PM, Aleksandar Kostadinov wrote:
We often need to test in non-ideal environments especially older
machines with proprietary software and cloud. Transient failures tend to
lose a lot of time especially when they happen to fail consistently in
particular environment. Not only QE time but also dev time.
Also test suite becomes hard to run by inexperienced with the particular
test suite people, e.g. self-certification and certification services
become a hard goal.
That's why I think that, as stupid as it sounds, such a loop is better
than dealing with this when least expected.
By loop, I meant looping-forever is a bad idea.
Does this class throw in your environment? If it works then perhaps
problem is an actual bug in test controller (it works for me on fedora
18). And if it fails then it must be a bug in the JVM.. at least the way
I understand mkdir() javadoc.
I'm running on Windows. (Windows 7). Quad-core. Dual Raid 0 Intel
SSDs. A lot of variables here. Could be the JVM, Windows, or some
quirkiness in SSD or Raid drivers. I don't know what to tell you and I
don't have time to dive into any one of those variables.
JBoss, a division of Red Hat