Hi Stefan, I stumbled upon this failed Jenkins Job (which is obviously back to stable now) and got curios. I tried to spot any significant differences between [1] and [2], but didn't find anything convincing. Is there an important difference, or was that failure in #437 just bad luck? And if so: How did you fix it (I suppose it was you) -- just by restarting the Job?
Thanks in advance, Franz [1] http://saros-build.imp.fu-berlin.de/jenkins/view/All/job/Test_STF/437/consoleText [2] http://saros-build.imp.fu-berlin.de/jenkins/view/All/job/Test_STF/438/consoleText -----Original Message----- From: nob...@fu-berlin.de [mailto:nob...@fu-berlin.de] Sent: Freitag, 14. September 2012 00:36 To: dpp-devel@lists.sourceforge.net Subject: [Dpp-devel] Build failed in Jenkins: Test_STF #437 See <http://saros-build.imp.fu-berlin.de/jenkins/job/Test_STF/437/> [...] ------------------------------------------------------------------------------ Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html _______________________________________________ Dpp-devel mailing list Dpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
