Given that mustella compiles swfs before running them, perhaps if we added a compile-time / post-compile-time step that replaced calls to trace() with a logging utility call, we could do that instead? We'd have to re-write the bit that checks the flashlog.txt to use something else, but that would also mean that people wouldn't have to make a mm.cfg file on their computers anymore as well. Even ErrorReportingEnable could go away with the new global exception handlers.
Is possible to replace calls to trace() to that logging method with something like as3-commons-bytecode or perhaps a tweak to mxmlc? If it's a simpler fix, we could just change all the code to call that method directly. Find and replace for the win? Jeff On Tue, Aug 14, 2012 at 3:41 PM, Om <bigosma...@gmail.com> wrote: > On Tue, Aug 14, 2012 at 12:37 PM, Michael A. Labriola < > labri...@digitalprimates.net> wrote: > > > > > > But I'm not up on cloud computing so maybe there is a way to do > > client-side > > > testing in the cloud. > > > > > > > Side note. I did some work back just working to spin up multiple > instances > > of Flash Player running on the same machine and I was able to get the > time > > to run the test dramatically reduced. The one problem I never finished > > resolving was the output to the flashlog.txt, which is validated in some > of > > the mustella tests I believe. Other than that, just this strategy can > make > > it much faster. > > > > Mike > > > > > +1 to what Mike said. A combination of what Alex's test selecting script > + running the tests parallely on multiple flash player instances on the > same computer should be a big improvement. > > Thanks, > Om >
