I am experiencing unusual eclipse freeze when I run test using TestNG. It goes until 57% and freezes. Is this because of any update or version mismatch
I am also facing the same problem.
Any solution for it??
Regards,
Fanindra
On Friday, 28 December 2012 15:24:21 UTC+5:30, amit tatiya wrote:I am experiencing unusual eclipse freeze when I run test using TestNG. It goes until 57% and freezes. Is this because of any update or version mismatch
--To view this discussion on the web visit https://groups.google.com/d/msg/testng-users/-/HQAb6-3-tnoJ.
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.
Just to update you all…this problem has been solved.
Following three things were done which resulted in solving this problem:
-Xms1024m
-Xmx2048m
In eclipse configuration settings file.
This may be due to having a previous running session hanging, and then trying to run another session.Go to your eclipse debug perspective and see what is running. There maybe an un-terminated previous thread/session hanging around which will have some control of testNG's communication port. So the newer session starts up but recieves wierd responses from the still open port, wont timeout per say and appears to hang at 57%.I noticed when running suites with a number of classes, that some classes will hang. Basically had to debug the test classes via eclipse to determine where they are hanging and determine a course of action to ensure continued running. (Sorry, have not found a single pattern as to the hanging). However, rn the test class by itself, there is no hang condition. Its as if a message has gone missing between a suite run and testNG next class to run selection.