db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-5014) Tests should restore the timeout values to default after they are done running.
Date Wed, 09 Mar 2011 17:38:59 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004676#comment-13004676
] 

Kathey Marsden commented on DERBY-5014:
---------------------------------------

I think this would be great as part of a GSOC test and fix project or even before if you want
to start working on it.
showing in your application that you have already started working on some of the issues is
always good.



> 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

Mime
View raw message