[
https://issues.apache.org/jira/browse/DERBY-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044743#comment-13044743
]
Knut Anders Hatlen commented on DERBY-5014:
-------------------------------------------
I don't think there's anything that needs to be fixed in those two tests.
Perhaps it would have been better if ResultSetsFromPreparedStatementTest had
cleared the timeout property (by setting it to NULL) instead of setting it to
60, since that would do the right thing even if we at some point change the
default timeout, but at least it does reset the timeout to the current default.
> Tests should restore the timeout values to default after they are done
> running.
> -------------------------------------------------------------------------------
>
> Key: DERBY-5014
> URL: https://issues.apache.org/jira/browse/DERBY-5014
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.7.1.1
> Reporter: Mamta A. Satoor
> Assignee: Siddharth Srivastava
> Labels: derby_triage10_8
> Attachments: d5014_1.diff, d5014_1.diff
>
>
> There are still couple more tests that change the lock time out during the
> test run but don't restore it to the default at the
> end of the test. Knut already fixed this behavior for
> SetTransactionIsolationTest.java and ResultSetMiscTest.java as part of
> DERBY-4273
> Following are some additional tests that should be fixed
> 1)ErrorMessageTest.java 2)StressMultiTest.java 3)Sttest.java
> 4)SysinfoTest.java 5)DatabaseMetaDataTest.java
> 6)ResultSetsFromPreparedStatementTest.java
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
