Hmm, http://saros-build.imp.fu-berlin.de/jenkins/job/Test_Saros_STF/
Maybe you should pay a little bit more attention which test case fail at random (and those that were reported did not belong to "random failure sometimes") BR, Stefan On 31.07.2013 10:26, Patrick Schlott wrote: > Not sure if this was the error that caused the build to becoming > unstable (tests worked fine locally, so probably just a one of these That is why we have a CI ... we do not care (well maybe a bit) about local test results. > > "One-day-Jenkins" fails; Lets see tomorrow again), but nevertheless I > uploaded a quickfix to prevents this IAE from happening. > > http://saros-build.imp.fu-berlin.de/gerrit/#/c/868/ > > Am 31.07.2013 06:24, schrieb Stefan Rossbach: >> ERROR 04:17:11,028 [main] (Utils.java:213) Internal Error: >> java.lang.IllegalArgumentException: target must not be null >> at >> de.fu_berlin.inf.dpp.activities.business.ProgressActivity.<init>(ProgressActivity.java:37) >> at >> de.fu_berlin.inf.dpp.ui.RemoteProgressManager$RemoteProgress.close(RemoteProgressManager.java:108) >> at >> de.fu_berlin.inf.dpp.ui.RemoteProgressManager$3.userLeft(RemoteProgressManager.java:219) >> at >> de.fu_berlin.inf.dpp.project.internal.SharedProjectListenerDispatch.userLeft(SharedProjectListenerDispatch.java:29) >> at >> de.fu_berlin.inf.dpp.project.internal.SarosSession.removeUser(SarosSession.java:537) >> at >> de.fu_berlin.inf.dpp.net.business.LeaveAndKickHandler$4.run(LeaveAndKickHandler.java:145) >> at de.fu_berlin.inf.dpp.util.Utils$3.run(Utils.java:211) >> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) >> at >> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) >> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3515) >> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) >> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) >> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) >> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) >> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) >> at >> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) >> at >> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) >> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) >> at >> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) >> at >> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) >> at >> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) >> at >> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) >> at >> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) >> at >> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at java.lang.reflect.Method.invoke(Method.java:616) >> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) >> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) >> at org.eclipse.equinox.launcher.Main.run(Main.java:1407) >> at org.eclipse.equinox.launcher.Main.main(Main.java:1383) >> ERROR 04:17:11,028 [main] (Utils.java:214) Original caller: >> StackTrace: >> at de.fu_berlin.inf.dpp.util.Utils.wrapSafe(Utils.java:205) >> at >> de.fu_berlin.inf.dpp.net.business.LeaveAndKickHandler.leaveReceived(LeaveAndKickHandler.java:142) >> at >> de.fu_berlin.inf.dpp.net.business.LeaveAndKickHandler.access$4(LeaveAndKickHandler.java:112) >> at >> de.fu_berlin.inf.dpp.net.business.LeaveAndKickHandler$2.processPacket(LeaveAndKickHandler.java:68) >> at >> de.fu_berlin.inf.dpp.net.internal.XMPPReceiver.forwardPacket(XMPPReceiver.java:155) >> at >> de.fu_berlin.inf.dpp.net.internal.XMPPReceiver.access$1(XMPPReceiver.java:144) >> at >> de.fu_berlin.inf.dpp.net.internal.XMPPReceiver$3.run(XMPPReceiver.java:99) >> at de.fu_berlin.inf.dpp.util.Utils$3.run(Utils.java:211) >> at >> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) >> at java.util.concurrent.FutureTask.run(FutureTask.java:166) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) >> at java.lang.Thread.run(Thread.java:679) >> >> >> On 31.07.2013 04:21, nob...@fu-berlin.de wrote: >>> See <http://saros-build.imp.fu-berlin.de/jenkins/job/Test_STF/772/> >>> >>> >>> ------------------------------------------------------------------------------ >>> Get your SQL database under version control now! >>> Version control is standard for application code, but databases havent >>> caught up. So what steps can you take to put your SQL databases under >>> version control? Why should you start doing it? Read more to find out. >>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> DPP-Devel mailing list >>> DPP-Devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/dpp-devel >> ------------------------------------------------------------------------------ >> Get your SQL database under version control now! >> Version control is standard for application code, but databases havent >> caught up. So what steps can you take to put your SQL databases under >> version control? Why should you start doing it? Read more to find out. >> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk >> _______________________________________________ >> DPP-Devel mailing list >> DPP-Devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/dpp-devel > ------------------------------------------------------------------------------ > Get your SQL database under version control now! > Version control is standard for application code, but databases havent > caught up. So what steps can you take to put your SQL databases under > version control? Why should you start doing it? Read more to find out. > http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk > _______________________________________________ > DPP-Devel mailing list > DPP-Devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dpp-devel ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
