You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <ji...@apache.org> on 2013/06/05 21:10:21 UTC
[jira] [Commented] (DERBY-4303) Handful of replication tests failed
because they failed to get a connection to the slave within two minutes.
[ https://issues.apache.org/jira/browse/DERBY-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676249#comment-13676249 ]
Mike Matrigali commented on DERBY-4303:
---------------------------------------
I think this is another example of this issue:
http://people.apache.org/~myrnavl/derby_test_results/v10_9/windows/testlog/ibm17/1476030-suites.All_diff.txt
1) testReplication_Local_TestStraightReplication(org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local)junit.framework.AssertionFailedError: Server did not start in time
at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.pingServer(ReplicationRun.java:2438)
at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.startServer(ReplicationRun.java:2132)
at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun_Local.testReplication_Local_TestStraightReplication(ReplicationRun_Local.java:112)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
at org.apache.derbyTesting.functionTests.tests.replicationTests.ReplicationRun.runBare(ReplicationRun.java:246)
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: 16535, Failures: 1, Errors: 0
> Handful of replication tests failed because they failed to get a connection to the slave within two minutes.
> -------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4303
> URL: https://issues.apache.org/jira/browse/DERBY-4303
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.6.1.0
> Reporter: Mamta A. Satoor
> Labels: derby_triage10_8
> Attachments: faillogs_06062012.zip, master_and_slave_logs.zip, TryReproDerby4303_diff.txt
>
>
> The nightly runs on trunk(revision 793163) using ibm15 had 19 failures in replication tests (all failing for same reason
> junit.framework.AssertionFailedError: startMaster did not succeed.) Copying Knut's comments to the failure
> **************
> It looks like all the failing tests failed to get a connection to the
> slave within two minutes. There may be more information in derby.log on
> the slave or on the master (should be available in the fail
> directory). It's probably best to log a JIRA issue and attach the
> information there. This is not one of the known replication test
> failures, I think, but since they all fail the same way it sounds likely
> that there is some test cleanup code that doesn't properly release all
> resources or an environment problem of some kind.
> **************
--
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