db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew McIntyre (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2543) testVirtualMemoryHeap junit test fails with "Virtual memory heap test failed! Got unexpected value. expected:<202> but was:<103>"
Date Fri, 13 Apr 2007 00:18:15 GMT

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

Andrew McIntyre commented on DERBY-2543:
----------------------------------------

It is clear from the comments in the previous test that the row order was an expected behavior
for the 'in-memory heap.'  But, it does seem a bit dubious to rely on any particular ordering
behavior for a Hashtable, and if we're talking about the behavior of BackingStoreHashtable,
then it is also worth mentioning that the underlying Hashtable was recently changed to a HashMap.

I'm also a bit confused about the fact that the old harness test reliably reproduced the behavior,
whereas the new JUnit one does not, and the fact that I cannot reproduce the failure that
the nightlies see. Also, from the failure in the nightlies, it appears that the row order
is not being reversed after all. It was expecting the first reversed row, but getting the
next row in order (103) instead. I'm curious if the rows are now coming back in order, or
if perhaps some improvement in memory usage is allowing us to stash one extra row in memory.

Should we just remove this testcase?

>  testVirtualMemoryHeap junit test fails with "Virtual memory heap test failed! Got unexpected
value. expected:<202> but was:<103>"
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2543
>                 URL: https://issues.apache.org/jira/browse/DERBY-2543
>             Project: Derby
>          Issue Type: Bug
>          Components: Regression Test Failure
>    Affects Versions: 10.3.0.0
>            Reporter: Mike Matrigali
>
> junit suite fails with the following error:
> 2) testVirtualMemoryHeap(org.apache.derbyTesting.functionTests.tests.lang.UpdateCursorTest)junit.framework.AssertionFailedError:
Virtual memory heap test failed! Got unexpected value. expected:<202> but was:<103>
> 	at org.apache.derbyTesting.functionTests.tests.lang.UpdateCursorTest.testVirtualMemoryHeap(UpdateCursorTest.java:178)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> 	at org.apache.derbyTesting.junit.BaseTestCase.runBare(BaseTestCase.java:88)
> 	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 junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
> 	at junit.extensions.TestSetup.run(TestSetup.java:25)

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


Mime
View raw message