[
https://issues.apache.org/jira/browse/DERBY-6107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13940047#comment-13940047
]
Myrna van Lunteren commented on DERBY-6107:
-------------------------------------------
On Linux, even with a jvm < 7u51, (ibm 1.7 sr6) I also got failures in
NativeAuthenticationTest when run with -Dderby.tests.login.timeout=10.
If that test is the only one in the _Suite, there is no such failure.
I blundered about going with the idea that there was one previous test that
would mess this up, but it seems more tricky than that. Here's what I found so
far:
- There are no failures if the suite consists of:
suite.addTest(OrderByAndOffsetFetchInSubqueries.suite());
suite.addTest(Derby5005Test.suite());
suite.addTest(OLAPTest.suite());
suite.addTest(NativeAuthenticationServiceTest.suite());
- But there are 2 failures if any of the following tests are run first:
suite.addTest(DBOAccessTest.suite());
suite.addTest(HalfCreatedDatabaseTest.suite());
- And there are 4 failures if the following test is run first:
suite.addTest(AutoIncrementTest.suite());
suite.addTest(SequenceGeneratorTest.suite());
Not sure if this information tells us anything useful.
> Investigate why setting a login timeout causes
> NativeAuthenticationServiceTest to fail when run in a suite
> ----------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6107
> URL: https://issues.apache.org/jira/browse/DERBY-6107
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.10.1.1
> Reporter: Rick Hillegas
>
> See DERBY-6094 for the details of this problem.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
