Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 8 Feb 2011 22:58:57 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <2143848193.3821.1297205937491.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Created: (DERBY-5014) Tests should restore the timeout
 values to default after they are done running.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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