Hi Jan, No luck with either @call and START.
1. Using @call made no difference. The test stopped after ~9minutes. 2. The START command, made the test stop just after a few seconds (instead of ~9minutes) I think you are right about the EOF, so I tried redirect output from the tests, like java -DTestSuite="My Regression Test" -cp test.jar org.testng.TestNG -d "testng-results" MyTest.xml 1>console.log 2>&1 but that did not help, I still get "Process leaked file descriptors..." /Kristian On Wednesday, April 4, 2012 1:50:35 PM UTC+2, Jan Seidel wrote: > > Hi Kristian, > > let the log level as it is ;) > I think there is an EOF occurring in the data stream of the pipe that > is not meant to be addressed to Jenkins but rather to some file for > test results or cache. > Maybe you can encapsule it by running it separated in the batch job (I > think the batch command was START /C /B COMMAND or so) but first you > should try to place a simple call infront like: > > @call java -DTestSuite="My Regression Test" -cp test.jar > org.testng.TestNG -d "testng-results" MyTest.xml > This should put the entire batch job and hopefully also the piped > reading of Jenkins into idle or at least into a more restrictive > activity that hopefully lets you finish the test before Jenkins > continues ;) > > Take care > Jan > >
