I ran the ResourceManager tests.  They all pass for me.  I haven’t looked
at the tests to see if any actually test for multiple locales, so the
issue may be that those tests will now need a .compile file like the kind
in RuntimeLocalization.

But if you haven’t made any changes and you can’t get the existing tests
to pass, post the full console output.

-Alex

On 12/11/14, 7:43 AM, "Chris Martin" <chrsm...@outlook.com> wrote:

>Hey Alex,
> 
>The compile worked fine and I have do have the fr_FR folder at
>frameworks/locale along with many others.  The fr_FR folder does contain
>the _rb.swc files.
> 
>I'm going to add a new mustella test to the mxml for getString().  I am
>running all tests for the ResourceManager to make sure everything runs as
>expected before I modify anything.  Seems many of the mustella tests for
>ResourceManager are failing with this "cannot find compiled locale" error
>for fr_FR.  I tried commenting the ones that failed out just  to see if I
>can't get a clean run, but after a few, I decided there were too many to
>ignore the error for now.  Don't worry before I commit, i'd make sure the
>tests ran completely okay :)
> 
>I'll didn't find any .compile files in the directory
>mustella/tests/resources/ResourceManager or its subdirectories.  Am I
>looking in the right spot?  I gotta get to the office, but i'll check out
>the example you gave when I get home this afternoon.  Are you able to run
>the tests for ResourceManager okay?
> 
>Thanks,
> 
>Chris
> 
>> From: aha...@adobe.com
>> To: dev@flex.apache.org
>> Subject: Re: Could not find compiled locale with mustella
>>ResourceManager tests
>> Date: Thu, 11 Dec 2014 00:50:40 +0000
>> 
>> First, did the locale compile work?  Are there _rb.swc files in the
>>sdk’s
>> frameworks/locale/fr_FR folder?
>> 
>> Are you adding a test to an existing file of tests or creating a whole
>>new
>> thing?  There are .compile files that control what locales get compiled
>> into a SWF.  See the mustella/tests/RuntimeLocalization folder for
>> examples of them.  The default just compiles en_US into the SWF.
>> 
>> -Alex
>> 
>> 
>> On 12/10/14, 3:23 PM, "Chris Martin" <chrsm...@outlook.com> wrote:
>> 
>> >Well, I was hoping compiling for all locales would do the trick, but
>>i'm
>> >still getting the same error.  Silly me was only looking at the readme
>> >for mustella and didn't think to check the readme for the SDK itself.
>> >Any other ideas?  I'm thinking it's a compile switch for the swf that
>>is
>> >generated for the specific test itself.  But that would mean everyone
>> >would be having the problem, and certain Jenkins would be freaking out
>> >with the same error.  So I feel this has to be environmental.
>> > 
>> >Chris
>> > 
>> >> From: bigosma...@gmail.com
>> >> Date: Wed, 10 Dec 2014 12:32:32 -0800
>> >> Subject: Re: Could not find compiled locale with mustella
>> >>ResourceManager tests
>> >> To: dev@flex.apache.org
>> >> 
>> >> Try doing ant other.locales first?  That's what the README seems to
>> >> indicate.
>> >> 
>> >> If you want only fr_FR, you could try ant -Dlocale=fr_FR
>> >> 
>> >> Thanks,
>> >> Om
>> >> 
>> >> On Wed, Dec 10, 2014 at 12:28 PM, Chris Martin <chrsm...@outlook.com>
>> >>wrote:
>> >> 
>> >> >  Hey everyone,
>> >> >
>> >> > In trying to create a new mustella test case for ResourceManager,
>>i'm
>> >> > trying to run the tests to get a baseline.  When I run the tests I
>> >>get a
>> >> > failure.
>> >> >
>> >> >      [java] =====================================================
>> >> >      [java]  Failed:
>> >> >      [java] =====================================================
>> >> >      [java]
>> >> > 
>> 
>>>>resources/ResourceManager/Integration/ResourceManager_Integration_UICom
>>>>po
>> >>nent_resourcesChanged
>> >> > 
>>ResourceManager_Integration_UIComponent_resourcesChanged_localeChain
>> >>Failed
>> >> > Timed out
>> >> >
>> >> > How when it fails, the swf that is running reports the following
>> >>error:
>> >> >
>> >> > Error: Could not find compiled locale 'fr_FR'.
>> >> >  at mx.resources::ResourceManagerImpl/set
>> >> > 
>> 
>>>>localeChain()[C:\Users\cmartin\Documents\GitHub\flex-sdk\frameworks\pro
>>>>je
>> >>cts\framework\src\mx\resources\ResourceManagerImpl.as:248]
>> >> >  at
>> >> > 
>> 
>>>>ResourceManager_Methods_findResourceBundleWithResource/___ResourceManag
>>>>er
>> 
>>>>_Methods_findResourceBundleWithResource_RunCode6_code()[C:\Users\cmarti
>>>>n\
>> 
>>>>Documents\GitHub\flex-sdk\mustella\tests\resources\ResourceManager\Meth
>>>>od
>> >>s\ResourceManager_Methods_findResourceBundleWithResource.mxml:137]
>> >> >  at flash.events::EventDispatcher/dispatchEventFunction()
>> >> >  at flash.events::EventDispatcher/dispatchEvent()
>> >> >  at
>> >> > 
>> 
>>>>RunCode/doStep()[C:\Users\cmartin\Documents\GitHub\flex-sdk\mustella\as
>>>>3\
>> >>src\mustella\RunCode.as:46]
>> >> >  at
>> >> > 
>> 
>>>>TestStep/execute()[C:\Users\cmartin\Documents\GitHub\flex-sdk\mustella\
>>>>as
>> >>3\src\mustella\TestStep.as:65]
>> >> >  at
>> >> > 
>> 
>>>>TestCase/runSteps()[C:\Users\cmartin\Documents\GitHub\flex-sdk\mustella
>>>>\a
>> >>s3\src\mustella\TestCase.as:418]
>> >> >  at
>> >> > 
>> 
>>>>TestCase/runSetup()[C:\Users\cmartin\Documents\GitHub\flex-sdk\mustella
>>>>\a
>> >>s3\src\mustella\TestCase.as:272]
>> >> >  at
>> >> > 
>> 
>>>>TestCase/runTest()[C:\Users\cmartin\Documents\GitHub\flex-sdk\mustella\
>>>>as
>> >>3\src\mustella\TestCase.as:251]
>> >> >  at
>> >> > 
>> 
>>>>UnitTester/runTests()[C:\Users\cmartin\Documents\GitHub\flex-sdk\mustel
>>>>la
>> >>\as3\src\mustella\UnitTester.as:1984]
>> >> >
>> >> > Now, I'm sure I'm just missing that "little something" to get this
>>to
>> >> > work, but I don't quite know my way around Mustella quite yet.  Any
>> >> > pointers would be awesome.  Or even if you get the same error when
>> >>you try
>> >> > to run the mustella tests for ResourceManager via the command line:
>> >> >
>> >> > ./mini_run.sh tests/resources/ResourceManager/
>> >> >
>> >> > while in the mustella directory.
>> >> >
>> >> > Thanks in advance,
>> >> >
>> >> > Chris
>> >> >
>> >                                      
>> 
>                                         

Reply via email to