You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Tiago R. Espinha (JIRA)" <ji...@apache.org> on 2011/06/06 23:20:58 UTC
[jira] [Resolved] (DERBY-5014) Tests should restore the timeout
values to default after they are done running.
[ https://issues.apache.org/jira/browse/DERBY-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tiago R. Espinha resolved DERBY-5014.
-------------------------------------
Resolution: Fixed
> 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