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

Kristian Waagan commented on DERBY-5797:
----------------------------------------

This is likely a test defect, and I believe it is caused by the poorer 
timer/clock resolution [by default] on Windows and the unfortunate timestamp 
comparison in the test.
I've been trying to reproduce this on the Windows systems I have easy access 
to, but I have been unable to do so this far. I see in the run mentioned above 
that there was only one failure, but it often comes as a pair (both embedded 
and client failing).

I'll rewrite the test logic, either adding a sleep (say 100 ms) or verifying 
the results using UUIDs instead of timestamps.
                
> AssertionFailedError in 
> functionTests.tests.lang.UpdateStatisticsTest.testDisposableStatsEagerness 
> ---------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5797
>                 URL: https://issues.apache.org/jira/browse/DERBY-5797
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.1.1
>         Environment: windows XP on vmware, ibm 1.6
>            Reporter: Myrna van Lunteren
>
> I noticed a test failure in UpdateStatisticsTest.testDisposableStatsEagerness.
> The link is: 
> http://people.apache.org/~myrnavl/derby_test_results/main/windows/testlog/ibm16/1345812-suites.All_diff.txt
> The stack trace: 
> testDisposableStatsEagerness(org.apache.derbyTesting.functionTests.tests.lang.UpdateStatisticsTest)junit.framework.AssertionFailedError
>                at 
> org.apache.derbyTesting.functionTests.tests.lang.UpdateStatisticsTest.testDisposableStatsEagerness(UpdateStatisticsTest.java:594)
>                at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>                at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
>                at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
>                at 
> org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:113)
>                at 
> org.apache.derbyTesting.junit.BaseJDBCTestCase.runBareOverridable(BaseJDBCTestCase.java:424)
>                at 
> org.apache.derbyTesting.junit.BaseJDBCTestCase.runBare(BaseJDBCTestCase.java:441)
>                at 
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>                at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>                at junit.extensions.TestSetup.run(TestSetup.java:25)
>                at 
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
>                at 
> junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
>                at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
>                at junit.extensions.TestSetup.run(TestSetup.java:25)
>                at 
> org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to