Andy Gumbrecht commented on Quality Risk CDITCK-297

All win buildbot test failures at OpenEJB/TomEE are related to file names that are too long - These file names are internally generated by the JBoss TCK.

See: http://ci.apache.org/builders/tomee-trunk-win-sunsdk6/

I am flagging the TomEE build green using the maven -fn option, which prevents failure due to failing tests. This is just a temporary measure.

The trace is as follows on all failing tests:

java.lang.RuntimeException: Error connecting to the container
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:883)
at org.jboss.testharness.impl.packaging.ArtifactDescriptor.copyClass(ArtifactDescriptor.java:363)
at org.jboss.testharness.impl.packaging.ArtifactDescriptor.copyClass(ArtifactDescriptor.java:325)
at org.jboss.testharness.impl.packaging.ArtifactDescriptor.create(ArtifactDescriptor.java:307)
at org.jboss.testharness.impl.packaging.ArtifactDescriptor.getExplodedJar(ArtifactDescriptor.java:292)
at org.jboss.testharness.impl.packaging.ArtifactDescriptor.getJarAsStream(ArtifactDescriptor.java:262)
at org.jboss.testharness.AbstractTest.deployArtifact(AbstractTest.java:86)
at org.jboss.testharness.AbstractTest.beforeClass(AbstractTest.java:206)

This is caused by the unchecked classFile.createNewFile() call, which should really be in it's own try/throwable block and also checked - if(!classFile.createNewFile()) throw new IOException(). The deeper 'FileSystem.createFileExclusively' call is NOT throwing an IOException, rather a native error which is not caught.

Somewhere between 'AbstractTest.deployArtifact' and 'ArtifactDescriptor.copyClass' there needs to be some sanity check on win platforms for the path length, which must be less than 256 characters in total.

Andy.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira