Community
Participate
Working Groups
See http://dev.eclipse.org/mhonarc/lists/platform-releng-dev/msg18345.html for some background, but if I'm reading it right, we can get the test framework to capture two thread dumps right before a test times out. We will need to update our custom "library.xml" file to pass in the ${timeout} value, as they did. (See https://bugs.eclipse.org/bugs/attachment.cgi?id=192770&action=diff for details.
Oh, correction ... now that I'm reading the referenced patch, it is not technically a "thread dump" ... just all the (active) stack traces at that moment ... which is really what most developers look at anyway, when debugging hangs ... just wanted to clarify terminology.
Created attachment 195906 [details] patch to add timeout to vm args, and udpate to latest platform to build with I'll be approving my own bug :) but will document well ... I'd like to try and take advantage of the improvement in ant runner, which will provide thread stack dump in console log, if a junit hangs. Do take advantage, we'd need M7 or above, so will move up to RC1 as base builder ... which should have pretty much final compiler, etc.
We get so many timeouts and hangs during unit tests, I think worth trying this out ... though, granted, some small chance something would go wrong and cause tests to fail prematurely, or something. And, we need to update base builder, to get near final compiler, etc. (We've been on M6 for last milestone, and RC1 ... we'll probably want to update again for RC3, at least).
released for final RC2 builds ... now I can't wait for a junit test to hang! :)
