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 "Siddharth Srivastava (JIRA)" <ji...@apache.org> on 2011/03/09 15:30:59 UTC

[jira] Commented: (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:comment-tabpanel&focusedCommentId=13004569#comment-13004569 ] 

Siddharth Srivastava commented on DERBY-5014:
---------------------------------------------

Any views on including this as Derby Test and Fix project in GSoC 2011 ?  (I am considering it to be in mine :) )

> 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
>              Labels: derby_triage10_8
>
> 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