I'm running a lot of JUnit tests in parallel, and I frequently get results along the lines of "N tests passed, M tests failed, P tests not started" (in contrast to this question, where no tests start at all).
What can cause this? I tried the "invalidate cache" option, however, this does not appear to solve anything. I should mention that tests take a while longer to run than the average JUnit tests (they can take up to 90 seconds to run), could this have anything to do with it? Right now I simply press "rerun failed tests" until I have forced IntelliJ do run all of them, which is rather cumbersome. I'm not sending anything weird to System.out either, and as I've stated I do get them to run eventually.
It runs tests for about ten minutes, and then no further tests are started. Is there a timeout of some kind somewhere that I can't find?
Sometimes this appears in the console after this happens:
Process finished with exit code 255
Version details:
There is a timeout option for the @Test annotation - have you tried increasing that?
And there is also a @Rule and Timeout option.
Info about Timeout for Tests - I hope it is relevant?