Code coverage not starting

I previously used the new Code Coverage about 2 weeks and it worked.

But i'm in the process of writing a new component (and its unit tests) and was trying to get it working again, i switched my jdk to 1.5 as it is needed for enabling code coverage and tried to run the unit test (which runs fine under 1.4).

The program seems to never start, the run dialog stays indefinitely in "INstanciating tests" state, with a timer running.
I tried disabling coverage (but keeping jdk 1.5) and the tests run fine.

I'm using 5245, and running again Sun 1.5_0_06.
Have anyone already encountered this ? (i get no information in IDEA logs, nor exceptions)

9 comments
Comment actions Permalink

Could you take a thread dump using IDEA's action with a photo camera in run toolwindow?

0
Comment actions Permalink

I've had this issue from time to time. Re-starting the tests sometimes clears the problem up. It rarely happens more than a couple times in a row.

0
Comment actions Permalink

Unless you're using Linux with a 2.6 kernel :P
R

0
Comment actions Permalink

As far as I can tell it is not related to code coverage.

0
Comment actions Permalink

Hi Thibaut,

T> The program seems to never start, the run dialog stays indefinitely
T> in "INstanciating tests" state, with a timer running.

Same here. Enabling code coverage results in my tests never starting. No
matter what I try for the class patterns (I even tried with a single one),
the results are the same. At one time I left IDEA to try to start the tests
more than five minutes, with no result.

I was about to open a bug report, but then I thought I'd wait for the next
build to do some more investigations, seeing that a lot of people seem to
not have any issues with it.

Best,
Andrei


0
Comment actions Permalink

I managed to reproduce this. It only happens when you don't specifiy any filters for the configuration, and only in run mode with IDEA's launcher. So there are several workarounds for this: either execute in debug mode, or launch IDEA with -Didea.no.launcher=true property.

0
Comment actions Permalink

Oops, forgot to mention, that I've fixed this.

0

Please sign in to leave a comment.