Most of the tests run relatively quickly but there are a set of tests that
import projects from the "eclipse" directory of the GWT source tree, and I've
seen these take over 5 minutes to run. The issue is that after doing the setup,
calls are made to JobsUtilities.waitForIdle(), and this gets blocked on the
Java Indexing jobs, which take over 5 minutes to complete.
There are several code paths that call JobsUtilities.waitForIdle(), so to
improve performance, you need to evaluate what is actually important to wait
for (it seems to be either that the Java builders complete or a classpath
change operation completes), and try waiting for just the job family of that
operation to complete.
Original issue reported on code.google.com by tpar...@google.com on 13 Feb 2015 at 5:25
Original issue reported on code.google.com by
tpar...@google.com
on 13 Feb 2015 at 5:25