Should the compiled JS code be browser dependent? With multiple threads, it ran out of memory for me couple times. Lastly, if one browser failed, it stops the rest of the tests.
On Wed, Sep 9, 2009 at 5:02 PM, Amit Manjhi <[email protected]> wrote: > For now, it seems fine. It is the same issue when running multiple browsers > simultaneously during remoteweb or selenium tests. > > > On Wed, Sep 9, 2009 at 1:45 PM, Frank Lin <[email protected]> wrote: > >> Just one issue: is it okay to use test.out for all platforms if using >> '-htmlunit FF3, FF2, IE6, IE7'? >> test.out="${junit.out}/${build.host.platform}-htmlunit-web-mode" >> >> On Wed, Sep 9, 2009 at 11:40 AM, Amit Manjhi <[email protected]>wrote: >> >>> >>> >>> On Wed, Sep 9, 2009 at 11:19 AM, Frank Lin <[email protected]> wrote: >>> >>>> Hi Amit, >>>> >>>> >>>> On Wed, Sep 9, 2009 at 9:25 AM, <[email protected]> wrote: >>>> >>>>> Hi Frank, >>>>> >>>>> Instead of having individual ant commands for each browser emulation, >>>>> it >>>>> would be better to test all the browsers in parallel using -htmlunit >>>>> FF3, FF2, IE6, IE7. >>>>> >>>>> I would suggest more ant targets rather let ant optimize the >>>> parallelism since blaze might be able to shard them better. We might need >>>> Freeland's expertise on that. >>>> >>> >>> When all browsers are specified, the parallelism is at the JVM level, not >>> at the ant level. A separate HtmlUnit thread is started to emulate each >>> browser. >>> >> >> > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
