Community
Participate
Working Groups
Created attachment 220956 [details] four dumps (two from two runs) I've been playing some with trying to get performance tests running on my local machine, and was successful in getting the 'uiperformance' to run, but .... I think when they are finished ... they (or framework?) seems to hang. Just wanted to log a few javadumps in case someone can easily see what the issue it (I've not looked closely, myself.) I was using M20120829-1200 and IBM's VM 1.6.
Created attachment 220957 [details] results generated from last run While I did have to "ctlr-c" out of the run, perhaps those familiar with these tests can tell from these results if the tests were done ... or if the "Waiting for operation to complete...." dialog was "in between" tests? Note, tests took approx. an hour, and I wasn't patient enough to wait another hour to see if the 2 hour time out would suffice to end the process, but I did wait at least 20 minutes or so, so pretty sure it wasn't just busy. I may need to try again with larger heap, or something? Just wanted to capture what I had.
Created attachment 221872 [details] first of short run of uiperformance test I tried running the "uiperformance" tests again, on a different linux box, hoping to run only those and investigate its "hanging" influence on Hudson. But, I didn't get that far. The reason being was that as I watched the log (attached), it seemed to almost immediately starting to have "out of memory" issues. This was using M2 build, which has settings of -Xms256M -Xmx512M -XX:MaxPermSize=500m We have since increased max heap to 1024m, but it happened so quickly in this run, thought I would point it out by posting the log. UI committers (or, others) might find some "obvious" memory hot spots by running this test "locally"? [Subject to all the usual qualifications .. this was on an "experimental" machine, etc. ... but ... pretty sure basics were working.]
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
