On Sun, Mar 3, 2013 at 8:31 PM, Alex Harui <aha...@adobe.com> wrote:

> We need to see the differences in the bitmap compare failures.
>
> But first:
> 1) Are you running FP11.1 or 11.2?  Anything older and newer might have
> bitmap compare issues.  But then I would expect even more failures.
>

I am running FP 11.1.  This is the
one: flashplayer11_1r102_63_win_sa_debug_32bit.exe



> 2) Can you try to open each font file in Assets/Fonts in the file Explorer?
> I got caught once when it thought one of the fonts was "downloaded from the
> internet" and that security dialog popped up.
>

I was able to open all the font files from explorer without any security
dialogs popping up.


> 3) The Marshall Plan failures imply that the HTTP server is not listening
> at
> port 80 or 8080 (depending on how you set it up and whether you used that
> Localhost8080 mixin) and rooted at mustella/tests.
>

I decided to run Jenkins on 8080 and mustella tests server from 80.  So, I
did not have to use the port switch arg.   I am in fact seeing the mustella
tests directory when I go to http://localhost from the browser.


>
> And to answer your earlier question, a second pass should be enough.  Any
> test that fails the second pass needs to be examined and fixed or excluded.
>

How would we fix timeout errors?  Or localconnection hangs?


> Really, we should be fixing all tests that fail on the first pass as well.
>
>
I agree.  That would make life easier.

Thanks,
Om


>
> On 3/3/13 3:06 PM, "Om" <bigosma...@gmail.com> wrote:
>
> > BTW, after running it on the same VM for 5 times, there are a whole bunch
> > of tests that are failing.  The complete results.txt file is here:
> >
> > http://pastebin.com/SvVtDigy
> >
> > How do we proceed?
> >
> > Thanks,
> > Om
> >
> > On Sun, Mar 3, 2013 at 7:34 AM, Frédéric THOMAS
> > <webdoubl...@hotmail.com>wrote:
> >
> >> Hi Om,
> >>
> >> It is difficult to say, it is really depending of the machine, consider
> >> that anyway, I run the test with -failures 3 times in general before the
> >> times out are gone.
> >> Not sure it helps but...
> >>
> >> -Fred
> >>
> >> -----Message d'origine----- From: OmPrakash Muppirala
> >> Sent: Sunday, March 03, 2013 7:02 AM
> >> To: dev@flex.apache.org
> >> Subject: Mustella CI server
> >>
> >>
> >> I have finally got a full run of Mustella running on a Windows Azure
> VM.  I
> >> am next planning to set up a Jenkins server to run it at least twice
> >> everyday at least 12 hours apart (on multiple servers including Carlos's
> >> private server, and at least one Windows Azure box)
> >>
> >> But I have a problem because of the Mustella works.  Ideally, I would
> like
> >> to get an email notification when the Mustella tests fail.  But it seems
> >> that some Mustella tests randomly fail due to time out errors.
> >>
> >> How many times should Jenkins run mini-run.sh -failures before it gives
> up
> >> and sends an email notification?  How was this handled internally at
> Adobe?
> >>
> >> Thanks,
> >> Om
> >>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>

Reply via email to