TestNG eclipse plug-in freezes eclipse

[Tamás Kende]

Hi all,

On Friday I decided to upgrade my testng plugin in my Helios (on Win7
64bit) previously I got version 5.9 (it is in the eclipse yoxos
marketplace). Everything went fine, till I try to run a test, then the
testng and the eclipse freezes at 57% (regardless of what I tried to
run (xml suite or test class)). Whole Eclipse freezes so I have to
kill the process... I don't see any testng logs, so I have no idea
what's happening.
Today I've downloaded a new Helios (simple java version not with JEE)
and I've installed the testng plugin and the m2eclipse plugin and it's
still not working....

Any solution or idea how to debug it?

Thanks you for your help,

Regards,

Tamas

[Cédric Beust ♔]

Version 5.9 is very old, please use the update site http://beust.com/eclipse

-- 

Cedric

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To post to this group, send email to testng...@googlegroups.com.
To unsubscribe from this group, send email to testng-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/testng-users?hl=en.

--
Cédric

[Tamás Kende]

Sorry Cedric, I was not clear enough, the version 5.9 is working for
me, the problem is with the newest 5.14 version. I used the update
site to upgrade the testng.

Regards,

Tamas

On nov. 22, 16:22, Cédric Beust ♔ <ced...@beust.com> wrote:
> Version 5.9 is very old, please use the update sitehttp://beust.com/eclipse

>
> --
> Cedric
>
>
>
>
>
>
>
>
>
> On Mon, Nov 22, 2010 at 2:09 AM, Tamás Kende <kende.ta...@gmail.com> wrote:
> > Hi all,
>
> > On Friday I decided to upgrade my testng plugin in my Helios (on Win7
> > 64bit) previously I got version 5.9 (it is in the eclipse yoxos
> > marketplace). Everything went fine, till I try to run a test, then the
> > testng and the eclipse freezes at 57% (regardless of what I tried to
> > run (xml suite or test class)). Whole Eclipse freezes so I have to
> > kill the process... I don't see any testng logs, so I have no idea
> > what's happening.
> > Today I've downloaded a new Helios (simple java version not with JEE)
> > and I've installed the testng plugin and the m2eclipse plugin and it's
> > still not working....
>
> > Any solution or idea how to debug it?
>
> > Thanks you for your help,
>
> > Regards,
>
> > Tamas
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "testng-users" group.
> > To post to this group, send email to testng...@googlegroups.com.
> > To unsubscribe from this group, send email to

> > testng-users...@googlegroups.com<testng-users%2Bunsubscribe@google groups.com>
> > .

[Cédric Beust ♔]

Hi Tamás,

On Mon, Nov 22, 2010 at 9:48 AM, Tamás Kende <kende...@gmail.com> wrote:

Sorry Cedric, I was not clear enough, the version 5.9 is working for
me, the problem is with the newest 5.14 version. I used the update
site to upgrade the testng.

Ah ok. Is the run freezing on the same test every time?

--
Cédric

[Tamás Kende]

I'll try to explain what's happening:
1. I select an XML suite or a simple test class to run (run as Testng
suite or run as Testng test)
2. A counter on the bottom right corner of Eclipse starts and it goes
to 57%, so at the moment no tests are running, possibly only the
compilation happened, or the testng initialization started.
3. At 57% the Eclipse freezes.
It could be a compatibility issue, or a jar has a wrong version. I
don't know how to debug it. Everything is fine with the older version.
And another thing, I tried to run Eclipse as administrator and it does
not help.

Thanks

Tamas

On nov. 22, 18:50, Cédric Beust ♔ <ced...@beust.com> wrote:
> Hi Tamás,
>

[Cédric Beust ♔]

Based on what you're saying, there is a possibility that this is not caused by the TestNG plug-in (which Eclipse might still be trying to launch when it freezes).

I'm afraid there is no easy way to find out what's going on unless you can do some debugging on your end. Here are a few steps if you are so inclined:

• git clone http://github.com/cbeust/testng-eclipse
  
  
• Import that project as an "Existing project" in Eclipse.
  
  
• Start a new "Debug Eclipse application", make sure that org.testng.eclipse will be included in it (it should by default).
  
  
• In the new Eclipse instance, import the project that you're having a problem with and launch the XML file.
  
  
• When Eclipse freezes at 57%, press the pause button in the first Eclipse instance and see if any of the threads displayed in the debugger looks suspicious.

-- 

Cédric

--
You received this message because you are subscribed to the Google Groups "testng-users" group.
To post to this group, send email to testng...@googlegroups.com.

To unsubscribe from this group, send email to testng-users...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/testng-users?hl=en.

--
Cédric

[Tamás Kende]

Ok thanks, I will try it tomorrow and let you know the result.

Thank you for your help!

Regards

On nov. 22, 21:51, Cédric Beust ♔ <ced...@beust.com> wrote:
> Based on what you're saying, there is a possibility that this is not caused
> by the TestNG plug-in (which Eclipse might still be trying to launch when it
> freezes).
>
> I'm afraid there is no easy way to find out what's going on unless you can
> do some debugging on your end. Here are a few steps if you are so inclined:
>

>    - git clonehttp://github.com/cbeust/testng-eclipse
>
>    - Import that project as an "Existing project" in Eclipse.
>
>    - Start a new "Debug Eclipse application", make sure that

>    org.testng.eclipse will be included in it (it should by default).
>

>    - In the new Eclipse instance, import the project that you're having a

>    problem with and launch the XML file.
>

>    - When Eclipse freezes at 57%, press the pause button in the first

[Tamás Kende]

Hi Cedric,

I could manage to debug the Eclipse, but it seems it was something on
my workspace which causes the eclipse to freeze. When I start to use a
new workspace the issue disappeared. So its great now, but meanwhile I
found something else, I don't think it is necessary to open a new
thread for it.
I'm creating a dynamic xml suite, and it seems to me the
setThreadCount method of the XmlTest does not affect the output xml.

I wrote a dummy test to reproduce (Here I use the toXml method of the
XmlSuite, but it is the same when I add the suite to testng and call
run... so it is not something in the toXml method...)
It is possible that I misunderstand something, but in the DTD it is
allowed to overwrite the thread-count on test level.

/**
* Create a suite
*/
XmlSuite suite = new XmlSuite();
suite.setName("Security Framework Method level suite");
suite.setVerbose(1);
suite.setParallel("classes");
/**
* Set thread count to 5
*/
suite.setThreadCount(5);

/**
* Create two packages for each test in the suite
*/
List<XmlPackage> packages = new ArrayList<XmlPackage>();
XmlPackage xmlPackage = new XmlPackage();
xmlPackage.setName("Xml Package 1");
packages.add(xmlPackage);

List<XmlPackage> packages2 = new ArrayList<XmlPackage>();
XmlPackage xmlPackage2 = new XmlPackage();
xmlPackage2.setName("Xml Package 2");
packages2.add(xmlPackage2);

/**
* Create two test, and overwrite thread-count in the second test to
1
*/
XmlTest test1 = new XmlTest(suite);
test1.setName("Test1");
test1.setXmlPackages(packages);

XmlTest test2 = new XmlTest(suite);
test2.setName("Test2");
test2.setXmlPackages(packages2);
test2.setThreadCount(1);

Assert.assertTrue(suite.toXml().indexOf("thread-count=\"1\"")!
=-1,"The second thread-count is not found in the string");

Thank you for your help,

Tamas

[Nick Stolwijk]

Hi Tamás,

This morning my Eclipse also started crashing, can you be somewhat
more specific about what caused it in your workspace. I wouldn't like
to throw my workspace away.

With regards,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.iprofs.nl

[Tamás Kende]

Hi Nick,

I did not debug the cause, luckily I have a new workspace with few
projects so it was easy to me to create a new one.
Do you have the same issue? Does it crash at 57% when you start
testng ?

[Nick Stolwijk]

Yep, exactly at the 57%.

At first I thought there was some problem with my kernel, as at the
same time a kworker thread started to blast the hell out of my cpu. It
seemed that was a problem with the new kernel in combination with the
HP EliteBook 8540w and I needed to add a boot parameter
(pcie_ports=compat). I don't know if these bugs are related, are you
also running on a similar system? However, it still kept crashing
altough the kworker thread was doing peacefully its work.

I also have a new workspace, copy of settings luckily didn't cause the
hangup to switch over to my new workspace. I even have kept the
projects (and project files, altough I work with the M2Eclipse plugin)
and even that kept working.

If I can test anything else, I still have my old workspace.

Systemspecs:

Kubuntu 10.10, running the liquorix Sid main kernel
(2.6.36-0.dmz.15-liquorix-amd64)
Eclipse Helios (up to date)
TestNg plugin
Other plugins, including M2Eclipse, Checkstyle, PMD, Findbugs,
EclEmma, EGit, Hudson

With regards,

Nick Stolwijk
~Java Developer~

IPROFS BV.
Claus Sluterweg 125

2012 WS Haarlem
http://www.iprofs.nl

[Tamás Kende]

That's strange, I use Win7 64bit
Same Eclipse version and almost every plugin is the same, the only
difference is that I don't have EclEmma EGit and Hudson.
I removed these plugins, but if it works fine for you I will try to
reinstall them.

[Scott@Egistix]

Exact same problem here, hang at 57%
Will try the debug as well...
--
View this message in context: http://old.nabble.com/TestNG-eclipse-plug-in-freezes-eclipse-tp30277073p30283829.html
Sent from the testng-users mailing list archive at Nabble.com.

[Mohamed Mansour]

Can any of you run eclipse from the command line with clean?

./eclipse -clean

See if that works for you. This will not remove your projects from your workplace. 

-
Mohamed Mansour
m...@chromium.org

[Kate]

I had the same problem, crashed at 57%. I was able to get mine working
by changing my project build path to point to eclipse\plugins
\org.testng.eclipse_5.14.3.20101122_1106\lib\testng.jar instead of the
testng jar in my project.
Debugging I got this stack trace:
Thread [main] (Suspended)
PlainSocketImpl.socketAccept(SocketImpl) line: not available [native
method]
SocksSocketImpl(PlainSocketImpl).accept(SocketImpl) line: not
available
ServerSocket.implAccept(Socket) line: not available
ServerSocket.accept() line: not available
SerializedMessageSender(BaseMessageSender).initReceiver() line: 135
TestRunnerViewPart.startTestRunListening(IJavaProject, String, int,
ILaunch) line: 394
TestNGPlugin.connectTestRunner(ILaunch, IJavaProject, String, int)
line: 213
TestNGPlugin$2.run() line: 202
RunnableLock.run() line: 35
UISynchronizer(Synchronizer).runAsyncMessages(boolean) line: 134
Display.runAsyncMessages(boolean) line: 4041
Display.readAndDispatch() line: 3660
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2629
Workbench.runUI() line: 2593
Workbench.access$4(Workbench) line: 2427
Workbench$7.run() line: 670
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 663
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line:
149
IDEApplication.start(IApplicationContext) line: 115
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not
available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: not
available
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: not
available
Method.invoke(Object, Object...) line: not available
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
Main.main(String[]) line: 1383

[Cédric Beust ♔]

Hi Kate,

Thanks for the debugging info, it helps.

The Eclipse client is waiting a connection from RemoteTestNG which doesn't seem to be coming.

Can you try to install the plug-in on a fresh workspace? My first suspicion is that the testng.jar of your installation might be out of sync with the plug-in, but this shouldn't happen unless you made some modifications to the plug-in yourself.

If you are seeing the same problem on the clean workspace, you can install an older version of the plug-in from there:

http://beust.com/eclipse-old/

and I'll release a plug-in with more debugging information so we can find out what's going on.

By the way, you can already get some information by launching your configuration with the following vmargs:

-Declipse.testng.debug

although I'm not sure there will be enough log information to solve this particular issue.

Thanks again for your help in debugging this.

-- 

Cédric

--

You received this message because you are subscribed to the Google Groups "testng-users" group.
To post to this group, send email to testng...@googlegroups.com.
To unsubscribe from this group, send email to testng-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/testng-users?hl=en.

--
Cédric

[Kate]

Hi Cedric,

I had version 5.14.1 of the testng.jar in my project's build path
because I also run the tests with ant so it was in my lib folder, I'm
guessing thats where the problem was. I just noticed the "Add TestNG
library" in the quick fix menu when the testng jar is missing, so I
added that and it works, thats probably how I should have had it set
up all along.

> > testng-users...@googlegroups.com<testng-users%2Bunsubscribe@google groups.com>
> > .

[Cédric Beust ♔]

Hi Kate,

Glad to hear this solved your problem.

-- 

Cédric

To unsubscribe from this group, send email to testng-users...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/testng-users?hl=en.

--
Cédric

[Scott@Egistix]

This solved my problem as well.
Thanks!
--
View this message in context: http://old.nabble.com/TestNG-eclipse-plug-in-freezes-eclipse-tp30277073p30297900.html

[Mohamed Mansour]

Hi everyone,

From my experimentation, I had it hangs as well at 57%. From looking at what happened. In Seamframework, they use TestNG 5.9 while eclipse plugin uses TestNG 5.14.

That makes Eclipse hang at 57%. By removing your projects TestNG and (update it), it will no longer hang. I updated Seamframework TestNG and it works beautifully.

I hope that will help any of you.

-
Mohamed Mansour

--

[Cédric Beust ♔]

I think I have identified why this is happening.

When you launch a TestNG configuration, the plug-in will add its own testng.jar file at the end of the classpath, but if your project already had testng.jar in its classpath, the plug-in will end using it and this will most likely cause a freeze or a crash.

I'll fix the plug-in as soon as I can.

-- 

Cédric

--
Cédric

[John]

Trying to use the plugin version 6.3.2, Eclipse 3.6 hangs when "Launching ..." reaches 57%. I had testng-6.0.1.jar in the classpath, but the hang is still occurring even after I remove the file. Would it be too hard to get the connection set-up to be done in a worker thread, so problems don't cause the UI to stop responding?

[Cédric Beust ♔]

Hi John,

I haven't noticed the UI freezing when this happens (I remember simply killing the process so I can fix the problem). If you're seeing something different, can you email me a small Eclipse project showing the problem?

Thanks.

-- 

Cédric

On Thu, Dec 8, 2011 at 6:04 PM, John <jwb...@gmail.com> wrote:

Trying to use the plugin version 6.3.2, Eclipse 3.6 hangs when "Launching ..." reaches 57%. I had testng-6.0.1.jar in the classpath, but the hang is still occurring even after I remove the file. Would it be too hard to get the connection set-up to be done in a worker thread, so problems don't cause the UI to stop responding?

--
You received this message because you are subscribed to the Google Groups "testng-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/testng-users/-/Nufc0M-c9LMJ.

[John Bito]

This seems to be related to a change made in the selenium jar - it includes a version of org.testng packages (not yet sure what version). In case it's obvious to you, this is the stack trace I get when I run the test from Ant.

  [testng] java.lang.NullPointerException
   [testng]     at org.testng.internal.

PoolService.isFinished(PoolService.java:148)
   [testng]     at org.testng.internal.PoolService.submitTasksAndWait(PoolService.java:104)
   [testng]     at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1159)
   [testng]     at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
   [testng]     at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:109)
   [testng]     at org.testng.TestRunner.runWorkers(TestRunner.java:1147)
   [testng]     at org.testng.TestRunner.privateRun(TestRunner.java:749)
   [testng]     at org.testng.TestRunner.run(TestRunner.java:600)
   [testng]     at org.testng.SuiteRunner.runTest(SuiteRunner.java:317)
   [testng]     at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:312)
   [testng]     at org.testng.SuiteRunner.privateRun(SuiteRunner.java:274)
   [testng]     at org.testng.SuiteRunner.run(SuiteRunner.java:223)
   [testng]     at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
   [testng]     at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
   [testng]     at org.testng.TestNG.runSuitesSequentially(TestNG.java:1039)
   [testng]     at org.testng.TestNG.runSuitesLocally(TestNG.java:964)
   [testng]     at org.testng.TestNG.run(TestNG.java:900)
   [testng]     at org.testng.TestNG.privateMain(TestNG.java:1182)
   [testng]     at org.testng.TestNG.main(TestNG.java:1146)

2011/12/8 Cédric Beust ♔ <ced...@beust.com>

[Cédric Beust ♔]

This usually happens because you have another testng.jar in your classpath. Try it from a clean workspace to verify.

-- 

Cédric

On Thu, Apr 11, 2013 at 2:03 AM, Kasun <info....@gmail.com> wrote:

Hi Cedric,

I have TestNG 6.8.1 installed in eclipse indigo. The TestNG version in the project pom file was 6.5.2 and I changed it to match the version of the plugin. But eclipse still freezes at 57% when I try to run OR debug a test class. I can't remove the TestNG library from my project workspace since all the test classes depend on that. And I can't remove the TestNG dependency from the pom file also. This has become so irritating now since I can't execute any test case using eclipse. Any help?

Thanks & regards,

Kasun

--
You received this message because you are subscribed to the Google Groups "testng-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.

To post to this group, send email to testng...@googlegroups.com.

Visit this group at http://groups.google.com/group/testng-users?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Kasun]

I tried with a different workspace but it didn't work. Even tried changing the testng plugin to match the version in the pom file. Still no luck.

[Krishnan Mahadevan]

Project > properties > TestNG > use project testng jar. 

Can you please try with this setting and see if that works ?

--
Thanks & Regards
Krishnan Mahadevan

"All the desirable things in life are either illegal, expensive, fattening or in love with someone else!"
My Scribblings @ http://wakened-cognition.blogspot.com/

[Fanindra Bapat]

Just to update you all…this problem has been solved.

Following three things were done which resulted in solving this problem:

•    Remove all existing breakpoints
•    Removing other versions of testing jars..Keeping only latest one i.e. 6.8 testng jar
•   Put the debug value as

-Xms1024m

-Xmx2048m

          In eclipse configuration settings file.

On Friday, 12 April 2013 08:12:23 UTC+5:30, Krishnan wrote:

Project > properties > TestNG > use project testng jar. 

Can you please try with this setting and see if that works ?

On Friday, April 12, 2013, Kasun wrote:

I tried with a different workspace but it didn't work. Even tried changing the testng plugin to match the version in the pom file. Still no luck.

On Thursday, April 11, 2013 9:38:36 PM UTC+5:30, Cédric Beust ♔ wrote:

This usually happens because you have another testng.jar in your classpath. Try it from a clean workspace to verify.

-- 

Cédric

On Thu, Apr 11, 2013 at 2:03 AM, Kasun <info....@gmail.com> wrote:

Hi Cedric,

I have TestNG 6.8.1 installed in eclipse indigo. The TestNG version in the project pom file was 6.5.2 and I changed it to match the version of the plugin. But eclipse still freezes at 57% when I try to run OR debug a test class. I can't remove the TestNG library from my project workspace since all the test classes depend on that. And I can't remove the TestNG dependency from the pom file also. This has become so irritating now since I can't execute any test case using eclipse. Any help?

Thanks & regards,

Kasun

--
You received this message because you are subscribed to the Google Groups "testng-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to testng-users...@googlegroups.com.

To post to this group, send email to testng...@googlegroups.com.

Visit this group at http://groups.google.com/group/testng-users?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
You received this message because you are subscribed to the Google Groups "testng-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to testng-users+unsubscribe@googlegroups.com.

To post to this group, send email to testng...@googlegroups.com.
Visit this group at http://groups.google.com/group/testng-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Kasun]

Krishnan,

I tried that but it only worked perfectly once. When I try to run the same test again (or any other test), it still fails.

Fanindra Bapat

Do you mean in the eclipse.ini file? If so, i get the error message saying "Failed to create the Java Virtual Machine"

-Kasun-

[Fanindra Bapat]

Right...You need to change in eclipse.ini file...also made changes to following
1.Navigate to windows tab in eclipse >> preferences
2.Expand Testng >> Run/Debug
3.Put value as "-XX:MaxPermSize=512m -Xmx1024M" in jvm args

[Kasun]

What did you mean by 

"Put the debug value as -Xms1024m -Xmx2048m"

Do you mean in -vmargs?

BTW I did what you mentioned here but still no luck

[Yogini Upadhye]

Hi Kasun and Cedric

I am facing same issue, TestNG hangs at 57%.

I have eclipse Indigo
TestnG plugin 6.8.1
In my pom.xml there is dependency for TestNG 6.8

I tried few things like setting -VMargs in TestNG -"-XX:MaxPermSize=512m -Xmx1024M" etc but that did not help.


Can anyone please please help? I can not run my tests.:(


On Monday, November 22, 2010 5:09:18 AM UTC-5, Tamás Kende wrote:

Hi all,

On Friday I decided to upgrade my testng plugin in my Helios (on Win7
64bit) previously I got version 5.9 (it is in the eclipse yoxos
marketplace). Everything went fine, till I try to run a test, then the
testng and the eclipse freezes at 57% (regardless of what I tried to
run (xml suite or test class)). Whole Eclipse freezes so I have to
kill the process... I don't see any testng logs, so I have no idea
what's happening.
Today I've downloaded a new Helios (simple java version not with JEE)
and I've installed the testng plugin and the m2eclipse plugin and it's
still not working....

Any solution or idea how to debug it?

Thanks you for your help,

Regards,

Tamas

[avinash verma]

Sorry for replying to a very old thread. But I faced similar issue and possible solutions on different forums did not help. 

In my case, I found that localhost in my etc/hosts file was pointing to my machine ip not to 127.0.0.1. Once I corrected that, issues was resolved.