Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <811345.1176494355567.JavaMail.jira@brutus>
Date: Fri, 13 Apr 2007 12:59:15 -0700 (PDT)
From: "Ugo Matrangolo (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-2467) Convert lang/updateCursor.java to
 JUnit
In-Reply-To: <20936028.1174349972143.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ 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.