2014-10-01 151 views
2

我注意到当我尝试运行TestNG测试用例时,Eclipse UI卡住了57%。我直接在库中创建了TestNG设置(Build路径)并且没有Jars存在。我该如何解决?我现在坐了几个小时。Eclipse UI以57%的速度运行TestNG测试时死机

java.net.SocketTimeoutException: Accept timed out 
    at java.net.DualStackPlainSocketImpl.waitForNewConnection(Native Method) 
    at java.net.DualStackPlainSocketImpl.socketAccept(Unknown Source) 
    at java.net.AbstractPlainSocketImpl.accept(Unknown Source) 
    at java.net.PlainSocketImpl.accept(Unknown Source) 
    at java.net.ServerSocket.implAccept(Unknown Source) 
    at java.net.ServerSocket.accept(Unknown Source) 
    at org.testng.remote.strprotocol.BaseMessageSender.initReceiver(BaseMessageSender.java:128) 
    at org.testng.eclipse.ui.TestRunnerViewPart.startTestRunListening(TestRunnerViewPart.java:362) 
    at org.testng.eclipse.TestNGPlugin.connectTestRunner(TestNGPlugin.java:213) 
    at org.testng.eclipse.TestNGPlugin$2.run(TestNGPlugin.java:201) 
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) 
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) 
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4147) 
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3764) 
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) 
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) 
    at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) 
    at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) 
    at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) 
    at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) 
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) 
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) 
    at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) 
    at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) 
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) 
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) 
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) 
    at java.lang.reflect.Method.invoke(Unknown Source) 
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) 
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) 
    at org.eclipse.equinox.launcher.Main.run(Main.java:1465) 
    at org.eclipse.equinox.launcher.Main.main(Main.java:1438) 

回答

0

这是known issue。我也在过去体验过它。不幸的是,我不知道是什么修复了我。我所知道的,在基于Eclipse 4的STS版本中,我不会发生这种情况。但是,自那以后,我也从零开始创建了工作空间。

0

杀死Eclipse,重新启动它,清除所有的断点,然后重新设置你想要的断点。这在Eclipse Luna v4.4.1中适用于我。

https://github.com/cbeust/testng-eclipse/issues/55

而且仔细检查TestNG的库在类路径中。我有一个Maven项目,其中一些旧的项目已经解决并放入类路径中。我将TestNG依赖关系更高地移动到了pom.xml的依赖项部分,并且在删除断点时对其进行了修复并没有帮助。

0

创建一个新的工作区并导入您的项目。您的旧工作区已损坏。