Looked at the full log. The tail of this log is misleading; the first mustella run failed so badly that the failures computation broke! Every SWF timed out like this:
[java] C:\jenkins_slave\workspace\flex-sdk_mustella-mobile\mustella\tests\mobile\C SSMediaQueries\swfs\ClassSelectorApp.xml Failed Timed out Can you pass along the contents of the .log files that should be next to a couple of the failing SWFs? Is there a way we can get read-only access to the file system from the browser? Then we could pull the log files ourselves. BTW, I ran the CSSMediaQueries folder locally and it all passed. Maybe a Windows thing? -Alex On 1/15/14 10:55 AM, "Alex Harui" <aha...@adobe.com> wrote: >OK. Didn't know that. How do we determine which tests to run in the >mobile run? It looks like it is trying to run non-mobile tests that >depend on MX components which aren't in a mobile config. > >-Alex > >On 1/15/14 9:59 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > >>> Yeah, but I was wondering if the main build screwed up and the mobile >>>run >>> is showing problems because it is downstream. >> >>Nope. Unlike the builds @ apache, the Mustella jobs are not dependent >>upon one another. They run in their own workspace. >> >>EdB >> >> >> >>-- >>Ix Multimedia Software >> >>Jan Luykenstraat 27 >>3521 VB Utrecht >> >>T. 06-51952295 >>I. www.ixsoftware.nl >
