I will certainly try different approaches. Yes, the tests runs for hours and hours :-)
More interesting info. I can get the same behavior using VirtualBox. If I launch the test on a VirtualBox guest from a host using following command: vboxmanage guestcontrol "$VM_NAME" exec --image "cmd.exe" --username "user" --password "passwd" --wait-exit -- "/c java -cp test.jar org.testng.TestNG -d testng-results MyTest.xml" The command will return after ~9 minutes, *but*, the test will go on executing.The difference is that Jenkins stops the job. - Is there a way to start a Jenkins job, and let Jenkins wait for some text to appear, and use that to decide if the job has passed or failed, no matter what EOF or other occurred? /Kristian
