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 "Deepa Remesh (JIRA)" <de...@db.apache.org> on 2006/09/11 23:57:25 UTC
[jira] Created: (DERBY-1840) lang/TimeHandling.junit test fails on
jdk13 vms
lang/TimeHandling.junit test fails on jdk13 vms
-----------------------------------------------
Key: DERBY-1840
URL: http://issues.apache.org/jira/browse/DERBY-1840
Project: Derby
Issue Type: Test
Components: Regression Test Failure
Reporter: Deepa Remesh
Priority: Minor
This test fails on IBM and Sun jdk13. Failure details:
1) testCurrentTimestamp(org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest)junit.framework.AssertionFailedError: expected:<684> but was:<0>
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.assertTimeEqual(TimeHandlingTest.java:786)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkTimestampValue(TimeHandlingTest.java:588)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampValue(TimeHandlingTest.java:660)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampMultiple(TimeHandlingTest.java:455)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentMultiple(TimeHandlingTest.java:388)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentQuery(TimeHandlingTest.java:362)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.currentFunctionTests(TimeHandlingTest.java:174)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.testCurrentTimestamp(TimeHandlingTest.java:152)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:76)
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)
The test fails when comparing the millisecond value from java.sql.Time and Timestamp objects.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1840) lang/TimeHandling.junit test fails
on jdk13 vms
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648355#action_12648355 ]
Myrna van Lunteren commented on DERBY-1840:
-------------------------------------------
I actually saw this fail just this weekend in a 10.2 regression run...
Maybe we can add a check somewhere in the 10.2 test.
> lang/TimeHandling.junit test fails on jdk13 vms
> -----------------------------------------------
>
> Key: DERBY-1840
> URL: https://issues.apache.org/jira/browse/DERBY-1840
> Project: Derby
> Issue Type: Test
> Components: Regression Test Failure
> Reporter: Deepa Remesh
> Priority: Minor
>
> This test fails on IBM and Sun jdk13. Failure details:
> 1) testCurrentTimestamp(org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest)junit.framework.AssertionFailedError: expected:<684> but was:<0>
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.assertTimeEqual(TimeHandlingTest.java:786)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkTimestampValue(TimeHandlingTest.java:588)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampValue(TimeHandlingTest.java:660)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampMultiple(TimeHandlingTest.java:455)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentMultiple(TimeHandlingTest.java:388)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentQuery(TimeHandlingTest.java:362)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.currentFunctionTests(TimeHandlingTest.java:174)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.testCurrentTimestamp(TimeHandlingTest.java:152)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:76)
> 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)
> The test fails when comparing the millisecond value from java.sql.Time and Timestamp objects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-1840) lang/TimeHandling.junit test fails on
jdk13 vms
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-1840.
-----------------------------------
Resolution: Won't Fix
1.3.1 is no longer supported. Resolving as won't fix.
> lang/TimeHandling.junit test fails on jdk13 vms
> -----------------------------------------------
>
> Key: DERBY-1840
> URL: https://issues.apache.org/jira/browse/DERBY-1840
> Project: Derby
> Issue Type: Test
> Components: Regression Test Failure
> Reporter: Deepa Remesh
> Priority: Minor
>
> This test fails on IBM and Sun jdk13. Failure details:
> 1) testCurrentTimestamp(org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest)junit.framework.AssertionFailedError: expected:<684> but was:<0>
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.assertTimeEqual(TimeHandlingTest.java:786)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkTimestampValue(TimeHandlingTest.java:588)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampValue(TimeHandlingTest.java:660)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampMultiple(TimeHandlingTest.java:455)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentMultiple(TimeHandlingTest.java:388)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentQuery(TimeHandlingTest.java:362)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.currentFunctionTests(TimeHandlingTest.java:174)
> at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.testCurrentTimestamp(TimeHandlingTest.java:152)
> at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:76)
> 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)
> The test fails when comparing the millisecond value from java.sql.Time and Timestamp objects.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.