> -----Original Message----- > From: David Leangen [mailto:[EMAIL PROTECTED] > Sent: 04 October 2004 17:22 > To: Avalon framework users > Subject: RE: OutOfMemoryError when running unit tests > > > Hi, Peter, > > > Did yo do "svn update" to get the latest magic source? You MUST have the > > patch applied (see the dev list) since in the unpatched source, the for > > property is set too early and does not have any effect. > > Well, just to be sure, I just did a complete rebuild of avalon following, > of > course, an svn update. I know this is a bit overkill, but I figured it was > about time to do this anyway. Also, I am sure that the property > project.test.compile.fork is set to true. > > Unfortunately, though, this didn't solve the problem. I'm wondering what > I'm doing wrong now...
Setting the "project.test.compile.fork" to "true" results in the unit tests be executed in a separate jvm, however, the JUnitTask includes support for the execution of a forked jvm per test (which is a much finer level of granularity). You mentioned on IRC that the tests are running in Eclipse but not under Magic - as such the only thing that seems to make sense is that Eclipse is forking per test. I'm going to add option to Magic's JUnit task and I'll be interested in feedback on the results of running with different fork modes. Cheers, Stephen. > > Any ideas? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
