[
https://issues.apache.org/jira/browse/DERBY-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12727125#action_12727125
]
Tiago R. Espinha commented on DERBY-3834:
-----------------------------------------
The said bug with the port is now fixed in DERBY-4217. Still, upon running
suites.All I got:
----------8<------------------------
Time: 5,827.406
There was 1 failure:
1)
org.apache.derbyTesting.functionTests.tests.derbynet.RuntimeInfoTestjunit.framework.AssertionFailedError:
Timed out waiting for network server to start
at
org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:200)
at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at
org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
FAILURES!!!
Tests run: 11312, Failures: 1, Errors: 0
----------------------8<----------------------------------
It seems a rather innocent failure and after running the derbynet suite again
twice the failure did not pop again. It needs to be said that the suites.All
was ran simultaneously with derbyall. Still, I think we can chalk it up to
delays in the server response due to the high load. Nonetheless, I will be
running suites.All again, this time alone.
Test runs permitting, the patch seems to be ready for commit.
> Convert derbynet/runtimeinfo to JUnit
> -------------------------------------
>
> Key: DERBY-3834
> URL: https://issues.apache.org/jira/browse/DERBY-3834
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Affects Versions: 10.5.1.1
> Reporter: Erlend Birkenes
> Assignee: Tiago R. Espinha
> Priority: Minor
> Attachments: DERBY-3834.patch, DERBY-3834.patch, DERBY-3834.patch,
> DERBY-3834.patch, DERBY-3834.patch, DERBY-3834.patch, DERBY-3834.stat,
> Derby-3834_1.diff
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
