[
https://issues.apache.org/jira/browse/DERBY-6400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815266#comment-13815266
]
Myrna van Lunteren edited comment on DERBY-6400 at 11/6/13 8:35 PM:
--------------------------------------------------------------------
My check-in to 10.10 caused a build failure in my nightly build/testing;
because it's using Str.isEmpty(), and that's a 1.6 method.
As a result, RunTest did not build, and so derbyall didn't get going, and in
addition, it resulted in the following 3 failures:
1)
testMissingCollatorSupport(org.apache.derbyTesting.functionTests.tests.lang.CollationTest)java.lang.NoClassDefFoundError:
org.apache.derbyTesting.functionTests.harness.RunTest
at
org.apache.derbyTesting.functionTests.util.TestUtil.getFramework(TestUtil.java:185)
at
org.apache.derbyTesting.functionTests.util.TestUtil.getConnection(TestUtil.java:808)
at
org.apache.derbyTesting.functionTests.tests.lang.CollationTest.testMissingCollatorSupport(CollationTest.java:2047)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:442)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:459)
Caused by: java.lang.ClassNotFoundException:
org.apache.derbyTesting.functionTests.harness.RunTest
at java.net.URLClassLoader.findClass(URLClassLoader.java:499)
at java.lang.ClassLoader.loadClass(ClassLoader.java:650)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:616)
... 27 more
2)
maxfieldsize(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest)java.lang.reflect.InvocationTargetException
...
Caused by: java.lang.NoClassDefFoundError:
org.apache.derbyTesting.functionTests.harness.RunTest
...
3)
maxfieldsize(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest)java.lang.reflect.InvocationTargetException
...
Caused by: java.lang.NoClassDefFoundError:
org.apache.derbyTesting.functionTests.harness.RunTest
..
I didn't realize the JDBCHarnessJavaTest and CollationTest actually use RunTest.
But I'll fix this build failure.
was (Author: myrna):
My check-in to 10.10 caused a build failure in my nightly build/testing;
because it's using Str.isEmpty(), and that's a 1.6 method.
As a result, RunTest did not build, and so derbyall didn't get going, and in
addition, it resulted in the following 3 failures:
1)
testMissingCollatorSupport(org.apache.derbyTesting.functionTests.tests.lang.CollationTest)java.lang.NoClassDefFoundError:
org.apache.derbyTesting.functionTests.harness.RunTest
at
org.apache.derbyTesting.functionTests.util.TestUtil.getFramework(TestUtil.java:185)
at
org.apache.derbyTesting.functionTests.util.TestUtil.getConnection(TestUtil.java:808)
at
org.apache.derbyTesting.functionTests.tests.lang.CollationTest.testMissingCollatorSupport(CollationTest.java:2047)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:117)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:442)
at
org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:459)
Caused by: java.lang.ClassNotFoundException:
org.apache.derbyTesting.functionTests.harness.RunTest
at java.net.URLClassLoader.findClass(URLClassLoader.java:499)
at java.lang.ClassLoader.loadClass(ClassLoader.java:650)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:616)
... 27 more
2)
maxfieldsize(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest)java.lang.reflect.InvocationTargetException
...
Caused by: java.lang.NoClassDefFoundError:
org.apache.derbyTesting.functionTests.harness.RunTest
...
3)
maxfieldsize(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest)java.lang.reflect.InvocationTargetException
...
Caused by: java.lang.NoClassDefFoundError:
org.apache.derbyTesting.functionTests.harness.RunTest
..
I didn't realize the JDBCHarnessJavaTest and CollationTest actually use RunTest.
But I'll fix this.
> harness.NetServer method waitFor() is not reflecting timeout values
> -------------------------------------------------------------------
>
> Key: DERBY-6400
> URL: https://issues.apache.org/jira/browse/DERBY-6400
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Myrna van Lunteren
> Priority: Minor
> Fix For: 10.10.1.3, 10.11.0.0
>
> Attachments: DERBY-6400.diff
>
>
> On a slow machine, derbynetclientmats was seen to fail (with no test pass,
> nor fail) with the following error:
> org.apache.derby.drda.NetworkServerControl start
> Attempt to shutdown framework: DerbyNetClient
> Server Process did not complete in time. Destroying...
> Server Process did not complete in time. Destroying...
> Exception in thread "main" java.io.IOException: Interrupted system call
> at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
> at
> org.apache.derbyTesting.functionTests.harness.BackgroundStreamSaver.run(BackgroundStreamSaver.java:51)
> at java.lang.Thread.run(Thread.java:853)
> It seems to me that the problem is here that in
> functionTests.harness.NetServer the waitFor() method has a hard value of 60
> in it. Instead, this value should be configurable.
> In functionTests.harness.RunTest the waitFor() method uses
> TimedProcess tp = new TimedProcess(pr);
> tp.waitFor(timeout*60);
> It seems NetServer should also be able to check on the timeout value.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
