Forum Discussion
Thanks Alex. I'll double check the silent log file and report back if it says anything. As part of smartbear's debug process I tried to capture the report generation file, but when it crashed no file was produced, so the same thing may be happening with silent log.
Here's an update:
1) our IS department created a brand new virtual machine. At that point the test execute crash seemed to vanish, and I could see the jobs run to completion
2) We did the same 177 windows updates on the old physical 32 bit machine.
3) However, I started getting a JVM heap error when my Hudson job tried to copy over the test log.
C:\Users\hicksc\.hudson\jobs\QA - Event Interface\workspace>exit 0 Archiving artifacts FATAL: Java heap space java.lang.OutOfMemoryError: Java heap space
There are numerous google references to this error with Hudson or Jenkins. However I am not using any of the Maven or Ant build options in Hudson. So, I used the Java Control Panel to increase the runtime parameters
-Xmx2048m and that seemed to help. However, on the original physical 32 bit machine, I can not increase the JVM size to too much so I am seeing the heap error frequently on the longer jobs. On the new 64 bit virtual machine after updating to 64 bit java and increasing the JVM heap size to 1 gig -Xmx10240m I have not seen the JVM heap crash (yet).
For some reason I am now getting the JVM heap space crash on some test execute jobs.
The virtual server with twice the minimum requirements for test execute and improved everything over the old 32 bit physical machine is taking significantly longer to run each test. I am seeing CPU processor use bump to almost 98 % when it is running. This may be a known issue with running Test Execute on virtual machines since they do not have video cards. Our IS department suspects that TE may be hitting the CPU to compensate for the missing video card.
- tristaanogre8 years agoEsteemed Contributor
That is VERY interesting. So it does seem like it was some sort of environmental factor playing into the problem that a re-fresh/reset of the VM image somehow corrected. Very odd. Thanks for the update, chicks. Here's hoping you get the rest of it sorted out.
Related Content
Recent Discussions
- 2 days agoGane195