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 "Mike Matrigali (JIRA)" <ji...@apache.org> on 2008/05/09 23:11:55 UTC

[jira] Updated: (DERBY-1848) jdbcapi/SetQueryTimeoutTest.java fails on IBM wctme 5.7

     [ https://issues.apache.org/jira/browse/DERBY-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali updated DERBY-1848:
----------------------------------

    Affects Version/s: 10.5.0.0

Saw again on the trunk in the following results, most recently on 5/6/08
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.1/649735-suites.All_diff.txt
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.1/649735-suites.All_diff.txt
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.1/650349-suites.All_diff.txt
http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/weme6.1/654381-suites.All_diff.txt

There was 1 failure:
1) SetQueryTimeoutTest(org.apache.derbyTesting.functionTests.tests.jdbcapi.JDBCHarnessJavaTest)junit.framework.ComparisonFailure: Output at line 7 expected:<Statement 1 completed> but was:<Test SetQueryTimeoutTest FAILED>
	at org.apache.derbyTesting.functionTests.util.CanonTestCase.compareCanon(CanonTestCase.java:100)
	at org.apache.derbyTesting.functionTests.util.HarnessJavaTest.runTest(HarnessJavaTest.java:91)
	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:103)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)
	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
	at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
	at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
	at junit.extensions.TestSetup.run(TestSetup.java:23)
	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)

> jdbcapi/SetQueryTimeoutTest.java fails on IBM  wctme 5.7
> --------------------------------------------------------
>
>                 Key: DERBY-1848
>                 URL: https://issues.apache.org/jira/browse/DERBY-1848
>             Project: Derby
>          Issue Type: Test
>          Components: Regression Test Failure
>    Affects Versions: 10.2.2.1, 10.3.1.4, 10.5.0.0
>         Environment: Windows
>            Reporter: Rajesh Kartha
>
> The following is the diff:
> *** Start: SetQueryTimeoutTest jdk1.3.1 subset - 2.2 derbyall:jdbcapi 2006-09-10 11:07:05 ***
> 7 del
> < Statement 1 completed
> 8 del
> < Statement 2 completed
> 9 del
> < Statement 3 completed
> 10 del
> < Testing timeout with an execute operation
> 11 del
> < Statements that should time out timed out, and statements that should complete completed
> 12 del
> < Testing setting a negative timeout value
> 13 del
> < Negative timeout value caused exception, as expected
> 14 del
> < Execute returned a ResultSet
> 15 del
> < Testing that Statement remembers timeout.
> 16 del
> < Testing that PreparedStatement remembers timeout.
> 17 del
> < Testing that CallableStatement remembers timeout.
> 18 del
> < Testing timeout with executeUpdate call.
> 19 del
> < Test SetQueryTimeoutTest PASSED
> 19a7,11
> > Test SetQueryTimeoutTest FAILED
> > org.apache.derbyTesting.functionTests.tests.jdbcapi.SetQueryTimeoutTest$TestFailedException: Unexpected exception in 1: java.sql.SQLException: The statement has been cancelled or timed out.
> > ERROR XCL52: The statement has been cancelled or timed out.
> > java.sql.SQLException: Invalid transaction state.
> > java.sql.SQLException: Invalid transaction state.
> Test Failed.
> *** End:   SetQueryTimeoutTest jdk1.3.1 subset - 2.2 derbyall:jdbcapi 2006-09-10 11:07:26 ***

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.