If you are going to ask, you may want to ask that you also have access to wherever the flashlog.txt is going to end up.
BTW, I briefly considered the idea that we collect all mustella output some other way. Mustella is already set up to send its output over a socket, for example. However, one of the goals of BasicTests was to examine the flashlog for extraneous trace statements in the common code paths that BasicTests runs. Flashlog also contains the stacktraces of any unhandled exception during the test. We could (should?) solve the trace problem by doing some other analysis on the source or swcs. After all, BasicTests won't catch every trace statement left in the code. We do leave trace statements commented out for debugging, though. And now that we have 10.2 as the min player version, we might be able to use the UncaughtError subsystem to catch exceptions during the test. It is work, but maybe less work that trying to figure out Jenkins? On 12/13/12 1:19 PM, "Om" <bigosma...@gmail.com> wrote: > I believe that the mm.cfg file is missing on the windows slave. How would > I get this added on to that server? Should I send an email to > bui...@apache.org? > > Once we have that, we should at least get to know what is happening by > looking at the flashlog.txt dump. > > Thanks, > Om > > On Thu, Dec 13, 2012 at 1:15 PM, Om <bigosma...@gmail.com> wrote: > >> On Thu, Dec 13, 2012 at 1:11 PM, Justin Mclean >> <jus...@classsoftware.com>wrote: >> >>> Hi, >>> >>>> Yeah, it seems like there is some secret place that the Global Settings >>> are >>>> stored. You might want to run a dummy swf and see what the right-click >>>> global settings say are trusted locations. >>> >>> Can you add a trusted location via the command line/parameters to the >>> debug player in any way? >>> >>> >> If that was possible, it would be a major security flaw :-) >> -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
