turns out this issue is "just" for the problem of "running all test at once" ? then yes most likely not a showstopper for M3 as long as normal test runs, but please take a look since some of these issues does look weird. Most of the problems does though look like its attempting to run *all* tests no matter if their original submodule have specific configuration for them. ie. the WS ones missing JDK 5 setup. The bot ones should all be assigned to QE since they own them - and those might be the only one able to run properly like this if local test module settings aren't applied when running /max On Aug 13, 2011, at 02:38, Max Rydahl Andersen wrote: /max http://about.me/maxandersen