You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flex.apache.org by Alex Harui <ah...@adobe.com> on 2012/08/14 00:02:49 UTC

Getting Mustella to work.

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’ll learn about how it works and we’ll 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 test media so component sizes and positions can be off.  If you are getting timeouts, try increasing the timeouts.

I’m starting in on tests/spark/validators.  Feel free to choose some other folder of tests and start fixing!  And feel free to ask questions.

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

On 8/28/12 7:08 AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:

>> regarding your 274...Erik and I gets only 273! ...as you say is very
>> frustrating the disparty of results and the OS inconsistences...
> 
> Before I went back and got a fresh working copy this morning, I got
> 274 tests as well, just not all passes... Running the 'old' working
> copy with -createImages got me 274 tests passed.
> 
> These results are not far off, but what causes that one test to appear
> at some point?
Which test is it?

I'm not sure why we get inconsistent tests run numbers.  It might be a
problem in the handshake between the runner and the SWFs.  For sure, if you
get a SWF timeout that will affect the numbers.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Erik de Bruin <er...@ixsoftware.nl>.

> regarding your 274...Erik and I gets only 273! ...as you say is very
> frustrating the disparty of results and the OS inconsistences...

Before I went back and got a fresh working copy this morning, I got
274 tests as well, just not all passes... Running the 'old' working
copy with -createImages got me 274 tests passed.

These results are not far off, but what causes that one test to appear
at some point?

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Peter,

thanks I now understand the -createImages better.

regarding your 274...Erik and I gets only 273! ...as you say is very
frustrating the disparty of results and the OS inconsistences...


2012/8/28 Peter Ent <pe...@adobe.com>:
> I just ran tests/components/Application (without -createImages) and
> received 274 (not 273!) passes. I will update the wiki this number.
>
> Personally, I find Mustella frustrating in that it gives me inconsistent
> passes and fails. You would think that each time you run it it would give
> you the same result. I don't know why it does not always do that and we
> need to figure this out. Alex might know or at least be able to explain
> the behavior.
>
> --peter
>
> On 8/28/12 5:50 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
>>Hi Erik,
>>
>>just try the Applications folder with:
>>
>>./mini_run.sh -createImages tests/Application/
>>
>>[java] =====================================================
>>     [java]     Passes: 273
>>     [java]     Fails: 0
>>     [java] =====================================================
>>
>>I'm on Mac OSX 10.8.1, as you say there's a missing tess the 124... :?
>>(maybe in Exclussion list?)
>>
>>Maybe Peter could know something about it.
>>
>>But, what is clear is that this folder seems ok...
>>
>>
>>
>>2012/8/28 Erik de Bruin <er...@ixsoftware.nl>:
>>> Carlos,
>>>
>>>> you should try to rerun with -createImages flag. See if that helps
>>>
>>> I just did: I fetched a clean working copy of the develop branch of
>>> the SDK and ran "./mini_run.sh tests/Application -createImages"
>>>
>>> It now passes 273 tests... which is a bit more than the table on the
>>> Wiki suggests there should be (124). Weird, or just a whoopsie in the
>>> table?
>>>
>>> Should I run all test with "-createImages"? Or only the first time I
>>>run a test?
>>>
>>> EdB
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>>--
>>Carlos Rovira
>>Director de Tecnología
>>M: +34 607 22 60 05
>>F:  +34 912 35 57 77
>>CODEOSCOPIC S.A.
>>Avd. del General Perón, 32
>>Planta 10, Puertas P-Q
>>28020 Madrid
>



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I've added this Q&A session to the Mustella wiki.

Peter Ent
Flex SDK Team
Adobe Systems

On 8/29/12 11:56 PM, "Alex Harui" <ah...@adobe.com> wrote:

>
>
>
>On 8/29/12 7:14 PM, "Kiel" <ki...@gmail.com> wrote:
>
>> Greetings,
>> 
>> 1. What will I see on the error log If the fail is timeouts
>> ... will it be like "property_scriptTimeLimit_test1 Failed"?
>It depends on what kind of timeout.  Here is a step timeout from the
>console
>output:
>     [java] 
>gumbo/components/RadioButton/properties/FxRadioButton_properties
>FxRadioButton_select_icon Failed DispatchMouseClickEvent(body:step 1)
>Timeout waiting for updateComplete from srg.s1
>
>It tells you what step number failed and what event it was waiting for.  I
>don't have a SWF timeout's output handy, but it does not tell you what
>step
>number failed.
>
>So far I've found a couple of reasons for SWF timeouts:
>1) An uncaught exception is thrown.  In this case the stack trace is in
>the
>.log file for the SWF.
>2) A really slow SWF.  Sometimes a SWF is creating tons of widgets up
>front
>and can't get output to the test engine in time.  Other times, the SWF
>doesn't have the correct fonts embedded and lots of warnings go into the
>log
>and that delays getting output to the test engine.
>
>> 
>> 2. Is there a way to check that the Embedded Fonts are working in
>>Mustella?
>There is a CheckEmbeddedFonts mixin, but it currently only works for MX
>components.  You can look at the log to see if warnings are going in
>there.
>I can tell generally because the fonts are Times New Roman in Spark if the
>font isn't embedded.  Or it will show up in the debug console when I run
>the
>SWF.
>
>> 
>> Mustella is something very new for me and I'm very much interested in
>> learning.
>> Very much appreciated.
>> 
>> Regards,
>> 
>> On 8/29/2012 10:33 PM, Alex Harui wrote:
>>> 
>>> 
>>> On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> Are the fails from timeouts? If so, reboot your machine and try again.
>>>> There is an issue with LocalConnection and I recall that Alex put a
>>>>change
>>>> into Mustella to deal with it, but it might not fix it all the time
>>>>(be
>>>> sure to sync mustella/as3 from the develop branch). Having so many
>>>> failures is generally a sign of this happening. I noted this on the
>>>>Wiki,
>>>> but it might need to stand out more.
>>> Also make sure you have embedded font support installed and working.
>>> 
>> 
>
>-- 
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/30/12 6:30 PM, "Kiel" <ki...@gmail.com> wrote:

> Greetings,
> 
> Thanks. That clears out a few things on Mustella.
> 
> The `Failed Timed out` on Mustella doesn't show up on the "results.txt".
> 1) Does this mean that there are _other_ "Failed" tests that doesn't
> show up on the "results.txt"
I've never looked in results.txt, I'm always using the console output and
.log files that go with the SWFs.
> 
> So it would be a good practice to log it entirely.
>      ./mini_run.sh tests/Application > applicationResult.txt
I just keep two console windows open.  One for the big runs, then I scroll
back through it to find folders to run individually.  But logging to file
should work as well.
> 
> 2) 'Reboot machine if there are fails on timeouts'
>      Does this mean the swf timeout, step timeout or any kind of timeout?
SWF Timeouts might require a reboot, but I haven't been caught by that since
I made those recent changes.  The others should not.
> 


-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Kiel <ki...@gmail.com>.

Greetings,

Thanks. That clears out a few things on Mustella.

The `Failed Timed out` on Mustella doesn't show up on the "results.txt".
1) Does this mean that there are _other_ "Failed" tests that doesn't 
show up on the "results.txt"

So it would be a good practice to log it entirely.
     ./mini_run.sh tests/Application > applicationResult.txt

2) 'Reboot machine if there are fails on timeouts'
     Does this mean the swf timeout, step timeout or any kind of timeout?

     [Step Timeout]  - shows up on "results.txt"

[java] gumbo/components/RadioButton/properties/FxRadioButton_properties
FxRadioButton_select_icon Failed DispatchMouseClickEvent(body:step 1)
Timeout waiting for updateComplete from srg.s1

     [SWF Timeout] - doesn't show up on "results.txt"

[java]
/Users/aharui/Work/apache/flex/mustella/tests/mx/styles/AdvancedStyleClient/
SWFs/ADV_flex_component_global_main.swf  Failed Timed out


Regards,

On 8/30/2012 2:02 PM, Alex Harui wrote:
> Oops!  Hit send too soon.
>
>       [java]
> /Users/aharui/Work/apache/flex/mustella/tests/mx/styles/AdvancedStyleClient/
> SWFs/ADV_flex_component_global_main.swf  Failed Timed out
>
> You can see it just mentions the SWF, no actual test or test step.
>
> On 8/29/12 10:38 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>> Here's a SWF timeout:
>>
>>
>>
>> On 8/29/12 8:56 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>>>
>>>
>>> On 8/29/12 7:14 PM, "Kiel" <ki...@gmail.com> wrote:
>>>
>>>> Greetings,
>>>>
>>>> 1. What will I see on the error log If the fail is timeouts
>>>> ... will it be like "property_scriptTimeLimit_test1 Failed"?
>>> It depends on what kind of timeout.  Here is a step timeout from the console
>>> output:
>>>       [java] gumbo/components/RadioButton/properties/FxRadioButton_properties
>>> FxRadioButton_select_icon Failed DispatchMouseClickEvent(body:step 1)
>>> Timeout waiting for updateComplete from srg.s1
>>>
>>> It tells you what step number failed and what event it was waiting for.  I
>>> don't have a SWF timeout's output handy, but it does not tell you what step
>>> number failed.
>>>
>>> So far I've found a couple of reasons for SWF timeouts:
>>> 1) An uncaught exception is thrown.  In this case the stack trace is in the
>>> .log file for the SWF.
>>> 2) A really slow SWF.  Sometimes a SWF is creating tons of widgets up front
>>> and can't get output to the test engine in time.  Other times, the SWF
>>> doesn't have the correct fonts embedded and lots of warnings go into the log
>>> and that delays getting output to the test engine.
>>>
>>>> 2. Is there a way to check that the Embedded Fonts are working in Mustella?
>>> There is a CheckEmbeddedFonts mixin, but it currently only works for MX
>>> components.  You can look at the log to see if warnings are going in there.
>>> I can tell generally because the fonts are Times New Roman in Spark if the
>>> font isn't embedded.  Or it will show up in the debug console when I run the
>>> SWF.
>>>
>>>> Mustella is something very new for me and I'm very much interested in
>>>> learning.
>>>> Very much appreciated.
>>>>
>>>> Regards,
>>>>
>>>> On 8/29/2012 10:33 PM, Alex Harui wrote:
>>>>>
>>>>> On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Are the fails from timeouts? If so, reboot your machine and try again.
>>>>>> There is an issue with LocalConnection and I recall that Alex put a change
>>>>>> into Mustella to deal with it, but it might not fix it all the time (be
>>>>>> sure to sync mustella/as3 from the develop branch). Having so many
>>>>>> failures is generally a sign of this happening. I noted this on the Wiki,
>>>>>> but it might need to stand out more.
>>>>> Also make sure you have embedded font support installed and working.
>>>>>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Oops!  Hit send too soon.

     [java] 
/Users/aharui/Work/apache/flex/mustella/tests/mx/styles/AdvancedStyleClient/
SWFs/ADV_flex_component_global_main.swf  Failed Timed out

You can see it just mentions the SWF, no actual test or test step.

On 8/29/12 10:38 PM, "Alex Harui" <ah...@adobe.com> wrote:

> Here's a SWF timeout:
> 
> 
> 
> On 8/29/12 8:56 PM, "Alex Harui" <ah...@adobe.com> wrote:
> 
>> 
>> 
>> 
>> On 8/29/12 7:14 PM, "Kiel" <ki...@gmail.com> wrote:
>> 
>>> Greetings,
>>> 
>>> 1. What will I see on the error log If the fail is timeouts
>>> ... will it be like "property_scriptTimeLimit_test1 Failed"?
>> It depends on what kind of timeout.  Here is a step timeout from the console
>> output:
>>      [java] gumbo/components/RadioButton/properties/FxRadioButton_properties
>> FxRadioButton_select_icon Failed DispatchMouseClickEvent(body:step 1)
>> Timeout waiting for updateComplete from srg.s1
>> 
>> It tells you what step number failed and what event it was waiting for.  I
>> don't have a SWF timeout's output handy, but it does not tell you what step
>> number failed.
>> 
>> So far I've found a couple of reasons for SWF timeouts:
>> 1) An uncaught exception is thrown.  In this case the stack trace is in the
>> .log file for the SWF.
>> 2) A really slow SWF.  Sometimes a SWF is creating tons of widgets up front
>> and can't get output to the test engine in time.  Other times, the SWF
>> doesn't have the correct fonts embedded and lots of warnings go into the log
>> and that delays getting output to the test engine.
>> 
>>> 
>>> 2. Is there a way to check that the Embedded Fonts are working in Mustella?
>> There is a CheckEmbeddedFonts mixin, but it currently only works for MX
>> components.  You can look at the log to see if warnings are going in there.
>> I can tell generally because the fonts are Times New Roman in Spark if the
>> font isn't embedded.  Or it will show up in the debug console when I run the
>> SWF.
>> 
>>> 
>>> Mustella is something very new for me and I'm very much interested in
>>> learning.
>>> Very much appreciated.
>>> 
>>> Regards,
>>> 
>>> On 8/29/2012 10:33 PM, Alex Harui wrote:
>>>> 
>>>> 
>>>> On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> Are the fails from timeouts? If so, reboot your machine and try again.
>>>>> There is an issue with LocalConnection and I recall that Alex put a change
>>>>> into Mustella to deal with it, but it might not fix it all the time (be
>>>>> sure to sync mustella/as3 from the develop branch). Having so many
>>>>> failures is generally a sign of this happening. I noted this on the Wiki,
>>>>> but it might need to stand out more.
>>>> Also make sure you have embedded font support installed and working.
>>>> 
>>> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Here's a SWF timeout:



On 8/29/12 8:56 PM, "Alex Harui" <ah...@adobe.com> wrote:

> 
> 
> 
> On 8/29/12 7:14 PM, "Kiel" <ki...@gmail.com> wrote:
> 
>> Greetings,
>> 
>> 1. What will I see on the error log If the fail is timeouts
>> ... will it be like "property_scriptTimeLimit_test1 Failed"?
> It depends on what kind of timeout.  Here is a step timeout from the console
> output:
>      [java] gumbo/components/RadioButton/properties/FxRadioButton_properties
> FxRadioButton_select_icon Failed DispatchMouseClickEvent(body:step 1)
> Timeout waiting for updateComplete from srg.s1
> 
> It tells you what step number failed and what event it was waiting for.  I
> don't have a SWF timeout's output handy, but it does not tell you what step
> number failed.
> 
> So far I've found a couple of reasons for SWF timeouts:
> 1) An uncaught exception is thrown.  In this case the stack trace is in the
> .log file for the SWF.
> 2) A really slow SWF.  Sometimes a SWF is creating tons of widgets up front
> and can't get output to the test engine in time.  Other times, the SWF
> doesn't have the correct fonts embedded and lots of warnings go into the log
> and that delays getting output to the test engine.
> 
>> 
>> 2. Is there a way to check that the Embedded Fonts are working in Mustella?
> There is a CheckEmbeddedFonts mixin, but it currently only works for MX
> components.  You can look at the log to see if warnings are going in there.
> I can tell generally because the fonts are Times New Roman in Spark if the
> font isn't embedded.  Or it will show up in the debug console when I run the
> SWF.
> 
>> 
>> Mustella is something very new for me and I'm very much interested in
>> learning.
>> Very much appreciated.
>> 
>> Regards,
>> 
>> On 8/29/2012 10:33 PM, Alex Harui wrote:
>>> 
>>> 
>>> On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>> 
>>>> Hi,
>>>> 
>>>> Are the fails from timeouts? If so, reboot your machine and try again.
>>>> There is an issue with LocalConnection and I recall that Alex put a change
>>>> into Mustella to deal with it, but it might not fix it all the time (be
>>>> sure to sync mustella/as3 from the develop branch). Having so many
>>>> failures is generally a sign of this happening. I noted this on the Wiki,
>>>> but it might need to stand out more.
>>> Also make sure you have embedded font support installed and working.
>>> 
>> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/29/12 7:14 PM, "Kiel" <ki...@gmail.com> wrote:

> Greetings,
> 
> 1. What will I see on the error log If the fail is timeouts
> ... will it be like "property_scriptTimeLimit_test1 Failed"?
It depends on what kind of timeout.  Here is a step timeout from the console
output:
     [java] gumbo/components/RadioButton/properties/FxRadioButton_properties
FxRadioButton_select_icon Failed DispatchMouseClickEvent(body:step 1)
Timeout waiting for updateComplete from srg.s1

It tells you what step number failed and what event it was waiting for.  I
don't have a SWF timeout's output handy, but it does not tell you what step
number failed.

So far I've found a couple of reasons for SWF timeouts:
1) An uncaught exception is thrown.  In this case the stack trace is in the
.log file for the SWF.
2) A really slow SWF.  Sometimes a SWF is creating tons of widgets up front
and can't get output to the test engine in time.  Other times, the SWF
doesn't have the correct fonts embedded and lots of warnings go into the log
and that delays getting output to the test engine.

> 
> 2. Is there a way to check that the Embedded Fonts are working in Mustella?
There is a CheckEmbeddedFonts mixin, but it currently only works for MX
components.  You can look at the log to see if warnings are going in there.
I can tell generally because the fonts are Times New Roman in Spark if the
font isn't embedded.  Or it will show up in the debug console when I run the
SWF.

> 
> Mustella is something very new for me and I'm very much interested in
> learning.
> Very much appreciated.
> 
> Regards,
> 
> On 8/29/2012 10:33 PM, Alex Harui wrote:
>> 
>> 
>> On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>> 
>>> Hi,
>>> 
>>> Are the fails from timeouts? If so, reboot your machine and try again.
>>> There is an issue with LocalConnection and I recall that Alex put a change
>>> into Mustella to deal with it, but it might not fix it all the time (be
>>> sure to sync mustella/as3 from the develop branch). Having so many
>>> failures is generally a sign of this happening. I noted this on the Wiki,
>>> but it might need to stand out more.
>> Also make sure you have embedded font support installed and working.
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Kiel <ki...@gmail.com>.

Greetings,

1. What will I see on the error log If the fail is timeouts
... will it be like "property_scriptTimeLimit_test1 Failed"?

2. Is there a way to check that the Embedded Fonts are working in Mustella?

Mustella is something very new for me and I'm very much interested in 
learning.
Very much appreciated.

Regards,

On 8/29/2012 10:33 PM, Alex Harui wrote:
>
>
> On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>
>> Hi,
>>
>> Are the fails from timeouts? If so, reboot your machine and try again.
>> There is an issue with LocalConnection and I recall that Alex put a change
>> into Mustella to deal with it, but it might not fix it all the time (be
>> sure to sync mustella/as3 from the develop branch). Having so many
>> failures is generally a sign of this happening. I noted this on the Wiki,
>> but it might need to stand out more.
> Also make sure you have embedded font support installed and working.
>

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I'll put you down for Formatters. I don't recall about generic loader, I
will have to look.
--peter

On 8/29/12 3:25 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

>Hi Peter,
>
>great :). For "Formatters" I run the test some days ago and was
>successful with 0 errors, and "genericLoader" seems to be not a test,
>is like a part to use in other code, isn't it?
>
>2012/8/29 Peter Ent <pe...@adobe.com>:
>> Hi,
>>
>> I have taken another stab at organizing the Mustella Test Journal
>>section
>> on the Mustella wiki page. All of the top-level tests are now listed
>>(with
>> TBD if no one is working on them). Those tests that have lots of parts
>> have been broken out into their tables. I've color coded some of the
>>notes
>> to make it easier to see what issues are being tackled; I could use
>> updates if these are not current and correct.
>>
>> Thanks,
>> Peter
>>
>> On 8/29/12 10:33 AM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>>>
>>>
>>>
>>>On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> Are the fails from timeouts? If so, reboot your machine and try again.
>>>> There is an issue with LocalConnection and I recall that Alex put a
>>>>change
>>>> into Mustella to deal with it, but it might not fix it all the time
>>>>(be
>>>> sure to sync mustella/as3 from the develop branch). Having so many
>>>> failures is generally a sign of this happening. I noted this on the
>>>>Wiki,
>>>> but it might need to stand out more.
>>>
>>>Also make sure you have embedded font support installed and working.
>>>
>>>--
>>>Alex Harui
>>>Flex SDK Team
>>>Adobe Systems, Inc.
>>>http://blogs.adobe.com/aharui
>>>
>>
>
>
>
>-- 
>Carlos Rovira
>Director de Tecnología
>M: +34 607 22 60 05
>F:  +34 912 35 57 77
>CODEOSCOPIC S.A.
>Avd. del General Perón, 32
>Planta 10, Puertas P-Q
>28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Peter,

great :). For "Formatters" I run the test some days ago and was
successful with 0 errors, and "genericLoader" seems to be not a test,
is like a part to use in other code, isn't it?

2012/8/29 Peter Ent <pe...@adobe.com>:
> Hi,
>
> I have taken another stab at organizing the Mustella Test Journal section
> on the Mustella wiki page. All of the top-level tests are now listed (with
> TBD if no one is working on them). Those tests that have lots of parts
> have been broken out into their tables. I've color coded some of the notes
> to make it easier to see what issues are being tackled; I could use
> updates if these are not current and correct.
>
> Thanks,
> Peter
>
> On 8/29/12 10:33 AM, "Alex Harui" <ah...@adobe.com> wrote:
>
>>
>>
>>
>>On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>>
>>> Hi,
>>>
>>> Are the fails from timeouts? If so, reboot your machine and try again.
>>> There is an issue with LocalConnection and I recall that Alex put a
>>>change
>>> into Mustella to deal with it, but it might not fix it all the time (be
>>> sure to sync mustella/as3 from the develop branch). Having so many
>>> failures is generally a sign of this happening. I noted this on the
>>>Wiki,
>>> but it might need to stand out more.
>>
>>Also make sure you have embedded font support installed and working.
>>
>>--
>>Alex Harui
>>Flex SDK Team
>>Adobe Systems, Inc.
>>http://blogs.adobe.com/aharui
>>
>



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Hi,

I have taken another stab at organizing the Mustella Test Journal section
on the Mustella wiki page. All of the top-level tests are now listed (with
TBD if no one is working on them). Those tests that have lots of parts
have been broken out into their tables. I've color coded some of the notes
to make it easier to see what issues are being tackled; I could use
updates if these are not current and correct.

Thanks,
Peter

On 8/29/12 10:33 AM, "Alex Harui" <ah...@adobe.com> wrote:

>
>
>
>On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:
>
>> Hi,
>> 
>> Are the fails from timeouts? If so, reboot your machine and try again.
>> There is an issue with LocalConnection and I recall that Alex put a
>>change
>> into Mustella to deal with it, but it might not fix it all the time (be
>> sure to sync mustella/as3 from the develop branch). Having so many
>> failures is generally a sign of this happening. I noted this on the
>>Wiki,
>> but it might need to stand out more.
>
>Also make sure you have embedded font support installed and working.
>
>-- 
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/29/12 6:22 AM, "Peter Ent" <pe...@adobe.com> wrote:

> Hi,
> 
> Are the fails from timeouts? If so, reboot your machine and try again.
> There is an issue with LocalConnection and I recall that Alex put a change
> into Mustella to deal with it, but it might not fix it all the time (be
> sure to sync mustella/as3 from the develop branch). Having so many
> failures is generally a sign of this happening. I noted this on the Wiki,
> but it might need to stand out more.

Also make sure you have embedded font support installed and working.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Hi,

Are the fails from timeouts? If so, reboot your machine and try again.
There is an issue with LocalConnection and I recall that Alex put a change
into Mustella to deal with it, but it might not fix it all the time (be
sure to sync mustella/as3 from the develop branch). Having so many
failures is generally a sign of this happening. I noted this on the Wiki,
but it might need to stand out more.

--peter

On 8/29/12 5:48 AM, "Kiel" <ki...@gmail.com> wrote:

>Greetings,
>
>I'm having these results.
>
>First run:
>./mini_run.sh tests/Application
>=====================================================
>     Passes: 233
>     Fails: 50
>=====================================================
>
>2nd run:
>./mini_run.sh -createImages tests/Application
>=====================================================
>     Passes: 272
>     Fails: 15
>=====================================================
>
>3rd run:
>./mini_run.sh tests/Application
>=====================================================
>     Passes: 272
>     Fails: 15
>=====================================================
>
>(Expecting that this should be same as 1st Result)
>did a svn revert to undo the -createImages
>
>4th run:
>./mini_run.sh tests/Application
>=====================================================
>     Passes: 237
>     Fails: 50
>=====================================================
>
>(Expecting that this should be same as 1st Result)
>4 Missing Passes: Result 1 vs Result 4
>Application_Binding_ExplicitConstraints_Tests_Halo
>
>I'm kinda getting lost in the process...
>
>Regards,
>
>On 8/28/2012 9:11 PM, Carol Frampton wrote:
>>
>> On 8/28/12 5 :53AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>>
>>> -createImages is now the default run option?
>> Personally I think you should not use -createImages the first time you
>>run
>> the tests.  Use imageDiff to make sure the failures are just font
>> differences.  If they are then rerun with -createImages.  If you use
>> -createImages right away you won't find other problems because they now
>> become the "good" images.
>>
>>> EdB
>>>
>>>
>>>
>>> On Tue, Aug 28, 2012 at 11:50 AM, Carlos Rovira
>>> <ca...@codeoscopic.com> wrote:
>>>> Hi Erik,
>>>>
>>>> just try the Applications folder with:
>>>>
>>>> ./mini_run.sh -createImages tests/Application/
>>>>
>>>> [java] =====================================================
>>>>       [java]     Passes: 273
>>>>       [java]     Fails: 0
>>>>       [java] =====================================================
>>>>
>>>> I'm on Mac OSX 10.8.1, as you say there's a missing tess the 124... :?
>>>> (maybe in Exclussion list?)
>>>>
>>>> Maybe Peter could know something about it.
>>>>
>>>> But, what is clear is that this folder seems ok...
>>>>
>>>>
>>>>
>>>> 2012/8/28 Erik de Bruin <er...@ixsoftware.nl>:
>>>>> Carlos,
>>>>>
>>>>>> you should try to rerun with -createImages flag. See if that helps
>>>>> I just did: I fetched a clean working copy of the develop branch of
>>>>> the SDK and ran "./mini_run.sh tests/Application -createImages"
>>>>>
>>>>> It now passes 273 tests... which is a bit more than the table on the
>>>>> Wiki suggests there should be (124). Weird, or just a whoopsie in the
>>>>> table?
>>>>>
>>>>> Should I run all test with "-createImages"? Or only the first time I
>>>>> run a test?
>>>>>
>>>>> EdB
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Ix Multimedia Software
>>>>>
>>>>> Jan Luykenstraat 27
>>>>> 3521 VB Utrecht
>>>>>
>>>>> T. 06-51952295
>>>>> I. www.ixsoftware.nl
>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>> Director de Tecnología
>>>> M: +34 607 22 60 05
>>>> F:  +34 912 35 57 77
>>>> CODEOSCOPIC S.A.
>>>> Avd. del General Perón, 32
>>>> Planta 10, Puertas P-Q
>>>> 28020 Madrid
>>>
>>>
>>> -- 
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>

Re: Getting Mustella to work.

Posted by Kiel <ki...@gmail.com>.

Greetings,

I'm having these results.

First run:
./mini_run.sh tests/Application
=====================================================
     Passes: 233
     Fails: 50
=====================================================

2nd run:
./mini_run.sh -createImages tests/Application
=====================================================
     Passes: 272
     Fails: 15
=====================================================

3rd run:
./mini_run.sh tests/Application
=====================================================
     Passes: 272
     Fails: 15
=====================================================

(Expecting that this should be same as 1st Result)
did a svn revert to undo the -createImages

4th run:
./mini_run.sh tests/Application
=====================================================
     Passes: 237
     Fails: 50
=====================================================

(Expecting that this should be same as 1st Result)
4 Missing Passes: Result 1 vs Result 4
Application_Binding_ExplicitConstraints_Tests_Halo

I'm kinda getting lost in the process...

Regards,

On 8/28/2012 9:11 PM, Carol Frampton wrote:
>
> On 8/28/12 5 :53AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:
>
>> -createImages is now the default run option?
> Personally I think you should not use -createImages the first time you run
> the tests.  Use imageDiff to make sure the failures are just font
> differences.  If they are then rerun with -createImages.  If you use
> -createImages right away you won't find other problems because they now
> become the "good" images.
>
>> EdB
>>
>>
>>
>> On Tue, Aug 28, 2012 at 11:50 AM, Carlos Rovira
>> <ca...@codeoscopic.com> wrote:
>>> Hi Erik,
>>>
>>> just try the Applications folder with:
>>>
>>> ./mini_run.sh -createImages tests/Application/
>>>
>>> [java] =====================================================
>>>       [java]     Passes: 273
>>>       [java]     Fails: 0
>>>       [java] =====================================================
>>>
>>> I'm on Mac OSX 10.8.1, as you say there's a missing tess the 124... :?
>>> (maybe in Exclussion list?)
>>>
>>> Maybe Peter could know something about it.
>>>
>>> But, what is clear is that this folder seems ok...
>>>
>>>
>>>
>>> 2012/8/28 Erik de Bruin <er...@ixsoftware.nl>:
>>>> Carlos,
>>>>
>>>>> you should try to rerun with -createImages flag. See if that helps
>>>> I just did: I fetched a clean working copy of the develop branch of
>>>> the SDK and ran "./mini_run.sh tests/Application -createImages"
>>>>
>>>> It now passes 273 tests... which is a bit more than the table on the
>>>> Wiki suggests there should be (124). Weird, or just a whoopsie in the
>>>> table?
>>>>
>>>> Should I run all test with "-createImages"? Or only the first time I
>>>> run a test?
>>>>
>>>> EdB
>>>>
>>>>
>>>>
>>>> --
>>>> Ix Multimedia Software
>>>>
>>>> Jan Luykenstraat 27
>>>> 3521 VB Utrecht
>>>>
>>>> T. 06-51952295
>>>> I. www.ixsoftware.nl
>>>
>>>
>>> --
>>> Carlos Rovira
>>> Director de Tecnología
>>> M: +34 607 22 60 05
>>> F:  +34 912 35 57 77
>>> CODEOSCOPIC S.A.
>>> Avd. del General Perón, 32
>>> Planta 10, Puertas P-Q
>>> 28020 Madrid
>>
>>
>> -- 
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl

Re: Getting Mustella to work.

Posted by Carol Frampton <cf...@adobe.com>.


On 8/28/12 5 :53AM, "Erik de Bruin" <er...@ixsoftware.nl> wrote:

>-createImages is now the default run option?

Personally I think you should not use -createImages the first time you run
the tests.  Use imageDiff to make sure the failures are just font
differences.  If they are then rerun with -createImages.  If you use
-createImages right away you won't find other problems because they now
become the "good" images.

>
>EdB
>
>
>
>On Tue, Aug 28, 2012 at 11:50 AM, Carlos Rovira
><ca...@codeoscopic.com> wrote:
>> Hi Erik,
>>
>> just try the Applications folder with:
>>
>> ./mini_run.sh -createImages tests/Application/
>>
>> [java] =====================================================
>>      [java]     Passes: 273
>>      [java]     Fails: 0
>>      [java] =====================================================
>>
>> I'm on Mac OSX 10.8.1, as you say there's a missing tess the 124... :?
>> (maybe in Exclussion list?)
>>
>> Maybe Peter could know something about it.
>>
>> But, what is clear is that this folder seems ok...
>>
>>
>>
>> 2012/8/28 Erik de Bruin <er...@ixsoftware.nl>:
>>> Carlos,
>>>
>>>> you should try to rerun with -createImages flag. See if that helps
>>>
>>> I just did: I fetched a clean working copy of the develop branch of
>>> the SDK and ran "./mini_run.sh tests/Application -createImages"
>>>
>>> It now passes 273 tests... which is a bit more than the table on the
>>> Wiki suggests there should be (124). Weird, or just a whoopsie in the
>>> table?
>>>
>>> Should I run all test with "-createImages"? Or only the first time I
>>>run a test?
>>>
>>> EdB
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>> --
>> Carlos Rovira
>> Director de Tecnología
>> M: +34 607 22 60 05
>> F:  +34 912 35 57 77
>> CODEOSCOPIC S.A.
>> Avd. del General Perón, 32
>> Planta 10, Puertas P-Q
>> 28020 Madrid
>
>
>
>-- 
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. www.ixsoftware.nl

Re: Getting Mustella to work.

Posted by Erik de Bruin <er...@ixsoftware.nl>.

-createImages is now the default run option?

EdB



On Tue, Aug 28, 2012 at 11:50 AM, Carlos Rovira
<ca...@codeoscopic.com> wrote:
> Hi Erik,
>
> just try the Applications folder with:
>
> ./mini_run.sh -createImages tests/Application/
>
> [java] =====================================================
>      [java]     Passes: 273
>      [java]     Fails: 0
>      [java] =====================================================
>
> I'm on Mac OSX 10.8.1, as you say there's a missing tess the 124... :?
> (maybe in Exclussion list?)
>
> Maybe Peter could know something about it.
>
> But, what is clear is that this folder seems ok...
>
>
>
> 2012/8/28 Erik de Bruin <er...@ixsoftware.nl>:
>> Carlos,
>>
>>> you should try to rerun with -createImages flag. See if that helps
>>
>> I just did: I fetched a clean working copy of the develop branch of
>> the SDK and ran "./mini_run.sh tests/Application -createImages"
>>
>> It now passes 273 tests... which is a bit more than the table on the
>> Wiki suggests there should be (124). Weird, or just a whoopsie in the
>> table?
>>
>> Should I run all test with "-createImages"? Or only the first time I run a test?
>>
>> EdB
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> M: +34 607 22 60 05
> F:  +34 912 35 57 77
> CODEOSCOPIC S.A.
> Avd. del General Perón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/28/12 8:12 AM, "Carol Frampton" <cf...@adobe.com> wrote:

> 
> 
> On 8/28/12 9 :32AM, "Peter Ent" <pe...@adobe.com> wrote:
> 
>> I just ran tests/components/Application (without -createImages) and
>> received 274 (not 273!) passes. I will update the wiki this number.
>> 
>> Personally, I find Mustella frustrating in that it gives me inconsistent
>> passes and fails. You would think that each time you run it it would give
>> you the same result. I don't know why it does not always do that and we
>> need to figure this out. Alex might know or at least be able to explain
>> the behavior.
> 
> If you are on the same platform, most of the time it is because of timing
> diffs and poorly written or incorrectly written tests.  The test could be
> waiting on the wrong event so it proceeds before it really should.  Or
> rather than figuring out the right event to wait on it just has a pause
> (which is generally not a good thing to do) and it might not be long
> enough.
> 
That would affect pass vs fail, but shouldn't affect the total tests run.

We also want to know what tests are failing (without using -createImages)
and why.  That way we can better identify whether folks are having
configuration issues, or there are bad tests, or there are platform
differences.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carol Frampton <cf...@adobe.com>.


On 8/28/12 9 :32AM, "Peter Ent" <pe...@adobe.com> wrote:

>I just ran tests/components/Application (without -createImages) and
>received 274 (not 273!) passes. I will update the wiki this number.
>
>Personally, I find Mustella frustrating in that it gives me inconsistent
>passes and fails. You would think that each time you run it it would give
>you the same result. I don't know why it does not always do that and we
>need to figure this out. Alex might know or at least be able to explain
>the behavior.

If you are on the same platform, most of the time it is because of timing
diffs and poorly written or incorrectly written tests.  The test could be
waiting on the wrong event so it proceeds before it really should.  Or
rather than figuring out the right event to wait on it just has a pause
(which is generally not a good thing to do) and it might not be long
enough.

Carol

>
>--peter
>
>On 8/28/12 5:50 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
>>Hi Erik,
>>
>>just try the Applications folder with:
>>
>>./mini_run.sh -createImages tests/Application/
>>
>>[java] =====================================================
>>     [java]     Passes: 273
>>     [java]     Fails: 0
>>     [java] =====================================================
>>
>>I'm on Mac OSX 10.8.1, as you say there's a missing tess the 124... :?
>>(maybe in Exclussion list?)
>>
>>Maybe Peter could know something about it.
>>
>>But, what is clear is that this folder seems ok...
>>
>>
>>
>>2012/8/28 Erik de Bruin <er...@ixsoftware.nl>:
>>> Carlos,
>>>
>>>> you should try to rerun with -createImages flag. See if that helps
>>>
>>> I just did: I fetched a clean working copy of the develop branch of
>>> the SDK and ran "./mini_run.sh tests/Application -createImages"
>>>
>>> It now passes 273 tests... which is a bit more than the table on the
>>> Wiki suggests there should be (124). Weird, or just a whoopsie in the
>>> table?
>>>
>>> Should I run all test with "-createImages"? Or only the first time I
>>>run a test?
>>>
>>> EdB
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>
>>
>>
>>-- 
>>Carlos Rovira
>>Director de Tecnología
>>M: +34 607 22 60 05
>>F:  +34 912 35 57 77
>>CODEOSCOPIC S.A.
>>Avd. del General Perón, 32
>>Planta 10, Puertas P-Q
>>28020 Madrid
>

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I just ran tests/components/Application (without -createImages) and
received 274 (not 273!) passes. I will update the wiki this number.

Personally, I find Mustella frustrating in that it gives me inconsistent
passes and fails. You would think that each time you run it it would give
you the same result. I don't know why it does not always do that and we
need to figure this out. Alex might know or at least be able to explain
the behavior.

--peter

On 8/28/12 5:50 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

>Hi Erik,
>
>just try the Applications folder with:
>
>./mini_run.sh -createImages tests/Application/
>
>[java] =====================================================
>     [java]     Passes: 273
>     [java]     Fails: 0
>     [java] =====================================================
>
>I'm on Mac OSX 10.8.1, as you say there's a missing tess the 124... :?
>(maybe in Exclussion list?)
>
>Maybe Peter could know something about it.
>
>But, what is clear is that this folder seems ok...
>
>
>
>2012/8/28 Erik de Bruin <er...@ixsoftware.nl>:
>> Carlos,
>>
>>> you should try to rerun with -createImages flag. See if that helps
>>
>> I just did: I fetched a clean working copy of the develop branch of
>> the SDK and ran "./mini_run.sh tests/Application -createImages"
>>
>> It now passes 273 tests... which is a bit more than the table on the
>> Wiki suggests there should be (124). Weird, or just a whoopsie in the
>> table?
>>
>> Should I run all test with "-createImages"? Or only the first time I
>>run a test?
>>
>> EdB
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
>-- 
>Carlos Rovira
>Director de Tecnología
>M: +34 607 22 60 05
>F:  +34 912 35 57 77
>CODEOSCOPIC S.A.
>Avd. del General Perón, 32
>Planta 10, Puertas P-Q
>28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Erik,

just try the Applications folder with:

./mini_run.sh -createImages tests/Application/

[java] =====================================================
     [java]     Passes: 273
     [java]     Fails: 0
     [java] =====================================================

I'm on Mac OSX 10.8.1, as you say there's a missing tess the 124... :?
(maybe in Exclussion list?)

Maybe Peter could know something about it.

But, what is clear is that this folder seems ok...



2012/8/28 Erik de Bruin <er...@ixsoftware.nl>:
> Carlos,
>
>> you should try to rerun with -createImages flag. See if that helps
>
> I just did: I fetched a clean working copy of the develop branch of
> the SDK and ran "./mini_run.sh tests/Application -createImages"
>
> It now passes 273 tests... which is a bit more than the table on the
> Wiki suggests there should be (124). Weird, or just a whoopsie in the
> table?
>
> Should I run all test with "-createImages"? Or only the first time I run a test?
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Carlos,

> you should try to rerun with -createImages flag. See if that helps

I just did: I fetched a clean working copy of the develop branch of
the SDK and ran "./mini_run.sh tests/Application -createImages"

It now passes 273 tests... which is a bit more than the table on the
Wiki suggests there should be (124). Weird, or just a whoopsie in the
table?

Should I run all test with "-createImages"? Or only the first time I run a test?

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Erik,

you should try to rerun with -createImages flag. See if that helps


2012/8/27 Erik de Bruin <er...@ixsoftware.nl>:
> Oh, this is getting confusing:
>
>> failures)??? Next, I tried to run "Applications" but that obviously
>> didn't work, since there is no such directory. So I ran "Application"
>> and that gave me not the expected 124 passed tests (from the table in
>> the Wiki), but 181 passed and 37 failed tests.
>
> I just re-run that same test: "./mini_run.sh tests/Application" and
> now it reported 239 passes and 34 fails...
>
> What am I doing wrong? I'm on OS X Mountain Lion,  Java 1.6.0_33.
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl



-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Oh, this is getting confusing:

> failures)??? Next, I tried to run "Applications" but that obviously
> didn't work, since there is no such directory. So I ran "Application"
> and that gave me not the expected 124 passed tests (from the table in
> the Wiki), but 181 passed and 37 failed tests.

I just re-run that same test: "./mini_run.sh tests/Application" and
now it reported 239 passes and 34 fails...

What am I doing wrong? I'm on OS X Mountain Lion,  Java 1.6.0_33.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Welcome Gordon Smith as Apache Flex Committer

Posted by Jitendra Jain <wa...@gmail.com>.

Great news !! But for us (flex community), he is more popular than other
Gordons ;)

On Fri, Aug 24, 2012 at 4:42 PM, Michael Schmalle
<ap...@teotigraphix.com>wrote:

> This is great news!
>
> I know some of you may have wondered where I have been (maybe not :)) but
> I took a sabbatical from the Flash Player for 8 months, defining a future
> that wasn't dependent on the Flash Player.
>
> It's ironic that the day I write my first blog post since January, Gordon
> Smith joins and the Falcon compiler is almost here.
>
> I have been catching up in the archives as well.
>
> Mike
>
>
> Alex Harui wrote:
>
> Hey Everybody!
>
> I wanted to formally announce that Gordon Smith is our newest project
> committer.  Gordon will be shepherding the donation of the Falcon Compiler.
>
> Gordon is one of the original Flex engineers.  He's also quite busy outside
> of Flex as you can see here [1][2]. ;-)
>
> Please welcome him to the team!
>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
>


-- 
Thanks and Regards,
JJain,

   If you have knowledge, let others light their candles in it --Margaret
Fuller:

Re: Welcome Gordon Smith as Apache Flex Committer

Posted by Michael Schmalle <ap...@teotigraphix.com>.

This is great news!

I know some of you may have wondered where I have been (maybe not :))  
but I took a sabbatical from the Flash Player for 8 months, defining a  
future that wasn't dependent on the Flash Player.

It's ironic that the day I write my first blog post since January,  
Gordon Smith joins and the Falcon compiler is almost here.

I have been catching up in the archives as well.

Mike

Alex Harui wrote:

Hey Everybody!

I wanted to formally announce that Gordon Smith is our newest project
committer.  Gordon will be shepherding the donation of the Falcon Compiler.

Gordon is one of the original Flex engineers.  He's also quite busy outside
of Flex as you can see here [1][2]. ;-)

Please welcome him to the team!

-- 
Michael Schmalle - Teoti Graphix, LLC
http://www.teotigraphix.com
http://blog.teotigraphix.com

Re: Getting Mustella to work.

Posted by Justin Mclean <ju...@classsoftware.com>.

Hi,

> Hopefully GIT is on the road to remove this problems away! :)
Actually we'll have the same issue with Git. In the Gitflow model as you will need to be working in the develop branch to get the latest changes.

Thanks,
Jusin

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

This is crucial, since I was working on "trunk". Since svn plugins should
set a layout with trunk-branches-tags...it's normal to checkout trunk
directly so +1 to notice that on web so people goes to develop instead of
trunk

Hopefully GIT is on the road to remove this problems away! :)


2012/8/24 Justin Mclean <ju...@classsoftware.com>

> Hi,
>
> > 1) I couldn't (easily) find on which source I'm supposed to work.
> > Eventually I found an email from Alex referring to 'develop', and in
> > the SVN repo
> We probably need to update the SVN info on the web site/wiki to make it
> clear that people wishing to contribute need to work out of develop not
> trunk.
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

When you run any mustella test set for the first time, DO NOT use
-createImages. Just run it simply, such as:

./mini_run tests/components/Application

This will run the tests and compare them to the current baseline images.
If you get any compare-bitmap failures, use ImageDiff to look at the
bad.png (the one just created by your test run) and the baseline .png
files. 

If you see differences in the fonts, which is to be expected, or a
baseline image had a graphic and the bad.png has a solid rectangle, that
is also expected. In these cases, new baselines need to be generated. I
tried to generate and save all new baselines, but with the thousands of
tests, I'm sure I missed some.

If you see minor differences, like I saw yesterday with a pixel that's
difference or something just slightly off, we should know about it and
then we can figure out what to do. I think we should at least get
confirmation of the same difference from several people so we can make an
informed decision.

--peter

On 8/28/12 5:56 AM, "Kiel" <ki...@gmail.com> wrote:

>Hi Carlos,
>
>I'll follow the steps mentioned.
>Got concerned since the number of Passes & Fails didn't match the lists
>on wiki.
>
>Thanks.
>
>On 8/28/2012 5:46 PM, Carlos Rovira wrote:
>> Hi Kiel,
>>
>> take into account that github is not synced with SVN right now, so
>> there you will not find the latest fixes to mustella for at least 2
>> weeks.
>>
>> the team is working with INFRA to get official GIT support. For the
>> latest news this will resolved in the following 1 to 3 weeks.
>>
>> In the meanwhile, we and others use the following path to work:
>>
>> 1) get SVN "develop" branch.
>> 2) work in your local copy.
>> 3) when you are done with a fix, extract the folder (I do this with
>> eclipse-subversive)
>>
>> now:
>>
>> 4) in github, fork apache flex
>> 5) in your machine clone the fork
>> 6) create a branch
>> 7) copy the extract folder created in 3) overlaying it (overwrite)
>> 8) commit to the new branch
>> 9) push to origin (github)
>> 10) create a JIRA ticket
>> 11) create a pull request
>> 12) link the jira ticket to the pull request and viceversa
>> 13) submit to this mailing list
>>
>> This works because the layout folder structure is the same and the
>> failing mustella folders are untouched at the moment so you can
>> overwrite with your changes and make a pull request only with the
>> changes.
>>
>> Alex, Peter and Carol are getting this pull request as patches without
>>problem.
>>
>> Best,
>>
>> Carlos
>>
>>
>> 2012/8/28 Kiel <ki...@gmail.com>:
>>> Greetings,
>>>
>>> How to do the Mustella tests on Git(Github)?
>>>
>>> Will I fork "unstable"?
>>>
>

Re: Getting Mustella to work.

Posted by Kiel <ki...@gmail.com>.

Hi Carlos,

I'll follow the steps mentioned.
Got concerned since the number of Passes & Fails didn't match the lists 
on wiki.

Thanks.

On 8/28/2012 5:46 PM, Carlos Rovira wrote:
> Hi Kiel,
>
> take into account that github is not synced with SVN right now, so
> there you will not find the latest fixes to mustella for at least 2
> weeks.
>
> the team is working with INFRA to get official GIT support. For the
> latest news this will resolved in the following 1 to 3 weeks.
>
> In the meanwhile, we and others use the following path to work:
>
> 1) get SVN "develop" branch.
> 2) work in your local copy.
> 3) when you are done with a fix, extract the folder (I do this with
> eclipse-subversive)
>
> now:
>
> 4) in github, fork apache flex
> 5) in your machine clone the fork
> 6) create a branch
> 7) copy the extract folder created in 3) overlaying it (overwrite)
> 8) commit to the new branch
> 9) push to origin (github)
> 10) create a JIRA ticket
> 11) create a pull request
> 12) link the jira ticket to the pull request and viceversa
> 13) submit to this mailing list
>
> This works because the layout folder structure is the same and the
> failing mustella folders are untouched at the moment so you can
> overwrite with your changes and make a pull request only with the
> changes.
>
> Alex, Peter and Carol are getting this pull request as patches without problem.
>
> Best,
>
> Carlos
>
>
> 2012/8/28 Kiel <ki...@gmail.com>:
>> Greetings,
>>
>> How to do the Mustella tests on Git(Github)?
>>
>> Will I fork "unstable"?
>>

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Kiel,

take into account that github is not synced with SVN right now, so
there you will not find the latest fixes to mustella for at least 2
weeks.

the team is working with INFRA to get official GIT support. For the
latest news this will resolved in the following 1 to 3 weeks.

In the meanwhile, we and others use the following path to work:

1) get SVN "develop" branch.
2) work in your local copy.
3) when you are done with a fix, extract the folder (I do this with
eclipse-subversive)

now:

4) in github, fork apache flex
5) in your machine clone the fork
6) create a branch
7) copy the extract folder created in 3) overlaying it (overwrite)
8) commit to the new branch
9) push to origin (github)
10) create a JIRA ticket
11) create a pull request
12) link the jira ticket to the pull request and viceversa
13) submit to this mailing list

This works because the layout folder structure is the same and the
failing mustella folders are untouched at the moment so you can
overwrite with your changes and make a pull request only with the
changes.

Alex, Peter and Carol are getting this pull request as patches without problem.

Best,

Carlos


2012/8/28 Kiel <ki...@gmail.com>:
> Greetings,
>
> How to do the Mustella tests on Git(Github)?
>
> Will I fork "unstable"?
>

-- 
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Kiel <ki...@gmail.com>.

Greetings,

How to do the Mustella tests on Git(Github)?

Will I fork "unstable"?

Thanks,

On 8/24/2012 10:45 PM, Peter Ent wrote:
> I've updated the mustella wiki to point to the
> https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop/mustel
> la location.
>
> As for the Exclusion lists, I'm not 100% sure, but most of the items in
> the list were tests that relied on Adobe test servers that cannot be
> accessed for obvious reasons. I put some TileList tests on there yesterday
> because I just could not figure out why they would not work with the
> intent of using that list for us to go back to investigate; probably not
> the wisest idea so I'll remove them today most likely. In the end, tests
> that are on that list should be there for a good reason, otherwise the
> tests should be repaired and run correctly or just removed because they
> aren't valid any longer (such as relying on inaccessible services).
>
> --peter
>
> On 8/24/12 6:25 AM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
>> Hi,
>>
>>> 1) I couldn't (easily) find on which source I'm supposed to work.
>>> Eventually I found an email from Alex referring to 'develop', and in
>>> the SVN repo
>> We probably need to update the SVN info on the web site/wiki to make it
>> clear that people wishing to contribute need to work out of develop not
>> trunk.
>>
>>> 2) spaces in paths... This gave me quit a headache.
>> It's a know issue and again probably need to be more clearly spelt out in
>> the documentation. A few people have looked fixing it but it's not
>> straight forward to fix.
>>
>>> 3) the first Mustella test I ran was on components/TextArea, as that
>>> was near the top of the table, didn't look to have too many test and
>>> it passes... To my suprise it did pass, but not with the 30 tests
>>> mentioned in the table, but it said it only passed 8 tests
>> I think that there are excluded tests depending on what platform you run
>> the tests on. Take a look at ExcludeListMac.txt (2600 lines) vs
>> ExcludeListWin.txt (0 lines) in the mustella/tests directory. Anyone know
>> why so many tests are excluded on OSX?
>>
>> Thanks,
>> Justin
>>

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I've updated the mustella wiki to point to the
https://svn.apache.org/repos/asf/incubator/flex/sdk/branches/develop/mustel
la location.

As for the Exclusion lists, I'm not 100% sure, but most of the items in
the list were tests that relied on Adobe test servers that cannot be
accessed for obvious reasons. I put some TileList tests on there yesterday
because I just could not figure out why they would not work with the
intent of using that list for us to go back to investigate; probably not
the wisest idea so I'll remove them today most likely. In the end, tests
that are on that list should be there for a good reason, otherwise the
tests should be repaired and run correctly or just removed because they
aren't valid any longer (such as relying on inaccessible services).

--peter

On 8/24/12 6:25 AM, "Justin Mclean" <ju...@classsoftware.com> wrote:

>Hi,
>
>> 1) I couldn't (easily) find on which source I'm supposed to work.
>> Eventually I found an email from Alex referring to 'develop', and in
>> the SVN repo
>We probably need to update the SVN info on the web site/wiki to make it
>clear that people wishing to contribute need to work out of develop not
>trunk.
>
>> 2) spaces in paths... This gave me quit a headache.
>It's a know issue and again probably need to be more clearly spelt out in
>the documentation. A few people have looked fixing it but it's not
>straight forward to fix.
>
>> 3) the first Mustella test I ran was on components/TextArea, as that
>> was near the top of the table, didn't look to have too many test and
>> it passes... To my suprise it did pass, but not with the 30 tests
>> mentioned in the table, but it said it only passed 8 tests
>I think that there are excluded tests depending on what platform you run
>the tests on. Take a look at ExcludeListMac.txt (2600 lines) vs
>ExcludeListWin.txt (0 lines) in the mustella/tests directory. Anyone know
>why so many tests are excluded on OSX?
>
>Thanks,
>Justin
>

Re: Getting Mustella to work.

Posted by Justin Mclean <ju...@classsoftware.com>.

Hi,

> 1) I couldn't (easily) find on which source I'm supposed to work.
> Eventually I found an email from Alex referring to 'develop', and in
> the SVN repo
We probably need to update the SVN info on the web site/wiki to make it clear that people wishing to contribute need to work out of develop not trunk.

> 2) spaces in paths... This gave me quit a headache.
It's a know issue and again probably need to be more clearly spelt out in the documentation. A few people have looked fixing it but it's not straight forward to fix.

> 3) the first Mustella test I ran was on components/TextArea, as that
> was near the top of the table, didn't look to have too many test and
> it passes... To my suprise it did pass, but not with the 30 tests
> mentioned in the table, but it said it only passed 8 tests 
I think that there are excluded tests depending on what platform you run the tests on. Take a look at ExcludeListMac.txt (2600 lines) vs ExcludeListWin.txt (0 lines) in the mustella/tests directory. Anyone know why so many tests are excluded on OSX?

Thanks,
Justin

Re: Getting Mustella to work.

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Hi,

> and the community would help repair them. Please join in the fun. You’ll learn about how it works and we’ll learn
> what else needs to be documented or fixed.

I have Mustella running on my machine, and I'm planning on "joining
the fun" after the weekend. However, I thought I'd share my
experiences setting things up before that:

1) I couldn't (easily) find on which source I'm supposed to work.
Eventually I found an email from Alex referring to 'develop', and in
the SVN repo I found that the latest changes were indeed made to the
Mustella in 'develop', so I figured that's the one... Some
documentation might be in order here.

2) spaces in paths... This gave me quit a headache. First I tried to
use env.properties, but the build of the SDK kept complaining that the
PIXELBENDER_HOME variable wasn't a directory. It was, I used a default
install on my Mac. So I decided to go the environment variables route,
as that is where ANT_HOME and JAVA_HOME were already defined. This
still didn't solve the problem, though. I ended up replacing the
spaces in the path to PixelBender with underscores and setting the
environment variable accordingly. One down... Next Mustella complained
that the spaces in FLASHPLAYER_DEBUGGER were a problem, but that I
could solve by wrapping the path in quotes. Done.

3) the first Mustella test I ran was on components/TextArea, as that
was near the top of the table, didn't look to have too many test and
it passes... To my suprise it did pass, but not with the 30 tests
mentioned in the table, but it said it only passed 8 tests (and NO
failures)??? Next, I tried to run "Applications" but that obviously
didn't work, since there is no such directory. So I ran "Application"
and that gave me not the expected 124 passed tests (from the table in
the Wiki), but 181 passed and 37 failed tests.

Now I don't have any time anymore, I will look into this more next
week, but maybe in the meantime someone can point me to my obvious
mistakes and maybe that will solve the issues I had.

Thanks,

EdB

--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

2012/8/18 Alex Harui <ah...@adobe.com>

> As you probably read in the documents on the Apache website, you have to
> contribute code in order to be nominated to become a committer.  So, if you
> take on mustella work, your first fixes will have to be in the form of
> patches.
>
>
Yes Alex, I count with that

Thanks


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Finaly found a failing folder at "tests/SparkModules/"

[java] =====================================================
     [java]     Passes: 17
     [java]     Fails: 2
     [java] =====================================================

so working on this...


2012/8/21 Carlos Rovira <ca...@codeoscopic.com>

> Hi Alex,
>
> I'll pass the test each knight as soon as I modified something. Until now
> all folders I test worked ok. I'm finding some folder failing to start
> fixing.
>
> I'm using the end of the wiki's page to know where is each working:
> https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview
>
> I'll try to update the page to add results of what I find, but I don't
> have permissions, so I'll report here what I found and someone of you could
> add to the wiki so we can strech the circle and get all.
>
> One more:
>
> tests/States/
>
> [java] =====================================================
>      [java]     Passes: 580
>      [java]     Fails: 0
>      [java] =====================================================
>
> Best,
>
> Carlos
>
>
>
> 2012/8/21 Alex Harui <ah...@adobe.com>
>
>> Hi Carlos,
>>
>> That's awesome.  Thanks for pitching in.  Peter, can you update the wiki?
>>
>> An interesting thing for you to do is before you quit working for the day,
>> run mini_run.sh -all and see what you get in the morning.  The failures
>> will
>> point to folders to work on.  Review this thread for what others are
>> working
>> on.  I've working on the entire spark folder, for example.
>>
>> -Alex
>>
>>
>> On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com>
>> wrote:
>>
>> > Ops! I reboot Terminal and pass it again and all is ok with
>> "GraphicTags"...
>> >
>> > [java] =====================================================
>> >      [java]     Passes: 3
>> >      [java]     Fails: 0
>> >      [java] =====================================================
>> >
>> >
>> > So It's needed at least two passes when a time out is thrown...I'm
>> > finishing to understand mustella ;)
>> >
>> >
>> >
>> > 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
>> >
>> >>
>> >> but "tests/GraphicTags/"
>> >>
>> >> reports
>> >> [java] =====================================================
>> >>      [java]     Passes: 2
>> >>      [java]     Fails: 1
>> >>      [java] =====================================================
>> >>
>> >> so I'll fix GraphicTags
>> >>
>> >>
>> >>
>> >> --
>> >> Carlos Rovira
>> >> Director de Tecnología
>> >> 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ón, 32
>> >> Planta 10, Puertas P-Q
>> >> 28020 Madrid
>> >>
>> >>
>> >
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> 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ón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Alex,

I'll pass the test each knight as soon as I modified something. Until now
all folders I test worked ok. I'm finding some folder failing to start
fixing.

I'm using the end of the wiki's page to know where is each working:
https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview

I'll try to update the page to add results of what I find, but I don't have
permissions, so I'll report here what I found and someone of you could add
to the wiki so we can strech the circle and get all.

One more:

tests/States/

[java] =====================================================
     [java]     Passes: 580
     [java]     Fails: 0
     [java] =====================================================

Best,

Carlos



2012/8/21 Alex Harui <ah...@adobe.com>

> Hi Carlos,
>
> That's awesome.  Thanks for pitching in.  Peter, can you update the wiki?
>
> An interesting thing for you to do is before you quit working for the day,
> run mini_run.sh -all and see what you get in the morning.  The failures
> will
> point to folders to work on.  Review this thread for what others are
> working
> on.  I've working on the entire spark folder, for example.
>
> -Alex
>
>
> On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> > Ops! I reboot Terminal and pass it again and all is ok with
> "GraphicTags"...
> >
> > [java] =====================================================
> >      [java]     Passes: 3
> >      [java]     Fails: 0
> >      [java] =====================================================
> >
> >
> > So It's needed at least two passes when a time out is thrown...I'm
> > finishing to understand mustella ;)
> >
> >
> >
> > 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
> >
> >>
> >> but "tests/GraphicTags/"
> >>
> >> reports
> >> [java] =====================================================
> >>      [java]     Passes: 2
> >>      [java]     Fails: 1
> >>      [java] =====================================================
> >>
> >> so I'll fix GraphicTags
> >>
> >>
> >>
> >> --
> >> Carlos Rovira
> >> Director de Tecnología
> >> 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ón, 32
> >> Planta 10, Puertas P-Q
> >> 28020 Madrid
> >>
> >>
> >
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Ok Peter,

I'll continue fixing and when have some fixes will made only one patch that
groups all changes and then send it.

Best

Carlos


2012/8/23 Peter Ent <pe...@adobe.com>

> Yes, I think that's the best solution for now. Maybe Alex or Carol will
> have another suggestion.
>
> It may take me awhile to figure out this patch thing anyway.
> --peter
>
> On 8/23/12 9:50 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> >Ok Peter,
> >
> >since I had to recreate it I was considering it derived and not needed in
> >VCS.
> >
> >So I understand I should make a patch with png I created with
> >-createImages
> >for test that already passed and send it to you for applying?
> >
> >Best,
> >
> >Carlos
> >
> >2012/8/23 Peter Ent <pe...@adobe.com>
> >
> >> No, I don't think the images should be removed. Once a test has been
> >> created and the test author believes the test is running correctly, the
> >> author creates the baseline against which all other runs are judged.
> >> Should the code being tested change, the baseline comparison can tell if
> >> something is amiss. If you don't have the baseline present you would not
> >> know there was a test failure.
> >>
> >> At least that's how it should work, as I understand it.
> >>
> >> --peter
> >>
> >>
> >> On 8/23/12 9:30 AM, "Carlos Rovira" <ca...@codeoscopic.com>
> >>wrote:
> >>
> >> >Hi,
> >> >
> >> >would it be better to remove the images in baseline folders since
> >>people
> >> >runing test should generate it with -createImages?
> >> >
> >> >Right now I think is confusing for people entering mustella since those
> >> >files are commited as part of the framework but are really derived
> >>files
> >> >that need to be constructed the first time (moreover I will point it
> >>as a
> >> >required step to setup mustella and be able to run test)
> >> >
> >> >
> >> >2012/8/22 Alex Harui <ah...@adobe.com>
> >> >
> >> >>
> >> >>
> >> >>
> >> >> On 8/22/12 9:19 AM, "Carlos Rovira" <ca...@codeoscopic.com>
> >> >>wrote:
> >> >>
> >> >> > Many Thanks Carol, I'm taking over mustella thanks to wiki, Peter,
> >> >>Alex
> >> >> and
> >> >> > you little by little.
> >> >> > Seems that many times as you fix a problem subsequent fails
> >>dissapear.
> >> >> I'll
> >> >> > try the imageDiffAIR you say, since creteImage this time left the
> >> >>first
> >> >> > error unexpectely...
> >> >> >
> >> >> No test should really affect another, but the clean up between tests
> >>is
> >> >>not
> >> >> perfect so that can occasionally happen.  Sometimes a fix for the
> >>first
> >> >> test
> >> >> is for an asset or style that is shared by other tests.
> >> >>
> >> >> Sometimes tests have timing issues and will work on some runs and
> >>not on
> >> >> others.  Hopefully we will flush out and fix those tests as we go
> >> >>through
> >> >> them on this pass.  But you are also welcome to give up and comment
> >>out
> >> >>a
> >> >> flaky test on occasion.
> >> >>
> >> >> --
> >> >> Alex Harui
> >> >> Flex SDK Team
> >> >> Adobe Systems, Inc.
> >> >> http://blogs.adobe.com/aharui
> >> >>
> >> >>
> >> >
> >> >
> >> >--
> >> >Carlos Rovira
> >> >Director de Tecnología
> >> >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ón, 32
> >> >Planta 10, Puertas P-Q
> >> >28020 Madrid
> >>
> >>
> >
> >
> >--
> >Carlos Rovira
> >Director de Tecnología
> >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ón, 32
> >Planta 10, Puertas P-Q
> >28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Yes, I think that's the best solution for now. Maybe Alex or Carol will
have another suggestion.

It may take me awhile to figure out this patch thing anyway.
--peter

On 8/23/12 9:50 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

>Ok Peter,
>
>since I had to recreate it I was considering it derived and not needed in
>VCS.
>
>So I understand I should make a patch with png I created with
>-createImages
>for test that already passed and send it to you for applying?
>
>Best,
>
>Carlos
>
>2012/8/23 Peter Ent <pe...@adobe.com>
>
>> No, I don't think the images should be removed. Once a test has been
>> created and the test author believes the test is running correctly, the
>> author creates the baseline against which all other runs are judged.
>> Should the code being tested change, the baseline comparison can tell if
>> something is amiss. If you don't have the baseline present you would not
>> know there was a test failure.
>>
>> At least that's how it should work, as I understand it.
>>
>> --peter
>>
>>
>> On 8/23/12 9:30 AM, "Carlos Rovira" <ca...@codeoscopic.com>
>>wrote:
>>
>> >Hi,
>> >
>> >would it be better to remove the images in baseline folders since
>>people
>> >runing test should generate it with -createImages?
>> >
>> >Right now I think is confusing for people entering mustella since those
>> >files are commited as part of the framework but are really derived
>>files
>> >that need to be constructed the first time (moreover I will point it
>>as a
>> >required step to setup mustella and be able to run test)
>> >
>> >
>> >2012/8/22 Alex Harui <ah...@adobe.com>
>> >
>> >>
>> >>
>> >>
>> >> On 8/22/12 9:19 AM, "Carlos Rovira" <ca...@codeoscopic.com>
>> >>wrote:
>> >>
>> >> > Many Thanks Carol, I'm taking over mustella thanks to wiki, Peter,
>> >>Alex
>> >> and
>> >> > you little by little.
>> >> > Seems that many times as you fix a problem subsequent fails
>>dissapear.
>> >> I'll
>> >> > try the imageDiffAIR you say, since creteImage this time left the
>> >>first
>> >> > error unexpectely...
>> >> >
>> >> No test should really affect another, but the clean up between tests
>>is
>> >>not
>> >> perfect so that can occasionally happen.  Sometimes a fix for the
>>first
>> >> test
>> >> is for an asset or style that is shared by other tests.
>> >>
>> >> Sometimes tests have timing issues and will work on some runs and
>>not on
>> >> others.  Hopefully we will flush out and fix those tests as we go
>> >>through
>> >> them on this pass.  But you are also welcome to give up and comment
>>out
>> >>a
>> >> flaky test on occasion.
>> >>
>> >> --
>> >> Alex Harui
>> >> Flex SDK Team
>> >> Adobe Systems, Inc.
>> >> http://blogs.adobe.com/aharui
>> >>
>> >>
>> >
>> >
>> >--
>> >Carlos Rovira
>> >Director de Tecnología
>> >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ón, 32
>> >Planta 10, Puertas P-Q
>> >28020 Madrid
>>
>>
>
>
>-- 
>Carlos Rovira
>Director de Tecnología
>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ón, 32
>Planta 10, Puertas P-Q
>28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Ok Peter,

since I had to recreate it I was considering it derived and not needed in
VCS.

So I understand I should make a patch with png I created with -createImages
for test that already passed and send it to you for applying?

Best,

Carlos

2012/8/23 Peter Ent <pe...@adobe.com>

> No, I don't think the images should be removed. Once a test has been
> created and the test author believes the test is running correctly, the
> author creates the baseline against which all other runs are judged.
> Should the code being tested change, the baseline comparison can tell if
> something is amiss. If you don't have the baseline present you would not
> know there was a test failure.
>
> At least that's how it should work, as I understand it.
>
> --peter
>
>
> On 8/23/12 9:30 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> >Hi,
> >
> >would it be better to remove the images in baseline folders since people
> >runing test should generate it with -createImages?
> >
> >Right now I think is confusing for people entering mustella since those
> >files are commited as part of the framework but are really derived files
> >that need to be constructed the first time (moreover I will point it as a
> >required step to setup mustella and be able to run test)
> >
> >
> >2012/8/22 Alex Harui <ah...@adobe.com>
> >
> >>
> >>
> >>
> >> On 8/22/12 9:19 AM, "Carlos Rovira" <ca...@codeoscopic.com>
> >>wrote:
> >>
> >> > Many Thanks Carol, I'm taking over mustella thanks to wiki, Peter,
> >>Alex
> >> and
> >> > you little by little.
> >> > Seems that many times as you fix a problem subsequent fails dissapear.
> >> I'll
> >> > try the imageDiffAIR you say, since creteImage this time left the
> >>first
> >> > error unexpectely...
> >> >
> >> No test should really affect another, but the clean up between tests is
> >>not
> >> perfect so that can occasionally happen.  Sometimes a fix for the first
> >> test
> >> is for an asset or style that is shared by other tests.
> >>
> >> Sometimes tests have timing issues and will work on some runs and not on
> >> others.  Hopefully we will flush out and fix those tests as we go
> >>through
> >> them on this pass.  But you are also welcome to give up and comment out
> >>a
> >> flaky test on occasion.
> >>
> >> --
> >> Alex Harui
> >> Flex SDK Team
> >> Adobe Systems, Inc.
> >> http://blogs.adobe.com/aharui
> >>
> >>
> >
> >
> >--
> >Carlos Rovira
> >Director de Tecnología
> >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ón, 32
> >Planta 10, Puertas P-Q
> >28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

No, I don't think the images should be removed. Once a test has been
created and the test author believes the test is running correctly, the
author creates the baseline against which all other runs are judged.
Should the code being tested change, the baseline comparison can tell if
something is amiss. If you don't have the baseline present you would not
know there was a test failure.

At least that's how it should work, as I understand it.

--peter


On 8/23/12 9:30 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

>Hi,
>
>would it be better to remove the images in baseline folders since people
>runing test should generate it with -createImages?
>
>Right now I think is confusing for people entering mustella since those
>files are commited as part of the framework but are really derived files
>that need to be constructed the first time (moreover I will point it as a
>required step to setup mustella and be able to run test)
>
>
>2012/8/22 Alex Harui <ah...@adobe.com>
>
>>
>>
>>
>> On 8/22/12 9:19 AM, "Carlos Rovira" <ca...@codeoscopic.com>
>>wrote:
>>
>> > Many Thanks Carol, I'm taking over mustella thanks to wiki, Peter,
>>Alex
>> and
>> > you little by little.
>> > Seems that many times as you fix a problem subsequent fails dissapear.
>> I'll
>> > try the imageDiffAIR you say, since creteImage this time left the
>>first
>> > error unexpectely...
>> >
>> No test should really affect another, but the clean up between tests is
>>not
>> perfect so that can occasionally happen.  Sometimes a fix for the first
>> test
>> is for an asset or style that is shared by other tests.
>>
>> Sometimes tests have timing issues and will work on some runs and not on
>> others.  Hopefully we will flush out and fix those tests as we go
>>through
>> them on this pass.  But you are also welcome to give up and comment out
>>a
>> flaky test on occasion.
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
>
>-- 
>Carlos Rovira
>Director de Tecnología
>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ón, 32
>Planta 10, Puertas P-Q
>28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi,

would it be better to remove the images in baseline folders since people
runing test should generate it with -createImages?

Right now I think is confusing for people entering mustella since those
files are commited as part of the framework but are really derived files
that need to be constructed the first time (moreover I will point it as a
required step to setup mustella and be able to run test)


2012/8/22 Alex Harui <ah...@adobe.com>

>
>
>
> On 8/22/12 9:19 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> > Many Thanks Carol, I'm taking over mustella thanks to wiki, Peter, Alex
> and
> > you little by little.
> > Seems that many times as you fix a problem subsequent fails dissapear.
> I'll
> > try the imageDiffAIR you say, since creteImage this time left the first
> > error unexpectely...
> >
> No test should really affect another, but the clean up between tests is not
> perfect so that can occasionally happen.  Sometimes a fix for the first
> test
> is for an asset or style that is shared by other tests.
>
> Sometimes tests have timing issues and will work on some runs and not on
> others.  Hopefully we will flush out and fix those tests as we go through
> them on this pass.  But you are also welcome to give up and comment out a
> flaky test on occasion.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

On 8/22/12 9:19 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

> Many Thanks Carol, I'm taking over mustella thanks to wiki, Peter, Alex and
> you little by little.
> Seems that many times as you fix a problem subsequent fails dissapear. I'll
> try the imageDiffAIR you say, since creteImage this time left the first
> error unexpectely...
> 
No test should really affect another, but the clean up between tests is not
perfect so that can occasionally happen.  Sometimes a fix for the first test
is for an asset or style that is shared by other tests.

Sometimes tests have timing issues and will work on some runs and not on
others.  Hopefully we will flush out and fix those tests as we go through
them on this pass.  But you are also welcome to give up and comment out a
flaky test on occasion.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Many Thanks Carol, I'm taking over mustella thanks to wiki, Peter, Alex and
you little by little.
Seems that many times as you fix a problem subsequent fails dissapear. I'll
try the imageDiffAIR you say, since creteImage this time left the first
error unexpectely...



2012/8/22 Carol Frampton <cf...@adobe.com>

> Above what you cut and pasted will be the log messages for each test that
> was run.  For the timeouts, go look in the log files for the tests.  For
> the first timeout, it looks like it didn't get an event it expected.  I'd
> start by looking at the test and making sure whatever event it is
> expecting is correct.
>
> I use mustella/as3/src/mustella/imageDiffAIR.air to look at the bitmap
> failures.  It is a very handy tool since you can see the good and the bad
> right next to each other.
>
> Carol
> --
>
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Cyrill Zadra <cy...@gmail.com>.

"tests/Managers/DragManager" has serveral failing tests after fixing them 3
tests still fails (patch -> attached to JIRA FLEX-33173 )

    [java] Managers/DragManager/Halo/DragManager_Cursors_RTL
DragManager_Mirroring_copyCursor Failed DispatchMouseEvent(body:step 4)
 Target mx.managers::DragManager.mx_internal:dragProxy not found
     [java] Managers/DragManager/Halo/DragManager_Cursors_RTL
DragManager_Mirroring_moveCursor Failed DispatchMouseEvent(body:step 4)
 Target mx.managers::DragManager.mx_internal:dragProxy not found
     [java] Managers/DragManager/Halo/DragManager_Cursors_RTL
DragManager_Mirroring_rejectCursor Failed DispatchMouseEvent(body:step 4)
 Target mx.managers::DragManager.mx_internal:dragProxy not found


[java] =====================================================
     [java]     Passes: 74
     [java]     Fails: 3
     [java] =====================================================

After severalI couldn't locate the problem so I started with
StyleManager/AdvancedCSS

"tests/Managers/StyleManager/AdvancedCSS/mixedSelectors" has no fails after
creating images (will attach patch to JIRA FLEX-33173 as soon it is up
again)

     [java] =====================================================
     [java]     Passes: 21
     [java]     Fails: 0
     [java] =====================================================

"tests/Managers/StyleManager/AdvancedCSS/descendantSelectors"

has few fails but after creating images and fixing mxml it works with zero
fails (needs patch -> will attach patch to JIRA FLEX-33173 as soon it is up
again )

[java] =====================================================
     [java]     Passes: 14
     [java]     Fails: 0
     [java] =====================================================

"tests/Managers/StyleManager/AdvancedCSS/pseudoSelectors"

[java] =====================================================
     [java]     Passes: 81
     [java]     Fails: 2
     [java] =====================================================


I'll start now trying to fix those 2 errors.

My environment is Windows 7.

cyrill

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Ok Alex,

I continue searching for a new folder:

"tests/Mirroring/" report ok

[java] =====================================================
     [java]     Passes: 9
     [java]     Fails: 0
     [java] =====================================================


"tests/PerModuleStyles/" report ok

[java] =====================================================
     [java]     Passes: 55
     [java]     Fails: 0
     [java] =====================================================


tomorrow will search something more...





2012/8/24 Alex Harui <ah...@adobe.com>

> I will take a look soon, but maybe not until the weekend.
>
>
-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Jose Barragán <jo...@codeoscopic.com>.

https://issues.apache.org/jira/browse/FLEX-33178

Sent from my iPhone

On 26/08/2012, at 03:45, Jose Barragan <jo...@codeoscopic.com>
wrote:

In order to get the mustella zero fails goal, I've exclude the Japanese
LangPack tests too in mustella1.properties file.

https://github.com/apache/flex/pull/13.patch

desktop_runner:
     [echo] **** Willkommen auf Runner ****
     [java] starting results server
     [java] starting baseline server
     [java] starting the baseline server: Sun Aug 26 03:21:24 CEST 2012
     [java] test script count: 1
     [java] Skipping:
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java] Passes: 0
     [java] Fails: 0
     [java] =====================================================
     [java]
     [java] =====================================================
     [java] =====================================================
     [java] Passed:
     [java] =====================================================
     [java] =====================================================
     [java] Failed:
     [java] =====================================================
     [java]
     [java]
     [java] =====================================================
     [java] Passes: 0
     [java] Fails: 0
     [java] =====================================================
     [java]
     [java]
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 24 seconds

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Hi Alex,

I just fixed the test's environment in order to compile with custom locale.

I'll cancel the pull-request related on https://issues.apache.org/jira/browse/FLEX-33178.

   [java] LangPacks/Japanese/tests/zipCodeFormatterTests JA_Formatters_ZipCode_Properties_FormatString Passed  
     [java] LangPacks/Japanese/tests/zipCodeValidatorTests JA_ZipCodeValidator_Properties_AllowedFormatChars Passed  
     [java] LangPacks/Japanese/tests/zipCodeValidatorTests JA_ZipCodeValidator_Properties_Domain Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] LangPacks/Japanese/tests/creditCardValidatorTests JA_CreditCardValidator_InvalidCharError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/creditCardValidatorTests JA_CreditCardValidator_invalidNumberError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/creditCardValidatorTests JA_CreditCardValidator_wrongLengthError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/creditCardValidatorTests JA_CreditCardValidator_wrongTypeError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/creditCardValidatorTests JA_CreditCardValidator_FieldRequired Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/creditCardValidatorTests JA_CreditCardValidator_TypeRequired Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/creditCardValidatorTests JA_CreditCardValidator_NumberRequired Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_currencySymbolError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_decimalPointCountError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_exceedsMaxError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_invalidCharError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_invalidFormatCharsError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_lowerThanMinError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_precisionError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_separationError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/currencyValidatorTests JA_CurrencyValidator_negativeError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/dateChooserTests JA_DateChooser_Japanese_Layout Failed CompareBitmap(body:step 1)  compare returned-3 
     [java] LangPacks/Japanese/tests/dateFieldTests JA_DateField_Dropdown_Japanese_Layout Failed CompareBitmap(body:step 2)  compare returned-3 
     [java] LangPacks/Japanese/tests/dateValidatorTests JA_DateValidator_formatError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/dateValidatorTests JA_DateValidator_invalidCharError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/dateValidatorTests JA_DateValidator_wrongDayError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/dateValidatorTests JA_DateValidator_wrongMonthError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/dateValidatorTests JA_DateValidator_wrongYearError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/dateValidatorTests JA_DateValidator_dateFormat Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_invalidCharError2 Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_invalidDomainError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_missingAtSignError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_missingUsernameError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_tooManyAtSignsError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_invalidPeriodsInDomainError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_missingPeriodInDomainError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_invalidDomainError2 Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_invalidIPDomainError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/emailValidatorTests JA_EmailValidator_invalidDomainError_noPeriod Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_decimalPointCountError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_exceedsMaxError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_integerError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_invalidFormatCharsError_Decimal Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_invalidFormatCharsError_Thousand Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_lowerThanMinError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_negativeError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_precisionError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/numberValidatorTests JA_NumberValidator_invalidCharError Failed CompareBitmap(body:step 6)  compare returned-3 
     [java] LangPacks/Japanese/tests/phoneNumberValidatorTests JA_PhoneNumberValidator_invalidCharError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/phoneNumberValidatorTests JA_PhoneNumberValidator_wrongLengthError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/socialSecurityValidatorTests JA_SocialSecurityValidator_invalidCharError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/socialSecurityValidatorTests JA_SocialSecurityValidator_wrongFormatError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/socialSecurityValidatorTests JA_SocialSecurityValidator_zeroStartError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/stringValidatorTests JA_StringValidator_tooLongError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/stringValidatorTests JA_StringValidator_tooLongError1 Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/stringValidatorTests JA_StringValidator_tooShortError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/stringValidatorTests JA_StringValidator_tooShortError1 Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/zipCodeValidatorTests JA_ZipCodeValidator_invalidCharError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/zipCodeValidatorTests JA_ZipCodeValidator_invalidDomainError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/zipCodeValidatorTests JA_ZipCodeValidator_wrongCAFormatError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/zipCodeValidatorTests JA_ZipCodeValidator_wrongLengthError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] LangPacks/Japanese/tests/zipCodeValidatorTests JA_ZipCodeValidator_wrongUSFormatError Failed CompareBitmap(body:step 7)  compare returned-3 
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 181
     [java]     Fails: 57
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

BUILD FAILED
/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/build.xml:1457: The following error occurred while executing this line:
/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/build.xml:1575: Java returned: 1

Total time: 1 minute 41 seconds

so, we still working on it 

Thanks, and sorry by my misunderstood of test's environment...

Jose.

On Aug 27, 2012, at 10:00 AM, Jose Barragan <jo...@codeoscopic.com> wrote:

> Hi Alex,
> 
> If you have read the description of https://issues.apache.org/jira/browse/FLEX-33178, you had to see the errors that occur.
> I thought that you had excluded the rest of LangPack tests, due to a problem with SDK current status, because the problems is not in runtime, but in compilation, due compiler not finding any resource bundles in SDK.
> 
> I compile the SDK running the "main", and other.locales goals in ANT build, maybe I missing something...
> 
> Thanks,
> 
> Jose.
> 
> On Aug 27, 2012, at 6:38 AM, Alex Harui <ah...@adobe.com> wrote:
> 
>> 
>> 
>> 
>> On 8/26/12 1:49 AM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>> 
>>> Hi Alex,
>>> 
>>> Because in mustella1.properties, that all the tests were excluded with the
>>> exception of the Japanese.
>>> I generated the locales packages in SDK, but it follows without compiling the
>>> Japanese test, because not to find the resource bundle in SDK.
>>> I deduced then that it must be a problem of construction of SDK to repair in
>>> another thread, and I assumed, that by that reason was excluded the others
>>> tests.
>>> 
>>> If I am mistaken, tell me, and I cancel the pull-request, but please, comment
>>> to me how I can confront the problem of the absence of resource bundles locale
>>> in the test SDK, in order to resolve this issue and mustella LangPack tests.
>>> 
>> AFAICT, we did not exclude the Japanese tests at Adobe, so I think they
>> should be running.  What kinds of errors did you get when they ran?
>> 
>> -- 
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
>

Re: Getting Mustella to work.

Posted by Erik de Bruin <er...@ixsoftware.nl>.

Peter,

> Tests that rely on a local server are currently not supported. However, if
> interested individuals want to figure out how to do that, it would make
> testing more robust. I think however, the best thing to do is skip this

Would a local server based on something like [1] be an option? Or does
the local server have to have specific (advanced) features?

EdB

1: http://coenraets.org/blog/2009/12/air-2-0-web-server-using-the-new-server-socket-api/



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

The tests that hit localhost may need their own list, maybe
browserIncludes.txt or something like that.  When folks run mustella in
browser mode, they need to set up an http server pointing at the tests
directory and these additional tests should run.

The ones that will be harder to fix are ones that hit the old flexqa server.


On 8/30/12 6:20 AM, "Peter Ent" <pe...@adobe.com> wrote:

> Tests that rely on a local server are currently not supported. However, if
> interested individuals want to figure out how to do that, it would make
> testing more robust. I think however, the best thing to do is skip this
> test and then we can revisit the issue once all the "normal" tests are
> working.
> 
> There are two approaches to skipping the test: add the test to the
> tests/ExcludeListMac.txt and tests/ExcludeListWin.txt files or comment-out
> the test, with a note, in the MXML test file. I personally think the
> exclusion file is better since it keeps a list of all of the tests being
> excluded in one location, but I don't think there is a provision for
> comments; I'm going to take a look at that and see if the Exclusion files
> will accept a comment and sent an email shortly.
> 
> --peter
> 
> On 8/30/12 9:13 AM, "Cyrill Zadra" <cy...@gmail.com> wrote:
> 
>> There's a test in test/Mangers/StyleManager/Versioning that tries to load
>> a
>> swf from a local server. Do I have to setup server .. or how is this been
>> tested in mustella?
>> 
>> <SetProperty target="swf1" propertyName="source"
>> value="http://localhost:{portNumber}/Managers/StyleManager/SWFs/assets/MP_
>> customStyles_embeddedImages.swf?port={portNumber}"
>> waitTarget="swf1" waitEvent="updateComplete"/>
>> 
>> regards
>> cyrill
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Tests that rely on a local server are currently not supported. However, if
interested individuals want to figure out how to do that, it would make
testing more robust. I think however, the best thing to do is skip this
test and then we can revisit the issue once all the "normal" tests are
working.

There are two approaches to skipping the test: add the test to the
tests/ExcludeListMac.txt and tests/ExcludeListWin.txt files or comment-out
the test, with a note, in the MXML test file. I personally think the
exclusion file is better since it keeps a list of all of the tests being
excluded in one location, but I don't think there is a provision for
comments; I'm going to take a look at that and see if the Exclusion files
will accept a comment and sent an email shortly.

--peter

On 8/30/12 9:13 AM, "Cyrill Zadra" <cy...@gmail.com> wrote:

>There's a test in test/Mangers/StyleManager/Versioning that tries to load
>a
>swf from a local server. Do I have to setup server .. or how is this been
>tested in mustella?
>
> <SetProperty target="swf1" propertyName="source"
>value="http://localhost:{portNumber}/Managers/StyleManager/SWFs/assets/MP_
>customStyles_embeddedImages.swf?port={portNumber}"
>waitTarget="swf1" waitEvent="updateComplete"/>
>
>regards
>cyrill

Re: Getting Mustella to work.

Posted by Cyrill Zadra <cy...@gmail.com>.

There's a test in test/Mangers/StyleManager/Versioning that tries to load a
swf from a local server. Do I have to setup server .. or how is this been
tested in mustella?

 <SetProperty target="swf1" propertyName="source"
value="http://localhost:{portNumber}/Managers/StyleManager/SWFs/assets/MP_customStyles_embeddedImages.swf?port={portNumber}"
waitTarget="swf1" waitEvent="updateComplete"/>

regards
cyrill

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Hi Alex,

If you have read the description of https://issues.apache.org/jira/browse/FLEX-33178, you had to see the errors that occur.
I thought that you had excluded the rest of LangPack tests, due to a problem with SDK current status, because the problems is not in runtime, but in compilation, due compiler not finding any resource bundles in SDK.

I compile the SDK running the "main", and other.locales goals in ANT build, maybe I missing something...

Thanks,

Jose.

On Aug 27, 2012, at 6:38 AM, Alex Harui <ah...@adobe.com> wrote:

> 
> 
> 
> On 8/26/12 1:49 AM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> 
>> Hi Alex,
>> 
>> Because in mustella1.properties, that all the tests were excluded with the
>> exception of the Japanese.
>> I generated the locales packages in SDK, but it follows without compiling the
>> Japanese test, because not to find the resource bundle in SDK.
>> I deduced then that it must be a problem of construction of SDK to repair in
>> another thread, and I assumed, that by that reason was excluded the others
>> tests.
>> 
>> If I am mistaken, tell me, and I cancel the pull-request, but please, comment
>> to me how I can confront the problem of the absence of resource bundles locale
>> in the test SDK, in order to resolve this issue and mustella LangPack tests.
>> 
> AFAICT, we did not exclude the Japanese tests at Adobe, so I think they
> should be running.  What kinds of errors did you get when they ran?
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/26/12 1:49 AM, "Jose Barragan" <jo...@codeoscopic.com> wrote:

> Hi Alex,
> 
> Because in mustella1.properties, that all the tests were excluded with the
> exception of the Japanese.
> I generated the locales packages in SDK, but it follows without compiling the
> Japanese test, because not to find the resource bundle in SDK.
> I deduced then that it must be a problem of construction of SDK to repair in
> another thread, and I assumed, that by that reason was excluded the others
> tests.
> 
> If I am mistaken, tell me, and I cancel the pull-request, but please, comment
> to me how I can confront the problem of the absence of resource bundles locale
> in the test SDK, in order to resolve this issue and mustella LangPack tests.
> 
AFAICT, we did not exclude the Japanese tests at Adobe, so I think they
should be running.  What kinds of errors did you get when they ran?

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Hi Alex,

Because in mustella1.properties, that all the tests were excluded with the exception of the Japanese.
I generated the locales packages in SDK, but it follows without compiling the Japanese test, because not to find the resource bundle in SDK. 
I deduced then that it must be a problem of construction of SDK to repair in another thread, and I assumed, that by that reason was excluded the others tests.

If I am mistaken, tell me, and I cancel the pull-request, but please, comment to me how I can confront the problem of the absence of resource bundles locale in the test SDK, in order to resolve this issue and mustella LangPack tests.

Thanks,

Jose.

On Aug 26, 2012, at 5:41 AM, Alex Harui <ah...@adobe.com> wrote:

> 
> 
> 
> On 8/25/12 6:45 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> 
>> In order to get the mustella zero fails goal, I've exclude the Japanese
>> LangPack tests too in mustella1.properties file.
>> 
> Why did you decide to exclude those tests?  Were there lots of errors?  Or
> do we need to know Japanese to get them to pass?
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/25/12 6:45 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:

> In order to get the mustella zero fails goal, I've exclude the Japanese
> LangPack tests too in mustella1.properties file.
> 
Why did you decide to exclude those tests?  Were there lots of errors?  Or
do we need to know Japanese to get them to pass?

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

In order to get the mustella zero fails goal, I've exclude the Japanese LangPack tests too in mustella1.properties file.

https://github.com/apache/flex/pull/13.patch

desktop_runner:
     [echo] **** Willkommen auf Runner ****
     [java] starting results server
     [java] starting baseline server
     [java] starting the baseline server: Sun Aug 26 03:21:24 CEST 2012
     [java] test script count: 1
     [java] Skipping: 
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java] Passes: 0
     [java] Fails: 0
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] Passed: 
     [java] =====================================================
     [java] =====================================================
     [java] Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java] Passes: 0
     [java] Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 24 seconds

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Here we go...
MarshallPlan and PerModuleStyle, I'll try to repair them...

     [java] Grabbing the log from: /Users/pepebarragan/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt to: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/MarshallPlan/SWFs/MP_simpleLoader.log
     [java] Grablog: never saw the ScriptDone for /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/MarshallPlan/SWFs/MP_simpleLoader.swf
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java]     Passes: 90
     [java]     Fails: 92
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] 	Passed: 
     [java] =====================================================
     [java] MarshallPlan/Bugs/MarshallPlan_Bugs_Tests MP_LoadFlexWithASLoader Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_DragManager_Compatibility_Tests DragManager_DragWithinSubApp_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_DragManager_Compatibility_Tests DragManager_DragSubAppToMain Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_Tab Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_ShiftTab Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_Tab_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_ShiftTab_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_Tab Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_ShiftTab Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_PopUps Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_TabIndex Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_Tab_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_ShiftTab_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_centerPopUp_modal Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_centerPopUp_nonmodal Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_createPopUP_modal Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_createPopUP_nonmodal Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_addPopUp_modal Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_addPopUp_nonmodal Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_createPopUP_modal_comp Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_createPopUP_nonmodal_comp Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_addPopUp_modal_comp Passed  
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_addPopUp_nonmodal_comp Passed  
     [java] MarshallPlan/RPC/MP_HTTPService_Tests MP_HTTPService_localXML Passed  
     [java] MarshallPlan/RPC/MP_HTTPService_Tests MP_HTTPService_localXML_compatibility Passed  
     [java] MarshallPlan/RPC/MP_HTTPService_Tests MP_HTTPService_localXML_fault Passed  
     [java] MarshallPlan/RPC/MP_HTTPService_Tests MP_HTTPService_localXML_fault_compatibility Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_EditableList_trusted Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_EditableList_compatible Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_EditableDataGrid_trusted Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_OpeningTreeNodes_trusted Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_OpeningTreeNodes_compatible Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_closeOnMouseDown_trusted Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_closeOnMouseDown_compatible Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_closeOnMouseDownOutside_trusted Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_closeOnMouseDownOutside_compatible Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_closeOnMouseDown_trusted Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_closeOnMouseDown_compatible Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_closeOnMouseDownOutside_trusted Passed  
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_closeOnMouseDownOutside_compatible Passed  
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_SetBusyCursor Passed  
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_RemoveBusyCursor Passed  
     [java] MarshallPlan/ManagerTests/MP_DragManager_Tests DragManager_DragWithinSubApp Passed  
     [java] MarshallPlan/ManagerTests/MP_DragManager_Tests DragManager_DragMainToSubApp Passed  
     [java] MarshallPlan/ManagerTests/MP_DragManager_Tests DragManager_DragSubAppToMain Passed  
     [java] MarshallPlan/ManagerTests/MP_DragManager_Compatibility_Tests DragManager_DragMainToSubApp_Compatiblity Passed  
     [java] MarshallPlan/ManagerTests/MP_DragManager_Compatibility_Tests DragManager_DragWithinSubApp_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/MP_DragManager_Compatibility_Tests DragManager_DragSubAppToMain Passed  
     [java] MarshallPlan/ManagerTests/MP_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_Tab Passed  
     [java] MarshallPlan/ManagerTests/MP_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_ShiftTab Passed  
     [java] MarshallPlan/ManagerTests/MP_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_TabIndex Passed  
     [java] MarshallPlan/ManagerTests/MP_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_Tab_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/MP_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_ShiftTab_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/MP_FocusManager_Tests MarshallPlan_FocusManager_Tab Passed  
     [java] MarshallPlan/ManagerTests/MP_FocusManager_Tests MarshallPlan_FocusManager_ShiftTab Passed  
     [java] MarshallPlan/ManagerTests/MP_FocusManager_Tests MarshallPlan_FocusManager_PopUps Passed  
     [java] MarshallPlan/ManagerTests/MP_FocusManager_Tests MarshallPlan_FocusManager_TabIndex Passed  
     [java] MarshallPlan/ManagerTests/MP_FocusManager_Tests MarshallPlan_FocusManager_Tab_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/MP_FocusManager_Tests MarshallPlan_FocusManager_ShiftTab_compatibilityMode Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_enabledFalse_trusted Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_currentTarget_trusted Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_enabledFalse_compatible Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_enabledTrue_compatible Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_hideDelay_trusted Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_showDelay_trusted Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_showDelay_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_currentTarget_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_hideDelay_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_centerPopUp_modal Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_centerPopUp_nonmodal Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_createPopUP_modal Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_createPopUP_nonmodal Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_addPopUp_modal Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_addPopUp_nonmodal Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_createPopUP_modal_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_createPopUP_nonmodal_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_addPopUp_modal_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_addPopUp_nonmodal_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_ResourceManager_Tests MP_Compc_Params_IncludeResourceBundles_VerifyLocales Passed  
     [java] MarshallPlan/ManagerTests/MP_ResourceManager_Tests MP_Compc_Params_IncludeResourceBundles_enUSResource Passed  
     [java] MarshallPlan/ManagerTests/MP_ResourceManager_Tests MP_Compc_Params_IncludeResourceBundles_jaJPResource Passed  
     [java] MarshallPlan/ManagerTests/MP_ResourceManager_Tests MP_Compc_Params_IncludeResourceBundles_Comma_frFRResource Passed  
     [java] MarshallPlan/ManagerTests/MP_ResourceManager_Tests MP_Compc_Params_IncludeResourceBundles_VerifyLocales_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_ResourceManager_Tests MP_Compc_Params_IncludeResourceBundles_enUSResource_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_ResourceManager_Tests MP_Compc_Params_IncludeResourceBundles_jaJPResource_comp Passed  
     [java] MarshallPlan/ManagerTests/MP_ResourceManager_Tests MP_Compc_Params_IncludeResourceBundles_Comma_frFRResource_comp Passed  
     [java] MarshallPlan/Spark/MP_Spark_Controls_Tests MP_Spark_Component_toolTip_compatibility Passed  
     [java] MarshallPlan/Spark/MP_Spark_Controls_Tests2 MP_Spark_Component_Effects_trusted Passed  
     [java] MarshallPlan/Spark/MP_Spark_Controls_Tests2 MP_Spark_Component_DropDownList_trusted Passed  
     [java] MarshallPlan/Spark/MP_Spark_Controls_Tests2 MP_Spark_Component_Effects_compatible Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] MarshallPlan/RSLs/allowDomain_Tests allowDomain_rsl Failed SetProperty(setup:step 12)  Timeout waiting for complete from sl2 
     [java] MarshallPlan/RSLs/allowDomainFalse_Tests allowDomainFalse_rsl Failed SetProperty(setup:step 12)  Timeout waiting for complete from sl2 
     [java] MarshallPlan/ManagerTests/bootstrap_DragManager_Compatibility_Tests DragManager_DragMainToSubApp_Compatiblity Failed SetProperty(setup:step 7)  Timeout waiting for complete from swf2 
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_Tab_fromLocalhost Failed SetProperty(setup:step 9)  Timeout waiting for complete from topSWF 
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_ShiftTab_fromLocalhost Failed SetProperty(setup:step 9)  Timeout waiting for complete from topSWF 
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_Tab_fromLocalhost_compatibilityMode Failed SetProperty(setup:step 9)  Timeout waiting for complete from topSWF 
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_ShiftTab_fromLocalhost_compatibilityMode Failed SetProperty(setup:step 9)  Timeout waiting for complete from topSWF 
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_Tab_compatibilityMode_2ndLevelUntrusted Failed SetProperty(setup:step 14)  Timeout waiting for complete from topSWF.content.document.swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_NestedSWF_FocusManager_Tests NestedSWF_ShiftTab_compatibilityMode_2ndLevelUntrusted Failed SetProperty(setup:step 14)  Timeout waiting for complete from topSWF.content.document.swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_Tab_fromLocalhost Failed SetProperty(setup:step 9)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_ShiftTab_fromLocalhost Failed SetProperty(setup:step 9)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_FocusManager_Tests MarshallPlan_FocusManager_Tab_fromLocalhost_compatibilityMode Failed SetProperty(setup:step 9)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_addPopUp_modal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_createPopUP_nonmodal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_addPopUp_nonmodal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_centerPopUp_nonmodal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_centerPopUp_modal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_addPopUp_modal_remote_comp Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_addPopUp_nonmodal_remote_comp Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_centerPopUp_nonmodal_remote_comp Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_centerPopUp_modal_remote_comp Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_createPopUP_nonmodal_remote_comp Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_dragTrustedPopUp Failed CompareBitmap(body:step 12)  compare returned[object BitmapData] 
     [java] MarshallPlan/ManagerTests/bootstrap_PopUpManager_Tests MP_PopUpManager_dragUnTrustedPopUp Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/RPC/MP_DataSetArraySQLTest getDataSetArray Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataSetArraySQLTest getDataSetArray_compatible Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataSetComplexSQLTest getCustomersAsComplexDS Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataSetComplexSQLTest getCustomersAsComplexDS_compatible Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataSetEmptySQLTest getEmptyDS Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataSetEmptySQLTest getEmptyDS_compatible Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataSetSingleSQLTest getCustomersAsDS Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataSetSingleSQLTest getCustomersAsDS_compatible Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataTableArraySQLTest getDataTableArray Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataTableArraySQLTest getDataTableArray_compatible Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataTableSingleSQLTest getCustomersAsDT Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataTableSingleSQLTest getCustomersAsDT_compatible Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataTypeSurveySQLAsDSTest getDatTypeSurveyAsDS Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/RPC/MP_DataTypeSurveySQLAsDSTest getDatTypeSurveyAsDS_compatible Failed RunCode(body:step 3)  Timeout waiting for updateComplete from swf22.content.document.dg 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_EditableList_remote Failed SetProperty(body:step 1)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_EditableDataGrid_untrusted Failed SetProperty(setup:step 7)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ButtonWithEmbeddedIcon_trusted Failed CompareBitmap(body:step 2)  compare returned-3 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ButtonWithEmbeddedIcon_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_OpeningTreeNodes_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_swatchPanel_trusted Failed AssertPropertyValue(body:step 4)  swf1.content.document.colorPicker1.mx_internal:dropdown.x 230 != 332 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_swatchPanel_compatible Failed AssertPropertyValue(body:step 4)  swf1.content.document.colorPicker1.mx_internal:dropdown.x 230 != 332 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_swatchPanel_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_closeOnMouseDown_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_ColorPicker_closeOnMouseDownOutside_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_calendar_trusted Failed AssertPropertyValue(body:step 4)  swf1.content.document.dateField1.dropdown.x 238 != 340 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_calendar_compatible Failed AssertPropertyValue(body:step 4)  swf1.content.document.dateField1.dropdown.x 238 != 340 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_calendar_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_closeOnMouseDown_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Controls/MP_Controls_Tests MP_DateField_closeOnMouseDownOutside_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_SetCursor_EmbeddedImage Failed AssertPixelValue(body:step 7)  swf1.content.document.testPanel pixel at (5,43) F3F3F3 != 0x2A4A76 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_SetCursor_XOffset Failed AssertPixelValue(body:step 5)  swf1.content.document.testPanel pixel at (35,43) FFFFFF != 0x2A4A76 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_SetCursor_YOffset Failed AssertPixelValue(body:step 5)  swf1.content.document.testPanel pixel at (5,73) F3F3F3 != 0x2A4A76 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_HideCursor Failed AssertPixelValue(body:step 5)  swf1.content.document.testPanel pixel at (30,67) FFFFFF != 0x29346E 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_ShowCursor Failed AssertPixelValue(body:step 8)  swf1.content.document.testPanel pixel at (30,67) FFFFFF != 0x29346E 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_RemoveAllCursors Failed AssertPixelValue(body:step 5)  swf1.content.document.testPanel pixel at (30,67) FFFFFF != 0x29346E 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_RemoveCursor Failed AssertPixelValue(body:step 5)  swf1.content.document.testPanel pixel at (30,67) FFFFFF != 0x29346E 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_SetCursor_InSubApp Failed AssertPixelValue(body:step 6)  swf1.content.document.testPanel pixel at (5,43) F3F3F3 != 0x2A4A76 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_SetCursor_InCompatibilitySubApp Failed AssertPixelValue(body:step 6)  swf1.content.document.testPanel pixel at (5,43) F3F3F3 != 0x2A4A76 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_DividedBox_local Failed CompareBitmap(body:step 7)  compare returned[object BitmapData] 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_DividedBox_remote Failed SetProperty(setup:step 9)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_CursorManager_Tests MP_CursorManager_DividedBox_compatibility Failed CompareBitmap(body:step 5)  compare returned[object BitmapData] 
     [java] MarshallPlan/ManagerTests/MP_DragManager_Tests DragManager_CustomDrag_Trusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swfLoader1 
     [java] MarshallPlan/ManagerTests/MP_DragManager_Tests DragManager_DragWithinSubApp_remote Failed SetProperty(setup:step 6)  Timeout waiting for complete from swfLoader1 
     [java] MarshallPlan/ManagerTests/MP_DragManager_Tests DragManager_DragMainToSubApp_remote Failed SetProperty(setup:step 6)  Timeout waiting for complete from swfLoader1 
     [java] MarshallPlan/ManagerTests/MP_DragManager_Tests DragManager_DragSubAppToMain_remote Failed SetProperty(setup:step 7)  Timeout waiting for complete from swfLoader1 
     [java] MarshallPlan/ManagerTests/MP_DragManager_Tests DragManager_CustomDrag_UnTrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swfLoader1 
     [java] MarshallPlan/ManagerTests/MP_DragManager_Compatibility_Tests DragManager_CustomDrag_Compatible Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf2 
     [java] MarshallPlan/Spark/MP_FCK_Tests MP_Spark_Component_DropDownList_compatible Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Spark/MP_FCK_Tests MP_Spark_Component_DropDownList_untrusted Failed SetProperty(setup:step 7)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_Tab_fromLocalhost Failed SetProperty(setup:step 9)  Timeout waiting for complete from topSWF 
     [java] MarshallPlan/ManagerTests/MP_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_ShiftTab_fromLocalhost Failed SetProperty(setup:step 9)  Timeout waiting for complete from topSWF 
     [java] MarshallPlan/ManagerTests/MP_NestedSWF_FocusManager_Tests NestedSWF_FocusManager_ShiftTab_fromLocalhost_compatibilityMode Failed Timed out
     [java] MarshallPlan/ManagerTests/MP_FocusManager_Tests MarshallPlan_FocusManager_Tab_fromLocalhost Failed SetProperty(setup:step 9)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_FocusManager_Tests MarshallPlan_FocusManager_ShiftTab_fromLocalhost Failed SetProperty(setup:step 9)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_enabledTrue_trusted Failed CompareBitmap, url = ../ManagerTests/baselines/ToolTip_main_trusted.pn(body:step 7)  compare returned[object BitmapData] 
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_toolTipClass_trusted Failed CompareBitmap, url = ../ManagerTests/baselines/ToolTip_main_trusted_toolTipClass.pn(body:step 6)  compare returned[object BitmapData] 
     [java] MarshallPlan/ManagerTests/MP_ToolTipManager_Tests MP_ToolTipManager_toolTipClass_comp Failed CompareBitmap, url = ../ManagerTests/baselines/ToolTip_main_comp_toolTipClass.pn(body:step 6)  compare returned[object BitmapData] 
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_addPopUp_modal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_createPopUP_nonmodal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_addPopUp_nonmodal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_centerPopUp_nonmodal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_centerPopUp_modal_remote Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_dragTrustedPopUp Failed CompareBitmap(body:step 12)  compare returned[object BitmapData] 
     [java] MarshallPlan/ManagerTests/MP_PopUpManager_Tests MP_PopUpManager_dragUnTrustedPopUp_remote Failed Timed out
     [java] MarshallPlan/Spark/MP_Spark_Controls_Tests MP_Spark_Component_toolTip_untrusted Failed SetProperty(setup:step 8)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Spark/MP_Spark_Controls_Tests2 MP_Spark_Component_DropDownList_untrusted Failed SetProperty(setup:step 7)  Timeout waiting for complete from swf1 
     [java] MarshallPlan/Spark/MP_Spark_Controls_Tests2 MP_Spark_Component_Effects_untrusted Failed SetProperty(setup:step 7)  Timeout waiting for complete from swf2 
     [java] MarshallPlan/Events/MP_Events_Tests MP_SandboxRootMouseEvent_click Failed SetProperty(setup:step 6)  Timeout waiting for complete from swf1 
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 90
     [java]     Fails: 92
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

BUILD FAILED
/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/build.xml:1457: The following error occurred while executing this line:
/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/build.xml:1575: Java returned: 1

Total time: 12 minutes 48 seconds




     [java] Grabbing the log from: /Users/pepebarragan/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt to: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/PerModuleStyles/SWFs/ViewStackApp.log
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java]     Passes: 27
     [java]     Fails: 28
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] 	Passed: 
     [java] =====================================================
     [java] PerModuleStyles/inheritance/checkInheritance_currentAppDomain styleInheritanceCurrentDomain Passed  
     [java] PerModuleStyles/merging/checkMerging2006 styleMerging2006 Passed  
     [java] PerModuleStyles/merging/checkMerging2006 styleMerging_module2006 Passed  
     [java] PerModuleStyles/merging/checkMergingWithCompatFlag styleMergingCompat Passed  
     [java] PerModuleStyles/merging/checkMergingWithCompatFlag styleMergingCompat_module Passed  
     [java] PerModuleStyles/styleManager/currentStyleManager checkTopLevelStyleManager Passed  
     [java] PerModuleStyles/styleManager/currentStyleManager checkModuleStyleManager Passed  
     [java] PerModuleStyles/styleManager/currentStyleManager2 testModuleStyleManager Passed  
     [java] PerModuleStyles/styleManager/currentStyleManager3 testTopLevelStyleManager Passed  
     [java] PerModuleStyles/styleManager/currentStyleManager3 testModuleStyleManager Passed  
     [java] PerModuleStyles/BasicTests/inheritingStyle inheritingStyles Passed  
     [java] PerModuleStyles/api/modifyStyleDeclaration modifyModuleStyleAfterReload Passed  
     [java] PerModuleStyles/inheritance/checkInheritanceModuleManager styleInheritanceModuleManager Passed  
     [java] PerModuleStyles/inheritance/checkInheritanceModuleManagerNoParentFactory styleInheritanceModuleManagerNoParentFactory Passed  
     [java] PerModuleStyles/BasicTests/alertTest alertTest_localModuleFactory Passed  
     [java] PerModuleStyles/BasicTests/alertTest alertTest Passed  
     [java] PerModuleStyles/BasicTests/checkStyles perModuleStyle Passed  
     [java] PerModuleStyles/inheritance/checkInheritance styleInheritance Passed  
     [java] PerModuleStyles/inheritance/checkInheritance_swfLoader styleInheritance_swfLoader Passed  
     [java] PerModuleStyles/BasicTests/checkRTE checkRTE Passed  
     [java] PerModuleStyles/regressions/SDK_22461 checkRTE Passed  
     [java] PerModuleStyles/regressions/SDK_25376 checkRTE_setStyle Passed  
     [java] PerModuleStyles/regressions/SDK_25444 checkRTE_setStyleSubApp Passed  
     [java] PerModuleStyles/BasicTests/themesTest themeTest Passed  
     [java] PerModuleStyles/api/checkStyleDeclaration perModuleStyle Passed  
     [java] PerModuleStyles/regressions/SDK_23081 checkRTE_SwfLoader Passed  
     [java] PerModuleStyles/BasicTests/tooltipTest tool_TipTest Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] PerModuleStyles/BasicTests/checkStylesSetViaSkin perModuleStyleViaSkin Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] PerModuleStyles/merging/checkMerging styleMerging Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/merging/checkMerging styleMergingChain Failed CompareBitmap(body:step 4)  compare returned-3 
     [java] PerModuleStyles/merging/checkMergingSwf styleMergingSwf Failed CompareBitmap(body:step 4)  compare returned-3 
     [java] PerModuleStyles/merging/checkMergingSwf styleMergingChainSwf Failed CompareBitmap(body:step 4)  compare returned-3 
     [java] PerModuleStyles/merging/checkMergingSwfModule styleMergingSwfModule Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/merging/checkMergingSwfModule styleMergingSwfModule_module Failed CompareBitmap(body:step 1)  compare returned-3 
     [java] PerModuleStyles/merging/checkMergingSwfModule styleMergingSwfModule_swf Failed CompareBitmap(body:step 1)  compare returned-3 
     [java] PerModuleStyles/merging/checkMergingModuleViaSwf styleMergingSwfViaModule Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/api/modifyStyleDeclarationInApp modifyAppStyle Failed CompareBitmap(body:step 3)  compare returned-4 
     [java] PerModuleStyles/api/modifyStyleDeclarationInApp modifyAppStyleAfterReload Failed AssertStyleValue(body:step 4)  mod_loader2.child.moduleList.color 0 != 255 
     [java] PerModuleStyles/merging/checkMergingVariousCssSelectors styleMergingVariousSelectors Failed CompareBitmap(body:step 2)  compare returned-3 
     [java] PerModuleStyles/merging/checkMergingVariousCssSelectors styleMergingVariousSelectors_module Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/merging/checkMergingVariousCssSelectors checkModuleWithIsolateStylesOff Failed CompareBitmap(body:step 4)  compare returned-3 
     [java] PerModuleStyles/BasicTests/loadFonts loadFonts Failed CompareBitmap(body:step 5)  compare returned[object BitmapData] 
     [java] PerModuleStyles/api/loadCSSSwf loadCSSSwf Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/api/loadCSSSwf_SubApp loadCSSSwf_SubApp Failed CompareBitmap(body:step 3)  compare returned-4 
     [java] PerModuleStyles/api/loadCSSSwf_SubAppEmbed loadCSSSwf_SubAppEmbed Failed CompareBitmap(body:step 3)  compare returned-4 
     [java] PerModuleStyles/api/modifyMergedStyleDeclarationInApp modifyAppMergedStyle Failed CompareBitmap(body:step 3)  compare returned-4 
     [java] PerModuleStyles/api/modifyStyleDeclaration modifyModuleStyle Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/api/modifyMergedStyleDeclaration modifyMergedModuleStyle Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/BasicTests/createPopupTest createPopUpTest Failed CompareBitmap(body:step 5)  compare returned[object BitmapData] 
     [java] PerModuleStyles/inheritance/checkInheritanceViaSkin styleInheritanceViaSkin Failed RunCode(body:step 1)  Timeout waiting for moduleLoaded from  
     [java] PerModuleStyles/BasicTests/popupTest PopUpTest_AppStyle Failed CompareBitmap(body:step 5)  compare returned[object BitmapData] 
     [java] PerModuleStyles/BasicTests/popupTest PopUpTest_ModuleStyle Failed CompareBitmap(body:step 5)  compare returned[object BitmapData] 
     [java] PerModuleStyles/api/loadCSSModule loadCSSModule Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/api/loadCSS_SubApp loadCSS_SubApp Failed CompareBitmap(body:step 3)  compare returned-3 
     [java] PerModuleStyles/BasicTests/deferredInstantiationTest styleDeferred Failed CompareBitmap(body:step 5)  compare returned-3 
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 27
     [java]     Fails: 28
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

BUILD FAILED
/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/build.xml:1457: The following error occurred while executing this line:
/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/build.xml:1575: Java returned: 1

Total time: 13 minutes 8 seconds

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

mustella/tests/ListDataEffects

Nothing to do here too..

[java] time: 08:58:42.903
     [java] clobberProcess
     [java] Grab log, do parse = false
     [java] Grabbing the log from: /Users/pepebarragan/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt to: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/ListDataEffects/TileList/SWFs/TileListMainoffScreen.log
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java]     Passes: 6
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] 	Passed: 
     [java] =====================================================
     [java] ListDataEffects/List/Properties/LDE_List_PropertyTester LDE_list_effect_dragDrop Passed  
     [java] ListDataEffects/List/Properties/LDE_List_PropertyTester LDE_list_modifiedCollectionView Passed  
     [java] ListDataEffects/List/Styles/LDE_List_Tester LDE_list_editable_LDE_default Passed  
     [java] ListDataEffects/List/Styles/LDE_List_Tester LDE_list_editable_with_LDE_default Passed  
     [java] ListDataEffects/List/Styles/LDE_List_Tester LDE_list_editable_with_LDE_Effect1 Passed  
     [java] ListDataEffects/List/Styles/LDE_List_Tester LDE_list_editable_with_LDE_Effect2 Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 6
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 40 seconds

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

mustella/tests/GraphicTags

Nothing to do here

     [java] time: 08:55:06.732
     [java] clobberProcess
     [java] Grab log, do parse = false
     [java] Grabbing the log from: /Users/pepebarragan/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt to: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/GraphicTags/SWFs/GraphicTags_RenderPosition.log
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java]     Passes: 3
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] 	Passed: 
     [java] =====================================================
     [java] GraphicTags/Bugs/GraphicTags_ObjectOrder_tests GraphicTags_ObjectOrder_1 Passed  
     [java] GraphicTags/Bugs/GraphicTags_ObjectOrder2_tests GraphicTags_ObjectOrder2_1 Passed  
     [java] GraphicTags/Bugs/GraphicTags_RenderPosition_test GraphicTags_RenderPosition_1 Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 3
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 29 seconds

Re: Getting Mustella to work.

Posted by Jose Barragan Andrade <pe...@me.com>.

mustella/tests/Formatters

nothing to do here 

   [java] time: 08:48:53.629
     [java] clobberProcess
     [java] Grab log, do parse = false
     [java] Grabbing the log from: /Users/pepebarragan/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt to: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/Formatters/SWFs/Formatters_Main.log
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 76
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 39 seconds

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Keeping work...

mustella/tests/DownloadProgressBar

nothing to do here :)

desktop_runner:
     [echo] **** Willkommen auf Runner ****
     [java] starting results server
     [java] starting baseline server
     [java] test script count: 1
     [java] new test file: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/DownloadProgressBar/SWFs/DownloadProgressBar_Main.swf
     [java] ******** cmdArr before: 
     [java] 	/Applications/Adobe Flash Builder 4.7/player/mac/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger
     [java] 	/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/DownloadProgressBar/SWFs/DownloadProgressBar_Main.swf
     [java] ******** moreParameters before: 
     [java] ******** cmdArr after: 
     [java] 	/Applications/Adobe Flash Builder 4.7/player/mac/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger
     [java] 	/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/DownloadProgressBar/SWFs/DownloadProgressBar_Main.swf
     [java] getting directory from the swf file
     [java] derived directory: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/DownloadProgressBar/SWFs
     [java] Launching: 
     [java]  /Applications/Adobe Flash Builder 4.7/player/mac/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/DownloadProgressBar/SWFs/DownloadProgressBar_Main.swf Launching: /Applications/Adobe Flash Builder 4.7/player/mac/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/DownloadProgressBar/SWFs/DownloadProgressBar_Main.swf
     [java] USING directory: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/DownloadProgressBar/SWFs
     [java] time: 08:41:17.363
     [java] starting the baseline server: Sat Aug 25 08:41:17 CEST 2012
     [java] clobberProcess
     [java] Grab log, do parse = false
     [java] Grabbing the log from: /Users/pepebarragan/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt to: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/DownloadProgressBar/SWFs/DownloadProgressBar_Main.log
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java]     Passes: 8
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] 	Passed: 
     [java] =====================================================
     [java] DownloadProgressBar/Properties/DownloadProgressBar_Properties DownloadProgressBar_properties_backgroundColor Passed  
     [java] DownloadProgressBar/Properties/DownloadProgressBar_Properties DownloadProgressBar_properties_backgroundAlpha Passed  
     [java] DownloadProgressBar/Properties/SparkDownloadProgressBar_Properties SparkDownloadProgressBar_default Passed  
     [java] DownloadProgressBar/Properties/SparkDownloadProgressBar_Properties SparkDownloadProgressBar_properties_backgroundColor Passed  
     [java] DownloadProgressBar/Properties/SparkDownloadProgressBar_Properties SparkDownloadProgressBar_properties_backgroundAlpha Passed  
     [java] DownloadProgressBar/Properties/SparkDownloadProgressBar_Properties SparkDownloadProgressBar_properties_backgroundImage Passed  
     [java] DownloadProgressBar/Properties/SparkDownloadProgressBar_Properties SparkDownloadProgressBar_properties_preloaderBaseColor Passed  
     [java] DownloadProgressBar/Properties/SparkDownloadProgressBar_Properties SparkDownloadProgressBar_RSL_NoError Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 8
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 59 seconds

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

On 8/23/12 5:45 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

> mmm...I think attachements was not allowed so this is the url of the file:
> 
> https://dl.dropbox.com/u/8496144/test_itemRenderers.patch
Carlos,

How did you create this patch file?  There are no paths to the files but the
files are from two different directories.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

mmm...I think attachements was not allowed so this is the url of the file:

https://dl.dropbox.com/u/8496144/test_itemRenderers.patch

best

C.

2012/8/24 Carlos Rovira <ca...@codeoscopic.com>

> Here is the patch (I already was reported by secretary that my ICLA was
> received, so there should be no problem with this donation).
>
> There's no bitmaps, only modified code (As I used createImages and revert
> deletions to be as close as possible to repo state)
>
> Let me know if this is ok since is my first SVN patch generated
> ever! (hope git support comes soon to return to commodity! :)). It was
> generated with eclipse subversive wizard and modifies five files in total.
>
>
> 2012/8/24 Alex Harui <ah...@adobe.com>
>>
>> Excellent!  If the patch file is huge, try skipping the bitmaps as we
>> should
>> be able to regenerate them after the patch on any machine.
>>
>>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> 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ón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

I will take a look soon, but maybe not until the weekend.


On 8/23/12 5:44 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

Here is the patch (I already was reported by secretary that my ICLA was received, so there should be no problem with this donation).

There's no bitmaps, only modified code (As I used createImages and revert deletions to be as close as possible to repo state)

Let me know if this is ok since is my first SVN patch generated ever! (hope git support comes soon to return to commodity! :)). It was generated with eclipse subversive wizard and modifies five files in total.


2012/8/24 Alex Harui <ah...@adobe.com>
Excellent!  If the patch file is huge, try skipping the bitmaps as we should
be able to regenerate them after the patch on any machine.




--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Here is the patch (I already was reported by secretary that my ICLA was
received, so there should be no problem with this donation).

There's no bitmaps, only modified code (As I used createImages and revert
deletions to be as close as possible to repo state)

Let me know if this is ok since is my first SVN patch generated ever! (hope
git support comes soon to return to commodity! :)). It was generated with
eclipse subversive wizard and modifies five files in total.


2012/8/24 Alex Harui <ah...@adobe.com>
>
> Excellent!  If the patch file is huge, try skipping the bitmaps as we
> should
> be able to regenerate them after the patch on any machine.
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/23/12 5:28 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

> "tests/itemRenderers/" passed :)
> 
> [java] =====================================================
>      [java]     Passes: 310
>      [java]     Fails: 0
>      [java] =====================================================
> 
> 90% of fails was due to bad location of mouse coordinates. Relocating from
> 5,5 to 10,10 was suficient to make it work.
> 
> ./mini_run.sh -createImages tests/itemRenderers/ was always used to ensure
> correct running tests.
> 
> Tomorrow will make a patch since multiple files where modified this time.
> 
Excellent!  If the patch file is huge, try skipping the bitmaps as we should
be able to regenerate them after the patch on any machine.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

"tests/itemRenderers/" passed :)

[java] =====================================================
     [java]     Passes: 310
     [java]     Fails: 0
     [java] =====================================================

90% of fails was due to bad location of mouse coordinates. Relocating from
5,5 to 10,10 was suficient to make it work.

./mini_run.sh -createImages tests/itemRenderers/ was always used to ensure
correct running tests.

Tomorrow will make a patch since multiple files where modified this time.

Best,


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carol Frampton <cf...@adobe.com>.

Above what you cut and pasted will be the log messages for each test that
was run.  For the timeouts, go look in the log files for the tests.  For
the first timeout, it looks like it didn't get an event it expected.  I'd
start by looking at the test and making sure whatever event it is
expecting is correct.

I use mustella/as3/src/mustella/imageDiffAIR.air to look at the bitmap
failures.  It is a very handy tool since you can see the good and the bad
right next to each other.

Carol

On 8/22/12 11 :11AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

>Hi Peter,
>
>thanks for updating the wiki. My SO is Mac OSX 10.8 if you want to
>complete
>that info.
>
>I'm now with "tests/itemRenderers/" that is throwing me some errors:
>
>[java] =====================================================
>     [java] Failed:
>     [java] =====================================================
>     [java] 
>itemRenderers/Halo/DataGrid/test_scripts/ItemRenderer_BugTests2
>itemRenderers_SDK13453 Failed CompareBitmap(body:step 3)  compare
>returned[object BitmapData]
>     [java]
>itemRenderers/Halo/DataGrid/test_scripts/DataGrid_customRenderers
>CustomHeaderRenderer_AS Failed AssertEvent(body:step 2)  Timeout waiting
>for complete from
>dataGrid_basic.mx_internal:rendererArray.0.0.getChildAt(0)
>     [java]
>itemRenderers/Spark/DataGrid/test_scripts/DataGrid_customRenderers_spark
>method_createEditor Failed Timed out
>     [java]
>itemRenderers/Spark/DataGrid/test_scripts/DataGrid_itemEditor_spark
>CheckBoxItemEditor_Basic Failed Timed out
>     [java] itemRenderers/Spark/List/test_scripts/List_itemEditor_spark
>CheckBoxItemEditor_Basic Failed Timed out
>     [java]
>     [java]
>     [java] =====================================================
>     [java]     Passes: 241
>     [java]     Fails: 5
>     [java] =====================================================
>
>
>Best
>
>Carlos
>
>
>2012/8/22 Peter Ent <pe...@adobe.com>
>
>> Once you generate a bitmap(s), re-run the test suite (without
>> -createImages) just to verify that it all works.
>>
>> Carol things some tests may have bugs which could lead to bad bitmap
>> comparisons and perhaps the old and new images should be compared using
>>a
>> tool like ImageDiffAIR. If you run across a test suite with lots of
>>tests
>> failing bitmap comparisons, it may be that the tests have bugs.
>>
>> --peter
>>
>> On 8/22/12 6:56 AM, "Carlos Rovira" <ca...@codeoscopic.com>
>>wrote:
>>
>> >Thanks Peter,
>> >
>> >I finaly get "tests/SparkModules/" without fails by applying the
>> >-createImages argument since I was only getting this output:
>> >
>> >[java] =====================================================
>> >     [java] Failed:
>> >     [java] =====================================================
>> >     [java] SparkModules/Constraints/Properties/Module_tester002
>> >MixedLayoutModule000 Failed CompareBitmap(body:step 1)  compare
>> >returned[object BitmapData]
>> >     [java]
>> >     [java]
>> >     [java] =====================================================
>> >     [java]     Passes: 23
>> >     [java]     Fails: 1
>> >     [java] =====================================================
>> >
>> >Now it's ok:
>> >
>> >java] =====================================================
>> >     [java]     Passes: 24
>> >     [java]     Fails: 0
>> >     [java] =====================================================
>> >
>> >
>> >So other folder is ok :)
>> >
>> >
>> >
>> >2012/8/22 Peter Ent <pe...@adobe.com>
>> >
>> >> I will check for all the emails from Carlos tomorrow morning and get
>> >>them
>> >> all in at once. Since Carlos is being very active I'll try to keep
>>up!
>> >>
>> >> Thanks, Carlos!
>> >> --peter
>> >>
>> >> On 8/21/12 5:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>> >>
>> >> >Hi Carlos,
>> >> >
>> >> >That's awesome.  Thanks for pitching in.  Peter, can you update the
>> >>wiki?
>> >> >
>> >> >An interesting thing for you to do is before you quit working for
>>the
>> >>day,
>> >> >run mini_run.sh -all and see what you get in the morning.  The
>>failures
>> >> >will
>> >> >point to folders to work on.  Review this thread for what others are
>> >> >working
>> >> >on.  I've working on the entire spark folder, for example.
>> >> >
>> >> >-Alex
>> >> >
>> >> >
>> >> >On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com>
>> >> wrote:
>> >> >
>> >> >> Ops! I reboot Terminal and pass it again and all is ok with
>> >> >>"GraphicTags"...
>> >> >>
>> >> >> [java] =====================================================
>> >> >>      [java]     Passes: 3
>> >> >>      [java]     Fails: 0
>> >> >>      [java] =====================================================
>> >> >>
>> >> >>
>> >> >> So It's needed at least two passes when a time out is thrown...I'm
>> >> >> finishing to understand mustella ;)
>> >> >>
>> >> >>
>> >> >>
>> >> >> 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
>> >> >>
>> >> >>>
>> >> >>> but "tests/GraphicTags/"
>> >> >>>
>> >> >>> reports
>> >> >>> [java] =====================================================
>> >> >>>      [java]     Passes: 2
>> >> >>>      [java]     Fails: 1
>> >> >>>      [java] =====================================================
>> >> >>>
>> >> >>> so I'll fix GraphicTags
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> --
>> >> >>> Carlos Rovira
>> >> >>> Director de Tecnología
>> >> >>> 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ón, 32
>> >> >>> Planta 10, Puertas P-Q
>> >> >>> 28020 Madrid
>> >> >>>
>> >> >>>
>> >> >>
>> >> >
>> >> >--
>> >> >Alex Harui
>> >> >Flex SDK Team
>> >> >Adobe Systems, Inc.
>> >> >http://blogs.adobe.com/aharui
>> >> >
>> >>
>> >>
>> >
>> >
>> >--
>> >Carlos Rovira
>> >Director de Tecnología
>> >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ón, 32
>> >Planta 10, Puertas P-Q
>> >28020 Madrid
>>
>>
>
>
>-- 
>Carlos Rovira
>Director de Tecnología
>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ón, 32
>Planta 10, Puertas P-Q
>28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Peter,

thanks for updating the wiki. My SO is Mac OSX 10.8 if you want to complete
that info.

I'm now with "tests/itemRenderers/" that is throwing me some errors:

[java] =====================================================
     [java] Failed:
     [java] =====================================================
     [java] itemRenderers/Halo/DataGrid/test_scripts/ItemRenderer_BugTests2
itemRenderers_SDK13453 Failed CompareBitmap(body:step 3)  compare
returned[object BitmapData]
     [java]
itemRenderers/Halo/DataGrid/test_scripts/DataGrid_customRenderers
CustomHeaderRenderer_AS Failed AssertEvent(body:step 2)  Timeout waiting
for complete from
dataGrid_basic.mx_internal:rendererArray.0.0.getChildAt(0)
     [java]
itemRenderers/Spark/DataGrid/test_scripts/DataGrid_customRenderers_spark
method_createEditor Failed Timed out
     [java]
itemRenderers/Spark/DataGrid/test_scripts/DataGrid_itemEditor_spark
CheckBoxItemEditor_Basic Failed Timed out
     [java] itemRenderers/Spark/List/test_scripts/List_itemEditor_spark
CheckBoxItemEditor_Basic Failed Timed out
     [java]
     [java]
     [java] =====================================================
     [java]     Passes: 241
     [java]     Fails: 5
     [java] =====================================================


Best

Carlos


2012/8/22 Peter Ent <pe...@adobe.com>

> Once you generate a bitmap(s), re-run the test suite (without
> -createImages) just to verify that it all works.
>
> Carol things some tests may have bugs which could lead to bad bitmap
> comparisons and perhaps the old and new images should be compared using a
> tool like ImageDiffAIR. If you run across a test suite with lots of tests
> failing bitmap comparisons, it may be that the tests have bugs.
>
> --peter
>
> On 8/22/12 6:56 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> >Thanks Peter,
> >
> >I finaly get "tests/SparkModules/" without fails by applying the
> >-createImages argument since I was only getting this output:
> >
> >[java] =====================================================
> >     [java] Failed:
> >     [java] =====================================================
> >     [java] SparkModules/Constraints/Properties/Module_tester002
> >MixedLayoutModule000 Failed CompareBitmap(body:step 1)  compare
> >returned[object BitmapData]
> >     [java]
> >     [java]
> >     [java] =====================================================
> >     [java]     Passes: 23
> >     [java]     Fails: 1
> >     [java] =====================================================
> >
> >Now it's ok:
> >
> >java] =====================================================
> >     [java]     Passes: 24
> >     [java]     Fails: 0
> >     [java] =====================================================
> >
> >
> >So other folder is ok :)
> >
> >
> >
> >2012/8/22 Peter Ent <pe...@adobe.com>
> >
> >> I will check for all the emails from Carlos tomorrow morning and get
> >>them
> >> all in at once. Since Carlos is being very active I'll try to keep up!
> >>
> >> Thanks, Carlos!
> >> --peter
> >>
> >> On 8/21/12 5:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
> >>
> >> >Hi Carlos,
> >> >
> >> >That's awesome.  Thanks for pitching in.  Peter, can you update the
> >>wiki?
> >> >
> >> >An interesting thing for you to do is before you quit working for the
> >>day,
> >> >run mini_run.sh -all and see what you get in the morning.  The failures
> >> >will
> >> >point to folders to work on.  Review this thread for what others are
> >> >working
> >> >on.  I've working on the entire spark folder, for example.
> >> >
> >> >-Alex
> >> >
> >> >
> >> >On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com>
> >> wrote:
> >> >
> >> >> Ops! I reboot Terminal and pass it again and all is ok with
> >> >>"GraphicTags"...
> >> >>
> >> >> [java] =====================================================
> >> >>      [java]     Passes: 3
> >> >>      [java]     Fails: 0
> >> >>      [java] =====================================================
> >> >>
> >> >>
> >> >> So It's needed at least two passes when a time out is thrown...I'm
> >> >> finishing to understand mustella ;)
> >> >>
> >> >>
> >> >>
> >> >> 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
> >> >>
> >> >>>
> >> >>> but "tests/GraphicTags/"
> >> >>>
> >> >>> reports
> >> >>> [java] =====================================================
> >> >>>      [java]     Passes: 2
> >> >>>      [java]     Fails: 1
> >> >>>      [java] =====================================================
> >> >>>
> >> >>> so I'll fix GraphicTags
> >> >>>
> >> >>>
> >> >>>
> >> >>> --
> >> >>> Carlos Rovira
> >> >>> Director de Tecnología
> >> >>> 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ón, 32
> >> >>> Planta 10, Puertas P-Q
> >> >>> 28020 Madrid
> >> >>>
> >> >>>
> >> >>
> >> >
> >> >--
> >> >Alex Harui
> >> >Flex SDK Team
> >> >Adobe Systems, Inc.
> >> >http://blogs.adobe.com/aharui
> >> >
> >>
> >>
> >
> >
> >--
> >Carlos Rovira
> >Director de Tecnología
> >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ón, 32
> >Planta 10, Puertas P-Q
> >28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Peter,

another folder tested without problems:  "tests/Modules/"

[java] =====================================================
     [java]     Passes: 173
     [java]     Fails: 0
     [java] =====================================================



2012/8/22 Carlos Rovira <ca...@codeoscopic.com>

> Thanks Peter,
>
> I finaly get "tests/SparkModules/" without fails by applying the
> -createImages argument since I was only getting this output:
>
> [java] =====================================================
>      [java] Failed:
>      [java] =====================================================
>      [java] SparkModules/Constraints/Properties/Module_tester002
> MixedLayoutModule000 Failed CompareBitmap(body:step 1)  compare
> returned[object BitmapData]
>      [java]
>      [java]
>      [java] =====================================================
>      [java]     Passes: 23
>      [java]     Fails: 1
>      [java] =====================================================
>
> Now it's ok:
>
> java] =====================================================
>      [java]     Passes: 24
>      [java]     Fails: 0
>      [java] =====================================================
>
>
> So other folder is ok :)
>
>
>
> 2012/8/22 Peter Ent <pe...@adobe.com>
>
>> I will check for all the emails from Carlos tomorrow morning and get them
>> all in at once. Since Carlos is being very active I'll try to keep up!
>>
>> Thanks, Carlos!
>> --peter
>>
>> On 8/21/12 5:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>> >Hi Carlos,
>> >
>> >That's awesome.  Thanks for pitching in.  Peter, can you update the wiki?
>> >
>> >An interesting thing for you to do is before you quit working for the
>> day,
>> >run mini_run.sh -all and see what you get in the morning.  The failures
>> >will
>> >point to folders to work on.  Review this thread for what others are
>> >working
>> >on.  I've working on the entire spark folder, for example.
>> >
>> >-Alex
>> >
>> >
>> >On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com>
>> wrote:
>> >
>> >> Ops! I reboot Terminal and pass it again and all is ok with
>> >>"GraphicTags"...
>> >>
>> >> [java] =====================================================
>> >>      [java]     Passes: 3
>> >>      [java]     Fails: 0
>> >>      [java] =====================================================
>> >>
>> >>
>> >> So It's needed at least two passes when a time out is thrown...I'm
>> >> finishing to understand mustella ;)
>> >>
>> >>
>> >>
>> >> 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
>> >>
>> >>>
>> >>> but "tests/GraphicTags/"
>> >>>
>> >>> reports
>> >>> [java] =====================================================
>> >>>      [java]     Passes: 2
>> >>>      [java]     Fails: 1
>> >>>      [java] =====================================================
>> >>>
>> >>> so I'll fix GraphicTags
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>> Director de Tecnología
>> >>> 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ón, 32
>> >>> Planta 10, Puertas P-Q
>> >>> 28020 Madrid
>> >>>
>> >>>
>> >>
>> >
>> >--
>> >Alex Harui
>> >Flex SDK Team
>> >Adobe Systems, Inc.
>> >http://blogs.adobe.com/aharui
>> >
>>
>>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> 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ón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Once you generate a bitmap(s), re-run the test suite (without
-createImages) just to verify that it all works.

Carol things some tests may have bugs which could lead to bad bitmap
comparisons and perhaps the old and new images should be compared using a
tool like ImageDiffAIR. If you run across a test suite with lots of tests
failing bitmap comparisons, it may be that the tests have bugs.

--peter

On 8/22/12 6:56 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

>Thanks Peter,
>
>I finaly get "tests/SparkModules/" without fails by applying the
>-createImages argument since I was only getting this output:
>
>[java] =====================================================
>     [java] Failed:
>     [java] =====================================================
>     [java] SparkModules/Constraints/Properties/Module_tester002
>MixedLayoutModule000 Failed CompareBitmap(body:step 1)  compare
>returned[object BitmapData]
>     [java]
>     [java]
>     [java] =====================================================
>     [java]     Passes: 23
>     [java]     Fails: 1
>     [java] =====================================================
>
>Now it's ok:
>
>java] =====================================================
>     [java]     Passes: 24
>     [java]     Fails: 0
>     [java] =====================================================
>
>
>So other folder is ok :)
>
>
>
>2012/8/22 Peter Ent <pe...@adobe.com>
>
>> I will check for all the emails from Carlos tomorrow morning and get
>>them
>> all in at once. Since Carlos is being very active I'll try to keep up!
>>
>> Thanks, Carlos!
>> --peter
>>
>> On 8/21/12 5:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>>
>> >Hi Carlos,
>> >
>> >That's awesome.  Thanks for pitching in.  Peter, can you update the
>>wiki?
>> >
>> >An interesting thing for you to do is before you quit working for the
>>day,
>> >run mini_run.sh -all and see what you get in the morning.  The failures
>> >will
>> >point to folders to work on.  Review this thread for what others are
>> >working
>> >on.  I've working on the entire spark folder, for example.
>> >
>> >-Alex
>> >
>> >
>> >On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com>
>> wrote:
>> >
>> >> Ops! I reboot Terminal and pass it again and all is ok with
>> >>"GraphicTags"...
>> >>
>> >> [java] =====================================================
>> >>      [java]     Passes: 3
>> >>      [java]     Fails: 0
>> >>      [java] =====================================================
>> >>
>> >>
>> >> So It's needed at least two passes when a time out is thrown...I'm
>> >> finishing to understand mustella ;)
>> >>
>> >>
>> >>
>> >> 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
>> >>
>> >>>
>> >>> but "tests/GraphicTags/"
>> >>>
>> >>> reports
>> >>> [java] =====================================================
>> >>>      [java]     Passes: 2
>> >>>      [java]     Fails: 1
>> >>>      [java] =====================================================
>> >>>
>> >>> so I'll fix GraphicTags
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>> Director de Tecnología
>> >>> 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ón, 32
>> >>> Planta 10, Puertas P-Q
>> >>> 28020 Madrid
>> >>>
>> >>>
>> >>
>> >
>> >--
>> >Alex Harui
>> >Flex SDK Team
>> >Adobe Systems, Inc.
>> >http://blogs.adobe.com/aharui
>> >
>>
>>
>
>
>-- 
>Carlos Rovira
>Director de Tecnología
>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ón, 32
>Planta 10, Puertas P-Q
>28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Thanks Peter,

I finaly get "tests/SparkModules/" without fails by applying the
-createImages argument since I was only getting this output:

[java] =====================================================
     [java] Failed:
     [java] =====================================================
     [java] SparkModules/Constraints/Properties/Module_tester002
MixedLayoutModule000 Failed CompareBitmap(body:step 1)  compare
returned[object BitmapData]
     [java]
     [java]
     [java] =====================================================
     [java]     Passes: 23
     [java]     Fails: 1
     [java] =====================================================

Now it's ok:

java] =====================================================
     [java]     Passes: 24
     [java]     Fails: 0
     [java] =====================================================


So other folder is ok :)



2012/8/22 Peter Ent <pe...@adobe.com>

> I will check for all the emails from Carlos tomorrow morning and get them
> all in at once. Since Carlos is being very active I'll try to keep up!
>
> Thanks, Carlos!
> --peter
>
> On 8/21/12 5:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
> >Hi Carlos,
> >
> >That's awesome.  Thanks for pitching in.  Peter, can you update the wiki?
> >
> >An interesting thing for you to do is before you quit working for the day,
> >run mini_run.sh -all and see what you get in the morning.  The failures
> >will
> >point to folders to work on.  Review this thread for what others are
> >working
> >on.  I've working on the entire spark folder, for example.
> >
> >-Alex
> >
> >
> >On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com>
> wrote:
> >
> >> Ops! I reboot Terminal and pass it again and all is ok with
> >>"GraphicTags"...
> >>
> >> [java] =====================================================
> >>      [java]     Passes: 3
> >>      [java]     Fails: 0
> >>      [java] =====================================================
> >>
> >>
> >> So It's needed at least two passes when a time out is thrown...I'm
> >> finishing to understand mustella ;)
> >>
> >>
> >>
> >> 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
> >>
> >>>
> >>> but "tests/GraphicTags/"
> >>>
> >>> reports
> >>> [java] =====================================================
> >>>      [java]     Passes: 2
> >>>      [java]     Fails: 1
> >>>      [java] =====================================================
> >>>
> >>> so I'll fix GraphicTags
> >>>
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> Director de Tecnología
> >>> 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ón, 32
> >>> Planta 10, Puertas P-Q
> >>> 28020 Madrid
> >>>
> >>>
> >>
> >
> >--
> >Alex Harui
> >Flex SDK Team
> >Adobe Systems, Inc.
> >http://blogs.adobe.com/aharui
> >
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Please use -createImages to generate baselines.  There can be faulty tests
where createImages produces a different image than at compare time.  We want
to use a consistent technique so we know how things get generated.

It should be rare for a baseline to be missing.  I believe you've said
you've been deleting them so there's a chance you are causing a problem by
doing that.  -createImages always overwrites current images and SVN won't
check them in unless it sees an actual difference.


On 8/23/12 1:29 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

> Hi Alex,
> 
> for this kind of message: "Failed CompareBitmap(body:step 3)  Baseline
> image could not be read.  Created image file as a .bad.png."
> 
> I'm renaming the created image .bad.png to the expected image to pass. The
> problem here is that there's no image, so I think the one created could be
> valid.
> 
> If some of the things I post here is not right let me know...
> 
> 2012/8/23 Alex Harui <ah...@adobe.com>
> 
>> 
>> 
>> 
>> On 8/23/12 9:29 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>> 
>>> Hi Alex,
>>> 
>>> 
>>> 2012/8/23 Alex Harui <ah...@adobe.com>
>>> 
>>>> 
>>>> I would use the ImageDiffAir tool to figure out what is different, then
>>>> examine the test to determine which image is the right one.
>>>> 
>>>> 
>>> The screen shot is from ImageDiffAir tool.
>> Yes, you can use the getPixel button and/or the pixel reading checkbox to
>> determine the pixel values at certain coordinates to determine in exact
>> detail the differences.
>>> 
>>> 
>>> 
>>>> If the red square asset got changed and is smaller then maybe the
>> baseline
>>>> wasn't refreshed after the asset changed.
>>>> 
>>> 
>>> I tried more than one time and remove the images to be generated again,
>> so
>>> I think there's no much to do there
>> I thought you'd already generated new baselines so it was making me think
>> that the test was unstable.  If that's not the case, then you're probably
>> ok
>> with just cutting a new one.
>>> 
>>> 
>>>> 
>>>> It could also be differences in rendering between platforms and machines
>>>> and
>>>> then we'll have to decide to exclude it or find a way to fix it.
>>>> 
>>>> 
>>> I think this is what is happening since from the capture I sent not only
>>> red square is different, "Name" text report changes too.
>> Yes, but the position of Name might be dependent on red square size.
>>> 
>>> As I'm new to mustella and already not have too much experience I'd like
>>> that someone point me how to proceed with this one.
>>> 
>> If the new baseline seems stable (a second run shows no differences) then
>> just check it in for now.  If there is a platform/machine difference we'll
>> find those as others run these tests and then try to figure out how to
>> stablize the test.
>> 
>> It gets trickier for tests of effects because timing can affect the
>> rendering, but most tests don't have moving parts so just getting the
>> folder
>> to run with zero failures on your machine is good enough for now.
>> 
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Alex,

for this kind of message: "Failed CompareBitmap(body:step 3)  Baseline
image could not be read.  Created image file as a .bad.png."

I'm renaming the created image .bad.png to the expected image to pass. The
problem here is that there's no image, so I think the one created could be
valid.

If some of the things I post here is not right let me know...

2012/8/23 Alex Harui <ah...@adobe.com>

>
>
>
> On 8/23/12 9:29 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> > Hi Alex,
> >
> >
> > 2012/8/23 Alex Harui <ah...@adobe.com>
> >
> >>
> >> I would use the ImageDiffAir tool to figure out what is different, then
> >> examine the test to determine which image is the right one.
> >>
> >>
> > The screen shot is from ImageDiffAir tool.
> Yes, you can use the getPixel button and/or the pixel reading checkbox to
> determine the pixel values at certain coordinates to determine in exact
> detail the differences.
> >
> >
> >
> >> If the red square asset got changed and is smaller then maybe the
> baseline
> >> wasn't refreshed after the asset changed.
> >>
> >
> > I tried more than one time and remove the images to be generated again,
> so
> > I think there's no much to do there
> I thought you'd already generated new baselines so it was making me think
> that the test was unstable.  If that's not the case, then you're probably
> ok
> with just cutting a new one.
> >
> >
> >>
> >> It could also be differences in rendering between platforms and machines
> >> and
> >> then we'll have to decide to exclude it or find a way to fix it.
> >>
> >>
> > I think this is what is happening since from the capture I sent not only
> > red square is different, "Name" text report changes too.
> Yes, but the position of Name might be dependent on red square size.
> >
> > As I'm new to mustella and already not have too much experience I'd like
> > that someone point me how to proceed with this one.
> >
> If the new baseline seems stable (a second run shows no differences) then
> just check it in for now.  If there is a platform/machine difference we'll
> find those as others run these tests and then try to figure out how to
> stablize the test.
>
> It gets trickier for tests of effects because timing can affect the
> rendering, but most tests don't have moving parts so just getting the
> folder
> to run with zero failures on your machine is good enough for now.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/23/12 9:29 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

> Hi Alex,
> 
> 
> 2012/8/23 Alex Harui <ah...@adobe.com>
> 
>> 
>> I would use the ImageDiffAir tool to figure out what is different, then
>> examine the test to determine which image is the right one.
>> 
>> 
> The screen shot is from ImageDiffAir tool.
Yes, you can use the getPixel button and/or the pixel reading checkbox to
determine the pixel values at certain coordinates to determine in exact
detail the differences.
> 
> 
> 
>> If the red square asset got changed and is smaller then maybe the baseline
>> wasn't refreshed after the asset changed.
>> 
> 
> I tried more than one time and remove the images to be generated again, so
> I think there's no much to do there
I thought you'd already generated new baselines so it was making me think
that the test was unstable.  If that's not the case, then you're probably ok
with just cutting a new one.
> 
> 
>> 
>> It could also be differences in rendering between platforms and machines
>> and
>> then we'll have to decide to exclude it or find a way to fix it.
>> 
>> 
> I think this is what is happening since from the capture I sent not only
> red square is different, "Name" text report changes too.
Yes, but the position of Name might be dependent on red square size.
> 
> As I'm new to mustella and already not have too much experience I'd like
> that someone point me how to proceed with this one.
> 
If the new baseline seems stable (a second run shows no differences) then
just check it in for now.  If there is a platform/machine difference we'll
find those as others run these tests and then try to figure out how to
stablize the test.

It gets trickier for tests of effects because timing can affect the
rendering, but most tests don't have moving parts so just getting the folder
to run with zero failures on your machine is good enough for now.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Alex,


2012/8/23 Alex Harui <ah...@adobe.com>

>
> I would use the ImageDiffAir tool to figure out what is different, then
> examine the test to determine which image is the right one.
>
>
The screen shot is from ImageDiffAir tool.



> If the red square asset got changed and is smaller then maybe the baseline
> wasn't refreshed after the asset changed.
>

I tried more than one time and remove the images to be generated again, so
I think there's no much to do there


>
> It could also be differences in rendering between platforms and machines
> and
> then we'll have to decide to exclude it or find a way to fix it.
>
>
I think this is what is happening since from the capture I sent not only
red square is different, "Name" text report changes too.

As I'm new to mustella and already not have too much experience I'd like
that someone point me how to proceed with this one.



> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

On 8/23/12 9:06 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

> Hi Alex,
> 
> this is the capture:
> 
> https://dl.dropbox.com/u/8496144/img_compare.png
> 
> thanks
> 
> C.

I would use the ImageDiffAir tool to figure out what is different, then
examine the test to determine which image is the right one.

If the red square asset got changed and is smaller then maybe the baseline
wasn't refreshed after the asset changed.

It could also be differences in rendering between platforms and machines and
then we'll have to decide to exclude it or find a way to fix it.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi Alex,

this is the capture:

https://dl.dropbox.com/u/8496144/img_compare.png

thanks

C.

2012/8/23 Alex Harui <ah...@adobe.com>

> I don’t think the attachments came through.
>
>
> On 8/23/12 8:11 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> Hi,
>
> how could we do when images differ like in the attached screenshot?
>
> The created image differs from the one that is rendered what is really
> weird...
>
>
> 2012/8/23 Peter Ent <pe...@adobe.com>
> I tried something like that, but there are options like: -source-path=
> with a hyphen in the option and a couple that begin with double hyphens. I
> started to switch over to String.split(" -") to break apart on the
> space+dash but then ran into this mysterious problem of mxmlc not liking
> the arguments it was given, even though, as far as I can tell, it was
> getting the same ones in the same order. Obviously that wasn't the case,
> but had trouble tracking it down, so it is on hold for now while we get
> the tests to run, unless someone else wants to take a stab at it.
>
> --peter
>
> On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
> wrote:
>
> >I'm not sure what Mustella is written in, but would something generic
> >like this work?
> >
> >If a string needs to be turned into an array then maybe... Use the "-" as
> >the first delimiter to break apart the options and use a temp array. Then
> >use the "=" to break out the names from the values.
> >
> >Keeping two arrays with the same number of elements.  One array stores
> >the argument name and the second argument value.
> >
> >//Declare arrays/string
> >string [] saNames = {"Option1", "Option2", "Option3"};
> >string [] saValues = {"My value with spaces", "test2", "test 3"};
> >string sCombinedOptions = "";
> >
> >//Loop through all elements in arrays
> >for (;;)
> >{
> >   //Combine names / values.
> >   sCombinedOptions += saNames[currentItem] + "=""" +
> >saValues[currentItem] + """ ";
> >}
> >
> >
> >//Add the command line and options.
> >"path\mxmlc.exe" + " " + sCombinedOptions;
> >
> >
> >-----Original Message-----
> >From: Peter Ent [mailto:pent@adobe.com]
> >Sent: Thursday, August 23, 2012 9:33
> >To: flex-dev@incubator.apache.org
> >Subject: Re: Getting Mustella to work.
> >
> >That ought to work, but does not. The Mustella code pieces together a
> >large string with all of the options on it, then turns the string into a
> >String[] by using space as the delimiter. Thus
> >
> >-source-path="C:\Program Files\Common Files\Microsoft
> >Shared\MSInfo\MSInfo32.exe"
> >
> >turns into
> >[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
> >Shared\MSInfo\MSInfo32.exe"
> >
> >And it does this several times (turning the array into a string,
> >inserting other args, back to an array) to build up the argument list.
> >Ultimately, the array of options is passed over to mxmlc to execute, so
> >it does need to turn into an array of options. I was working on putting
> >everything into an ArrayList but more and more code needed to change and
> >then I was getting errors from mxmlc saying parameters were being mixed
> >which I didn't understand since it was getting the same parameters in the
> >same order.
> >
> >So I have to re-think the approach.
> >
> >--peter
> >
> >On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
> >wrote:
> >
> >>I know this may sound silly, but windows deals with the spaces in path
> >>using quotes around the whole path.  Is there something similar with
> >>Mustella?
> >>
> >>So a windows command prompt example, I could do something like the
> >>following...
> >>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
> >>
> >>
> >>Whereas the old non spaced dos style naming convention would do this
> >>without quotes..
> >>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
> >>
> >>
> >>r/s
> >>-Mark
> >>
> >>-----Original Message-----
> >>From: Peter Ent [mailto:pent@adobe.com]
> >>Sent: Wednesday, August 22, 2012 9:20
> >>To: flex-dev@incubator.apache.org
> >>Subject: Re: Getting Mustella to work.
> >>
> >>I have not have luck solving the problem. It is much trickier than I
> >>anticipated. I am going to jump back into getting more tests to run and
> >>think more about the problem. Operating systems have allowed spaces in
> >>file names for many, many years and you'd think would be an easily
> >>solvable problem (or not even a problem at all).
> >>
> >>--peter
> >>
> >>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> >>
> >>>Hi,
> >>>
> >>>If the space path issue was fixed you have more to add. Any luck with
> >>>that yet?
> >>>
> >>>Justin
> >>
> >
>
>
>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>



-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

I don’t think the attachments came through.


On 8/23/12 8:11 AM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

Hi,

how could we do when images differ like in the attached screenshot?

The created image differs from the one that is rendered what is really weird...


2012/8/23 Peter Ent <pe...@adobe.com>
I tried something like that, but there are options like: -source-path=
with a hyphen in the option and a couple that begin with double hyphens. I
started to switch over to String.split(" -") to break apart on the
space+dash but then ran into this mysterious problem of mxmlc not liking
the arguments it was given, even though, as far as I can tell, it was
getting the same ones in the same order. Obviously that wasn't the case,
but had trouble tracking it down, so it is on hold for now while we get
the tests to run, unless someone else wants to take a stab at it.

--peter

On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
wrote:

>I'm not sure what Mustella is written in, but would something generic
>like this work?
>
>If a string needs to be turned into an array then maybe... Use the "-" as
>the first delimiter to break apart the options and use a temp array. Then
>use the "=" to break out the names from the values.
>
>Keeping two arrays with the same number of elements.  One array stores
>the argument name and the second argument value.
>
>//Declare arrays/string
>string [] saNames = {"Option1", "Option2", "Option3"};
>string [] saValues = {"My value with spaces", "test2", "test 3"};
>string sCombinedOptions = "";
>
>//Loop through all elements in arrays
>for (;;)
>{
>   //Combine names / values.
>   sCombinedOptions += saNames[currentItem] + "=""" +
>saValues[currentItem] + """ ";
>}
>
>
>//Add the command line and options.
>"path\mxmlc.exe" + " " + sCombinedOptions;
>
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 9:33
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>That ought to work, but does not. The Mustella code pieces together a
>large string with all of the options on it, then turns the string into a
>String[] by using space as the delimiter. Thus
>
>-source-path="C:\Program Files\Common Files\Microsoft
>Shared\MSInfo\MSInfo32.exe"
>
>turns into
>[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>Shared\MSInfo\MSInfo32.exe"
>
>And it does this several times (turning the array into a string,
>inserting other args, back to an array) to build up the argument list.
>Ultimately, the array of options is passed over to mxmlc to execute, so
>it does need to turn into an array of options. I was working on putting
>everything into an ArrayList but more and more code needed to change and
>then I was getting errors from mxmlc saying parameters were being mixed
>which I didn't understand since it was getting the same parameters in the
>same order.
>
>So I have to re-think the approach.
>
>--peter
>
>On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>I know this may sound silly, but windows deals with the spaces in path
>>using quotes around the whole path.  Is there something similar with
>>Mustella?
>>
>>So a windows command prompt example, I could do something like the
>>following...
>>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>
>>
>>Whereas the old non spaced dos style naming convention would do this
>>without quotes..
>>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>
>>
>>r/s
>>-Mark
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Wednesday, August 22, 2012 9:20
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>I have not have luck solving the problem. It is much trickier than I
>>anticipated. I am going to jump back into getting more tests to run and
>>think more about the problem. Operating systems have allowed spaces in
>>file names for many, many years and you'd think would be an easily
>>solvable problem (or not even a problem at all).
>>
>>--peter
>>
>>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>
>>>Hi,
>>>
>>>If the space path issue was fixed you have more to add. Any luck with
>>>that yet?
>>>
>>>Justin
>>
>




--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi,

how could we do when images differ like in the attached screenshot?

The created image differs from the one that is rendered what is really
weird...


2012/8/23 Peter Ent <pe...@adobe.com>

> I tried something like that, but there are options like: -source-path=
> with a hyphen in the option and a couple that begin with double hyphens. I
> started to switch over to String.split(" -") to break apart on the
> space+dash but then ran into this mysterious problem of mxmlc not liking
> the arguments it was given, even though, as far as I can tell, it was
> getting the same ones in the same order. Obviously that wasn't the case,
> but had trouble tracking it down, so it is on hold for now while we get
> the tests to run, unless someone else wants to take a stab at it.
>
> --peter
>
> On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
> wrote:
>
> >I'm not sure what Mustella is written in, but would something generic
> >like this work?
> >
> >If a string needs to be turned into an array then maybe... Use the "-" as
> >the first delimiter to break apart the options and use a temp array. Then
> >use the "=" to break out the names from the values.
> >
> >Keeping two arrays with the same number of elements.  One array stores
> >the argument name and the second argument value.
> >
> >//Declare arrays/string
> >string [] saNames = {"Option1", "Option2", "Option3"};
> >string [] saValues = {"My value with spaces", "test2", "test 3"};
> >string sCombinedOptions = "";
> >
> >//Loop through all elements in arrays
> >for (;;)
> >{
> >   //Combine names / values.
> >   sCombinedOptions += saNames[currentItem] + "=""" +
> >saValues[currentItem] + """ ";
> >}
> >
> >
> >//Add the command line and options.
> >"path\mxmlc.exe" + " " + sCombinedOptions;
> >
> >
> >-----Original Message-----
> >From: Peter Ent [mailto:pent@adobe.com]
> >Sent: Thursday, August 23, 2012 9:33
> >To: flex-dev@incubator.apache.org
> >Subject: Re: Getting Mustella to work.
> >
> >That ought to work, but does not. The Mustella code pieces together a
> >large string with all of the options on it, then turns the string into a
> >String[] by using space as the delimiter. Thus
> >
> >-source-path="C:\Program Files\Common Files\Microsoft
> >Shared\MSInfo\MSInfo32.exe"
> >
> >turns into
> >[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
> >Shared\MSInfo\MSInfo32.exe"
> >
> >And it does this several times (turning the array into a string,
> >inserting other args, back to an array) to build up the argument list.
> >Ultimately, the array of options is passed over to mxmlc to execute, so
> >it does need to turn into an array of options. I was working on putting
> >everything into an ArrayList but more and more code needed to change and
> >then I was getting errors from mxmlc saying parameters were being mixed
> >which I didn't understand since it was getting the same parameters in the
> >same order.
> >
> >So I have to re-think the approach.
> >
> >--peter
> >
> >On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
> >wrote:
> >
> >>I know this may sound silly, but windows deals with the spaces in path
> >>using quotes around the whole path.  Is there something similar with
> >>Mustella?
> >>
> >>So a windows command prompt example, I could do something like the
> >>following...
> >>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
> >>
> >>
> >>Whereas the old non spaced dos style naming convention would do this
> >>without quotes..
> >>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
> >>
> >>
> >>r/s
> >>-Mark
> >>
> >>-----Original Message-----
> >>From: Peter Ent [mailto:pent@adobe.com]
> >>Sent: Wednesday, August 22, 2012 9:20
> >>To: flex-dev@incubator.apache.org
> >>Subject: Re: Getting Mustella to work.
> >>
> >>I have not have luck solving the problem. It is much trickier than I
> >>anticipated. I am going to jump back into getting more tests to run and
> >>think more about the problem. Operating systems have allowed spaces in
> >>file names for many, many years and you'd think would be an easily
> >>solvable problem (or not even a problem at all).
> >>
> >>--peter
> >>
> >>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> >>
> >>>Hi,
> >>>
> >>>If the space path issue was fixed you have more to add. Any luck with
> >>>that yet?
> >>>
> >>>Justin
> >>
> >
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

RE: Getting Mustella to work.

Posted by Kessler CTR Mark J <ma...@usmc.mil>.

   NP take your time.  The test mxml file was a quick throw together.  The source up top is the test data you gave me.  The run button processes it through the class and shows the results. Then it runs half a dozen functions and shows the results again.  You should be able to change out the source text and rerun it to find any problems.  

I didn't test it against CR if there are any by default, I could just add a replace for them in the class before it processes it.




-----Original Message-----
From: Peter Ent [mailto:pent@adobe.com] 
Sent: Monday, August 27, 2012 14:13
To: flex-dev@incubator.apache.org
Subject: Re: Getting Mustella to work.

I'll try and look at it today. I'm in the middle of figuring out why some bitmaps aren't showing up in the tests.

Thanks!
--peter

On 8/27/12 2:09 PM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:

>Gonna play a game of see if the exchange server strips my attachments...
>-----
>Ok I've worked on it a bit here and there.  I rolled it up to a class 
>to make it easier to implement. By far the regex was the longest pieces.
>For those who want to know, the Regex in actioscript is the same flavor 
>as javascript.  Can use this website to fiddle with it without having 
>to complile http://jsfiddle.net/
>
>
>
>//Create an instance of the class.
>var oArgs:ArgManage = new ArgManage();
>
>//Toss in the argument string.
>oArgs.StringArugments = sMyExistingArgumentsString;
>
>
>//Run any of the stock functions to add/update/remove arguments.
>//The AddStaticArg is for strange things like "-debug" having no value 
>assignment.
>public function AddArg(sName:String, sValue:String):void; public 
>function AddStaticArg(sName:String):void; public function 
>RemoveArg(sName:String):void; public function UpdateArg(sName:String, 
>sValue:String):Boolean;
>
>//Get your new combined string back out.
>sMyExistingArgumentsString = oArgs.StringArugments;
>
>
>Possible things left to do:
>-Change arraylists to vectors.
>-Take a little redundancy out of the code.
>-Change variable/function naming convention to some actionscript standard.
>-
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Monday, August 27, 2012 13:30
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>Sure, I can work it in and give it a try.
>
>Thanks.
>--peter
>
>On 8/27/12 1:26 PM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>Peter, did you want to test the argument handler test code today?
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Thursday, August 23, 2012 11:56
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>Certainly appreciate the help. Here's a typical one when running
>>Mustella:
>>
>>-debug -define=CONFIG::skaha,false
>>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFon
>>t
>>Man
>>a
>>ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>>-source-path=/Users/pent/apache/flex/mustella/Assets
>>-includes=ExcludeFileLocation -includes=SetShowRTE 
>>-includes=SaveBitmapFailures 
>>-includes=datagrid_properties_lockedColumnCount_mxml
>>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGri
>>d
>>/Da
>>t
>>aGrid_SparkSkin/Properties --allow-source-path-overlap=true 
>>-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>>-source-path=/Users/pent/apache/flex/mustella/../frameworks/
>>-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>>
>>Try changing my path, "/Users/pent/apache/" to something like 
>>"/Users/pent/apache with spaces/" to get a better example.
>>
>>What happens in the code is that groups of these options may be coming 
>>from the environment, so you might find "-debug 
>>-define=CONFIG::skaha,false" being added as a single entity. Then code 
>>turns what it has at the moment into a String[] and passes that to 
>>another function that might add more arguments. If that function does, 
>>it will turn the String[] back into a String, add the arguments, then 
>>turn it back into String[].
>>
>>But if you can make something that will convert the args into an 
>>acceptable String[] it would be super-helpful.
>>
>>Thanks!
>>--peter

RE: Getting Mustella to work.

Posted by Kessler CTR Mark J <ma...@usmc.mil>.

Updated to use vectors, changed some naming convention, reduced a bit of redundant code, updated the example to better display the internal arguments and allow minor modification.

Attachments have an additional extension of .txt just to keep them from getting stripped.


//
//  public properties
//

//Length of the arrays
length [get]

//Gets or sets all the arguments in a single string.
stringArguments [get, set]


//
//  public methods
//

//Adds a new argument and value or a new argument with no assignment.
public function add(sName:String, sValue:String = null):void

//Remove an argument by its name.
public function remove(sName:String):void

//Update an argument by its name.
public function update(sName:String, sValue:String = null):Boolean


//Return the argument name at the given index.
public function getNameAt(nIndex:int):String

//Return the argument value at the given index.
public function getValueAt(nIndex:int):String

//Find the index of an argument by its name
public function indexOf(sName:String):int

//Remove an argument by its index.
public function removeAt(nIndex:int):void

//Updates the argument value at the given index.
public function setValueAt(nIndex:int, sValue:String = null):Boolean



-----Original Message-----
From: Kessler CTR Mark J [mailto:mark.kessler.ctr@usmc.mil] 
Sent: Monday, August 27, 2012 14:12
To: flex-dev@incubator.apache.org
Subject: RE: Getting Mustella to work.

I'll try the attachments again with txt extensions

>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 11:56
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>Certainly appreciate the help. Here's a typical one when running Mustella:
>
>-debug -define=CONFIG::skaha,false
>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFont
>Man
>a
>ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>-source-path=/Users/pent/apache/flex/mustella/Assets
>-includes=ExcludeFileLocation -includes=SetShowRTE 
>-includes=SaveBitmapFailures 
>-includes=datagrid_properties_lockedColumnCount_mxml
>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid
>/Da
>t
>aGrid_SparkSkin/Properties --allow-source-path-overlap=true 
>-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>-source-path=/Users/pent/apache/flex/mustella/../frameworks/
>-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>
>Try changing my path, "/Users/pent/apache/" to something like 
>"/Users/pent/apache with spaces/" to get a better example.
>
>What happens in the code is that groups of these options may be coming 
>from the environment, so you might find "-debug 
>-define=CONFIG::skaha,false" being added as a single entity. Then code 
>turns what it has at the moment into a String[] and passes that to 
>another function that might add more arguments. If that function does, 
>it will turn the String[] back into a String, add the arguments, then 
>turn it back into String[].
>
>But if you can make something that will convert the args into an 
>acceptable String[] it would be super-helpful.
>
>Thanks!
>--peter

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

These came through
--peter

On 8/27/12 2:11 PM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:

>I'll try the attachments again with txt extensions
>
>-----Original Message-----
>From: Kessler CTR Mark J [mailto:mark.kessler.ctr@usmc.mil]
>Sent: Monday, August 27, 2012 14:09
>To: flex-dev@incubator.apache.org
>Subject: RE: Getting Mustella to work.
>
>Gonna play a game of see if the exchange server strips my attachments...
>-----
>Ok I've worked on it a bit here and there.  I rolled it up to a class to
>make it easier to implement. By far the regex was the longest pieces.
>For those who want to know, the Regex in actioscript is the same flavor
>as javascript.  Can use this website to fiddle with it without having to
>complile http://jsfiddle.net/
>
>
>
>//Create an instance of the class.
>var oArgs:ArgManage = new ArgManage();
>
>//Toss in the argument string.
>oArgs.StringArugments = sMyExistingArgumentsString;
>
>
>//Run any of the stock functions to add/update/remove arguments.
>//The AddStaticArg is for strange things like "-debug" having no value
>assignment.
>public function AddArg(sName:String, sValue:String):void; public function
>AddStaticArg(sName:String):void; public function
>RemoveArg(sName:String):void; public function UpdateArg(sName:String,
>sValue:String):Boolean;
>
>//Get your new combined string back out.
>sMyExistingArgumentsString = oArgs.StringArugments;
>
>
>Possible things left to do:
>-Change arraylists to vectors.
>-Take a little redundancy out of the code.
>-Change variable/function naming convention to some actionscript standard.
>-
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Monday, August 27, 2012 13:30
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>Sure, I can work it in and give it a try.
>
>Thanks.
>--peter
>
>On 8/27/12 1:26 PM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>Peter, did you want to test the argument handler test code today?
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Thursday, August 23, 2012 11:56
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>Certainly appreciate the help. Here's a typical one when running
>>Mustella:
>>
>>-debug -define=CONFIG::skaha,false
>>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFont
>>Man
>>a
>>ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>>-source-path=/Users/pent/apache/flex/mustella/Assets
>>-includes=ExcludeFileLocation -includes=SetShowRTE
>>-includes=SaveBitmapFailures
>>-includes=datagrid_properties_lockedColumnCount_mxml
>>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid
>>/Da
>>t
>>aGrid_SparkSkin/Properties --allow-source-path-overlap=true
>>-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>>-source-path=/Users/pent/apache/flex/mustella/../frameworks/
>>-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>>
>>Try changing my path, "/Users/pent/apache/" to something like
>>"/Users/pent/apache with spaces/" to get a better example.
>>
>>What happens in the code is that groups of these options may be coming
>>from the environment, so you might find "-debug
>>-define=CONFIG::skaha,false" being added as a single entity. Then code
>>turns what it has at the moment into a String[] and passes that to
>>another function that might add more arguments. If that function does,
>>it will turn the String[] back into a String, add the arguments, then
>>turn it back into String[].
>>
>>But if you can make something that will convert the args into an
>>acceptable String[] it would be super-helpful.
>>
>>Thanks!
>>--peter

RE: Getting Mustella to work.

Posted by Kessler CTR Mark J <ma...@usmc.mil>.

I'll try the attachments again with txt extensions

-----Original Message-----
From: Kessler CTR Mark J [mailto:mark.kessler.ctr@usmc.mil] 
Sent: Monday, August 27, 2012 14:09
To: flex-dev@incubator.apache.org
Subject: RE: Getting Mustella to work.

Gonna play a game of see if the exchange server strips my attachments...
-----
Ok I've worked on it a bit here and there.  I rolled it up to a class to make it easier to implement. By far the regex was the longest pieces.  For those who want to know, the Regex in actioscript is the same flavor as javascript.  Can use this website to fiddle with it without having to complile http://jsfiddle.net/



//Create an instance of the class.
var oArgs:ArgManage = new ArgManage();

//Toss in the argument string.
oArgs.StringArugments = sMyExistingArgumentsString;


//Run any of the stock functions to add/update/remove arguments.
//The AddStaticArg is for strange things like "-debug" having no value assignment.
public function AddArg(sName:String, sValue:String):void; public function AddStaticArg(sName:String):void; public function RemoveArg(sName:String):void; public function UpdateArg(sName:String, sValue:String):Boolean;

//Get your new combined string back out.
sMyExistingArgumentsString = oArgs.StringArugments;


Possible things left to do:
-Change arraylists to vectors.
-Take a little redundancy out of the code.
-Change variable/function naming convention to some actionscript standard.
-

-----Original Message-----
From: Peter Ent [mailto:pent@adobe.com]
Sent: Monday, August 27, 2012 13:30
To: flex-dev@incubator.apache.org
Subject: Re: Getting Mustella to work.

Sure, I can work it in and give it a try.

Thanks.
--peter

On 8/27/12 1:26 PM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:

>Peter, did you want to test the argument handler test code today?
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 11:56
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>Certainly appreciate the help. Here's a typical one when running Mustella:
>
>-debug -define=CONFIG::skaha,false
>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFont
>Man
>a
>ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>-source-path=/Users/pent/apache/flex/mustella/Assets
>-includes=ExcludeFileLocation -includes=SetShowRTE 
>-includes=SaveBitmapFailures 
>-includes=datagrid_properties_lockedColumnCount_mxml
>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid
>/Da
>t
>aGrid_SparkSkin/Properties --allow-source-path-overlap=true 
>-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>-source-path=/Users/pent/apache/flex/mustella/../frameworks/
>-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>
>Try changing my path, "/Users/pent/apache/" to something like 
>"/Users/pent/apache with spaces/" to get a better example.
>
>What happens in the code is that groups of these options may be coming 
>from the environment, so you might find "-debug 
>-define=CONFIG::skaha,false" being added as a single entity. Then code 
>turns what it has at the moment into a String[] and passes that to 
>another function that might add more arguments. If that function does, 
>it will turn the String[] back into a String, add the arguments, then 
>turn it back into String[].
>
>But if you can make something that will convert the args into an 
>acceptable String[] it would be super-helpful.
>
>Thanks!
>--peter

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I'll try and look at it today. I'm in the middle of figuring out why some
bitmaps aren't showing up in the tests.

Thanks!
--peter

On 8/27/12 2:09 PM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:

>Gonna play a game of see if the exchange server strips my attachments...
>-----
>Ok I've worked on it a bit here and there.  I rolled it up to a class to
>make it easier to implement. By far the regex was the longest pieces.
>For those who want to know, the Regex in actioscript is the same flavor
>as javascript.  Can use this website to fiddle with it without having to
>complile http://jsfiddle.net/
>
>
>
>//Create an instance of the class.
>var oArgs:ArgManage = new ArgManage();
>
>//Toss in the argument string.
>oArgs.StringArugments = sMyExistingArgumentsString;
>
>
>//Run any of the stock functions to add/update/remove arguments.
>//The AddStaticArg is for strange things like "-debug" having no value
>assignment.
>public function AddArg(sName:String, sValue:String):void;
>public function AddStaticArg(sName:String):void;
>public function RemoveArg(sName:String):void;
>public function UpdateArg(sName:String, sValue:String):Boolean;
>
>//Get your new combined string back out.
>sMyExistingArgumentsString = oArgs.StringArugments;
>
>
>Possible things left to do:
>-Change arraylists to vectors.
>-Take a little redundancy out of the code.
>-Change variable/function naming convention to some actionscript standard.
>-
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Monday, August 27, 2012 13:30
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>Sure, I can work it in and give it a try.
>
>Thanks.
>--peter
>
>On 8/27/12 1:26 PM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>Peter, did you want to test the argument handler test code today?
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Thursday, August 23, 2012 11:56
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>Certainly appreciate the help. Here's a typical one when running
>>Mustella:
>>
>>-debug -define=CONFIG::skaha,false
>>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFont
>>Man
>>a
>>ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>>-source-path=/Users/pent/apache/flex/mustella/Assets
>>-includes=ExcludeFileLocation -includes=SetShowRTE
>>-includes=SaveBitmapFailures
>>-includes=datagrid_properties_lockedColumnCount_mxml
>>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid
>>/Da
>>t
>>aGrid_SparkSkin/Properties --allow-source-path-overlap=true
>>-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>>-source-path=/Users/pent/apache/flex/mustella/../frameworks/
>>-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>>
>>Try changing my path, "/Users/pent/apache/" to something like
>>"/Users/pent/apache with spaces/" to get a better example.
>>
>>What happens in the code is that groups of these options may be coming
>>from the environment, so you might find "-debug
>>-define=CONFIG::skaha,false" being added as a single entity. Then code
>>turns what it has at the moment into a String[] and passes that to
>>another function that might add more arguments. If that function does,
>>it will turn the String[] back into a String, add the arguments, then
>>turn it back into String[].
>>
>>But if you can make something that will convert the args into an
>>acceptable String[] it would be super-helpful.
>>
>>Thanks!
>>--peter

RE: Getting Mustella to work.

Posted by Kessler CTR Mark J <ma...@usmc.mil>.

Gonna play a game of see if the exchange server strips my attachments...
-----
Ok I've worked on it a bit here and there.  I rolled it up to a class to make it easier to implement. By far the regex was the longest pieces.  For those who want to know, the Regex in actioscript is the same flavor as javascript.  Can use this website to fiddle with it without having to complile http://jsfiddle.net/



//Create an instance of the class.
var oArgs:ArgManage = new ArgManage();

//Toss in the argument string.
oArgs.StringArugments = sMyExistingArgumentsString;


//Run any of the stock functions to add/update/remove arguments.
//The AddStaticArg is for strange things like "-debug" having no value assignment.
public function AddArg(sName:String, sValue:String):void;
public function AddStaticArg(sName:String):void;
public function RemoveArg(sName:String):void;
public function UpdateArg(sName:String, sValue:String):Boolean;

//Get your new combined string back out.
sMyExistingArgumentsString = oArgs.StringArugments;


Possible things left to do:
-Change arraylists to vectors.
-Take a little redundancy out of the code.
-Change variable/function naming convention to some actionscript standard.
-

-----Original Message-----
From: Peter Ent [mailto:pent@adobe.com] 
Sent: Monday, August 27, 2012 13:30
To: flex-dev@incubator.apache.org
Subject: Re: Getting Mustella to work.

Sure, I can work it in and give it a try.

Thanks.
--peter

On 8/27/12 1:26 PM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:

>Peter, did you want to test the argument handler test code today?
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 11:56
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>Certainly appreciate the help. Here's a typical one when running Mustella:
>
>-debug -define=CONFIG::skaha,false
>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFont
>Man
>a
>ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>-source-path=/Users/pent/apache/flex/mustella/Assets
>-includes=ExcludeFileLocation -includes=SetShowRTE 
>-includes=SaveBitmapFailures 
>-includes=datagrid_properties_lockedColumnCount_mxml
>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid
>/Da
>t
>aGrid_SparkSkin/Properties --allow-source-path-overlap=true 
>-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>-source-path=/Users/pent/apache/flex/mustella/../frameworks/
>-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>
>Try changing my path, "/Users/pent/apache/" to something like 
>"/Users/pent/apache with spaces/" to get a better example.
>
>What happens in the code is that groups of these options may be coming 
>from the environment, so you might find "-debug 
>-define=CONFIG::skaha,false" being added as a single entity. Then code 
>turns what it has at the moment into a String[] and passes that to 
>another function that might add more arguments. If that function does, 
>it will turn the String[] back into a String, add the arguments, then 
>turn it back into String[].
>
>But if you can make something that will convert the args into an 
>acceptable String[] it would be super-helpful.
>
>Thanks!
>--peter

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Sure, I can work it in and give it a try.

Thanks.
--peter

On 8/27/12 1:26 PM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:

>Peter, did you want to test the argument handler test code today?
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 11:56
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>Certainly appreciate the help. Here's a typical one when running Mustella:
>
>-debug -define=CONFIG::skaha,false
>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFontMan
>a
>ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>-source-path=/Users/pent/apache/flex/mustella/Assets
>-includes=ExcludeFileLocation -includes=SetShowRTE
>-includes=SaveBitmapFailures
>-includes=datagrid_properties_lockedColumnCount_mxml
>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid/Da
>t
>aGrid_SparkSkin/Properties --allow-source-path-overlap=true
>-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>-source-path=/Users/pent/apache/flex/mustella/../frameworks/
>-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>
>Try changing my path, "/Users/pent/apache/" to something like
>"/Users/pent/apache with spaces/" to get a better example.
>
>What happens in the code is that groups of these options may be coming
>from the environment, so you might find "-debug
>-define=CONFIG::skaha,false" being added as a single entity. Then code
>turns what it has at the moment into a String[] and passes that to another
>function that might add more arguments. If that function does, it will
>turn the String[] back into a String, add the arguments, then turn it back
>into String[].  
>
>But if you can make something that will convert the args into an
>acceptable String[] it would be super-helpful.
>
>Thanks!
>--peter
>
>On 8/23/12 11:44 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>String.split(regexpattern)  can match pretty much anything.  Definitely
>>would be able to comeup with a pattern to match embedded dashes.
>>
>>I'll see if I can come up with something that can properly strip down a
>>completed command with arguments.  If you would give me a more complex
>>command line that would be great.  I can test against it.
>>
>>Currently my setup uses few command line arguments and instead adds to
>>the "-load-config+=mycustomconfig.xml"
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Thursday, August 23, 2012 10:52
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>I tried something like that, but there are options like: -source-path=
>>with a hyphen in the option and a couple that begin with double hyphens.
>>I started to switch over to String.split(" -") to break apart on the
>>space+dash but then ran into this mysterious problem of mxmlc not liking
>>the arguments it was given, even though, as far as I can tell, it was
>>getting the same ones in the same order. Obviously that wasn't the case,
>>but had trouble tracking it down, so it is on hold for now while we get
>>the tests to run, unless someone else wants to take a stab at it.
>>
>>--peter
>>
>>On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>wrote:
>>
>>>I'm not sure what Mustella is written in, but would something generic
>>>like this work?
>>>
>>>If a string needs to be turned into an array then maybe... Use the "-"
>>>as the first delimiter to break apart the options and use a temp array.
>>>Then use the "=" to break out the names from the values.
>>>
>>>Keeping two arrays with the same number of elements.  One array stores
>>>the argument name and the second argument value.
>>>
>>>//Declare arrays/string
>>>string [] saNames = {"Option1", "Option2", "Option3"}; string []
>>>saValues = {"My value with spaces", "test2", "test 3"}; string
>>>sCombinedOptions = "";
>>>
>>>//Loop through all elements in arrays
>>>for (;;)
>>>{
>>>   //Combine names / values.
>>>   sCombinedOptions += saNames[currentItem] + "=""" +
>>>saValues[currentItem] + """ "; }
>>>
>>>
>>>//Add the command line and options.
>>>"path\mxmlc.exe" + " " + sCombinedOptions;
>>>
>>>
>>>-----Original Message-----
>>>From: Peter Ent [mailto:pent@adobe.com]
>>>Sent: Thursday, August 23, 2012 9:33
>>>To: flex-dev@incubator.apache.org
>>>Subject: Re: Getting Mustella to work.
>>>
>>>That ought to work, but does not. The Mustella code pieces together a
>>>large string with all of the options on it, then turns the string into
>>>a String[] by using space as the delimiter. Thus
>>>
>>>-source-path="C:\Program Files\Common Files\Microsoft
>>>Shared\MSInfo\MSInfo32.exe"
>>>
>>>turns into
>>>[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>>>Shared\MSInfo\MSInfo32.exe"
>>>
>>>And it does this several times (turning the array into a string,
>>>inserting other args, back to an array) to build up the argument list.
>>>Ultimately, the array of options is passed over to mxmlc to execute, so
>>>it does need to turn into an array of options. I was working on putting
>>>everything into an ArrayList but more and more code needed to change
>>>and then I was getting errors from mxmlc saying parameters were being
>>>mixed which I didn't understand since it was getting the same
>>>parameters in the same order.
>>>
>>>So I have to re-think the approach.
>>>
>>>--peter
>>>
>>>On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>>wrote:
>>>
>>>>I know this may sound silly, but windows deals with the spaces in path
>>>>using quotes around the whole path.  Is there something similar with
>>>>Mustella?
>>>>
>>>>So a windows command prompt example, I could do something like the
>>>>following...
>>>>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>>>
>>>>
>>>>Whereas the old non spaced dos style naming convention would do this
>>>>without quotes..
>>>>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>>>
>>>>
>>>>r/s
>>>>-Mark
>>>>
>>>>-----Original Message-----
>>>>From: Peter Ent [mailto:pent@adobe.com]
>>>>Sent: Wednesday, August 22, 2012 9:20
>>>>To: flex-dev@incubator.apache.org
>>>>Subject: Re: Getting Mustella to work.
>>>>
>>>>I have not have luck solving the problem. It is much trickier than I
>>>>anticipated. I am going to jump back into getting more tests to run
>>>>and think more about the problem. Operating systems have allowed
>>>>spaces in file names for many, many years and you'd think would be an
>>>>easily solvable problem (or not even a problem at all).
>>>>
>>>>--peter
>>>>
>>>>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>>>
>>>>>Hi,
>>>>>
>>>>>If the space path issue was fixed you have more to add. Any luck with
>>>>>that yet?
>>>>>
>>>>>Justin
>>>>
>>>
>>
>

RE: Getting Mustella to work.

Posted by Kessler CTR Mark J <ma...@usmc.mil>.

Peter, did you want to test the argument handler test code today?

-----Original Message-----
From: Peter Ent [mailto:pent@adobe.com] 
Sent: Thursday, August 23, 2012 11:56
To: flex-dev@incubator.apache.org
Subject: Re: Getting Mustella to work.

Certainly appreciate the help. Here's a typical one when running Mustella:

-debug -define=CONFIG::skaha,false
-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFontMana
ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
-source-path=/Users/pent/apache/flex/mustella/Assets
-includes=ExcludeFileLocation -includes=SetShowRTE
-includes=SaveBitmapFailures
-includes=datagrid_properties_lockedColumnCount_mxml
-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid/Dat
aGrid_SparkSkin/Properties --allow-source-path-overlap=true
-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
-source-path=/Users/pent/apache/flex/mustella/../frameworks/
-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella

Try changing my path, "/Users/pent/apache/" to something like
"/Users/pent/apache with spaces/" to get a better example.

What happens in the code is that groups of these options may be coming
from the environment, so you might find "-debug
-define=CONFIG::skaha,false" being added as a single entity. Then code
turns what it has at the moment into a String[] and passes that to another
function that might add more arguments. If that function does, it will
turn the String[] back into a String, add the arguments, then turn it back
into String[].  

But if you can make something that will convert the args into an
acceptable String[] it would be super-helpful.

Thanks!
--peter

On 8/23/12 11:44 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
wrote:

>String.split(regexpattern)  can match pretty much anything.  Definitely
>would be able to comeup with a pattern to match embedded dashes.
>
>I'll see if I can come up with something that can properly strip down a
>completed command with arguments.  If you would give me a more complex
>command line that would be great.  I can test against it.
>
>Currently my setup uses few command line arguments and instead adds to
>the "-load-config+=mycustomconfig.xml"
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 10:52
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>I tried something like that, but there are options like: -source-path=
>with a hyphen in the option and a couple that begin with double hyphens.
>I started to switch over to String.split(" -") to break apart on the
>space+dash but then ran into this mysterious problem of mxmlc not liking
>the arguments it was given, even though, as far as I can tell, it was
>getting the same ones in the same order. Obviously that wasn't the case,
>but had trouble tracking it down, so it is on hold for now while we get
>the tests to run, unless someone else wants to take a stab at it.
>
>--peter
>
>On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>I'm not sure what Mustella is written in, but would something generic
>>like this work?
>>
>>If a string needs to be turned into an array then maybe... Use the "-"
>>as the first delimiter to break apart the options and use a temp array.
>>Then use the "=" to break out the names from the values.
>>
>>Keeping two arrays with the same number of elements.  One array stores
>>the argument name and the second argument value.
>>
>>//Declare arrays/string
>>string [] saNames = {"Option1", "Option2", "Option3"}; string []
>>saValues = {"My value with spaces", "test2", "test 3"}; string
>>sCombinedOptions = "";
>>
>>//Loop through all elements in arrays
>>for (;;)
>>{
>>   //Combine names / values.
>>   sCombinedOptions += saNames[currentItem] + "=""" +
>>saValues[currentItem] + """ "; }
>>
>>
>>//Add the command line and options.
>>"path\mxmlc.exe" + " " + sCombinedOptions;
>>
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Thursday, August 23, 2012 9:33
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>That ought to work, but does not. The Mustella code pieces together a
>>large string with all of the options on it, then turns the string into
>>a String[] by using space as the delimiter. Thus
>>
>>-source-path="C:\Program Files\Common Files\Microsoft
>>Shared\MSInfo\MSInfo32.exe"
>>
>>turns into
>>[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>>Shared\MSInfo\MSInfo32.exe"
>>
>>And it does this several times (turning the array into a string,
>>inserting other args, back to an array) to build up the argument list.
>>Ultimately, the array of options is passed over to mxmlc to execute, so
>>it does need to turn into an array of options. I was working on putting
>>everything into an ArrayList but more and more code needed to change
>>and then I was getting errors from mxmlc saying parameters were being
>>mixed which I didn't understand since it was getting the same
>>parameters in the same order.
>>
>>So I have to re-think the approach.
>>
>>--peter
>>
>>On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>wrote:
>>
>>>I know this may sound silly, but windows deals with the spaces in path
>>>using quotes around the whole path.  Is there something similar with
>>>Mustella?
>>>
>>>So a windows command prompt example, I could do something like the
>>>following...
>>>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>>
>>>
>>>Whereas the old non spaced dos style naming convention would do this
>>>without quotes..
>>>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>>
>>>
>>>r/s
>>>-Mark
>>>
>>>-----Original Message-----
>>>From: Peter Ent [mailto:pent@adobe.com]
>>>Sent: Wednesday, August 22, 2012 9:20
>>>To: flex-dev@incubator.apache.org
>>>Subject: Re: Getting Mustella to work.
>>>
>>>I have not have luck solving the problem. It is much trickier than I
>>>anticipated. I am going to jump back into getting more tests to run
>>>and think more about the problem. Operating systems have allowed
>>>spaces in file names for many, many years and you'd think would be an
>>>easily solvable problem (or not even a problem at all).
>>>
>>>--peter
>>>
>>>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>>
>>>>Hi,
>>>>
>>>>If the space path issue was fixed you have more to add. Any luck with
>>>>that yet?
>>>>
>>>>Justin
>>>
>>
>

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

It's not listed on "Mustella Test Journall" (at the end of
https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview)

 so I think nobody is on it...

Great to see you working on Mustella! :)


2012/8/24 Jose Barragan <jo...@codeoscopic.com>

> If anybody are working on mx, I'll try it
>
>      [java]
>      [java]
>      [java] =====================================================
>      [java]     Passes: 656
>      [java]     Fails: 39
>      [java] =====================================================
>      [java]
>      [java]
>      [java] Wrote summary to results.txt
>      [java] Wrote failures to failures.txt
>
> BUILD FAILED
> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:1453:
> The following error occurred while executing this line:
> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:1571:
> Java returned: 1
>
> Total time: 18 minutes 28 seconds
>
> Thanks,
> Jose
>
> On Aug 24, 2012, at 12:43 AM, Justin Mclean <ju...@classsoftware.com>
> wrote:
>
> > Hi,
> >
> >> I think I found that quotes are ok even on Mac.  Isn't the code that
> makes
> >> the initial command line building it up out of pieces?  If so, I'd add
> the
> >> quotes as the initial command line is getting built up.
> > Need to be adde din about a dozen places but that's not too hard.
> However it still fails as the spilt ignore quotes.
> >
> > This is the offending line:
> >    defaultArgs=StringUtils.StringToArray(args);
> >
> > Something along the lines of this may work (assuming quotes have been
> added).
> >
> >    Matcher match =
> Pattern.compile("([^\\S]*\"[^\"]*\")|(\\S+)").matcher(args);
> >    ArrayList argList = new ArrayList();
> >
> >    while (match.find()) {
> >        if (match.group(1) == null) {
> >               argList.add(match.group(2));
> >        } else {
> >               argList.add(match.group(1));
> >        }
> >    }
> >
> > Anyone want to give it a go/come up with a better regex?
> >
> > The better way to fix as Peter said would just to use an Array/arrayList
> and not go back and forth between Arrays and Strings.
> >
> > Thanks,
> > Justin
> >
> >
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

mx/controls working too :)

https://github.com/apache/flex/pull/9.patch

  [java] =====================================================
     [java]     Passes: 71
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] 	Passed: 
     [java] =====================================================
     [java] mx/controls/MovieClipSWFLoader/versioning/MP_Spark_MovieClipSWFLoader_Tests MP_MovieClipSWFLoader_toolTip_compatibility Passed  
     [java] mx/controls/MovieClipSWFLoader/versioning/MP_Spark_MovieClipSWFLoader_Tests MP_MovieClipSWFLoader_toolTip_untrusted Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_stop Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_play Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_gotoAndPlay Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_gotoAndStop Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_gotoFirstFrameAndStop Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_nextFrame Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_prevFrame Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_nextScene Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_prevScene Passed  
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_startDelay Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_play_externalSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_play_afterStop Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_play_embeddedSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_stop_externalSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_stop_autoStopFalse Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_stop_afterStop Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoAndPlay Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoAndPlay_frameOnly Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoAndPlay_playingMovie Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoAndPlay_embeddedSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoAndStop Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoAndStop_frameOnly Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoAndStop_playingMovie Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoAndStop_embeddedSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoFirstFrameAndStop_playingMovie Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoFirstFrameAndStop_autoStopTrue Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoFirstFrameAndStop_afterForward Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_gotoFirstFrameAndStop_embeddedSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MClipSWFLoader_gotoFirstFrameAndStop_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MClipSWFLoader_play_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MClipSWFLoader_stop_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MClipSWFLoader_nextFrame_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MClipSWFLoader_prevFrame_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MClipSWFLoader_nextScene_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MClipSWFLoader_prevScene_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_nextFrame_beginning Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_prevFrame_beginning Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_nextFrame_end Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_prevFrame_end Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_nextFrame_playing Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_prevFrame_playing Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_nextFrame_embeddedSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_prevFrame_embeddedSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_nextScene_beginning Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_prevScene_beginning Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_nextScene_end Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_prevScene_end Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_nextScene_playing Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_prevScene_playing Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_nextScene_embeddedSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_prevScene_embeddedSource Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_stop Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_play Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_gotoAndStop Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_gotoAndPlay Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_gotoFirstFrameAndStop Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_nextFrame Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_prevFrame Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_nextScene Passed  
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_noOp_prevScene Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MovieClipSWFLoader_autoStop_default Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MClipSWFLoader_autoStop_true_externalSource Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MClipSWFLoader_autoStop_false_externalSource Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MClipSWFLoader_autoStop_true_mxml Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MClipSWFLoader_autoStop_false_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MClipSWFLoader_autoStop_true_MCInstance Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MovieClipSWFLoader_noOp_autoStop Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MovieClipSWFLoader_noOp_movieClip Passed  
     [java] mx/controls/MovieClipSWFLoader/properties/MovieClipSWFLoader_Properties MovieClipSWFLoader_FlexApp_movieClip Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 71
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 1 minute 10 seconds



On Aug 25, 2012, at 12:36 AM, Jose Barragan <jo...@codeoscopic.com> wrote:

> Hi Alex,
> 
> I made this pull-request on GitHub: https://github.com/apache/flex/pull/8.patch for this patch. 
> I know this repo is obsolete, but is a good way to generate and host the patch's
> 
> @Peter, I'm using Mac OSX 10.8 for the wiki :P
> 
> Thanks,
> 
> Jose

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/26/12 1:57 AM, "Jose Barragan" <jo...@codeoscopic.com> wrote:

> 
> Hi Alex,
> 
> Works for me :P, may be you need pass the first time with -createImages as
> I've done.
> 
Running -createImages first is not a good practice.  In theory, the
baselines in SVN are machine and platform independent references of
"correctness".  If you create your own baselines, you have no way of knowing
if something in your configuration is incorrect, or you have different code
on your system or the test is incorrect.  For me, several of the failed
image comparisons from the run with your patch have missing controls.  That
needs further investigation before accepting your patches.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Hi Alex,

Works for me :P, may be you need pass the first time with -createImages as I've done.

desktop_runner:
     [echo] **** Willkommen auf Runner ****
     [java] starting results server
     [java] starting baseline server
     [java] test script count: 1
     [java] new test file: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/effects/Effect/SWFs/Effect_main.swf
     [java] ******** cmdArr before: 
     [java] 	/Applications/Adobe Flash Builder 4.6/player/mac/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger
     [java] 	/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/effects/Effect/SWFs/Effect_main.swf
     [java] ******** moreParameters before: 
     [java] ******** cmdArr after: 
     [java] 	/Applications/Adobe Flash Builder 4.6/player/mac/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger
     [java] 	/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/effects/Effect/SWFs/Effect_main.swf
     [java] starting the baseline server: Sun Aug 26 10:52:03 CEST 2012
     [java] getting directory from the swf file
     [java] derived directory: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/effects/Effect/SWFs
     [java] Launching: 
     [java]  /Applications/Adobe Flash Builder 4.6/player/mac/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/effects/Effect/SWFs/Effect_main.swf Launching: /Applications/Adobe Flash Builder 4.6/player/mac/11.1/Flash Player Debugger.app/Contents/MacOS/Flash Player Debugger /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/effects/Effect/SWFs/Effect_main.swf
     [java] USING directory: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/effects/Effect/SWFs
     [java] time: 10:52:03.329
     [java] clobberProcess
     [java] Grab log, do parse = false
     [java] Grabbing the log from: /Users/pepebarragan/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt to: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/effects/Effect/SWFs/Effect_main.log
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java]     Passes: 27
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] 	Passed: 
     [java] =====================================================
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Blur Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Dissolve Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Fade Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Glow Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Iris Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_MaskEffect Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Move Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Resize Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Rotate Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_WipeDown Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_WipeLeft Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_WipeRight Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_WipeUp Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_Zoom Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_FxAnimate Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_FxAnimateColor Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_FxFade Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_FxMove Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_FxResize Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_FxRotate Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_FxRotate3D Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_IntoRC1 Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_IntoRC2 Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_IntoRC2SD Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_IntoRD Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_IntoRCLoop Passed  
     [java] mx/effects/Effect/seek/Effect_seek Effect_seek_IntoRCReverse Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 27
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 1 minute 23 seconds

Best,

-Jose

On Aug 26, 2012, at 7:09 AM, Alex Harui <ah...@adobe.com> wrote:

> Hi,
> 
> I applied your patches, but I am getting bad results in
> mx/effects/Effect/seek.  Bitmap failures and timeouts.
> 
> Also, I am getting lots of font differences elsewhere in the mx folder that
> make it seem that you haven¹t installed the embedded font library because I
> believe the baselines were incorrectly created without fonts embedded.
> 
> Can you double-check those two things?
> 
> Thanks,
> 
> -Alex
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Hi,

I applied your patches, but I am getting bad results in
mx/effects/Effect/seek.  Bitmap failures and timeouts.

Also, I am getting lots of font differences elsewhere in the mx folder that
make it seem that you haven¹t installed the embedded font library because I
believe the baselines were incorrectly created without fonts embedded.

Can you double-check those two things?

Thanks,

-Alex

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Jose Barragan Andrade <pe...@me.com>.

Mustella mx folder summary,   All green :)

All patches are in [1], and use in the first pass, -createImages param.

     [java] time: 05:15:24.769
     [java] clobberProcess
     [java] Grab log, do parse = false
     [java] Grabbing the log from: /Users/pepebarragan/Library/Preferences/Macromedia/Flash Player/Logs/flashlog.txt to: /Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/tests/mx/utils/MediaQueryParser/swfs/MediaQueryCSSModuleApp.log
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java]     Passes: 1755
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] =====================================================
     [java] =====================================================
     [java] 	Passed: 
     [java] =====================================================
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindSetter Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindSetter_nullHost Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindSetter_nullChain Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindSetter_deepChainArray Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindSetter_deepChainBad Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindSetter_changeWatcher Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindProperty Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindProperty_nullProp Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindProperty_nullChain Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindProperty_nullSite Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindProperty_nullHost Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindProperty_changeWatcher Passed  
     [java] mx/binding/utils/BindingUtils/method/BindingUtils_method BindingUtils_bindProperty_deepChain Passed  
     [java] mx/binding/utils/ChangeWatcher/method/ChangeWatcher_method ChangeWatcher_getEvents_false Passed  
     [java] mx/binding/utils/ChangeWatcher/method/ChangeWatcher_method ChangeWatcher_canWatch_true Passed  
     [java] mx/binding/utils/ChangeWatcher/method/ChangeWatcher_method ChangeWatcher_canWatch_false Passed  
     [java] mx/binding/utils/ChangeWatcher/method/ChangeWatcher_method ChangeWatcher_isWatching Passed  
     [java] mx/binding/utils/ChangeWatcher/method/ChangeWatcher_method ChangeWatcher_canWatch_nullHost Passed  	
    
     {....}

     [java] mx/utils/ColorUtil/method/ColorUtil_method ColorUtil_adjustBrightness_bleed Passed  
     [java] mx/utils/ColorUtil/method/ColorUtil_method ColorUtil_adjustBrightness_negative Passed  
     [java] mx/utils/ColorUtil/method/ColorUtil_method ColorUtil_adjustBrightness2_max Passed  
     [java] mx/utils/ColorUtil/method/ColorUtil_method ColorUtil_adjustBrightness_positive Passed  
     [java] mx/utils/ColorUtil/method/ColorUtil_method ColorUtil_adjustBrightness2_min Passed  
     [java] mx/utils/ColorUtil/method/ColorUtil_method ColorUtil_adjustBrightness_uberPositive Passed  
     [java] mx/utils/ColorUtil/method/ColorUtil_method ColorUtil_rgbMultiply_multiChannel Passed  
     [java] mx/utils/MediaQueryParser/integration/MediaQueryParser_Integration MediaQueryParser_Integration_TypeSelectors Passed  
     [java] mx/utils/MediaQueryParser/integration/MediaQueryParser_Integration MediaQueryParser_Integration_ClassSelectors Passed  
     [java] mx/utils/MediaQueryParser/integration/MediaQueryParser_Integration_CSSModule MediaQueryParser_Integration_CSSModule_TypeSelectors Passed  
     [java] mx/utils/MediaQueryParser/integration/MediaQueryParser_Integration_CSSModule MediaQueryParser_Integration_CSSModule_ClassSelectors Passed  
     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 1755
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 28 minutes 5 seconds


1.- https://issues.apache.org/jira/browse/FLEX-33177 

Bests,

Jose

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Wow!

seems that Jose has been busy arranging some tests ....have you left
something for others? ;)

@alex: I just returned from the weekend and later I will see the patch
for itemRenderers. I'll send you the update...

Best

--
Carlos Rovira
Director de Tecnología
M: +34 607 22 60 05
F:  +34 912 35 57 77
CODEOSCOPIC S.A.
Avd. del General Perón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Cyrill Zadra <cy...@gmail.com>.

Hi alex


Am Montag, 27. August 2012 schrieb Alex Harui :

>
> On 8/26/12 10:02 PM, "Cyrill Zadra" <cyrill.zadra@gmail.com <javascript:;>>
> wrote:
>
> >> Cyrill, Are you still thinking there is an SDK bug?
> >>
> >
> > Yes.. the css in pseudo selector still doesn't get applied to the MX
> Button. I
> > found an existing fixed bug in jira
> > https://issues.apache.org/jira/browse/FLEX-20541. The difference in the
> test
> > case is the custom state "SubmitState" on the button.
> >
> I haven't looked at the patch.  How did you get to zero failures?


The classSelectors tests have 0 fails but in the pseudoSelectors folder are
still 2 fails.


>
> >> --
> >> Alex Harui
> >> Flex SDK Team
> >> Adobe Systems, Inc.
> >> http://blogs.adobe.com/aharui
> >>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

On 8/26/12 10:02 PM, "Cyrill Zadra" <cy...@gmail.com> wrote:

>> Cyrill, Are you still thinking there is an SDK bug?
>> 
> 
> Yes.. the css in pseudo selector still doesn't get applied to the MX Button. I
> found an existing fixed bug in jira
> https://issues.apache.org/jira/browse/FLEX-20541. The difference in the test
> case is the custom state "SubmitState" on the button.
> 
I haven't looked at the patch.  How did you get to zero failures?

>> -- 
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Cyrill Zadra <cy...@gmail.com>.

Hi Alex

Am 27.08.2012 um 06:11 schrieb Alex Harui <ah...@adobe.com>:

> 
> 
> 
> On 8/26/12 8:12 AM, "Cyrill Zadra" <cy...@gmail.com> wrote:
> 
>> "tests\Managers\StyleManager\AdvancedCSS\classSelectors"
>> 
>> Created images and test had zero fails. I added patch
>> (mustellaStyleManagerAdvancedCSSClassSelectorsPatch.zip) to
>> https://issues.apache.org/jira/browse/FLEX-33173
>> 
>>     [java] =====================================================
>>     [java]     Passes: 52
>>     [java]     Fails: 0
>>     [java] =====================================================
>> 
> Cyrill, Are you still thinking there is an SDK bug?
> 

Yes.. the css in pseudo selector still doesn't get applied to the MX Button. I found an existing fixed bug in jira https://issues.apache.org/jira/browse/FLEX-20541. The difference in the test case is the custom state "SubmitState" on the button.

> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/26/12 8:12 AM, "Cyrill Zadra" <cy...@gmail.com> wrote:

>  "tests\Managers\StyleManager\AdvancedCSS\classSelectors"
> 
> Created images and test had zero fails. I added patch
> (mustellaStyleManagerAdvancedCSSClassSelectorsPatch.zip) to
> https://issues.apache.org/jira/browse/FLEX-33173
> 
>      [java] =====================================================
>      [java]     Passes: 52
>      [java]     Fails: 0
>      [java] =====================================================
> 
Cyrill, Are you still thinking there is an SDK bug?

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Cyrill Zadra <cy...@gmail.com>.

 "tests\Managers\StyleManager\AdvancedCSS\classSelectors"

Created images and test had zero fails. I added patch
(mustellaStyleManagerAdvancedCSSClassSelectorsPatch.zip) to
https://issues.apache.org/jira/browse/FLEX-33173

     [java] =====================================================
     [java]     Passes: 52
     [java]     Fails: 0
     [java] =====================================================


On Sun, Aug 26, 2012 at 1:43 PM, Cyrill Zadra <cy...@gmail.com>wrote:

> Hi
>
> There is a pseudo selector test on mx:Button with custom states
> "tests\Managers\StyleManager\AdvancedCSS\pseudoSelectors" and it looks for
> me there's a bug in the sdk. If somebody can confirm that ..
>
> The same test for spark button works seamless.
>
> codesnippet
>
> <?xml version="1.0"?>
> <!-- styles/PseudoSelectorExample.mxml -->
> <mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
> xmlns:comp="comp.*">
>  <mx:Style>
> @namespace mx "library://ns.adobe.com/flex/mx";
>  mx|Button:SubmitState {
> cornerRadius: 15;
>  }
> </mx:Style>
>  <comp:TestMxButton id="button" label="Click Me 2" x="10" y="65" />
> </mx:Application>
>
> <?xml version="1.0" encoding="utf-8"?>
> <!--  comp/TestMxButton.mxml -->
> <mx:Button  xmlns:mx="http://www.adobe.com/2006/mxml"
>  width="120" height="50" currentState="SubmitState">
> <mx:states>
>  <mx:State name="SubmitState" >
> <mx:SetProperty target="{this}" name="label" value="submit" />
>  </mx:State>
> <mx:State name="ClearState" >
> <mx:SetProperty target="{this}" name="label" value="clear" />
>  </mx:State>
> </mx:states>
> </mx:Button>
>
> I'll continue with "tests\Managers\StyleManager\AdvancedCSS\classSelectors"
>
> cyrill
>

Re: Getting Mustella to work.

Posted by Cyrill Zadra <cy...@gmail.com>.

Hi

There is a pseudo selector test on mx:Button with custom states
"tests\Managers\StyleManager\AdvancedCSS\pseudoSelectors" and it looks for
me there's a bug in the sdk. If somebody can confirm that ..

The same test for spark button works seamless.

codesnippet

<?xml version="1.0"?>
<!-- styles/PseudoSelectorExample.mxml -->
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml"
xmlns:comp="comp.*">
<mx:Style>
@namespace mx "library://ns.adobe.com/flex/mx";
 mx|Button:SubmitState {
cornerRadius: 15;
}
</mx:Style>
<comp:TestMxButton id="button" label="Click Me 2" x="10" y="65" />
</mx:Application>

<?xml version="1.0" encoding="utf-8"?>
<!--  comp/TestMxButton.mxml -->
<mx:Button  xmlns:mx="http://www.adobe.com/2006/mxml"
width="120" height="50" currentState="SubmitState">
<mx:states>
<mx:State name="SubmitState" >
<mx:SetProperty target="{this}" name="label" value="submit" />
</mx:State>
<mx:State name="ClearState" >
<mx:SetProperty target="{this}" name="label" value="clear" />
</mx:State>
</mx:states>
</mx:Button>

I'll continue with "tests\Managers\StyleManager\AdvancedCSS\classSelectors"

cyrill

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Hi Alex,

In this task I'll publishing the patches of progress for mustella/mx/*

https://issues.apache.org/jira/browse/FLEX-33177

thanks,

-Jose

On Aug 25, 2012, at 1:34 AM, Alex Harui <ah...@adobe.com> wrote:

> Sorry, I misunderstood.
> 
> It is my understanding that you should file a new issue for your patch.
> That way we have a clean record of your contribution and intention.
> 
> -Alex
> 
> 
> On 8/24/12 4:31 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> 
>> He he he... funny Alex ;)
>> 
>> I known where is Apache Flex JIRA, I asked you for the link of the specific
>> ticket for "[Mustella] Getting to Work" or whatever it called if exists.
>> 
>> Well, as I see, I will create it for this thread contributions in ahead
>> 
>> Jose
>> 
>> On Aug 25, 2012, at 1:11 AM, Alex Harui <ah...@adobe.com> wrote:
>> 
>>> Apache Flex JIRA is here [1]
>>> 
>>> [1] https://issues.apache.org/jira/browse/FLEX
>>> 
>>> Thanks,
>>> 
>>> 
>>> On 8/24/12 4:08 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>>> 
>>>> Please, give me the link to the official post in JIRA, I can't found it,
>>>> when
>>>> I search 5 minutes ago.
>> 
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Sorry, I misunderstood.

It is my understanding that you should file a new issue for your patch.
That way we have a clean record of your contribution and intention.

-Alex


On 8/24/12 4:31 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:

> He he he... funny Alex ;)
>   
> I known where is Apache Flex JIRA, I asked you for the link of the specific
> ticket for "[Mustella] Getting to Work" or whatever it called if exists.
> 
> Well, as I see, I will create it for this thread contributions in ahead
> 
> Jose
> 
> On Aug 25, 2012, at 1:11 AM, Alex Harui <ah...@adobe.com> wrote:
> 
>> Apache Flex JIRA is here [1]
>> 
>> [1] https://issues.apache.org/jira/browse/FLEX
>> 
>> Thanks,
>> 
>> 
>> On 8/24/12 4:08 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>> 
>>> Please, give me the link to the official post in JIRA, I can't found it,
>>> when
>>> I search 5 minutes ago.
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

He he he... funny Alex ;)

I known where is Apache Flex JIRA, I asked you for the link of the specific ticket for "[Mustella] Getting to Work" or whatever it called if exists.

Well, as I see, I will create it for this thread contributions in ahead

Jose

On Aug 25, 2012, at 1:11 AM, Alex Harui <ah...@adobe.com> wrote:

> Apache Flex JIRA is here [1]
> 
> [1] https://issues.apache.org/jira/browse/FLEX
> 
> Thanks,
> 
> 
> On 8/24/12 4:08 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> 
>> Please, give me the link to the official post in JIRA, I can't found it, when
>> I search 5 minutes ago.

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Apache Flex JIRA is here [1]

[1] https://issues.apache.org/jira/browse/FLEX

Thanks,


On 8/24/12 4:08 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:

> Please, give me the link to the official post in JIRA, I can't found it, when
> I search 5 minutes ago.
> 
> 
> On Aug 25, 2012, at 1:03 AM, Alex Harui <ah...@adobe.com> wrote:
> 
>> Please file a JIRA issue.  We need some official tracking that you are
>> contributing this information.
>> 
>> 
>> On 8/24/12 3:36 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>> 
>>> Hi Alex,
>>> 
>>> I made this pull-request on GitHub:
>>> https://github.com/apache/flex/pull/8.patch for this patch.
>>> I know this repo is obsolete, but is a good way to generate and host the
>>> patch's
>>> 
>>> @Peter, I'm using Mac OSX 10.8 for the wiki :P
>>> 
>>> Thanks,
>>> 
>>> Jose
>>> 
>>> On Aug 25, 2012, at 12:12 AM, Jose Barragán <jo...@codeoscopic.com>
>>> wrote:
>>> 
>>>> Hi Alex,
>>>> 
>>>> Sure, let me a few minutes to prepare it...
>>>> 
>>>> 
>>>> 
>>>> On Friday, August 24, 2012, Alex Harui wrote:
>>>> Excellent!  Do you have a patch file?
>>>> 
>>>> 
>>>> On 8/24/12 2:05 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>>>> 
>>>>> Thanks Peter,
>>>>> 
>>>>> Well, step by step, i've fixed the mx/collections
>>>>> 
>>>>>     [java] =====================================================
>>>>>     [java]  Failed:
>>>>>     [java] =====================================================
>>>>>     [java]
>>>>>     [java]
>>>>>     [java] =====================================================
>>>>>     [java]     Passes: 393
>>>>>     [java]     Fails: 0
>>>>>     [java] =====================================================
>>>>>     [java]
>>>>>     [java]
>>>>>     [java] Wrote summary to results.txt
>>>>>     [java] Wrote failures to failures.txt
>>>>> 
>>>>> call_runners:
>>>>> 
>>>>> run:
>>>>> 
>>>>> BUILD SUCCESSFUL
>>>>> Total time: 2 minutes 45 seconds
>>>>> 
>>> 
>> 
>> -- 
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Please, give me the link to the official post in JIRA, I can't found it, when I search 5 minutes ago.


On Aug 25, 2012, at 1:03 AM, Alex Harui <ah...@adobe.com> wrote:

> Please file a JIRA issue.  We need some official tracking that you are
> contributing this information.
> 
> 
> On 8/24/12 3:36 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> 
>> Hi Alex,
>> 
>> I made this pull-request on GitHub:
>> https://github.com/apache/flex/pull/8.patch for this patch.
>> I know this repo is obsolete, but is a good way to generate and host the
>> patch's
>> 
>> @Peter, I'm using Mac OSX 10.8 for the wiki :P
>> 
>> Thanks,
>> 
>> Jose
>> 
>> On Aug 25, 2012, at 12:12 AM, Jose Barragán <jo...@codeoscopic.com>
>> wrote:
>> 
>>> Hi Alex,
>>> 
>>> Sure, let me a few minutes to prepare it...
>>> 
>>> 
>>> 
>>> On Friday, August 24, 2012, Alex Harui wrote:
>>> Excellent!  Do you have a patch file?
>>> 
>>> 
>>> On 8/24/12 2:05 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>>> 
>>>> Thanks Peter,
>>>> 
>>>> Well, step by step, i've fixed the mx/collections
>>>> 
>>>>     [java] =====================================================
>>>>     [java]  Failed:
>>>>     [java] =====================================================
>>>>     [java]
>>>>     [java]
>>>>     [java] =====================================================
>>>>     [java]     Passes: 393
>>>>     [java]     Fails: 0
>>>>     [java] =====================================================
>>>>     [java]
>>>>     [java]
>>>>     [java] Wrote summary to results.txt
>>>>     [java] Wrote failures to failures.txt
>>>> 
>>>> call_runners:
>>>> 
>>>> run:
>>>> 
>>>> BUILD SUCCESSFUL
>>>> Total time: 2 minutes 45 seconds
>>>> 
>> 
> 
> -- 
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Please file a JIRA issue.  We need some official tracking that you are
contributing this information.


On 8/24/12 3:36 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:

> Hi Alex,
> 
> I made this pull-request on GitHub:
> https://github.com/apache/flex/pull/8.patch for this patch.
> I know this repo is obsolete, but is a good way to generate and host the
> patch's
> 
> @Peter, I'm using Mac OSX 10.8 for the wiki :P
> 
> Thanks,
> 
> Jose
> 
> On Aug 25, 2012, at 12:12 AM, Jose Barragán <jo...@codeoscopic.com>
> wrote:
> 
>> Hi Alex,
>> 
>> Sure, let me a few minutes to prepare it...
>> 
>> 
>> 
>> On Friday, August 24, 2012, Alex Harui wrote:
>> Excellent!  Do you have a patch file?
>> 
>> 
>> On 8/24/12 2:05 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>> 
>>> Thanks Peter,
>>> 
>>> Well, step by step, i've fixed the mx/collections
>>> 
>>>      [java] =====================================================
>>>      [java]  Failed:
>>>      [java] =====================================================
>>>      [java]
>>>      [java]
>>>      [java] =====================================================
>>>      [java]     Passes: 393
>>>      [java]     Fails: 0
>>>      [java] =====================================================
>>>      [java]
>>>      [java]
>>>      [java] Wrote summary to results.txt
>>>      [java] Wrote failures to failures.txt
>>> 
>>> call_runners:
>>> 
>>> run:
>>> 
>>> BUILD SUCCESSFUL
>>> Total time: 2 minutes 45 seconds
>>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Hi Alex,

I made this pull-request on GitHub: https://github.com/apache/flex/pull/8.patch for this patch. 
I know this repo is obsolete, but is a good way to generate and host the patch's

@Peter, I'm using Mac OSX 10.8 for the wiki :P

Thanks,

Jose

On Aug 25, 2012, at 12:12 AM, Jose Barragán <jo...@codeoscopic.com> wrote:

> Hi Alex,
> 
> Sure, let me a few minutes to prepare it... 
> 
> 
> 
> On Friday, August 24, 2012, Alex Harui wrote:
> Excellent!  Do you have a patch file?
> 
> 
> On 8/24/12 2:05 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> 
> > Thanks Peter,
> >
> > Well, step by step, i've fixed the mx/collections
> >
> >      [java] =====================================================
> >      [java]  Failed:
> >      [java] =====================================================
> >      [java]
> >      [java]
> >      [java] =====================================================
> >      [java]     Passes: 393
> >      [java]     Fails: 0
> >      [java] =====================================================
> >      [java]
> >      [java]
> >      [java] Wrote summary to results.txt
> >      [java] Wrote failures to failures.txt
> >
> > call_runners:
> >
> > run:
> >
> > BUILD SUCCESSFUL
> > Total time: 2 minutes 45 seconds
> >

Re: Getting Mustella to work.

Posted by Jose Barragán <jo...@codeoscopic.com>.

Hi Alex,

Sure, let me a few minutes to prepare it...



On Friday, August 24, 2012, Alex Harui wrote:

> Excellent!  Do you have a patch file?
>
>
> On 8/24/12 2:05 PM, "Jose Barragan" <jose.barragan@codeoscopic.com<javascript:;>>
> wrote:
>
> > Thanks Peter,
> >
> > Well, step by step, i've fixed the mx/collections
> >
> >      [java] =====================================================
> >      [java]  Failed:
> >      [java] =====================================================
> >      [java]
> >      [java]
> >      [java] =====================================================
> >      [java]     Passes: 393
> >      [java]     Fails: 0
> >      [java] =====================================================
> >      [java]
> >      [java]
> >      [java] Wrote summary to results.txt
> >      [java] Wrote failures to failures.txt
> >
> > call_runners:
> >
> > run:
> >
> > BUILD SUCCESSFUL
> > Total time: 2 minutes 45 seconds
> >
> >
> >
> > On Aug 24, 2012, at 3:57 PM, Peter Ent <pent@adobe.com <javascript:;>>
> wrote:
> >
> >> I have Jose listed in the table on the Wiki page for the whole 'mx'
> suite.
> >> Thanks and good hunting.
> >>
> >> --peter
> >>
> >> On 8/23/12 7:00 PM, "Jose Barragan" <jose.barragan@codeoscopic.com<javascript:;>>
> wrote:
> >>
> >>> If anybody are working on mx, I'll try it
> >>>
> >>>    [java]
> >>>    [java]
> >>>    [java] =====================================================
> >>>    [java]     Passes: 656
> >>>    [java]     Fails: 39
> >>>    [java] =====================================================
> >>>    [java]
> >>>    [java]
> >>>    [java] Wrote summary to results.txt
> >>>    [java] Wrote failures to failures.txt
> >>>
> >>> BUILD FAILED
> >>>
> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:145
> >>> 3: The following error occurred while executing this line:
> >>>
> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:157
> >>> 1: Java returned: 1
> >>>
> >>> Total time: 18 minutes 28 seconds
> >>>
> >>> Thanks,
> >>> Jose
> >>>
> >>> On Aug 24, 2012, at 12:43 AM, Justin Mclean <justin@classsoftware.com<javascript:;>
> >
> >>> wrote:
> >>>
> >>>> Hi,
> >>>>
> >>>>> I think I found that quotes are ok even on Mac.  Isn't the code that
> >>>>> makes
> >>>>> the initial command line building it up out of pieces?  If so, I'd
> add
> >>>>> the
> >>>>> quotes as the initial command line is getting built up.
> >>>> Need to be adde din about a dozen places but that's not too hard.
> >>>> However it still fails as the spilt ignore quotes.
> >>>>
> >>>> This is the offending line:
> >>>>   defaultArgs=StringUtils.StringToArray(args);
> >>>>
> >>>> Something along the lines of this may work (assuming quotes have been
> >>>> added).
> >>>>
> >>>>   Matcher match =
> >>>> Pattern.compile("([^\\S]*\"[^\"]*\")|(\\S+)").matcher(args);
> >>>>   ArrayList argList = new ArrayList();
> >>>>
> >>>>   while (match.find()) {
> >>>>       if (match.group(1) == null) {
> >>>> argList.add(match.group(2));
> >>>>       } else {
> >>>> argList.add(match.group(1));
> >>>>       }
> >>>>   }
> >>>>
> >>>> Anyone want to give it a go/come up with a better regex?
> >>>>
> >>>> The better way to fix as Peter said would just to use an
> >>>> Array/arrayList and not go back and forth between Arrays and Strings.
> >>>>
> >>>> Thanks,
> >>>> Justin
> >>>>
> >>>>
> >>>
> >>
> >
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Mustella mx folder progress summary,

     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] mx/controls/MovieClipSWFLoader/versioning/MP_Spark_MovieClipSWFLoader_Tests MP_MovieClipSWFLoader_toolTip_compatibility Failed SetProperty(setup:step 3)  Timeout waiting for complete from swf1 
     [java] mx/controls/MovieClipSWFLoader/versioning/MP_Spark_MovieClipSWFLoader_Tests MP_MovieClipSWFLoader_toolTip_untrusted Failed SetProperty(setup:step 3)  Timeout waiting for complete from swf1 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_stop Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_play Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_gotoAndPlay Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_gotoAndStop Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_gotoFirstFrameAndStop Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_nextFrame Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_prevFrame Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_nextScene Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_prevScene Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/effects/MovieClipSWFLoader_Test MovieClipSWFLoader_CallAction_startDelay Failed SetProperty(body:step 4)  Timeout waiting for complete from myMovie5 
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_play_externalSource Failed SetProperty(body:step 3)  Timeout waiting for complete from myMovie 
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_play_afterStop Failed SetProperty(body:step 3)  Timeout waiting for complete from myMovie 
     [java] mx/controls/MovieClipSWFLoader/methods/MovieClipSWFLoader_Methods MovieClipSWFLoader_play_embeddedSource Failed Timed out
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_CheckBox Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_DataGrid Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_DateChooser Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_DateField Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_HorizontalList Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_Label Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_List Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_NumericStepper Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_RadioButton Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_RichTextEditor Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_Text Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_TextArea Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_TextInput Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_TileList Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Dissolve/object/Dissolve_object Dissolve_Tree Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_CheckBox Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_DataGrid Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_DateChooser Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_DateField Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_HorizontalList Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_Label Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_List Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_NumericStepper Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_RadioButton Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_RichTextEditor Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_Text Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_TextArea Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_TextInput Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_TileList Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Glow/object/Glow_object Glow_Tree Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/Zoom/Controls/Zoom_Controls Effects_Zoom_Controls_DateField Failed AssertPixelValue(body:step 4)  uiComponent pixel at (139,4) A0A7AB != 0x9FA3A4 
     [java] mx/effects/Zoom/Controls/Zoom_Controls Effects_Zoom_Controls_Tree Failed AssertPixelValue(body:step 4)  uiComponent pixel at (28,42) 65747E != 0x656565 
     [java] mx/effects/effectClasses/AddRemoveEffectTargetFilter/usability/AddRemoveEffectTargetFilter_usability AddRemoveEffectTargetFilter_addItem Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] mx/effects/effectClasses/AddRemoveEffectTargetFilter/usability/AddRemoveEffectTargetFilter_usability AddRemoveEffectTargetFilter_removeItem Failed CompareBitmap(body:step 2)  compare returned[object BitmapData] 
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 1174
     [java]     Fails: 49
     [java] =====================================================
     [java] 
     [java] 
     [java] Waiting for results...
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

BUILD FAILED
/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/build.xml:1457: The following error occurred while executing this line:
/Users/pepebarragan/Developer/apache/flex/sdk/branches/develop/mustella/build.xml:1575: Java returned: 1

Total time: 19 minutes 4 seconds


On Aug 24, 2012, at 11:05 PM, Jose Barragan <jo...@codeoscopic.com> wrote:

> Thanks Peter,
> 
> Well, step by step, i've fixed the mx/collections
> 
>     [java] =====================================================
>     [java] 	Failed: 
>     [java] =====================================================
>     [java] 
>     [java] 
>     [java] =====================================================
>     [java]     Passes: 393
>     [java]     Fails: 0
>     [java] =====================================================
>     [java] 
>     [java] 
>     [java] Wrote summary to results.txt
>     [java] Wrote failures to failures.txt
> 
> call_runners:
> 
> run:
> 
> BUILD SUCCESSFUL
> Total time: 2 minutes 45 seconds
> 
> 
> 
> On Aug 24, 2012, at 3:57 PM, Peter Ent <pe...@adobe.com> wrote:
> 
>> I have Jose listed in the table on the Wiki page for the whole 'mx' suite.
>> Thanks and good hunting.
>> 
>> --peter
>> 
>> On 8/23/12 7:00 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>> 
>>> If anybody are working on mx, I'll try it
>>> 
>>>   [java] 
>>>   [java] 
>>>   [java] =====================================================
>>>   [java]     Passes: 656
>>>   [java]     Fails: 39
>>>   [java] =====================================================
>>>   [java] 
>>>   [java] 
>>>   [java] Wrote summary to results.txt
>>>   [java] Wrote failures to failures.txt
>>> 
>>> BUILD FAILED
>>> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:145
>>> 3: The following error occurred while executing this line:
>>> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:157
>>> 1: Java returned: 1
>>> 
>>> Total time: 18 minutes 28 seconds
>>> 
>>> Thanks,
>>> Jose
>>> 
>>> On Aug 24, 2012, at 12:43 AM, Justin Mclean <ju...@classsoftware.com>
>>> wrote:
>>> 
>>>> Hi,
>>>> 
>>>>> I think I found that quotes are ok even on Mac.  Isn't the code that
>>>>> makes
>>>>> the initial command line building it up out of pieces?  If so, I'd add
>>>>> the
>>>>> quotes as the initial command line is getting built up.
>>>> Need to be adde din about a dozen places but that's not too hard.
>>>> However it still fails as the spilt ignore quotes.
>>>> 
>>>> This is the offending line:
>>>>  defaultArgs=StringUtils.StringToArray(args);
>>>> 
>>>> Something along the lines of this may work (assuming quotes have been
>>>> added).
>>>> 
>>>>  Matcher match =
>>>> Pattern.compile("([^\\S]*\"[^\"]*\")|(\\S+)").matcher(args);
>>>>  ArrayList argList = new ArrayList();
>>>> 
>>>>  while (match.find()) {
>>>>      if (match.group(1) == null) {
>>>>      	argList.add(match.group(2));
>>>>      } else {
>>>>      	argList.add(match.group(1));
>>>>      }
>>>>  }
>>>> 
>>>> Anyone want to give it a go/come up with a better regex?
>>>> 
>>>> The better way to fix as Peter said would just to use an
>>>> Array/arrayList and not go back and forth between Arrays and Strings.
>>>> 
>>>> Thanks,
>>>> Justin
>>>> 
>>>> 
>>> 
>> 
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Excellent!  Do you have a patch file?


On 8/24/12 2:05 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:

> Thanks Peter,
> 
> Well, step by step, i've fixed the mx/collections
> 
>      [java] =====================================================
>      [java]  Failed:
>      [java] =====================================================
>      [java] 
>      [java] 
>      [java] =====================================================
>      [java]     Passes: 393
>      [java]     Fails: 0
>      [java] =====================================================
>      [java] 
>      [java] 
>      [java] Wrote summary to results.txt
>      [java] Wrote failures to failures.txt
> 
> call_runners:
> 
> run:
> 
> BUILD SUCCESSFUL
> Total time: 2 minutes 45 seconds
> 
> 
> 
> On Aug 24, 2012, at 3:57 PM, Peter Ent <pe...@adobe.com> wrote:
> 
>> I have Jose listed in the table on the Wiki page for the whole 'mx' suite.
>> Thanks and good hunting.
>> 
>> --peter
>> 
>> On 8/23/12 7:00 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
>> 
>>> If anybody are working on mx, I'll try it
>>> 
>>>    [java] 
>>>    [java] 
>>>    [java] =====================================================
>>>    [java]     Passes: 656
>>>    [java]     Fails: 39
>>>    [java] =====================================================
>>>    [java] 
>>>    [java] 
>>>    [java] Wrote summary to results.txt
>>>    [java] Wrote failures to failures.txt
>>> 
>>> BUILD FAILED
>>> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:145
>>> 3: The following error occurred while executing this line:
>>> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:157
>>> 1: Java returned: 1
>>> 
>>> Total time: 18 minutes 28 seconds
>>> 
>>> Thanks,
>>> Jose
>>> 
>>> On Aug 24, 2012, at 12:43 AM, Justin Mclean <ju...@classsoftware.com>
>>> wrote:
>>> 
>>>> Hi,
>>>> 
>>>>> I think I found that quotes are ok even on Mac.  Isn't the code that
>>>>> makes
>>>>> the initial command line building it up out of pieces?  If so, I'd add
>>>>> the
>>>>> quotes as the initial command line is getting built up.
>>>> Need to be adde din about a dozen places but that's not too hard.
>>>> However it still fails as the spilt ignore quotes.
>>>> 
>>>> This is the offending line:
>>>>   defaultArgs=StringUtils.StringToArray(args);
>>>> 
>>>> Something along the lines of this may work (assuming quotes have been
>>>> added).
>>>> 
>>>>   Matcher match =
>>>> Pattern.compile("([^\\S]*\"[^\"]*\")|(\\S+)").matcher(args);
>>>>   ArrayList argList = new ArrayList();
>>>> 
>>>>   while (match.find()) {
>>>>       if (match.group(1) == null) {
>>>> argList.add(match.group(2));
>>>>       } else {
>>>> argList.add(match.group(1));
>>>>       }
>>>>   }
>>>> 
>>>> Anyone want to give it a go/come up with a better regex?
>>>> 
>>>> The better way to fix as Peter said would just to use an
>>>> Array/arrayList and not go back and forth between Arrays and Strings.
>>>> 
>>>> Thanks,
>>>> Justin
>>>> 
>>>> 
>>> 
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

Thanks Peter,

Well, step by step, i've fixed the mx/collections

     [java] =====================================================
     [java] 	Failed: 
     [java] =====================================================
     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 393
     [java]     Fails: 0
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 2 minutes 45 seconds



On Aug 24, 2012, at 3:57 PM, Peter Ent <pe...@adobe.com> wrote:

> I have Jose listed in the table on the Wiki page for the whole 'mx' suite.
> Thanks and good hunting.
> 
> --peter
> 
> On 8/23/12 7:00 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:
> 
>> If anybody are working on mx, I'll try it
>> 
>>    [java] 
>>    [java] 
>>    [java] =====================================================
>>    [java]     Passes: 656
>>    [java]     Fails: 39
>>    [java] =====================================================
>>    [java] 
>>    [java] 
>>    [java] Wrote summary to results.txt
>>    [java] Wrote failures to failures.txt
>> 
>> BUILD FAILED
>> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:145
>> 3: The following error occurred while executing this line:
>> /Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:157
>> 1: Java returned: 1
>> 
>> Total time: 18 minutes 28 seconds
>> 
>> Thanks,
>> Jose
>> 
>> On Aug 24, 2012, at 12:43 AM, Justin Mclean <ju...@classsoftware.com>
>> wrote:
>> 
>>> Hi,
>>> 
>>>> I think I found that quotes are ok even on Mac.  Isn't the code that
>>>> makes
>>>> the initial command line building it up out of pieces?  If so, I'd add
>>>> the
>>>> quotes as the initial command line is getting built up.
>>> Need to be adde din about a dozen places but that's not too hard.
>>> However it still fails as the spilt ignore quotes.
>>> 
>>> This is the offending line:
>>>   defaultArgs=StringUtils.StringToArray(args);
>>> 
>>> Something along the lines of this may work (assuming quotes have been
>>> added).
>>> 
>>>   Matcher match =
>>> Pattern.compile("([^\\S]*\"[^\"]*\")|(\\S+)").matcher(args);
>>>   ArrayList argList = new ArrayList();
>>> 
>>>   while (match.find()) {
>>>       if (match.group(1) == null) {
>>>       	argList.add(match.group(2));
>>>       } else {
>>>       	argList.add(match.group(1));
>>>       }
>>>   }
>>> 
>>> Anyone want to give it a go/come up with a better regex?
>>> 
>>> The better way to fix as Peter said would just to use an
>>> Array/arrayList and not go back and forth between Arrays and Strings.
>>> 
>>> Thanks,
>>> Justin
>>> 
>>> 
>> 
>

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I have Jose listed in the table on the Wiki page for the whole 'mx' suite.
Thanks and good hunting.

--peter

On 8/23/12 7:00 PM, "Jose Barragan" <jo...@codeoscopic.com> wrote:

>If anybody are working on mx, I'll try it
>
>     [java] 
>     [java] 
>     [java] =====================================================
>     [java]     Passes: 656
>     [java]     Fails: 39
>     [java] =====================================================
>     [java] 
>     [java] 
>     [java] Wrote summary to results.txt
>     [java] Wrote failures to failures.txt
>
>BUILD FAILED
>/Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:145
>3: The following error occurred while executing this line:
>/Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:157
>1: Java returned: 1
>
>Total time: 18 minutes 28 seconds
>
>Thanks,
>Jose
>
>On Aug 24, 2012, at 12:43 AM, Justin Mclean <ju...@classsoftware.com>
>wrote:
>
>> Hi,
>> 
>>> I think I found that quotes are ok even on Mac.  Isn't the code that
>>>makes
>>> the initial command line building it up out of pieces?  If so, I'd add
>>>the
>>> quotes as the initial command line is getting built up.
>> Need to be adde din about a dozen places but that's not too hard.
>>However it still fails as the spilt ignore quotes.
>> 
>> This is the offending line:
>>    defaultArgs=StringUtils.StringToArray(args);
>> 
>> Something along the lines of this may work (assuming quotes have been
>>added).
>> 
>>    Matcher match =
>>Pattern.compile("([^\\S]*\"[^\"]*\")|(\\S+)").matcher(args);
>>    ArrayList argList = new ArrayList();
>> 
>>    while (match.find()) {
>>        if (match.group(1) == null) {
>>        	argList.add(match.group(2));
>>        } else {
>>        	argList.add(match.group(1));
>>        }
>>    }
>> 
>> Anyone want to give it a go/come up with a better regex?
>> 
>> The better way to fix as Peter said would just to use an
>>Array/arrayList and not go back and forth between Arrays and Strings.
>> 
>> Thanks,
>> Justin
>> 
>> 
>

Re: Getting Mustella to work.

Posted by Jose Barragan <jo...@codeoscopic.com>.

If anybody are working on mx, I'll try it

     [java] 
     [java] 
     [java] =====================================================
     [java]     Passes: 656
     [java]     Fails: 39
     [java] =====================================================
     [java] 
     [java] 
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

BUILD FAILED
/Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:1453: The following error occurred while executing this line:
/Users/pepebarragan/Developer/apache/flex/sdk/trunk/mustella/build.xml:1571: Java returned: 1

Total time: 18 minutes 28 seconds

Thanks,
Jose

On Aug 24, 2012, at 12:43 AM, Justin Mclean <ju...@classsoftware.com> wrote:

> Hi,
> 
>> I think I found that quotes are ok even on Mac.  Isn't the code that makes
>> the initial command line building it up out of pieces?  If so, I'd add the
>> quotes as the initial command line is getting built up.
> Need to be adde din about a dozen places but that's not too hard. However it still fails as the spilt ignore quotes.
> 
> This is the offending line:
>    defaultArgs=StringUtils.StringToArray(args);
> 
> Something along the lines of this may work (assuming quotes have been added).
> 
>    Matcher match = Pattern.compile("([^\\S]*\"[^\"]*\")|(\\S+)").matcher(args);
>    ArrayList argList = new ArrayList();
> 
>    while (match.find()) {
>        if (match.group(1) == null) {
>        	argList.add(match.group(2));
>        } else {
>        	argList.add(match.group(1));
>        }
>    }
> 
> Anyone want to give it a go/come up with a better regex?
> 
> The better way to fix as Peter said would just to use an Array/arrayList and not go back and forth between Arrays and Strings.
> 
> Thanks,
> Justin
> 
>

Re: Getting Mustella to work.

Posted by Justin Mclean <ju...@classsoftware.com>.

Hi,

> I think I found that quotes are ok even on Mac.  Isn't the code that makes
> the initial command line building it up out of pieces?  If so, I'd add the
> quotes as the initial command line is getting built up.
Need to be adde din about a dozen places but that's not too hard. However it still fails as the spilt ignore quotes.

This is the offending line:
    defaultArgs=StringUtils.StringToArray(args);

Something along the lines of this may work (assuming quotes have been added).

    Matcher match = Pattern.compile("([^\\S]*\"[^\"]*\")|(\\S+)").matcher(args);
    ArrayList argList = new ArrayList();
    
    while (match.find()) {
        if (match.group(1) == null) {
        	argList.add(match.group(2));
        } else {
        	argList.add(match.group(1));
        }
    }

Anyone want to give it a go/come up with a better regex?

The better way to fix as Peter said would just to use an Array/arrayList and not go back and forth between Arrays and Strings.

Thanks,
Justin

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

I think I found that quotes are ok even on Mac.  Isn't the code that makes
the initial command line building it up out of pieces?  If so, I'd add the
quotes as the initial command line is getting built up.  You might need to
test if quotes already exist in the piece.

But anyway, let's table the actual work for that until we get the tests
running.


On 8/23/12 9:13 AM, "Peter Ent" <pe...@adobe.com> wrote:

> The code makes an initial command line, then separates them into String[].
> A bit later it joins the String[] back to string, adds more arguments, and
> splits it again. I think it sounds simpler than it is, but that's the gist
> of it. I think the code should have been written to just create an
> ArrayList of all the arguments and then turn that into an Array when ready
> to launch the compiler; that's how I would ultimately solve it.
> 
> --peter
> 
> On 8/23/12 12:01 PM, "Alex Harui" <ah...@adobe.com> wrote:
> 
>> It might be better to figure out how to quote those entries.  Why was it
>> hard to do that as the command line gets built up?
>> 
>> 
>> On 8/23/12 8:55 AM, "Peter Ent" <pe...@adobe.com> wrote:
>> 
>>> Certainly appreciate the help. Here's a typical one when running
>>> Mustella:
>>> 
>>> -debug -define=CONFIG::skaha,false
>>> 
>>> -compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFontMa
>>> na
>>> ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>>> -source-path=/Users/pent/apache/flex/mustella/Assets
>>> -includes=ExcludeFileLocation -includes=SetShowRTE
>>> -includes=SaveBitmapFailures
>>> -includes=datagrid_properties_lockedColumnCount_mxml
>>> 
>>> -source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid/D
>>> at
>>> aGrid_SparkSkin/Properties --allow-source-path-overlap=true
>>> -includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>>> -source-path=/Users/pent/apache/flex/mustella/../frameworks/
>>> -source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>>> 
>>> Try changing my path, "/Users/pent/apache/" to something like
>>> "/Users/pent/apache with spaces/" to get a better example.
>>> 
>>> What happens in the code is that groups of these options may be coming
>>> from the environment, so you might find "-debug
>>> -define=CONFIG::skaha,false" being added as a single entity. Then code
>>> turns what it has at the moment into a String[] and passes that to
>>> another
>>> function that might add more arguments. If that function does, it will
>>> turn the String[] back into a String, add the arguments, then turn it
>>> back
>>> into String[]. 
>>> 
>>> But if you can make something that will convert the args into an
>>> acceptable String[] it would be super-helpful.
>>> 
>>> Thanks!
>>> --peter
>>> 
>>> On 8/23/12 11:44 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>> wrote:
>>> 
>>>> String.split(regexpattern)  can match pretty much anything.  Definitely
>>>> would be able to comeup with a pattern to match embedded dashes.
>>>> 
>>>> I'll see if I can come up with something that can properly strip down a
>>>> completed command with arguments.  If you would give me a more complex
>>>> command line that would be great.  I can test against it.
>>>> 
>>>> Currently my setup uses few command line arguments and instead adds to
>>>> the "-load-config+=mycustomconfig.xml"
>>>> 
>>>> -----Original Message-----
>>>> From: Peter Ent [mailto:pent@adobe.com]
>>>> Sent: Thursday, August 23, 2012 10:52
>>>> To: flex-dev@incubator.apache.org
>>>> Subject: Re: Getting Mustella to work.
>>>> 
>>>> I tried something like that, but there are options like: -source-path=
>>>> with a hyphen in the option and a couple that begin with double
>>>> hyphens.
>>>> I started to switch over to String.split(" -") to break apart on the
>>>> space+dash but then ran into this mysterious problem of mxmlc not
>>>> liking
>>>> the arguments it was given, even though, as far as I can tell, it was
>>>> getting the same ones in the same order. Obviously that wasn't the
>>>> case,
>>>> but had trouble tracking it down, so it is on hold for now while we get
>>>> the tests to run, unless someone else wants to take a stab at it.
>>>> 
>>>> --peter
>>>> 
>>>> On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>>> wrote:
>>>> 
>>>>> I'm not sure what Mustella is written in, but would something generic
>>>>> like this work?
>>>>> 
>>>>> If a string needs to be turned into an array then maybe... Use the "-"
>>>>> as the first delimiter to break apart the options and use a temp
>>>>> array.
>>>>> Then use the "=" to break out the names from the values.
>>>>> 
>>>>> Keeping two arrays with the same number of elements.  One array stores
>>>>> the argument name and the second argument value.
>>>>> 
>>>>> //Declare arrays/string
>>>>> string [] saNames = {"Option1", "Option2", "Option3"}; string []
>>>>> saValues = {"My value with spaces", "test2", "test 3"}; string
>>>>> sCombinedOptions = "";
>>>>> 
>>>>> //Loop through all elements in arrays
>>>>> for (;;)
>>>>> {
>>>>>   //Combine names / values.
>>>>>   sCombinedOptions += saNames[currentItem] + "=""" +
>>>>> saValues[currentItem] + """ "; }
>>>>> 
>>>>> 
>>>>> //Add the command line and options.
>>>>> "path\mxmlc.exe" + " " + sCombinedOptions;
>>>>> 
>>>>> 
>>>>> -----Original Message-----
>>>>> From: Peter Ent [mailto:pent@adobe.com]
>>>>> Sent: Thursday, August 23, 2012 9:33
>>>>> To: flex-dev@incubator.apache.org
>>>>> Subject: Re: Getting Mustella to work.
>>>>> 
>>>>> That ought to work, but does not. The Mustella code pieces together a
>>>>> large string with all of the options on it, then turns the string into
>>>>> a String[] by using space as the delimiter. Thus
>>>>> 
>>>>> -source-path="C:\Program Files\Common Files\Microsoft
>>>>> Shared\MSInfo\MSInfo32.exe"
>>>>> 
>>>>> turns into
>>>>> [] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>>>>> Shared\MSInfo\MSInfo32.exe"
>>>>> 
>>>>> And it does this several times (turning the array into a string,
>>>>> inserting other args, back to an array) to build up the argument list.
>>>>> Ultimately, the array of options is passed over to mxmlc to execute,
>>>>> so
>>>>> it does need to turn into an array of options. I was working on
>>>>> putting
>>>>> everything into an ArrayList but more and more code needed to change
>>>>> and then I was getting errors from mxmlc saying parameters were being
>>>>> mixed which I didn't understand since it was getting the same
>>>>> parameters in the same order.
>>>>> 
>>>>> So I have to re-think the approach.
>>>>> 
>>>>> --peter
>>>>> 
>>>>> On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>>>> wrote:
>>>>> 
>>>>>> I know this may sound silly, but windows deals with the spaces in
>>>>>> path
>>>>>> using quotes around the whole path.  Is there something similar with
>>>>>> Mustella?
>>>>>> 
>>>>>> So a windows command prompt example, I could do something like the
>>>>>> following...
>>>>>> "C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>>>>> 
>>>>>> 
>>>>>> Whereas the old non spaced dos style naming convention would do this
>>>>>> without quotes..
>>>>>> c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>>>>> 
>>>>>> 
>>>>>> r/s
>>>>>> -Mark
>>>>>> 
>>>>>> -----Original Message-----
>>>>>> From: Peter Ent [mailto:pent@adobe.com]
>>>>>> Sent: Wednesday, August 22, 2012 9:20
>>>>>> To: flex-dev@incubator.apache.org
>>>>>> Subject: Re: Getting Mustella to work.
>>>>>> 
>>>>>> I have not have luck solving the problem. It is much trickier than I
>>>>>> anticipated. I am going to jump back into getting more tests to run
>>>>>> and think more about the problem. Operating systems have allowed
>>>>>> spaces in file names for many, many years and you'd think would be an
>>>>>> easily solvable problem (or not even a problem at all).
>>>>>> 
>>>>>> --peter
>>>>>> 
>>>>>> On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com>
>>>>>> wrote:
>>>>>> 
>>>>>>> Hi,
>>>>>>> 
>>>>>>> If the space path issue was fixed you have more to add. Any luck
>>>>>>> with
>>>>>>> that yet?
>>>>>>> 
>>>>>>> Justin
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>> -- 
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

The code makes an initial command line, then separates them into String[].
A bit later it joins the String[] back to string, adds more arguments, and
splits it again. I think it sounds simpler than it is, but that's the gist
of it. I think the code should have been written to just create an
ArrayList of all the arguments and then turn that into an Array when ready
to launch the compiler; that's how I would ultimately solve it.

--peter

On 8/23/12 12:01 PM, "Alex Harui" <ah...@adobe.com> wrote:

>It might be better to figure out how to quote those entries.  Why was it
>hard to do that as the command line gets built up?
>
>
>On 8/23/12 8:55 AM, "Peter Ent" <pe...@adobe.com> wrote:
>
>> Certainly appreciate the help. Here's a typical one when running
>>Mustella:
>> 
>> -debug -define=CONFIG::skaha,false
>> 
>>-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFontMa
>>na
>> ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
>> -source-path=/Users/pent/apache/flex/mustella/Assets
>> -includes=ExcludeFileLocation -includes=SetShowRTE
>> -includes=SaveBitmapFailures
>> -includes=datagrid_properties_lockedColumnCount_mxml
>> 
>>-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid/D
>>at
>> aGrid_SparkSkin/Properties --allow-source-path-overlap=true
>> -includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
>> -source-path=/Users/pent/apache/flex/mustella/../frameworks/
>> -source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
>> 
>> Try changing my path, "/Users/pent/apache/" to something like
>> "/Users/pent/apache with spaces/" to get a better example.
>> 
>> What happens in the code is that groups of these options may be coming
>> from the environment, so you might find "-debug
>> -define=CONFIG::skaha,false" being added as a single entity. Then code
>> turns what it has at the moment into a String[] and passes that to
>>another
>> function that might add more arguments. If that function does, it will
>> turn the String[] back into a String, add the arguments, then turn it
>>back
>> into String[].  
>> 
>> But if you can make something that will convert the args into an
>> acceptable String[] it would be super-helpful.
>> 
>> Thanks!
>> --peter
>> 
>> On 8/23/12 11:44 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>> wrote:
>> 
>>> String.split(regexpattern)  can match pretty much anything.  Definitely
>>> would be able to comeup with a pattern to match embedded dashes.
>>> 
>>> I'll see if I can come up with something that can properly strip down a
>>> completed command with arguments.  If you would give me a more complex
>>> command line that would be great.  I can test against it.
>>> 
>>> Currently my setup uses few command line arguments and instead adds to
>>> the "-load-config+=mycustomconfig.xml"
>>> 
>>> -----Original Message-----
>>> From: Peter Ent [mailto:pent@adobe.com]
>>> Sent: Thursday, August 23, 2012 10:52
>>> To: flex-dev@incubator.apache.org
>>> Subject: Re: Getting Mustella to work.
>>> 
>>> I tried something like that, but there are options like: -source-path=
>>> with a hyphen in the option and a couple that begin with double
>>>hyphens.
>>> I started to switch over to String.split(" -") to break apart on the
>>> space+dash but then ran into this mysterious problem of mxmlc not
>>>liking
>>> the arguments it was given, even though, as far as I can tell, it was
>>> getting the same ones in the same order. Obviously that wasn't the
>>>case,
>>> but had trouble tracking it down, so it is on hold for now while we get
>>> the tests to run, unless someone else wants to take a stab at it.
>>> 
>>> --peter
>>> 
>>> On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>> wrote:
>>> 
>>>> I'm not sure what Mustella is written in, but would something generic
>>>> like this work?
>>>> 
>>>> If a string needs to be turned into an array then maybe... Use the "-"
>>>> as the first delimiter to break apart the options and use a temp
>>>>array.
>>>> Then use the "=" to break out the names from the values.
>>>> 
>>>> Keeping two arrays with the same number of elements.  One array stores
>>>> the argument name and the second argument value.
>>>> 
>>>> //Declare arrays/string
>>>> string [] saNames = {"Option1", "Option2", "Option3"}; string []
>>>> saValues = {"My value with spaces", "test2", "test 3"}; string
>>>> sCombinedOptions = "";
>>>> 
>>>> //Loop through all elements in arrays
>>>> for (;;)
>>>> {
>>>>   //Combine names / values.
>>>>   sCombinedOptions += saNames[currentItem] + "=""" +
>>>> saValues[currentItem] + """ "; }
>>>> 
>>>> 
>>>> //Add the command line and options.
>>>> "path\mxmlc.exe" + " " + sCombinedOptions;
>>>> 
>>>> 
>>>> -----Original Message-----
>>>> From: Peter Ent [mailto:pent@adobe.com]
>>>> Sent: Thursday, August 23, 2012 9:33
>>>> To: flex-dev@incubator.apache.org
>>>> Subject: Re: Getting Mustella to work.
>>>> 
>>>> That ought to work, but does not. The Mustella code pieces together a
>>>> large string with all of the options on it, then turns the string into
>>>> a String[] by using space as the delimiter. Thus
>>>> 
>>>> -source-path="C:\Program Files\Common Files\Microsoft
>>>> Shared\MSInfo\MSInfo32.exe"
>>>> 
>>>> turns into
>>>> [] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>>>> Shared\MSInfo\MSInfo32.exe"
>>>> 
>>>> And it does this several times (turning the array into a string,
>>>> inserting other args, back to an array) to build up the argument list.
>>>> Ultimately, the array of options is passed over to mxmlc to execute,
>>>>so
>>>> it does need to turn into an array of options. I was working on
>>>>putting
>>>> everything into an ArrayList but more and more code needed to change
>>>> and then I was getting errors from mxmlc saying parameters were being
>>>> mixed which I didn't understand since it was getting the same
>>>> parameters in the same order.
>>>> 
>>>> So I have to re-think the approach.
>>>> 
>>>> --peter
>>>> 
>>>> On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>>> wrote:
>>>> 
>>>>> I know this may sound silly, but windows deals with the spaces in
>>>>>path
>>>>> using quotes around the whole path.  Is there something similar with
>>>>> Mustella?
>>>>> 
>>>>> So a windows command prompt example, I could do something like the
>>>>> following...
>>>>> "C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>>>> 
>>>>> 
>>>>> Whereas the old non spaced dos style naming convention would do this
>>>>> without quotes..
>>>>> c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>>>> 
>>>>> 
>>>>> r/s
>>>>> -Mark
>>>>> 
>>>>> -----Original Message-----
>>>>> From: Peter Ent [mailto:pent@adobe.com]
>>>>> Sent: Wednesday, August 22, 2012 9:20
>>>>> To: flex-dev@incubator.apache.org
>>>>> Subject: Re: Getting Mustella to work.
>>>>> 
>>>>> I have not have luck solving the problem. It is much trickier than I
>>>>> anticipated. I am going to jump back into getting more tests to run
>>>>> and think more about the problem. Operating systems have allowed
>>>>> spaces in file names for many, many years and you'd think would be an
>>>>> easily solvable problem (or not even a problem at all).
>>>>> 
>>>>> --peter
>>>>> 
>>>>> On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com>
>>>>>wrote:
>>>>> 
>>>>>> Hi,
>>>>>> 
>>>>>> If the space path issue was fixed you have more to add. Any luck
>>>>>>with
>>>>>> that yet?
>>>>>> 
>>>>>> Justin
>>>>> 
>>>> 
>>> 
>> 
>
>-- 
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

It might be better to figure out how to quote those entries.  Why was it
hard to do that as the command line gets built up?


On 8/23/12 8:55 AM, "Peter Ent" <pe...@adobe.com> wrote:

> Certainly appreciate the help. Here's a typical one when running Mustella:
> 
> -debug -define=CONFIG::skaha,false
> -compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFontMana
> ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
> -source-path=/Users/pent/apache/flex/mustella/Assets
> -includes=ExcludeFileLocation -includes=SetShowRTE
> -includes=SaveBitmapFailures
> -includes=datagrid_properties_lockedColumnCount_mxml
> -source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid/Dat
> aGrid_SparkSkin/Properties --allow-source-path-overlap=true
> -includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
> -source-path=/Users/pent/apache/flex/mustella/../frameworks/
> -source-path=/Users/pent/apache/flex/mustella/as3/src/mustella
> 
> Try changing my path, "/Users/pent/apache/" to something like
> "/Users/pent/apache with spaces/" to get a better example.
> 
> What happens in the code is that groups of these options may be coming
> from the environment, so you might find "-debug
> -define=CONFIG::skaha,false" being added as a single entity. Then code
> turns what it has at the moment into a String[] and passes that to another
> function that might add more arguments. If that function does, it will
> turn the String[] back into a String, add the arguments, then turn it back
> into String[].  
> 
> But if you can make something that will convert the args into an
> acceptable String[] it would be super-helpful.
> 
> Thanks!
> --peter
> 
> On 8/23/12 11:44 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
> wrote:
> 
>> String.split(regexpattern)  can match pretty much anything.  Definitely
>> would be able to comeup with a pattern to match embedded dashes.
>> 
>> I'll see if I can come up with something that can properly strip down a
>> completed command with arguments.  If you would give me a more complex
>> command line that would be great.  I can test against it.
>> 
>> Currently my setup uses few command line arguments and instead adds to
>> the "-load-config+=mycustomconfig.xml"
>> 
>> -----Original Message-----
>> From: Peter Ent [mailto:pent@adobe.com]
>> Sent: Thursday, August 23, 2012 10:52
>> To: flex-dev@incubator.apache.org
>> Subject: Re: Getting Mustella to work.
>> 
>> I tried something like that, but there are options like: -source-path=
>> with a hyphen in the option and a couple that begin with double hyphens.
>> I started to switch over to String.split(" -") to break apart on the
>> space+dash but then ran into this mysterious problem of mxmlc not liking
>> the arguments it was given, even though, as far as I can tell, it was
>> getting the same ones in the same order. Obviously that wasn't the case,
>> but had trouble tracking it down, so it is on hold for now while we get
>> the tests to run, unless someone else wants to take a stab at it.
>> 
>> --peter
>> 
>> On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>> wrote:
>> 
>>> I'm not sure what Mustella is written in, but would something generic
>>> like this work?
>>> 
>>> If a string needs to be turned into an array then maybe... Use the "-"
>>> as the first delimiter to break apart the options and use a temp array.
>>> Then use the "=" to break out the names from the values.
>>> 
>>> Keeping two arrays with the same number of elements.  One array stores
>>> the argument name and the second argument value.
>>> 
>>> //Declare arrays/string
>>> string [] saNames = {"Option1", "Option2", "Option3"}; string []
>>> saValues = {"My value with spaces", "test2", "test 3"}; string
>>> sCombinedOptions = "";
>>> 
>>> //Loop through all elements in arrays
>>> for (;;)
>>> {
>>>   //Combine names / values.
>>>   sCombinedOptions += saNames[currentItem] + "=""" +
>>> saValues[currentItem] + """ "; }
>>> 
>>> 
>>> //Add the command line and options.
>>> "path\mxmlc.exe" + " " + sCombinedOptions;
>>> 
>>> 
>>> -----Original Message-----
>>> From: Peter Ent [mailto:pent@adobe.com]
>>> Sent: Thursday, August 23, 2012 9:33
>>> To: flex-dev@incubator.apache.org
>>> Subject: Re: Getting Mustella to work.
>>> 
>>> That ought to work, but does not. The Mustella code pieces together a
>>> large string with all of the options on it, then turns the string into
>>> a String[] by using space as the delimiter. Thus
>>> 
>>> -source-path="C:\Program Files\Common Files\Microsoft
>>> Shared\MSInfo\MSInfo32.exe"
>>> 
>>> turns into
>>> [] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>>> Shared\MSInfo\MSInfo32.exe"
>>> 
>>> And it does this several times (turning the array into a string,
>>> inserting other args, back to an array) to build up the argument list.
>>> Ultimately, the array of options is passed over to mxmlc to execute, so
>>> it does need to turn into an array of options. I was working on putting
>>> everything into an ArrayList but more and more code needed to change
>>> and then I was getting errors from mxmlc saying parameters were being
>>> mixed which I didn't understand since it was getting the same
>>> parameters in the same order.
>>> 
>>> So I have to re-think the approach.
>>> 
>>> --peter
>>> 
>>> On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>> wrote:
>>> 
>>>> I know this may sound silly, but windows deals with the spaces in path
>>>> using quotes around the whole path.  Is there something similar with
>>>> Mustella?
>>>> 
>>>> So a windows command prompt example, I could do something like the
>>>> following...
>>>> "C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>>> 
>>>> 
>>>> Whereas the old non spaced dos style naming convention would do this
>>>> without quotes..
>>>> c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>>> 
>>>> 
>>>> r/s
>>>> -Mark
>>>> 
>>>> -----Original Message-----
>>>> From: Peter Ent [mailto:pent@adobe.com]
>>>> Sent: Wednesday, August 22, 2012 9:20
>>>> To: flex-dev@incubator.apache.org
>>>> Subject: Re: Getting Mustella to work.
>>>> 
>>>> I have not have luck solving the problem. It is much trickier than I
>>>> anticipated. I am going to jump back into getting more tests to run
>>>> and think more about the problem. Operating systems have allowed
>>>> spaces in file names for many, many years and you'd think would be an
>>>> easily solvable problem (or not even a problem at all).
>>>> 
>>>> --peter
>>>> 
>>>> On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> If the space path issue was fixed you have more to add. Any luck with
>>>>> that yet?
>>>>> 
>>>>> Justin
>>>> 
>>> 
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Certainly appreciate the help. Here's a typical one when running Mustella:

-debug -define=CONFIG::skaha,false
-compiler.fonts.managers=flash.fonts.JREFontManager,flash.fonts.AFEFontMana
ger,flash.fonts.BatikFontManager,flash.fonts.CFFFontManager
-source-path=/Users/pent/apache/flex/mustella/Assets
-includes=ExcludeFileLocation -includes=SetShowRTE
-includes=SaveBitmapFailures
-includes=datagrid_properties_lockedColumnCount_mxml
-source-path=/Users/pent/apache/flex/mustella/tests/components/DataGrid/Dat
aGrid_SparkSkin/Properties --allow-source-path-overlap=true
-includes=SendResultsToRunner  -includes=ExitWhenDone -source-path=.
-source-path=/Users/pent/apache/flex/mustella/../frameworks/
-source-path=/Users/pent/apache/flex/mustella/as3/src/mustella

Try changing my path, "/Users/pent/apache/" to something like
"/Users/pent/apache with spaces/" to get a better example.

What happens in the code is that groups of these options may be coming
from the environment, so you might find "-debug
-define=CONFIG::skaha,false" being added as a single entity. Then code
turns what it has at the moment into a String[] and passes that to another
function that might add more arguments. If that function does, it will
turn the String[] back into a String, add the arguments, then turn it back
into String[].  

But if you can make something that will convert the args into an
acceptable String[] it would be super-helpful.

Thanks!
--peter

On 8/23/12 11:44 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
wrote:

>String.split(regexpattern)  can match pretty much anything.  Definitely
>would be able to comeup with a pattern to match embedded dashes.
>
>I'll see if I can come up with something that can properly strip down a
>completed command with arguments.  If you would give me a more complex
>command line that would be great.  I can test against it.
>
>Currently my setup uses few command line arguments and instead adds to
>the "-load-config+=mycustomconfig.xml"
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 10:52
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>I tried something like that, but there are options like: -source-path=
>with a hyphen in the option and a couple that begin with double hyphens.
>I started to switch over to String.split(" -") to break apart on the
>space+dash but then ran into this mysterious problem of mxmlc not liking
>the arguments it was given, even though, as far as I can tell, it was
>getting the same ones in the same order. Obviously that wasn't the case,
>but had trouble tracking it down, so it is on hold for now while we get
>the tests to run, unless someone else wants to take a stab at it.
>
>--peter
>
>On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>I'm not sure what Mustella is written in, but would something generic
>>like this work?
>>
>>If a string needs to be turned into an array then maybe... Use the "-"
>>as the first delimiter to break apart the options and use a temp array.
>>Then use the "=" to break out the names from the values.
>>
>>Keeping two arrays with the same number of elements.  One array stores
>>the argument name and the second argument value.
>>
>>//Declare arrays/string
>>string [] saNames = {"Option1", "Option2", "Option3"}; string []
>>saValues = {"My value with spaces", "test2", "test 3"}; string
>>sCombinedOptions = "";
>>
>>//Loop through all elements in arrays
>>for (;;)
>>{
>>   //Combine names / values.
>>   sCombinedOptions += saNames[currentItem] + "=""" +
>>saValues[currentItem] + """ "; }
>>
>>
>>//Add the command line and options.
>>"path\mxmlc.exe" + " " + sCombinedOptions;
>>
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Thursday, August 23, 2012 9:33
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>That ought to work, but does not. The Mustella code pieces together a
>>large string with all of the options on it, then turns the string into
>>a String[] by using space as the delimiter. Thus
>>
>>-source-path="C:\Program Files\Common Files\Microsoft
>>Shared\MSInfo\MSInfo32.exe"
>>
>>turns into
>>[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>>Shared\MSInfo\MSInfo32.exe"
>>
>>And it does this several times (turning the array into a string,
>>inserting other args, back to an array) to build up the argument list.
>>Ultimately, the array of options is passed over to mxmlc to execute, so
>>it does need to turn into an array of options. I was working on putting
>>everything into an ArrayList but more and more code needed to change
>>and then I was getting errors from mxmlc saying parameters were being
>>mixed which I didn't understand since it was getting the same
>>parameters in the same order.
>>
>>So I have to re-think the approach.
>>
>>--peter
>>
>>On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>>wrote:
>>
>>>I know this may sound silly, but windows deals with the spaces in path
>>>using quotes around the whole path.  Is there something similar with
>>>Mustella?
>>>
>>>So a windows command prompt example, I could do something like the
>>>following...
>>>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>>
>>>
>>>Whereas the old non spaced dos style naming convention would do this
>>>without quotes..
>>>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>>
>>>
>>>r/s
>>>-Mark
>>>
>>>-----Original Message-----
>>>From: Peter Ent [mailto:pent@adobe.com]
>>>Sent: Wednesday, August 22, 2012 9:20
>>>To: flex-dev@incubator.apache.org
>>>Subject: Re: Getting Mustella to work.
>>>
>>>I have not have luck solving the problem. It is much trickier than I
>>>anticipated. I am going to jump back into getting more tests to run
>>>and think more about the problem. Operating systems have allowed
>>>spaces in file names for many, many years and you'd think would be an
>>>easily solvable problem (or not even a problem at all).
>>>
>>>--peter
>>>
>>>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>>
>>>>Hi,
>>>>
>>>>If the space path issue was fixed you have more to add. Any luck with
>>>>that yet?
>>>>
>>>>Justin
>>>
>>
>

RE: Getting Mustella to work.

Posted by Kessler CTR Mark J <ma...@usmc.mil>.

String.split(regexpattern)  can match pretty much anything.  Definitely would be able to comeup with a pattern to match embedded dashes.

I'll see if I can come up with something that can properly strip down a completed command with arguments.  If you would give me a more complex command line that would be great.  I can test against it.

Currently my setup uses few command line arguments and instead adds to the "-load-config+=mycustomconfig.xml"

-----Original Message-----
From: Peter Ent [mailto:pent@adobe.com] 
Sent: Thursday, August 23, 2012 10:52
To: flex-dev@incubator.apache.org
Subject: Re: Getting Mustella to work.

I tried something like that, but there are options like: -source-path= with a hyphen in the option and a couple that begin with double hyphens. I started to switch over to String.split(" -") to break apart on the
space+dash but then ran into this mysterious problem of mxmlc not liking
the arguments it was given, even though, as far as I can tell, it was getting the same ones in the same order. Obviously that wasn't the case, but had trouble tracking it down, so it is on hold for now while we get the tests to run, unless someone else wants to take a stab at it.

--peter

On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
wrote:

>I'm not sure what Mustella is written in, but would something generic 
>like this work?
>
>If a string needs to be turned into an array then maybe... Use the "-" 
>as the first delimiter to break apart the options and use a temp array. 
>Then use the "=" to break out the names from the values.
>
>Keeping two arrays with the same number of elements.  One array stores 
>the argument name and the second argument value.
>
>//Declare arrays/string
>string [] saNames = {"Option1", "Option2", "Option3"}; string [] 
>saValues = {"My value with spaces", "test2", "test 3"}; string 
>sCombinedOptions = "";
>
>//Loop through all elements in arrays
>for (;;)
>{
>   //Combine names / values.
>   sCombinedOptions += saNames[currentItem] + "=""" + 
>saValues[currentItem] + """ "; }
>
>
>//Add the command line and options.
>"path\mxmlc.exe" + " " + sCombinedOptions;
>
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 9:33
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>That ought to work, but does not. The Mustella code pieces together a 
>large string with all of the options on it, then turns the string into 
>a String[] by using space as the delimiter. Thus
>
>-source-path="C:\Program Files\Common Files\Microsoft 
>Shared\MSInfo\MSInfo32.exe"
>
>turns into
>[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] = 
>Shared\MSInfo\MSInfo32.exe"
>
>And it does this several times (turning the array into a string, 
>inserting other args, back to an array) to build up the argument list.
>Ultimately, the array of options is passed over to mxmlc to execute, so 
>it does need to turn into an array of options. I was working on putting 
>everything into an ArrayList but more and more code needed to change 
>and then I was getting errors from mxmlc saying parameters were being 
>mixed which I didn't understand since it was getting the same 
>parameters in the same order.
>
>So I have to re-think the approach.
>
>--peter
>
>On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>I know this may sound silly, but windows deals with the spaces in path 
>>using quotes around the whole path.  Is there something similar with 
>>Mustella?
>>
>>So a windows command prompt example, I could do something like the 
>>following...
>>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>
>>
>>Whereas the old non spaced dos style naming convention would do this 
>>without quotes..
>>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>
>>
>>r/s
>>-Mark
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Wednesday, August 22, 2012 9:20
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>I have not have luck solving the problem. It is much trickier than I 
>>anticipated. I am going to jump back into getting more tests to run 
>>and think more about the problem. Operating systems have allowed 
>>spaces in file names for many, many years and you'd think would be an 
>>easily solvable problem (or not even a problem at all).
>>
>>--peter
>>
>>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>
>>>Hi,
>>>
>>>If the space path issue was fixed you have more to add. Any luck with 
>>>that yet?
>>>
>>>Justin
>>
>

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I tried something like that, but there are options like: -source-path=
with a hyphen in the option and a couple that begin with double hyphens. I
started to switch over to String.split(" -") to break apart on the
space+dash but then ran into this mysterious problem of mxmlc not liking
the arguments it was given, even though, as far as I can tell, it was
getting the same ones in the same order. Obviously that wasn't the case,
but had trouble tracking it down, so it is on hold for now while we get
the tests to run, unless someone else wants to take a stab at it.

--peter

On 8/23/12 10:43 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
wrote:

>I'm not sure what Mustella is written in, but would something generic
>like this work?  
>
>If a string needs to be turned into an array then maybe... Use the "-" as
>the first delimiter to break apart the options and use a temp array. Then
>use the "=" to break out the names from the values.
>
>Keeping two arrays with the same number of elements.  One array stores
>the argument name and the second argument value.
>
>//Declare arrays/string
>string [] saNames = {"Option1", "Option2", "Option3"};
>string [] saValues = {"My value with spaces", "test2", "test 3"};
>string sCombinedOptions = "";
>
>//Loop through all elements in arrays
>for (;;)
>{
>   //Combine names / values.
>   sCombinedOptions += saNames[currentItem] + "=""" +
>saValues[currentItem] + """ ";
>}
>
>
>//Add the command line and options.
>"path\mxmlc.exe" + " " + sCombinedOptions;
>
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Thursday, August 23, 2012 9:33
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>That ought to work, but does not. The Mustella code pieces together a
>large string with all of the options on it, then turns the string into a
>String[] by using space as the delimiter. Thus
>
>-source-path="C:\Program Files\Common Files\Microsoft
>Shared\MSInfo\MSInfo32.exe"
>
>turns into
>[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] =
>Shared\MSInfo\MSInfo32.exe"
>
>And it does this several times (turning the array into a string,
>inserting other args, back to an array) to build up the argument list.
>Ultimately, the array of options is passed over to mxmlc to execute, so
>it does need to turn into an array of options. I was working on putting
>everything into an ArrayList but more and more code needed to change and
>then I was getting errors from mxmlc saying parameters were being mixed
>which I didn't understand since it was getting the same parameters in the
>same order.
>
>So I have to re-think the approach.
>
>--peter
>
>On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil>
>wrote:
>
>>I know this may sound silly, but windows deals with the spaces in path
>>using quotes around the whole path.  Is there something similar with
>>Mustella?
>>
>>So a windows command prompt example, I could do something like the
>>following...
>>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>>
>>
>>Whereas the old non spaced dos style naming convention would do this
>>without quotes..
>>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>>
>>
>>r/s
>>-Mark
>>
>>-----Original Message-----
>>From: Peter Ent [mailto:pent@adobe.com]
>>Sent: Wednesday, August 22, 2012 9:20
>>To: flex-dev@incubator.apache.org
>>Subject: Re: Getting Mustella to work.
>>
>>I have not have luck solving the problem. It is much trickier than I
>>anticipated. I am going to jump back into getting more tests to run and
>>think more about the problem. Operating systems have allowed spaces in
>>file names for many, many years and you'd think would be an easily
>>solvable problem (or not even a problem at all).
>>
>>--peter
>>
>>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>>
>>>Hi,
>>>
>>>If the space path issue was fixed you have more to add. Any luck with
>>>that yet?
>>>
>>>Justin
>>
>

RE: Getting Mustella to work.

Posted by Kessler CTR Mark J <ma...@usmc.mil>.

I'm not sure what Mustella is written in, but would something generic like this work?  

If a string needs to be turned into an array then maybe... Use the "-" as the first delimiter to break apart the options and use a temp array. Then use the "=" to break out the names from the values.

Keeping two arrays with the same number of elements.  One array stores the argument name and the second argument value.

//Declare arrays/string
string [] saNames = {"Option1", "Option2", "Option3"};
string [] saValues = {"My value with spaces", "test2", "test 3"};
string sCombinedOptions = "";

//Loop through all elements in arrays
for (;;)
{
   //Combine names / values.
   sCombinedOptions += saNames[currentItem] + "=""" + saValues[currentItem] + """ ";
}

//Add the command line and options.
"path\mxmlc.exe" + " " + sCombinedOptions;

-----Original Message-----
From: Peter Ent [mailto:pent@adobe.com] 
Sent: Thursday, August 23, 2012 9:33
To: flex-dev@incubator.apache.org
Subject: Re: Getting Mustella to work.

That ought to work, but does not. The Mustella code pieces together a large string with all of the options on it, then turns the string into a String[] by using space as the delimiter. Thus

-source-path="C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"

turns into
[] = -source-path="C:\Program Files\Common [] = Files\Microsoft [] = Shared\MSInfo\MSInfo32.exe"

And it does this several times (turning the array into a string, inserting other args, back to an array) to build up the argument list. Ultimately, the array of options is passed over to mxmlc to execute, so it does need to turn into an array of options. I was working on putting everything into an ArrayList but more and more code needed to change and then I was getting errors from mxmlc saying parameters were being mixed which I didn't understand since it was getting the same parameters in the same order.

So I have to re-think the approach.

--peter

On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:

>I know this may sound silly, but windows deals with the spaces in path 
>using quotes around the whole path.  Is there something similar with 
>Mustella?
>
>So a windows command prompt example, I could do something like the 
>following...
>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>
>
>Whereas the old non spaced dos style naming convention would do this 
>without quotes..
>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>
>
>r/s
>-Mark
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Wednesday, August 22, 2012 9:20
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>I have not have luck solving the problem. It is much trickier than I 
>anticipated. I am going to jump back into getting more tests to run and 
>think more about the problem. Operating systems have allowed spaces in 
>file names for many, many years and you'd think would be an easily 
>solvable problem (or not even a problem at all).
>
>--peter
>
>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
>>Hi,
>>
>>If the space path issue was fixed you have more to add. Any luck with 
>>that yet?
>>
>>Justin
>

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

That ought to work, but does not. The Mustella code pieces together a
large string with all of the options on it, then turns the string into a
String[] by using space as the delimiter. Thus

-source-path="C:\Program Files\Common Files\Microsoft
Shared\MSInfo\MSInfo32.exe"

turns into
[] = -source-path="C:\Program Files\Common
[] = Files\Microsoft
[] = Shared\MSInfo\MSInfo32.exe"

And it does this several times (turning the array into a string, inserting
other args, back to an array) to build up the argument list. Ultimately,
the array of options is passed over to mxmlc to execute, so it does need
to turn into an array of options. I was working on putting everything into
an ArrayList but more and more code needed to change and then I was
getting errors from mxmlc saying parameters were being mixed which I
didn't understand since it was getting the same parameters in the same
order.

So I have to re-think the approach.

--peter

On 8/23/12 6:59 AM, "Kessler CTR Mark J" <ma...@usmc.mil> wrote:

>I know this may sound silly, but windows deals with the spaces in path
>using quotes around the whole path.  Is there something similar with
>Mustella?
>
>So a windows command prompt example, I could do something like the
>following...
>"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"
>
>
>Whereas the old non spaced dos style naming convention would do this
>without quotes..
>c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe
>
>
>r/s
>-Mark
>
>-----Original Message-----
>From: Peter Ent [mailto:pent@adobe.com]
>Sent: Wednesday, August 22, 2012 9:20
>To: flex-dev@incubator.apache.org
>Subject: Re: Getting Mustella to work.
>
>I have not have luck solving the problem. It is much trickier than I
>anticipated. I am going to jump back into getting more tests to run and
>think more about the problem. Operating systems have allowed spaces in
>file names for many, many years and you'd think would be an easily
>solvable problem (or not even a problem at all).
>
>--peter
>
>On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
>
>>Hi,
>>
>>If the space path issue was fixed you have more to add. Any luck with
>>that yet?
>>
>>Justin
>

RE: Getting Mustella to work.

Posted by Kessler CTR Mark J <ma...@usmc.mil>.

I know this may sound silly, but windows deals with the spaces in path using quotes around the whole path.  Is there something similar with Mustella?

So a windows command prompt example, I could do something like the following...
"C:\Program Files\Common Files\Microsoft Shared\MSInfo\MSInfo32.exe"

Whereas the old non spaced dos style naming convention would do this without quotes..
c:\progra~1\common~1\micros~1\msinfo\MSInfo32.exe

r/s
-Mark

-----Original Message-----
From: Peter Ent [mailto:pent@adobe.com] 
Sent: Wednesday, August 22, 2012 9:20
To: flex-dev@incubator.apache.org
Subject: Re: Getting Mustella to work.

I have not have luck solving the problem. It is much trickier than I anticipated. I am going to jump back into getting more tests to run and think more about the problem. Operating systems have allowed spaces in file names for many, many years and you'd think would be an easily solvable problem (or not even a problem at all).

--peter

On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

>Hi,
>
>If the space path issue was fixed you have more to add. Any luck with 
>that yet?
>
>Justin

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I have not have luck solving the problem. It is much trickier than I
anticipated. I am going to jump back into getting more tests to run and
think more about the problem. Operating systems have allowed spaces in
file names for many, many years and you'd think would be an easily
solvable problem (or not even a problem at all).

--peter

On 8/21/12 11:12 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:

>Hi,
>
>If the space path issue was fixed you have more to add. Any luck with
>that yet?
>
>Justin

Re: Getting Mustella to work.

Posted by Justin Mclean <ju...@classsoftware.com>.

Hi,

If the space path issue was fixed you have more to add. Any luck with that yet?

Justin

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

The wiki is updated with Carlos' test data. I will continue with the
tests/components directory

On 8/21/12 10:56 PM, "Peter Ent" <pe...@adobe.com> wrote:

>I will check for all the emails from Carlos tomorrow morning and get them
>all in at once. Since Carlos is being very active I'll try to keep up!
>
>Thanks, Carlos!
>--peter
>
>On 8/21/12 5:31 PM, "Alex Harui" <ah...@adobe.com> wrote:
>
>>Hi Carlos,
>>
>>That's awesome.  Thanks for pitching in.  Peter, can you update the wiki?
>>
>>An interesting thing for you to do is before you quit working for the
>>day,
>>run mini_run.sh -all and see what you get in the morning.  The failures
>>will
>>point to folders to work on.  Review this thread for what others are
>>working
>>on.  I've working on the entire spark folder, for example.
>>
>>-Alex
>>
>>
>>On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com>
>>wrote:
>>
>>> Ops! I reboot Terminal and pass it again and all is ok with
>>>"GraphicTags"...
>>> 
>>> [java] =====================================================
>>>      [java]     Passes: 3
>>>      [java]     Fails: 0
>>>      [java] =====================================================
>>> 
>>> 
>>> So It's needed at least two passes when a time out is thrown...I'm
>>> finishing to understand mustella ;)
>>> 
>>> 
>>> 
>>> 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
>>> 
>>>> 
>>>> but "tests/GraphicTags/"
>>>> 
>>>> reports
>>>> [java] =====================================================
>>>>      [java]     Passes: 2
>>>>      [java]     Fails: 1
>>>>      [java] =====================================================
>>>> 
>>>> so I'll fix GraphicTags
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Carlos Rovira
>>>> Director de Tecnología
>>>> 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ón, 32
>>>> Planta 10, Puertas P-Q
>>>> 28020 Madrid
>>>> 
>>>> 
>>> 
>>
>>-- 
>>Alex Harui
>>Flex SDK Team
>>Adobe Systems, Inc.
>>http://blogs.adobe.com/aharui
>>
>

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I will check for all the emails from Carlos tomorrow morning and get them
all in at once. Since Carlos is being very active I'll try to keep up!

Thanks, Carlos!
--peter

On 8/21/12 5:31 PM, "Alex Harui" <ah...@adobe.com> wrote:

>Hi Carlos,
>
>That's awesome.  Thanks for pitching in.  Peter, can you update the wiki?
>
>An interesting thing for you to do is before you quit working for the day,
>run mini_run.sh -all and see what you get in the morning.  The failures
>will
>point to folders to work on.  Review this thread for what others are
>working
>on.  I've working on the entire spark folder, for example.
>
>-Alex
>
>
>On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
>> Ops! I reboot Terminal and pass it again and all is ok with
>>"GraphicTags"...
>> 
>> [java] =====================================================
>>      [java]     Passes: 3
>>      [java]     Fails: 0
>>      [java] =====================================================
>> 
>> 
>> So It's needed at least two passes when a time out is thrown...I'm
>> finishing to understand mustella ;)
>> 
>> 
>> 
>> 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
>> 
>>> 
>>> but "tests/GraphicTags/"
>>> 
>>> reports
>>> [java] =====================================================
>>>      [java]     Passes: 2
>>>      [java]     Fails: 1
>>>      [java] =====================================================
>>> 
>>> so I'll fix GraphicTags
>>> 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> Director de Tecnología
>>> 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ón, 32
>>> Planta 10, Puertas P-Q
>>> 28020 Madrid
>>> 
>>> 
>> 
>
>-- 
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Hi Carlos,

That's awesome.  Thanks for pitching in.  Peter, can you update the wiki?

An interesting thing for you to do is before you quit working for the day,
run mini_run.sh -all and see what you get in the morning.  The failures will
point to folders to work on.  Review this thread for what others are working
on.  I've working on the entire spark folder, for example.

-Alex


On 8/21/12 2:06 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

> Ops! I reboot Terminal and pass it again and all is ok with "GraphicTags"...
> 
> [java] =====================================================
>      [java]     Passes: 3
>      [java]     Fails: 0
>      [java] =====================================================
> 
> 
> So It's needed at least two passes when a time out is thrown...I'm
> finishing to understand mustella ;)
> 
> 
> 
> 2012/8/21 Carlos Rovira <ca...@codeoscopic.com>
> 
>> 
>> but "tests/GraphicTags/"
>> 
>> reports
>> [java] =====================================================
>>      [java]     Passes: 2
>>      [java]     Fails: 1
>>      [java] =====================================================
>> 
>> so I'll fix GraphicTags
>> 
>> 
>> 
>> --
>> Carlos Rovira
>> Director de Tecnología
>> 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ón, 32
>> Planta 10, Puertas P-Q
>> 28020 Madrid
>> 
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Ops! I reboot Terminal and pass it again and all is ok with "GraphicTags"...

[java] =====================================================
     [java]     Passes: 3
     [java]     Fails: 0
     [java] =====================================================


So It's needed at least two passes when a time out is thrown...I'm
finishing to understand mustella ;)



2012/8/21 Carlos Rovira <ca...@codeoscopic.com>

>
> but "tests/GraphicTags/"
>
> reports
> [java] =====================================================
>      [java]     Passes: 2
>      [java]     Fails: 1
>      [java] =====================================================
>
> so I'll fix GraphicTags
>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> 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ón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

"tests/Graphics/" is OK

java] =====================================================
     [java]     Passes: 2
     [java]     Fails: 0
     [java] =====================================================

but "tests/GraphicTags/"

reports
[java] =====================================================
     [java]     Passes: 2
     [java]     Fails: 1
     [java] =====================================================

so I'll fix GraphicTags



-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

"tests/Embed/" already pass OK

[java] =====================================================
     [java]     Passes: 1
     [java]     Fails: 0
     [java] =====================================================

-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

for "tests/DownloadProgressBar" all seems ok:

[java] =====================================================
     [java] Failed:
     [java] =====================================================
     [java]
     [java]
     [java] =====================================================
     [java]     Passes: 8
     [java]     Fails: 0
     [java] =====================================================
     [java]
     [java]
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 51 seconds


btw, I'm testing on Mac OSX 10.8 (to complete wiki page)



2012/8/21 Carlos Rovira <ca...@codeoscopic.com>

> Thanks Alex,
>
> after reboot and launch collection suite again all failures go away...I'm
> really asthonished for this results:
>
> d
>      [java] =====================================================
>      [java] Failed:
>      [java] =====================================================
>      [java]
>      [java]
>      [java] =====================================================
>      [java]     Passes: 54
>      [java]     Fails: 0
>      [java] =====================================================
>      [java]
>      [java]
>      [java] Wrote summary to results.txt
>      [java] Wrote failures to failures.txt
>
> call_runners:
>
> run:
>
> BUILD SUCCESSFUL
> Total time: 42 seconds
>
>
> So I think we could give collections the OK, isn't it?
>
> I'll search other test to work with
>
>
>
> 2012/8/21 Alex Harui <ah...@adobe.com>
>
>> Everytime you use mini_run, the AS3 code is re-compiled so it should be in
>> effect.  Someday someone will make that slightly more efficient, but
>> that's
>> the way it is for now.
>>
>> Also, I just hit some tests that are returning timeouts because of too
>> many
>> embedded font warnings.  I am going to try to fix those tests by adjusting
>> the styles and embeds so those warnings go away.
>>
>> Other tests will timeout because they throw an error.  The .log file next
>> to
>> each SWF will contain the stack trace if that's true.
>>
>>
>> On 8/21/12 12:47 PM, "Carlos Rovira" <ca...@codeoscopic.com>
>> wrote:
>>
>> > Thanks Peter,
>> >
>> > i'll make a reboot right now and will launch rigth now.
>> >
>> > Regarding Alex AS3 updates, I see the folder... Imust to do something?
>> or
>> > that code is already taken into account? how can I see it's been
>> applied?
>> >
>> >
>> > 2012/8/21 Peter Ent <pe...@adobe.com>
>> >
>> >> Hi,
>> >>
>> >> test/collections is great, thanks. I'll mark it in the Wiki. Try the
>> tests
>> >> again after doing a reboot and make sure you grab Alex's updates to the
>> >> mustella code base (mustella/as3). If you are still getting time-outs,
>> >> looks to see if these tests are requesting data from a remote system;
>> we
>> >> might just have to exclude them.
>> >>
>> >> --peter
>> >>
>> >> On 8/21/12 3:33 PM, "Carlos Rovira" <ca...@codeoscopic.com>
>> wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>> I think I'm prepared to start working on Mustella. I think I will
>> start
>> >>> for
>> >>> test/collections if nobody is working on it (please tell me if you
>> are ok
>> >>> with I starting here)
>> >>>
>> >>> running  ./mini_run.sh tests/collections/
>> >>>
>> >>> reports me:
>> >>>
>> >>> [java] =====================================================
>> >>>     [java] Failed:
>> >>>     [java] =====================================================
>> >>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>> >>> ArrayCollection_Method_AddItemAtEnd Failed Timed out
>> >>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>> >>> ArrayCollection_Method_SetItemAtBeforeBeginning Failed Timed out
>> >>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>> >>> ArrayCollection_Method_itemUpdated Failed Timed out
>> >>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>> >>> ArrayCollection_Method_AddItemAtEndPastOne Failed Timed out
>> >>>     [java]
>> >>>     [java]
>> >>>     [java] =====================================================
>> >>>     [java]     Passes: 29
>> >>>     [java]     Fails: 4
>> >>>     [java] =====================================================
>> >>>     [java]
>> >>>     [java]
>> >>>     [java] Firing Timeout for
>> >>>
>> collections/ArrayCollection/Methods/ArrayCollection_Methods$ArrayCollectio
>> >>> n_Method_AddItemAt1
>> >>> HTTP/1.1 after 10000 millis at: 19:27:16.179
>> >>>     [java] hello from setDone, but we've been here, bye
>> >>>     [java] Wrote summary to results.txt
>> >>>     [java] Wrote failures to failures.txt
>> >>>
>> >>>
>> >>>
>> >>> 2012/8/20 Carol Frampton <cf...@adobe.com>
>> >>>
>> >>>>
>> >>>>
>> >>>> On 8/18/12 8 :11AM, "Cyrill Zadra" <cy...@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
>> >>>> that
>> >>>>> all the language tests exception japanes are excluded?
>> >>>>>
>> >>>>> ./mini_run.sh tests/LangPacks/German
>> >>>>
>> >>>> This may not be the reason but Flex was in the process of dropping
>> >>>> support
>> >>>> for many of the languages that there are still property files for.
>> >>>> Also,
>> >>>> the language files were done by the internationalization group and
>> >>>> usually
>> >>>> just updated in our repository at the send of the release.
>> >>>>
>> >>>> Car
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Carlos Rovira
>> >>> Director de Tecnología
>> >>> 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ón, 32
>> >>> Planta 10, Puertas P-Q
>> >>> 28020 Madrid
>> >>
>> >>
>> >
>>
>> --
>> Alex Harui
>> Flex SDK Team
>> Adobe Systems, Inc.
>> http://blogs.adobe.com/aharui
>>
>>
>
>
> --
> Carlos Rovira
> Director de Tecnología
> 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ón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Thanks Alex,

after reboot and launch collection suite again all failures go away...I'm
really asthonished for this results:

d
     [java] =====================================================
     [java] Failed:
     [java] =====================================================
     [java]
     [java]
     [java] =====================================================
     [java]     Passes: 54
     [java]     Fails: 0
     [java] =====================================================
     [java]
     [java]
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

call_runners:

run:

BUILD SUCCESSFUL
Total time: 42 seconds


So I think we could give collections the OK, isn't it?

I'll search other test to work with



2012/8/21 Alex Harui <ah...@adobe.com>

> Everytime you use mini_run, the AS3 code is re-compiled so it should be in
> effect.  Someday someone will make that slightly more efficient, but that's
> the way it is for now.
>
> Also, I just hit some tests that are returning timeouts because of too many
> embedded font warnings.  I am going to try to fix those tests by adjusting
> the styles and embeds so those warnings go away.
>
> Other tests will timeout because they throw an error.  The .log file next
> to
> each SWF will contain the stack trace if that's true.
>
>
> On 8/21/12 12:47 PM, "Carlos Rovira" <ca...@codeoscopic.com>
> wrote:
>
> > Thanks Peter,
> >
> > i'll make a reboot right now and will launch rigth now.
> >
> > Regarding Alex AS3 updates, I see the folder... Imust to do something? or
> > that code is already taken into account? how can I see it's been applied?
> >
> >
> > 2012/8/21 Peter Ent <pe...@adobe.com>
> >
> >> Hi,
> >>
> >> test/collections is great, thanks. I'll mark it in the Wiki. Try the
> tests
> >> again after doing a reboot and make sure you grab Alex's updates to the
> >> mustella code base (mustella/as3). If you are still getting time-outs,
> >> looks to see if these tests are requesting data from a remote system; we
> >> might just have to exclude them.
> >>
> >> --peter
> >>
> >> On 8/21/12 3:33 PM, "Carlos Rovira" <ca...@codeoscopic.com>
> wrote:
> >>
> >>> Hi,
> >>>
> >>> I think I'm prepared to start working on Mustella. I think I will start
> >>> for
> >>> test/collections if nobody is working on it (please tell me if you are
> ok
> >>> with I starting here)
> >>>
> >>> running  ./mini_run.sh tests/collections/
> >>>
> >>> reports me:
> >>>
> >>> [java] =====================================================
> >>>     [java] Failed:
> >>>     [java] =====================================================
> >>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
> >>> ArrayCollection_Method_AddItemAtEnd Failed Timed out
> >>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
> >>> ArrayCollection_Method_SetItemAtBeforeBeginning Failed Timed out
> >>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
> >>> ArrayCollection_Method_itemUpdated Failed Timed out
> >>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
> >>> ArrayCollection_Method_AddItemAtEndPastOne Failed Timed out
> >>>     [java]
> >>>     [java]
> >>>     [java] =====================================================
> >>>     [java]     Passes: 29
> >>>     [java]     Fails: 4
> >>>     [java] =====================================================
> >>>     [java]
> >>>     [java]
> >>>     [java] Firing Timeout for
> >>>
> collections/ArrayCollection/Methods/ArrayCollection_Methods$ArrayCollectio
> >>> n_Method_AddItemAt1
> >>> HTTP/1.1 after 10000 millis at: 19:27:16.179
> >>>     [java] hello from setDone, but we've been here, bye
> >>>     [java] Wrote summary to results.txt
> >>>     [java] Wrote failures to failures.txt
> >>>
> >>>
> >>>
> >>> 2012/8/20 Carol Frampton <cf...@adobe.com>
> >>>
> >>>>
> >>>>
> >>>> On 8/18/12 8 :11AM, "Cyrill Zadra" <cy...@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
> >>>> that
> >>>>> all the language tests exception japanes are excluded?
> >>>>>
> >>>>> ./mini_run.sh tests/LangPacks/German
> >>>>
> >>>> This may not be the reason but Flex was in the process of dropping
> >>>> support
> >>>> for many of the languages that there are still property files for.
> >>>> Also,
> >>>> the language files were done by the internationalization group and
> >>>> usually
> >>>> just updated in our repository at the send of the release.
> >>>>
> >>>> Car
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> Director de Tecnología
> >>> 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ón, 32
> >>> Planta 10, Puertas P-Q
> >>> 28020 Madrid
> >>
> >>
> >
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

Everytime you use mini_run, the AS3 code is re-compiled so it should be in
effect.  Someday someone will make that slightly more efficient, but that's
the way it is for now.

Also, I just hit some tests that are returning timeouts because of too many
embedded font warnings.  I am going to try to fix those tests by adjusting
the styles and embeds so those warnings go away.

Other tests will timeout because they throw an error.  The .log file next to
each SWF will contain the stack trace if that's true.


On 8/21/12 12:47 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

> Thanks Peter,
> 
> i'll make a reboot right now and will launch rigth now.
> 
> Regarding Alex AS3 updates, I see the folder... Imust to do something? or
> that code is already taken into account? how can I see it's been applied?
> 
> 
> 2012/8/21 Peter Ent <pe...@adobe.com>
> 
>> Hi,
>> 
>> test/collections is great, thanks. I'll mark it in the Wiki. Try the tests
>> again after doing a reboot and make sure you grab Alex's updates to the
>> mustella code base (mustella/as3). If you are still getting time-outs,
>> looks to see if these tests are requesting data from a remote system; we
>> might just have to exclude them.
>> 
>> --peter
>> 
>> On 8/21/12 3:33 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>> 
>>> Hi,
>>> 
>>> I think I'm prepared to start working on Mustella. I think I will start
>>> for
>>> test/collections if nobody is working on it (please tell me if you are ok
>>> with I starting here)
>>> 
>>> running  ./mini_run.sh tests/collections/
>>> 
>>> reports me:
>>> 
>>> [java] =====================================================
>>>     [java] Failed:
>>>     [java] =====================================================
>>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>>> ArrayCollection_Method_AddItemAtEnd Failed Timed out
>>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>>> ArrayCollection_Method_SetItemAtBeforeBeginning Failed Timed out
>>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>>> ArrayCollection_Method_itemUpdated Failed Timed out
>>>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>>> ArrayCollection_Method_AddItemAtEndPastOne Failed Timed out
>>>     [java]
>>>     [java]
>>>     [java] =====================================================
>>>     [java]     Passes: 29
>>>     [java]     Fails: 4
>>>     [java] =====================================================
>>>     [java]
>>>     [java]
>>>     [java] Firing Timeout for
>>> collections/ArrayCollection/Methods/ArrayCollection_Methods$ArrayCollectio
>>> n_Method_AddItemAt1
>>> HTTP/1.1 after 10000 millis at: 19:27:16.179
>>>     [java] hello from setDone, but we've been here, bye
>>>     [java] Wrote summary to results.txt
>>>     [java] Wrote failures to failures.txt
>>> 
>>> 
>>> 
>>> 2012/8/20 Carol Frampton <cf...@adobe.com>
>>> 
>>>> 
>>>> 
>>>> On 8/18/12 8 :11AM, "Cyrill Zadra" <cy...@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
>>>> that
>>>>> all the language tests exception japanes are excluded?
>>>>> 
>>>>> ./mini_run.sh tests/LangPacks/German
>>>> 
>>>> This may not be the reason but Flex was in the process of dropping
>>>> support
>>>> for many of the languages that there are still property files for.
>>>> Also,
>>>> the language files were done by the internationalization group and
>>>> usually
>>>> just updated in our repository at the send of the release.
>>>> 
>>>> Car
>>>> 
>>>> 
>>> 
>>> 
>>> --
>>> Carlos Rovira
>>> Director de Tecnología
>>> 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ón, 32
>>> Planta 10, Puertas P-Q
>>> 28020 Madrid
>> 
>> 
> 

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Thanks Peter,

i'll make a reboot right now and will launch rigth now.

Regarding Alex AS3 updates, I see the folder... Imust to do something? or
that code is already taken into account? how can I see it's been applied?


2012/8/21 Peter Ent <pe...@adobe.com>

> Hi,
>
> test/collections is great, thanks. I'll mark it in the Wiki. Try the tests
> again after doing a reboot and make sure you grab Alex's updates to the
> mustella code base (mustella/as3). If you are still getting time-outs,
> looks to see if these tests are requesting data from a remote system; we
> might just have to exclude them.
>
> --peter
>
> On 8/21/12 3:33 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:
>
> >Hi,
> >
> >I think I'm prepared to start working on Mustella. I think I will start
> >for
> >test/collections if nobody is working on it (please tell me if you are ok
> >with I starting here)
> >
> >running  ./mini_run.sh tests/collections/
> >
> >reports me:
> >
> >[java] =====================================================
> >     [java] Failed:
> >     [java] =====================================================
> >     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
> >ArrayCollection_Method_AddItemAtEnd Failed Timed out
> >     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
> >ArrayCollection_Method_SetItemAtBeforeBeginning Failed Timed out
> >     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
> >ArrayCollection_Method_itemUpdated Failed Timed out
> >     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
> >ArrayCollection_Method_AddItemAtEndPastOne Failed Timed out
> >     [java]
> >     [java]
> >     [java] =====================================================
> >     [java]     Passes: 29
> >     [java]     Fails: 4
> >     [java] =====================================================
> >     [java]
> >     [java]
> >     [java] Firing Timeout for
> >collections/ArrayCollection/Methods/ArrayCollection_Methods$ArrayCollectio
> >n_Method_AddItemAt1
> >HTTP/1.1 after 10000 millis at: 19:27:16.179
> >     [java] hello from setDone, but we've been here, bye
> >     [java] Wrote summary to results.txt
> >     [java] Wrote failures to failures.txt
> >
> >
> >
> >2012/8/20 Carol Frampton <cf...@adobe.com>
> >
> >>
> >>
> >> On 8/18/12 8 :11AM, "Cyrill Zadra" <cy...@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
> >>that
> >> >all the language tests exception japanes are excluded?
> >> >
> >> >./mini_run.sh tests/LangPacks/German
> >>
> >> This may not be the reason but Flex was in the process of dropping
> >>support
> >> for many of the languages that there are still property files for.
> >>Also,
> >> the language files were done by the internationalization group and
> >>usually
> >> just updated in our repository at the send of the release.
> >>
> >> Car
> >>
> >>
> >
> >
> >--
> >Carlos Rovira
> >Director de Tecnología
> >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ón, 32
> >Planta 10, Puertas P-Q
> >28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Hi,

test/collections is great, thanks. I'll mark it in the Wiki. Try the tests
again after doing a reboot and make sure you grab Alex's updates to the
mustella code base (mustella/as3). If you are still getting time-outs,
looks to see if these tests are requesting data from a remote system; we
might just have to exclude them.

--peter

On 8/21/12 3:33 PM, "Carlos Rovira" <ca...@codeoscopic.com> wrote:

>Hi,
>
>I think I'm prepared to start working on Mustella. I think I will start
>for
>test/collections if nobody is working on it (please tell me if you are ok
>with I starting here)
>
>running  ./mini_run.sh tests/collections/
>
>reports me:
>
>[java] =====================================================
>     [java] Failed:
>     [java] =====================================================
>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>ArrayCollection_Method_AddItemAtEnd Failed Timed out
>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>ArrayCollection_Method_SetItemAtBeforeBeginning Failed Timed out
>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>ArrayCollection_Method_itemUpdated Failed Timed out
>     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
>ArrayCollection_Method_AddItemAtEndPastOne Failed Timed out
>     [java]
>     [java]
>     [java] =====================================================
>     [java]     Passes: 29
>     [java]     Fails: 4
>     [java] =====================================================
>     [java]
>     [java]
>     [java] Firing Timeout for
>collections/ArrayCollection/Methods/ArrayCollection_Methods$ArrayCollectio
>n_Method_AddItemAt1
>HTTP/1.1 after 10000 millis at: 19:27:16.179
>     [java] hello from setDone, but we've been here, bye
>     [java] Wrote summary to results.txt
>     [java] Wrote failures to failures.txt
>
>
>
>2012/8/20 Carol Frampton <cf...@adobe.com>
>
>>
>>
>> On 8/18/12 8 :11AM, "Cyrill Zadra" <cy...@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
>>that
>> >all the language tests exception japanes are excluded?
>> >
>> >./mini_run.sh tests/LangPacks/German
>>
>> This may not be the reason but Flex was in the process of dropping
>>support
>> for many of the languages that there are still property files for.
>>Also,
>> the language files were done by the internationalization group and
>>usually
>> just updated in our repository at the send of the release.
>>
>> Car
>>
>>
>
>
>-- 
>Carlos Rovira
>Director de Tecnología
>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ón, 32
>Planta 10, Puertas P-Q
>28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi,

I think I'm prepared to start working on Mustella. I think I will start for
test/collections if nobody is working on it (please tell me if you are ok
with I starting here)

running  ./mini_run.sh tests/collections/

reports me:

[java] =====================================================
     [java] Failed:
     [java] =====================================================
     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
ArrayCollection_Method_AddItemAtEnd Failed Timed out
     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
ArrayCollection_Method_SetItemAtBeforeBeginning Failed Timed out
     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
ArrayCollection_Method_itemUpdated Failed Timed out
     [java] collections/ArrayCollection/Methods/ArrayCollection_Methods
ArrayCollection_Method_AddItemAtEndPastOne Failed Timed out
     [java]
     [java]
     [java] =====================================================
     [java]     Passes: 29
     [java]     Fails: 4
     [java] =====================================================
     [java]
     [java]
     [java] Firing Timeout for
collections/ArrayCollection/Methods/ArrayCollection_Methods$ArrayCollection_Method_AddItemAt1
HTTP/1.1 after 10000 millis at: 19:27:16.179
     [java] hello from setDone, but we've been here, bye
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt



2012/8/20 Carol Frampton <cf...@adobe.com>

>
>
> On 8/18/12 8 :11AM, "Cyrill Zadra" <cy...@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 that
> >all the language tests exception japanes are excluded?
> >
> >./mini_run.sh tests/LangPacks/German
>
> This may not be the reason but Flex was in the process of dropping support
> for many of the languages that there are still property files for.  Also,
> the language files were done by the internationalization group and usually
> just updated in our repository at the send of the release.
>
> Car
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Hi,

I left mustella passing this night and the build failed after 628 min (wow!
I remember someone says it takes to long but I thought it was 1 hour, not
10! :)).

I expect the build ends ok with 14k test passing an 2k failing for what I
remember to read in some thread, but not to fail, taking into account it
went to far

This is what I get:

[java] Grablog: never saw the ScriptDone for
/Users/carlosrovira/Documents/workspaces/flex/flex/mustella/tests/spark/validators/NumberValidator/SWFs/NV_validateNumber.swf
     [java] at the end of main
     [java] Shutting down the results server
     [java] shutting down the baseline server
     [java] done waiting for results...bye
     [java] =====================================================
     [java]     Passes: 0
     [java]     Fails: 469
     [java] =====================================================
     [java]
     [java] =====================================================
     [java] =====================================================
     [java] Passed:
     [java] =====================================================
     [java] =====================================================
     [java] Failed:
     [java] =====================================================
     [java]
/Users/carlosrovira/Documents/workspaces/flex/flex/mustella/tests/MarshallPlan/SWFs/Bootstrap_PopUpManager.swf
 Failed Timed out

...then lots of "Failed Timed out" lines and finally...

     [java]
/Users/carlosrovira/Documents/workspaces/flex/flex/mustella/tests/spark/validators/NumberValidator/SWFs/NV_validateNumber.swf
 Failed Timed out
     [java]
     [java]
     [java] =====================================================
     [java]     Passes: 0
     [java]     Fails: 469
     [java] =====================================================
     [java]
     [java]
     [java] Wrote summary to results.txt
     [java] Wrote failures to failures.txt

BUILD FAILED
/Users/carlosrovira/Documents/workspaces/flex/flex/mustella/build.xml:1453:
The following error occurred while executing this line:
/Users/carlosrovira/Documents/workspaces/flex/flex/mustella/build.xml:1571:
Java returned: 1

Someone knows what's happening?

I'm running in a OSX Mountain Lion and as I'm this weekend off of my house
I'm without Internet (only 3G shared for things like to send this email)

One more thing, before I tried -rerun flag thinking it was valid when I
have all mustella compiled and only want to run test but it seems does not
work.

Maybe it could be of great help:

1) know what are the main points that made test stop to fail (like the one
alex pointed about font replacement). I understand that before donation
test passed, but the changes made for donation made test break, but we have
the list of changes that made test break?

2) Can someone recommend me a package to start that nobody were fixing?

Thanks in advance


El domingo, 19 de agosto de 2012, Alex Harui escribió:

>
>
>
> On 8/18/12 9:52 AM, "Cyrill Zadra" <cy...@gmail.com> wrote:
> > 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?
> In order to donate Mustella, we changed fonts to OFL fonts.  Lots of tests
> broke when we did that because they might be expecting certain strings to
> have certain dimensions.  If that's the case, then fix up the tests to work
> with those OFL fonts.
>
> >
> >
> > 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
> that
> >> all the language tests exception japanes are excluded?
> >>
> Probably just to shorten total run time.
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/18/12 9:52 AM, "Cyrill Zadra" <cy...@gmail.com> wrote:
> 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?
In order to donate Mustella, we changed fonts to OFL fonts.  Lots of tests
broke when we did that because they might be expecting certain strings to
have certain dimensions.  If that's the case, then fix up the tests to work
with those OFL fonts.

> 
> 
> On Sat, Aug 18, 2012 at 2:11 PM, Cyrill Zadra <cy...@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 that
>> all the language tests exception japanes are excluded?
>> 
Probably just to shorten total run time.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Cyrill Zadra <cy...@gmail.com>.

Hi

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

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

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 <cy...@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 that
> 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 <pe...@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" <ca...@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 start.
>> > >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 <bi...@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 <cf...@adobe.com>
>> > >> wrote:
>> > >>
>> > >> >
>> > >> >
>> > >> > On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll
>> > >>learn
>> > >> > >about how it works and we¹ll 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 test
>> > >>media
>> > >> > >so component sizes and positions can be off.  If you are getting
>> > >> > >timeouts, try increasing the timeouts.
>> > >> > >
>> > >> > >I¹m starting in on tests/spark/validators.  Feel free to choose
>> 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ía
>> > >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ón, 32
>> > >Planta 10, Puertas P-Q
>> > >28020 Madrid
>> >
>> >
>>
>>
>> --
>> Carlos Rovira
>> Director de Tecnología
>> 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ón, 32
>> Planta 10, Puertas P-Q
>> 28020 Madrid
>>
>
>

Re: Getting Mustella to work.

Posted by Carol Frampton <cf...@adobe.com>.

On 8/18/12 8 :11AM, "Cyrill Zadra" <cy...@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 that
>all the language tests exception japanes are excluded?
>
>./mini_run.sh tests/LangPacks/German

This may not be the reason but Flex was in the process of dropping support
for many of the languages that there are still property files for.  Also,
the language files were done by the internationalization group and usually
just updated in our repository at the send of the release.

Car

Re: Getting Mustella to work.

Posted by Cyrill Zadra <cy...@gmail.com>.

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 that
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 <pe...@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" <ca...@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 start.
> > >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 <bi...@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 <cf...@adobe.com>
> > >> wrote:
> > >>
> > >> >
> > >> >
> > >> > On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll
> > >>learn
> > >> > >about how it works and we¹ll 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 test
> > >>media
> > >> > >so component sizes and positions can be off.  If you are getting
> > >> > >timeouts, try increasing the timeouts.
> > >> > >
> > >> > >I¹m starting in on tests/spark/validators.  Feel free to choose
> 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ía
> > >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ón, 32
> > >Planta 10, Puertas P-Q
> > >28020 Madrid
> >
> >
>
>
> --
> Carlos Rovira
> Director de Tecnología
> 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ón, 32
> Planta 10, Puertas P-Q
> 28020 Madrid
>

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

Thanks Peter!

I'll check the link, seems very useful to start runing :)


2012/8/17 Peter Ent <pe...@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" <ca...@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 start.
> >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 <bi...@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 <cf...@adobe.com>
> >> wrote:
> >>
> >> >
> >> >
> >> > On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll
> >>learn
> >> > >about how it works and we¹ll 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 test
> >>media
> >> > >so component sizes and positions can be off.  If you are getting
> >> > >timeouts, try increasing the timeouts.
> >> > >
> >> > >I¹m starting in on tests/spark/validators.  Feel free to choose 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ía
> >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ón, 32
> >Planta 10, Puertas P-Q
> >28020 Madrid
>
>


-- 
Carlos Rovira
Director de Tecnología
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@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" <ca...@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 start.
>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 <bi...@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 <cf...@adobe.com>
>> wrote:
>>
>> >
>> >
>> > On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll
>>learn
>> > >about how it works and we¹ll 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 test
>>media
>> > >so component sizes and positions can be off.  If you are getting
>> > >timeouts, try increasing the timeouts.
>> > >
>> > >I¹m starting in on tests/spark/validators.  Feel free to choose 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ía
>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ón, 32
>Planta 10, Puertas P-Q
>28020 Madrid

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.



On 8/17/12 1:13 PM, "Carlos Rovira" <ca...@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 start. 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.
> 
As you probably read in the documents on the Apache website, you have to
contribute code in order to be nominated to become a committer.  So, if you
take on mustella work, your first fixes will have to be in the form of
patches.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carlos Rovira <ca...@codeoscopic.com>.

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 start. 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 <bi...@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 <cf...@adobe.com>
> wrote:
>
> >
> >
> > On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll learn
> > >about how it works and we¹ll 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 test media
> > >so component sizes and positions can be off.  If you are getting
> > >timeouts, try increasing the timeouts.
> > >
> > >I¹m starting in on tests/spark/validators.  Feel free to choose 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ía
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ón, 32
Planta 10, Puertas P-Q
28020 Madrid

Re: Getting Mustella to work.

Posted by João Fernandes <jo...@gmail.com>.

Om,

Mustella clearly is something I want to learn and contribute but I just
started holidays and unfortunately won't have access to a dev machine for 2
weeks.

João Fernandes

Re: Getting Mustella to work.

Posted by Om <bi...@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 <cf...@adobe.com> wrote:

>
>
> On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll learn
> >about how it works and we¹ll 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 test media
> >so component sizes and positions can be off.  If you are getting
> >timeouts, try increasing the timeouts.
> >
> >I¹m starting in on tests/spark/validators.  Feel free to choose some
> >other folder of tests and start fixing!  And feel free to ask questions.
>
> I'm looking at the spark text components.
>
> Carol
>
>

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

On 8/16/12 12:13 AM, "João Fernandes" <jo...@gmail.com>
wrote:

> I have just run the entire suite in my laptop (windows) and got
> 
> =====================================================
>     Passes: 12124
>     Fails: 2226
> =====================================================
> 
> now, how do you guys usually debug failing tests?
> 
> João Fernandes
I use FDB.  In the output of the failures there should either be
1) a SWF that timed out, or 2) a test name that failed.

For (1) I go find the SWF and run it in FDB and see if I can figure out why
it got stuck.

For (2) I look at the failing test and find the SWF it is linked into and
launch that SWF in FDB>  I try to get a breakpoint on the failing step in
FDB.  Most steps have a "doStep()" method that is a good place to start.

There is a way to launch the FB debugger, but I don't know it OTOH since I
don't use it.

Using the mini_run.sh -failures option helps you get to the failing test
faster, but sometimes I comment out stuff so I don't have to skip past a lot
of breakpoints.

Remember, I'm working on validators, Peter is working on the apollo folder
and Carol is working on text-related components, so claim another folder and
cross your fingers.

HTH,
-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by João Fernandes <jo...@gmail.com>.

I have just run the entire suite in my laptop (windows) and got

=====================================================
    Passes: 12124
    Fails: 2226
=====================================================

now, how do you guys usually debug failing tests?

João Fernandes

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

Hi,

Unlike Alex and Carol who have worked deep with Flex and probably other
SDKs, I have an application-developer background (which I hope proves
useful down the road when growing Flex for application development), so I
have found working, what I call, "behind the scenes", to be a bit
overwhelming.

This is especially true for Mustella which is a very complex thing.
Getting an event-driven, asynchronous framework like Flex to have an
automated test structure is no easy feat. I, personally, am very grateful
to have such a community to help, no matter how much time you can spare,
make Flex better by having a robust and complete test system.

Regards,
Peter 

On 8/15/12 12:27 PM, "Omar Gonzalez" <om...@gmail.com> wrote:

>On Wednesday, August 15, 2012, Carol Frampton wrote:
>
>>
>>
>> On 8/15/12 12 :02PM, "Omar Gonzalez"
>><omarg.developer@gmail.com<javascript:;>>
>> wrote:
>>
>> >On Wednesday, August 15, 2012, Carol Frampton wrote:
>> >
>> >> I would like to reiterate what Alex is saying.  All the mustella code
>> >>has
>> >> been donated.  Yes there are many failing tests.
>> >>
>> >> I read several emails this morning about the level of commit activity
>> >>not
>> >> being higher because we're waiting for mustella.  Well mustella is
>>here.
>> >> It is time for the community to help out and get all the tests up and
>> >> running.  Or contribute an entirely different test system if you'd
>> >>rather.
>> >>
>> >> Carol
>> >>
>> >>
>> > Like I've said before, a lot of us were waiting on this. This doesn't
>> >mean
>> >that we are now able to drop everything and dedicate as much time as
>> >yourself or Alex. I don't get paid to help Apache Flex, so I have to
>>find
>> >the time where I can, and now that the tests are up I'll be helping
>>Peter
>> >test his work whenever I am able to find time when I'm not at work. The
>> >way
>> >you point it out comes off a little condescending, for lack of a better
>> >word. We're all aware of how much effort you've put in, Carol, and we
>>all
>> >truly appreciate it. We're just not all in the same boat as you being
>>able
>> >to contribute during our work days.
>> >
>> >Just my thoughts, they'll probably fall on deaf ears.
>>
>> I hear you and I totally understand that most people can only contribute
>> here and there when they have a few spare cycles.
>> I will try to chose my words more carefully next time.
>>
>> Carol
>>
>>
>Thank you I appreciate your response. I also hear what you're saying and I
>hear your point, my Things has a Work on Mustella entry now though, the
>work Peter, Alex, Gordon and yourself have done is encouraging and
>motivating. I suspect other committers/contributors feel the same and I
>hope to see activity ramp up in the coming weeks. I really hope I'm right.
>
>-omar

Re: Getting Mustella to work.

Posted by Omar Gonzalez <om...@gmail.com>.

On Wednesday, August 15, 2012, Carol Frampton wrote:

>
>
> On 8/15/12 12 :02PM, "Omar Gonzalez" <omarg.developer@gmail.com<javascript:;>>
> wrote:
>
> >On Wednesday, August 15, 2012, Carol Frampton wrote:
> >
> >> I would like to reiterate what Alex is saying.  All the mustella code
> >>has
> >> been donated.  Yes there are many failing tests.
> >>
> >> I read several emails this morning about the level of commit activity
> >>not
> >> being higher because we're waiting for mustella.  Well mustella is here.
> >> It is time for the community to help out and get all the tests up and
> >> running.  Or contribute an entirely different test system if you'd
> >>rather.
> >>
> >> Carol
> >>
> >>
> > Like I've said before, a lot of us were waiting on this. This doesn't
> >mean
> >that we are now able to drop everything and dedicate as much time as
> >yourself or Alex. I don't get paid to help Apache Flex, so I have to find
> >the time where I can, and now that the tests are up I'll be helping Peter
> >test his work whenever I am able to find time when I'm not at work. The
> >way
> >you point it out comes off a little condescending, for lack of a better
> >word. We're all aware of how much effort you've put in, Carol, and we all
> >truly appreciate it. We're just not all in the same boat as you being able
> >to contribute during our work days.
> >
> >Just my thoughts, they'll probably fall on deaf ears.
>
> I hear you and I totally understand that most people can only contribute
> here and there when they have a few spare cycles.
> I will try to chose my words more carefully next time.
>
> Carol
>
>
Thank you I appreciate your response. I also hear what you're saying and I
hear your point, my Things has a Work on Mustella entry now though, the
work Peter, Alex, Gordon and yourself have done is encouraging and
motivating. I suspect other committers/contributors feel the same and I
hope to see activity ramp up in the coming weeks. I really hope I'm right.

-omar

Re: Getting Mustella to work.

Posted by Carol Frampton <cf...@adobe.com>.


On 8/15/12 12 :02PM, "Omar Gonzalez" <om...@gmail.com> wrote:

>On Wednesday, August 15, 2012, Carol Frampton wrote:
>
>> I would like to reiterate what Alex is saying.  All the mustella code
>>has
>> been donated.  Yes there are many failing tests.
>>
>> I read several emails this morning about the level of commit activity
>>not
>> being higher because we're waiting for mustella.  Well mustella is here.
>> It is time for the community to help out and get all the tests up and
>> running.  Or contribute an entirely different test system if you'd
>>rather.
>>
>> Carol
>>
>>
> Like I've said before, a lot of us were waiting on this. This doesn't
>mean
>that we are now able to drop everything and dedicate as much time as
>yourself or Alex. I don't get paid to help Apache Flex, so I have to find
>the time where I can, and now that the tests are up I'll be helping Peter
>test his work whenever I am able to find time when I'm not at work. The
>way
>you point it out comes off a little condescending, for lack of a better
>word. We're all aware of how much effort you've put in, Carol, and we all
>truly appreciate it. We're just not all in the same boat as you being able
>to contribute during our work days.
>
>Just my thoughts, they'll probably fall on deaf ears.

I hear you and I totally understand that most people can only contribute
here and there when they have a few spare cycles.
I will try to chose my words more carefully next time.

Carol

Re: Getting Mustella to work.

Posted by Omar Gonzalez <om...@gmail.com>.

On Wednesday, August 15, 2012, Carol Frampton wrote:

> I would like to reiterate what Alex is saying.  All the mustella code has
> been donated.  Yes there are many failing tests.
>
> I read several emails this morning about the level of commit activity not
> being higher because we're waiting for mustella.  Well mustella is here.
> It is time for the community to help out and get all the tests up and
> running.  Or contribute an entirely different test system if you'd rather.
>
> Carol
>
>
 Like I've said before, a lot of us were waiting on this. This doesn't mean
that we are now able to drop everything and dedicate as much time as
yourself or Alex. I don't get paid to help Apache Flex, so I have to find
the time where I can, and now that the tests are up I'll be helping Peter
test his work whenever I am able to find time when I'm not at work. The way
you point it out comes off a little condescending, for lack of a better
word. We're all aware of how much effort you've put in, Carol, and we all
truly appreciate it. We're just not all in the same boat as you being able
to contribute during our work days.

Just my thoughts, they'll probably fall on deaf ears.

-omar




>
> On 8/13/12 6 :02PM, "Alex Harui" <aharui@adobe.com <javascript:;>> 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¹ll learn
> >about how it works and we¹ll 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 test media
> >so component sizes and positions can be off.  If you are getting
> >timeouts, try increasing the timeouts.
> >
> >I¹m starting in on tests/spark/validators.  Feel free to choose some
> >other folder of tests and start fixing!  And feel free to ask questions.
> >
> >--
> >Alex Harui
> >Flex SDK Team
> >Adobe Systems, Inc.
> >http://blogs.adobe.com/aharui
>
>

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I'll start at the top and work on the apollo (aka AIR) tests.

-peter

On 8/13/12 6:02 PM, "Alex Harui" <ah...@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¹ll learn
>about how it works and we¹ll 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 test media
>so component sizes and positions can be off.  If you are getting
>timeouts, try increasing the timeouts.
>
>I¹m starting in on tests/spark/validators.  Feel free to choose some
>other folder of tests and start fixing!  And feel free to ask questions.
>
>--
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.


BTW, if you see lots of SWF timeouts, you be running into a stuck
LocalConnection.  Mustella uses the LocalConnection hack to force GC and
occasionally the hack hangs and you have to reboot or shut down all
instances of the player (browser, Yahoo IM, for example) and then you should
get better results.

-- 
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Peter Ent <pe...@adobe.com>.

I've been working on the AIR tests (aka, apollo) and am still receiving 15
failures which I am looking into. I've created a table at the bottom of
the Mustella Wiki page
(https://cwiki.apache.org/confluence/display/FLEX/Mustella+Overview) to
journal the progress. When you feel you have something (such as all tests
working), send me the info and I will update the wiki (or update it
yourself if you have permission, of course).

Peter Ent
Flex SDK Team
Adobe Systems

On 8/13/12 7:58 PM, "Carol Frampton" <cf...@adobe.com> wrote:

>
>
>On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll learn
>>about how it works and we¹ll 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 test media
>>so component sizes and positions can be off.  If you are getting
>>timeouts, try increasing the timeouts.
>>
>>I¹m starting in on tests/spark/validators.  Feel free to choose some
>>other folder of tests and start fixing!  And feel free to ask questions.
>
>I'm looking at the spark text components.
>
>Carol
>

Re: Getting Mustella to work.

Posted by Carol Frampton <cf...@adobe.com>.


On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll learn
>about how it works and we¹ll 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 test media
>so component sizes and positions can be off.  If you are getting
>timeouts, try increasing the timeouts.
>
>I¹m starting in on tests/spark/validators.  Feel free to choose some
>other folder of tests and start fixing!  And feel free to ask questions.

I'm looking at the spark text components.

Carol

Re: Getting Mustella to work.

Posted by Alex Harui <ah...@adobe.com>.

OK, spark validators are running.  I’m taking on the rest of the Spark folder.


On 8/13/12 3:02 PM, "Alex Harui" <ah...@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’ll learn about how it works and we’ll 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 test media so component sizes and positions can be off.  If you are getting timeouts, try increasing the timeouts.

I’m starting in on tests/spark/validators.  Feel free to choose some other folder of tests and start fixing!  And feel free to ask questions.

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Re: Getting Mustella to work.

Posted by Carol Frampton <cf...@adobe.com>.

I would like to reiterate what Alex is saying.  All the mustella code has
been donated.  Yes there are many failing tests.

I read several emails this morning about the level of commit activity not
being higher because we're waiting for mustella.  Well mustella is here.
It is time for the community to help out and get all the tests up and
running.  Or contribute an entirely different test system if you'd rather.

Carol

On 8/13/12 6 :02PM, "Alex Harui" <ah...@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¹ll learn
>about how it works and we¹ll 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 test media
>so component sizes and positions can be off.  If you are getting
>timeouts, try increasing the timeouts.
>
>I¹m starting in on tests/spark/validators.  Feel free to choose some
>other folder of tests and start fixing!  And feel free to ask questions.
>
>--
>Alex Harui
>Flex SDK Team
>Adobe Systems, Inc.
>http://blogs.adobe.com/aharui