Anyone else seeing a problem where preparing the unit tests is PAINFULLY slow? I get this little timer saying "preparing unit tests" and it sometimes counts up to 0:20 (as in twenty seconds). Right now I'm running a single unit test and it takes 9 seconds to "prepare", whatever that means. This is pretty annoying!

Note: I have two VMs open in debug mode while doing this. Not sure if this helps, but whenever I change my test and re-run it, the Make command takes forever as well (usually 5+ seconds). And then if I choose to Hotswap, it sometimes happens instantly but other times takes 3-4 seconds. Add it all up and my test-code-test cycle is getting REALLY delayed.

Anyone else seeing a problem where preparing the unit tests is PAINFULLY

slow? I get this little timer saying "preparing unit tests" and it sometimescounts up to 0:20 (as in twenty seconds). Right now I'm running a singleunit test and it takes 9 seconds to "prepare", whatever that means. This ispretty annoying!>

Note: I have two VMs open in debug mode while doing this. Not sure if this

helps, but whenever I change my test and re-run it, the Make command takesforever as well (usually 5+ seconds). And then if I choose to Hotswap, itsometimes happens instantly but other times takes 3-4 seconds. Add it all upand my test-code-test cycle is getting REALLY delayed.>

Actually "Instantiating tests..." doesn't mean "tests are still notinstantiated". You may see this until some of them becomes finished. Forinstance you may see such message if the first test takes much time to startup (in spite of test is counted started before TestCase.setUp() methodcalled).

Also, doing a project build (Make) has this weird delay that is the most obnoxious thing in the world. You guys really need to figure out where these delays are coming from (logging? some lock somewhere?) and get rid of them once and for all. I see delays (maybe related, maybe not) in unit tests, building, and debugging. The three things I do more of than anything else.