Bryan Pendleton (JIRA) wrote:
[ https://issues.apache.org/jira/browse/DERBY-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488531 ]
Bryan Pendleton commented on DERBY-2526:
----------------------------------------
The UpdateCursorTest failure appears to be in a test (testVirtualMemoryHeap)
which is intimately tied to a particular query execution plan, but I'm not sure
how the test is forcing that particular query plan to be chosen. I sent a
message about that test to the derby-dev list to see if I could get some help.
Note that this test is failing in the tinderbox test too. I have not
checked whether it is the same failure, but it may not be related to
your proposed fix.
It seems this test has failed every time since it was converted from
JUnit. First time it failed was after this change:
Changes from 525953/526069 to 526070:
------------------------------------------------------------------------
r526070 | fuzzylogic | 2007-04-06 08:20:46 +0200 (Fri, 06 Apr 2007) | 4
lines
DERBY-2467: Convert lang/updateCursor.java to JUnit.
Committed for Ugo Matrangolo <[EMAIL PROTECTED]>
------------------------------------------------------------------------
D
java/testing/org/apache/derbyTesting/functionTests/tests/lang/updateCursor.java
D
java/testing/org/apache/derbyTesting/functionTests/tests/lang/updateCursor_derby.properties
U
java/testing/org/apache/derbyTesting/functionTests/tests/lang/_Suite.java
A
java/testing/org/apache/derbyTesting/functionTests/tests/lang/UpdateCursorTest.java
D
java/testing/org/apache/derbyTesting/functionTests/master/updateCursor.out
U
java/testing/org/apache/derbyTesting/functionTests/suites/derbylang.runall
--
Øystein
