db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-3337) convert jdbcapi/derbyStress.java to JUnit
Date Thu, 16 Jun 2011 18:40:47 GMT

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

Kathey Marsden commented on DERBY-3337:

In working on DERBY-4200, I decided finally that it makes most sense to first convert this
test to JUnit and add it to the memory suite and then add in a property for the periodic sleeps
where needed for DERBY-4200. I think I will rename the test to MemoryLeakFixesTest and move
it to the memory directory and suite.

Although the test currently runs with 64MB, I found that at least on Windows it runs fine
with 16MB like the other memory tests so I think can be pulled into memory._Suite

> convert jdbcapi/derbyStress.java to JUnit
> -----------------------------------------
>                 Key: DERBY-3337
>                 URL: https://issues.apache.org/jira/browse/DERBY-3337
>             Project: Derby
>          Issue Type: Task
>          Components: Test
>            Reporter: Kathey Marsden
>            Assignee: Kathey Marsden
>            Priority: Minor
> Convert derbyStress to JUnit. Framework will have to be setup for running in a low memory
profile.  Temporarily moved the test back to derbyall. See DERBY-3336 for details and possible
options moving forward.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message