[
https://issues.apache.org/jira/browse/DERBY-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12488767
]
Ugo Matrangolo commented on DERBY-2467:
---------------------------------------
I updated all the trunk code and restarted the test. It goes fine.
I think that the failure is caused by the fact that the test is executed inside
a suite where other tests can influence its environment.
The failing test depends heavily on the derby.language.maxMemoryPerTable
property. Changing this to a different value than 1
fails the test.
I'm investigating how this value can be influenced by other tests.
> Convert lang/updateCursor.java to JUnit
> ---------------------------------------
>
> Key: DERBY-2467
> URL: https://issues.apache.org/jira/browse/DERBY-2467
> Project: Derby
> Issue Type: Test
> Components: Test
> Affects Versions: 10.3.0.0
> Reporter: Ugo Matrangolo
> Assigned To: Ugo Matrangolo
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: DERBY-2467_diff_03_27.txt, DERBY-2467_diff_050407.txt,
> DERBY-2467_diff_050407_2.txt, DERBY-2467_diff_300307.txt,
> DERBY-2467_stat_03_27.txt, DERBY-2467_stat_050407.txt,
> DERBY-2467_stat_300307.txt
>
>
> Convert lang/updateCursor.java to JUnit
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
