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 On 4 Apr., 13:23, krikar <kristian.hermann.k...@gmail.com> wrote: > I'm trying to run a TestNG suite. This is not a daemon job. But the Jenkins > thinks it is, and shuts it down.... > > 1. I'm running a job on a Windows 7 slave. > 2. I execute a windows batch command: > java -DTestSuite="My Regression Test" -cp test.jar org.testng.TestNG -d > "testng-results" MyTest.xml > 3. After about 9 minutes, Jenkins stops the execution of the TestNG test > with: > Process leaked file descriptors. See > http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build > for more information > > So, as I understand, this can happen if you spawn a process, but thats not > what I'm doing here. I'm running a TestNG test that continuously talks on > STDOUT to Jenkins. But maybe TestNG is forking something?? > > I tired also to run the tests using ant, but I got the same failure: > Process leaked file descriptors. > Seehttp://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build > for more information > > One odd thing, I changed the log level (from the Manage Jenkins -> System > Log -> Log Levels) from OFF to ALL. This made the TestNG to successfully > run all tests!! I tried again, and when running for 20 minutes, I changed > the logging back to OFF, and just after a minute or so, the test stopped: > Process leaked file descriptors. > Seehttp://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build > for more information > > What to do?
