So I have a jenkins slave that runs Fitnesse tests. I have several suites set to run on this one slave and each suite should take no more than a couple of hours. I have it automated to run at midnight and have the HTTP timeout set to 4 hours.
The problem I'm having is that when I run the suites, it goes through them and the fitnesse tests finish, but jenkins still hangs. The console output just has it running. Then eventually it will hit the 4 hour timeout and throw an exception. However, all of the fitnesse tests are finished and their history recorded in our database. I've tried increasing the 4 hour limit to 6 hours and that didn't work. I thought about perhaps the idea that fitnesse isn't returning the control back to jenkins, but I don't think that's the issue because all of my fitnesse tests have tear downs. Please advise as I don't have any idea as to where I should look to next. Thanks! -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-hangs-even-after-Fitnesse-tests-are-finished-tp4641038.html Sent from the Jenkins issues mailing list archive at Nabble.com.
