I tend to run out of heap when I run tests from inside Eclipse, so
that's why I prefer doing it from the command line. I am sure we have
a big honking memory leak somewhere in the code.
(I don't have a profiler, unfortunately. What I should do is use the
profiling tools in the Windows version of Eclipse, which means firing
up a VM...)
On Apr 6, 2009, at 3:58, Janne Jalkanen <[email protected]>
wrote:
BTW, running the tests from inside Eclipse is way faster than
running "ant tests" and does not run MassiveRepositoryTest at all.
Just right-click on "org.apache.wiki.AllTests" and select "Run As ->
Unit Test".
It's a good idea to run "ant tests-init" first though.
/Janne
On 6 Apr 2009, at 05:53, Andrew Jaquith wrote:
Maybe I need to be whacked with the cluestick, but when I run 'ant
tests' I cannot, under any circumstances turn off
MassiveRepositoryTest. Setting "tests.stress.enabled=false" in
build.properties does not seem to work.
With 'massive' enabled, tests takes like 30-40 minutes to run, and I
need a faster test run cycle than that based on where we are in the
build cycle. How do I turn it off?
