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 Mamta Satoor <ms...@gmail.com> on 2009/04/06 18:16:29 UTC
Failure in testCurrentTimestamp on 10.5 codeline using ibm16 on Linux
platform
Hi,
Just wondered if anyone is aware of the following failure on 10.5
codeline? Thanks.
There were 2 failures:
1) testCurrentTimestamp(org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest)junit.framework.AssertionFailedError:
CURRENT TIME after end of statement
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampValue(TimeHandlingTest.java:804)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampMultiple(TimeHandlingTest.java:571)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentMultiple(TimeHandlingTest.java:504)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentQuery(TimeHandlingTest.java:479)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.currentFunctionTests(TimeHandlingTest.java:291)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.testCurrentTimestamp(TimeHandlingTest.java:269)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)
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)
2) testCurrentTimestamp(org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest)junit.framework.AssertionFailedError:
CURRENT TIME before start of statement
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampValue(TimeHandlingTest.java:803)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentTimestampMultiple(TimeHandlingTest.java:571)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.checkCurrentMultiple(TimeHandlingTest.java:504)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.currentFunctionTests(TimeHandlingTest.java:436)
at org.apache.derbyTesting.functionTests.tests.lang.TimeHandlingTest.testCurrentTimestamp(TimeHandlingTest.java:269)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:45)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:105)
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 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)
Re: Failure in testCurrentTimestamp on 10.5 codeline using ibm16 on
Linux platform
Posted by Myrna van Lunteren <m....@gmail.com>.
On Mon, Jul 13, 2009 at 9:00 AM, Mamta Satoor<ms...@gmail.com> wrote:
> I see the failure again on 10.5 codeline(793171) with ibm142
>
I think this is because for some reason the Linux kernel on the
machine has reverted to the time-travelling implementation instead of
the altered one (VMI). I know someone's working on addressing this.
Myrna
Re: Failure in testCurrentTimestamp on 10.5 codeline using ibm16 on
Linux platform
Posted by Mamta Satoor <ms...@gmail.com>.
I see the failure again on 10.5 codeline(793171) with ibm142
Mamta
On Mon, Apr 6, 2009 at 10:01 AM, Myrna van
Lunteren<m....@gmail.com> wrote:
> I wonder if these instances are maybe related to unexpected time
> changes on the machine?
> Maybe the test can be adjusted to at least print out the expected and
> what it thinks is the current time.
> Myrna
>
Re: Failure in testCurrentTimestamp on 10.5 codeline using ibm16 on
Linux platform
Posted by Myrna van Lunteren <m....@gmail.com>.
I wonder if these instances are maybe related to unexpected time
changes on the machine?
Maybe the test can be adjusted to at least print out the expected and
what it thinks is the current time.
Myrna
Re: Failure in testCurrentTimestamp on 10.5 codeline using ibm16 on
Linux platform
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Knut Anders Hatlen <Kn...@Sun.COM> writes:
> Mamta Satoor <ms...@gmail.com> writes:
>
>> Hi,
>>
>> Just wondered if anyone is aware of the following failure on 10.5
>> codeline? Thanks.
>
> I found that it has happened once in Ole's testing, on the 10.3
> branch. See:
> http://dbtg.thresher.com/derby/test/10.3Branch/jvm1.6/testing/testlog/w2003/589147-suitesAll_diff.txt
Not sure if it's related, but the failure seen in Ole's tests coincided
with the change from daylight saving time (CEST -> CET) in October 2007.
--
Knut Anders
Re: Failure in testCurrentTimestamp on 10.5 codeline using ibm16 on
Linux platform
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Mamta Satoor <ms...@gmail.com> writes:
> Hi,
>
> Just wondered if anyone is aware of the following failure on 10.5
> codeline? Thanks.
I found that it has happened once in Ole's testing, on the 10.3
branch. See:
http://dbtg.thresher.com/derby/test/10.3Branch/jvm1.6/testing/testlog/w2003/589147-suitesAll_diff.txt
No bug has been logged, as far as I can see. (DERBY-1840 is close, but
the stack trace tells that it fails earlier.)
--
Knut Anders