Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of cyrill.zadra@gmail.com
 designates 209.85.216.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAOHe5BErGWSWv5bcZ7HaQzWf1=Xf7QNBfJAPH4tQuXpta+q7Hw@mail.gmail.com>
References: 
 <CAMFKFRjxYnwjzAhN-rv8DzMPdtahZJoC=7KjQNirevHFF9S1oA@mail.gmail.com>
	<CC541EB7.1D47%pent@adobe.com>
	<CAMFKFRh4kNX19zGzu7C7a+HovwjUzkvA4RoC3FJcTg-e+Uu3RQ@mail.gmail.com>
	<CAOHe5BErGWSWv5bcZ7HaQzWf1=Xf7QNBfJAPH4tQuXpta+q7Hw@mail.gmail.com>
Date: Sat, 18 Aug 2012 18:52:00 +0200
Message-ID: 
 <CAOHe5BH0FxkiTrX1oygt+8vUsNWVcF6YNc4-=K5eQgZiJWRJVQ@mail.gmail.com>
Subject: Re: Getting Mustella to work.
From: Cyrill Zadra <cyrill.zadra@gmail.com>
To: flex-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0021cc0229c66f6b9204c78d1896

--0021cc0229c66f6b9204c78d1896
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi

Running mustella test ./mini_run.sh tests/LangPacks/German gives currently
following result.

     [java] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D
     [java]     Passes: 181
     [java]     Fails: 57
     [java] =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D

It looks like they failed because of a wrong font even I accepted the
license agreement for the Flash Player embedded font support. Is there
anything else that needs to be done that mustella uses the correct font?


On Sat, Aug 18, 2012 at 2:11 PM, Cyrill Zadra <cyrill.zadra@gmail.com>wrote=
:

> Hi
>
> Started to test the LangPacks/German and after a while I found out that
> this path is added to the exclude propertey (sdk.mustella.excludes). in
> mustella/properties/musstella1.properties. Is there a specific reason tha=
t
> all the language tests exception japanes are excluded?
>
> ./mini_run.sh tests/LangPacks/German
>
> regards
> cyrill
>
>
> On Sat, Aug 18, 2012 at 1:12 AM, Carlos Rovira <
> carlos.rovira@codeoscopic.com> wrote:
>
>> Thanks Peter!
>>
>> I'll check the link, seems very useful to start runing :)
>>
>>
>> 2012/8/17 Peter Ent <pent@adobe.com>
>>
>> > Thanks!
>> >
>> > I've been working on a Wiki page to get people started:
>> > https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview
>> >
>> > Please let us know if you need clarification on any of the details; it
>> is
>> > still a work in progress.
>> >
>> > Peter Ent
>> > Flex SDK Team
>> > Adobe Systems
>> >
>> > On 8/17/12 4:13 PM, "Carlos Rovira" <carlos.rovira@codeoscopic.com>
>> wrote:
>> >
>> > >I will spend the following days with Mustella in order to learn and
>> help,
>> > >as soon as I feel I had the knowledge, I'll ask here where I can star=
t.
>> > >I'd
>> > >like to be a committer since I think I can help more from inside than
>> from
>> > >outside, and afterall, I think Mustella must be known in the end in
>> order
>> > >to make patchs with a minimun of value.
>> > >
>> > >
>> > >
>> > >2012/8/17 Om <bigosmallm@gmail.com>
>> > >
>> > >> Bumping this thread up.
>> > >>
>> > >> Folks, please help out in fixing the broken tests in the Mustella
>> test
>> > >> suite.
>> > >>
>> > >> Yet-to-become-committers, this is a great way to get noticed and be
>> > >>invited
>> > >> to become committers.
>> > >>
>> > >> (I have yet to get my hands on Mustella.  Once I do, I will pick up
>> > >>package
>> > >> to work on)
>> > >>
>> > >> Thanks,
>> > >> Om
>> > >>
>> > >>
>> > >> On Mon, Aug 13, 2012 at 4:58 PM, Carol Frampton <cframpto@adobe.com=
>
>> > >> wrote:
>> > >>
>> > >> >
>> > >> >
>> > >> > On 8/13/12 6 :02PM, "Alex Harui" <aharui@adobe.com> wrote:
>> > >> >
>> > >> > >So, the Mustella test media is now checked in an compiles for
>> Peter
>> > >>and
>> > >> > >I.  As was previously agreed, many tests would be broken and the
>> > >> > >community would help repair them.  Please join in the fun.  You=
=B9ll
>> > >>learn
>> > >> > >about how it works and we=B9ll learn what else needs to be
>> documented
>> > >>or
>> > >> > >fixed.
>> > >> > >
>> > >> > >I think the best way is to carve out a folder of tests and get
>> them
>> > >>to
>> > >> > >run without errors.  Most errors should be because we changed te=
st
>> > >>media
>> > >> > >so component sizes and positions can be off.  If you are getting
>> > >> > >timeouts, try increasing the timeouts.
>> > >> > >
>> > >> > >I=B9m starting in on tests/spark/validators.  Feel free to choos=
e
>> some
>> > >> > >other folder of tests and start fixing!  And feel free to ask
>> > >>questions.
>> > >> >
>> > >> > I'm looking at the spark text components.
>> > >> >
>> > >> > Carol
>> > >> >
>> > >> >
>> > >>
>> > >
>> > >
>> > >
>> > >--
>> > >Carlos Rovira
>> > >Director de Tecnolog=EDa
>> > >M: +34 607 22 60 05
>> > >F:  +34 912 35 57 77
>> > ><http://www.codeoscopic.com>
>> > >CODEOSCOPIC S.A. <http://www.codeoscopic.com>
>> > >Avd. del General Per=F3n, 32
>> > >Planta 10, Puertas P-Q
>> > >28020 Madrid
>> >
>> >
>>
>>
>> --
>> Carlos Rovira
>> Director de Tecnolog=EDa
>> M: +34 607 22 60 05
>> F:  +34 912 35 57 77
>> <http://www.codeoscopic.com>
>> CODEOSCOPIC S.A. <http://www.codeoscopic.com>
>> Avd. del General Per=F3n, 32
>> Planta 10, Puertas P-Q
>> 28020 Madrid
>>
>
>

--0021cc0229c66f6b9204c78d1896--