Jenkins的Junit Test Hang

Question

we run our junit tests in Eclipse seems fine, but when we move it to hudson or jenkins, the tests seems hangs there never returns. its definitely the same code, I just wandering whats the difference between running tests in Eclipse and Hudson.

Answer 1

In eclipse you usually just run one test class or one test method. A "fresh" Java Virtual machine is started and stopped for this test.

I suppose that Jenkins runs all tests in one Java Virtual machine. This can make a huge difference.

Try to run all test outside eclipse and outside hudson at once (should be simple if you have a maven project). What is the result? Maybe you can configure your test run to fork the Java VM on each test (this is possible with maven by configuring the surefire plugin).

Answer 2

My guess would be to look at the memory limit. Try to increase the memory limit of the maven process started from Jenkins.

My other guess would be to look whether the Maven build from Jenkins is allowed to execute submodules parallel. If yes, it might cause some race conditions that are hard to find.

Answer 3

Are the tests executed in the same way in Eclipse and in Hudson? My guess is that the tests are executed one by one (or class by class) in Eclipse, and by a build script such as Maven or Ant in Hudson? What happens if you execute the test suite from a terminal on your local machine?