the solution was that Selenium tests made firefox-bin crash because the $HOME variable was not set. This pulled Jenkins down and when the service manager saw it then restarted Jenkins service.
On Mar 7, 9:02 am, jabal <jant...@gmail.com> wrote: > (1) I moved running these tests to a separate jenkins job but it still > restarts. > (2) I placed the ant invocation into a separate shell script and the > my single build step is > executing this shell script: jenkins still restarts. > > very strange.. > > On Mar 7, 8:45 am, jabal <jant...@gmail.com> wrote: > > > > > > > > > hi! > > > I'm quite new to Jenkins CI but happy to have assembled a freestyle > > project that builds and test my program starting from git checkout. As > > the final point I wanted to integrate my Selenium tests into this > > process and added a final Ant build step that calls this target. I was > > struggling with the display server and playing with the $DISPLAY > > environment variable, when suddenly Jenkins started to do something > > very strange: when it gets to my ant target it throws a bunch of > > exeptions and restarts, with all build history thrown. (Can be > > reloaded from disk of after restart.) > > > In the log I see the messages that are similar to those shown in this > > issue:https://issues.jenkins-ci.org/browse/JENKINS-11938?page=com.atlassian... > > > hudson.util.IOException2: Unable to read /proj/nss/tools/jenkins/run/ > > jobs/myJob/builds/2012-03-06_13-52-08/build.xml > > 144019 at hudson.XmlFile.unmarshal(XmlFile.java:160) > > 144020 at hudson.model.Run.reload(Run.java:283) > > > If I run the very same ant target from bash logged in as jenkins, the > > tests run perfectly. Do you have any idea how to get this fixed? Do > > you have any workaround tips?
