[
https://issues.apache.org/jira/browse/DERBY-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161769#comment-13161769
]
Knut Anders Hatlen commented on DERBY-5123:
-------------------------------------------
These are the intermittent failures seen in Oracle's tests the last two weeks:
2x DERBY-5194 - AutoloadTest timed out waiting for network server to start
2x DERBY-4916 - Upgrade tests fail in DropDatabaseSetup.tearDown unable to
delete a directory
DERBY-5197 - AssertionFailedError: Could not connect in 20000 ms in
ReplicationRun_Local_3_p2.testReplication_Local_3_p2_StateTests_bigInsert_immediateStopMaster
DERBY-5517 - testReplication_Local_3_p1_StateNegativeTests failed with
connection refused
DERBY-5518 - NetworkServerMBeanTest timed out waiting for network server to
start
DERBY-4269 - Failover did not succeed in 2 min.:
testReplication_Local_3_p6_autocommit_OK
DERBY-5003 - NPE in ReplicationRun_Local_3_p5 when stopping slave after
purposely crashing master
> address a select number of intermittent test issues - goal is to get all
> nightly tests at trunk running clean for at least 2 weeks
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-5123
> URL: https://issues.apache.org/jira/browse/DERBY-5123
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.8.1.2
> Reporter: Myrna van Lunteren
>
> There have been relatively large number of intermittent test failures over
> the last month or so, and it would be nice to fix these.
> If an issue cannot be reproduced, we should consider changing the test or
> other code so more information gets reflected in case it occurs again.
> If they can't be fixed in the short term, we should consider disabling the
> smallest part of the test that will make it pass, and listing it in
> DERBY-5122.
> This is just a place holder to highlight the test failures that at this point
> appear relevant.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
