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.0.0
Reporter: Mamta A. Satoor
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.
-
You can reply to this email to add a comment to the issue online.
