db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tiago R. Espinha (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5014) Tests should restore the timeout values to default after they are done running.
Date Mon, 06 Jun 2011 21:19:00 GMT

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

Tiago R. Espinha commented on DERBY-5014:
-----------------------------------------

suites.All was a go, so I went ahead and committed this patch with revision 1132747.

> 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

Mime
View raw message