On 4/12/08, Tiago R. Espinha (JIRA) <[EMAIL PROTECTED]> wrote: > > [ > https://issues.apache.org/jira/browse/DERBY-3574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588315#action_12588315 > ] > > Tiago R. Espinha commented on DERBY-3574: > ----------------------------------------- > > Ok I have a problem. > > I ran the command that Kathey posted (without the -D switch and with > -Xmx1024M since it gave out of memory with just 512MiB) and I got a stackload > of error lines after a few hours of running. Here's what it said in the end: > > FAILURES!!! > Tests run: 8010, Failures: 1, Errors: 8 > > Somehow I get the feeling that this is still a memory issue. I'm running the > tests in a Virtual Machine running Ubuntu 7.10 with just 1GiB of RAM, and > after a while, java is using all the RAM and has entered the swap file. > Should I discard the VM and run it all natively on XP where I have 2GiB of > RAM? > Actually, considering 8010 fixtures were run, 9 failing fixtures is not that bad... And yes, you'd get a stack for each of the failures/errors; that is to help analyze the problems - obviously, there is something off still.
I'm not entirely certain what is enough RAM these days, but I can run on a windows machine with 1.5 Gi RAM, and I used to be able to run on a box that had 1/4 Gi, although it's been a while I tried it (machine is slow as well as not much RAM). Ubuntu should be fine too. What made you think there was still a memory issue, did any of the error messages on the stacks indicate so? I'm curious to see an example of the stack traces. Myrna
