[
https://issues.apache.org/jira/browse/DERBY-5975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488001#comment-13488001
]
Mike Matrigali commented on DERBY-5975:
---------------------------------------
failed against 10.8, windows, weme 6.2, non-vmware - on 10/16, 10/22, 10/24,
10/28, 10/30.
All failed with Derby5937SlaveShutdownTest.testSlaveFailoverLeak failed as last
test in result and nothing else in result, indicating test hung and then
eventually harness killed test
> intermittent nightly test failure across releases in
> Derby5937SlaveShutdownTest.testSlaveFailoverLeak
> -----------------------------------------------------------------------------------------------------
>
> Key: DERBY-5975
> URL: https://issues.apache.org/jira/browse/DERBY-5975
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.10.0.0
> Environment: windows weme6.2
> Reporter: Mike Matrigali
>
> Across multiple versions nightly tests have failed in
> Derby5937SlaveShutdownTest.testSlaveFailoverLeak.
> Subsequent to this no other test runs and thus we get no info printed to the
> log, and the ibm test
> reporter does not post anything other than a red box if the tests do not
> finish. Not sure if the
> tests are hanging as part of trying to clean up the failure or if the next
> test is hanging. Will post
> test runs that have failed in additional comments.
> (emb)jdbcapi.DatabaseMetaDataTest.testGetColumns_DERBY5274 used 343 ms .
> (emb)jdbcapi.DatabaseMetaDataTest.testDMDconnClosed used 79 ms Test upgrade
> done.
> Test upgrade from: 10.9.1.0, phase: POST UPGRADE
> .
> (emb)upgradeTests.BasicSetup.noConnectionAfterHardUpgrade used 156 ms Test
> upgrade done.
> .
> (emb)replicationTests.Derby5937SlaveShutdownTest.testSlaveFailoverLeak used
> 24221 ms F
--
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
