After a small phone-discussion ;-)

The problem is indeed related to the issue I described in my
confluence. Unfortunately I can't find the link with the error codes
of the flash player. But it seems to be that it only occurs on 64bit
linux distributions. The problem is that a 64bit VM tries to load the
flashplayer. As far as I know the player comes with some broken 32bit
shared-libs (0 byte size). If you start the flash player it will fail
to load these, but as being a 32bit process it looks in the 32bit lib
directory and will find correct versions there. If you start it from a
64bit process it will fail to load the bundled libs but won't find the
libs in its 64bit lib directory as these 3 libs are only available in
32bit versions. Replacing the broken libs with the ones in the 32bit
lib directory resolved the issue for me.

I realize that my description is a little to vague for someone to fix
the problem without any further assistance. I acutally thought this
was only happening when running the integrationtests of the flexmojos
trunk build. I will try to reproduce my fix and update the
documentation some time next week.

Chris



2011/4/14 Christofer Dutz <[email protected]>:
> I recently documented what I had to do to get the build up and running
> on Ubuntu 10
> http://dev.c-ware.de/confluence/display/PUBLIC/Building+Flexmojos+on+a+Headless+64Bit+Ubuntu+10.04+CI-Server
> I guess the main part was that one of the files downloaded from adobe
> contains invalid so-files (all are 0 bytes) but I guess this only
> occurs with 64bit linuxes.
>
> But I have to admit that my TeamCity build of FM is currently still
> running as I just updated my fm-branch a few minutes ago and in this
> command a lot of tests are enabled again that were disabled for a few
> weeks ... if I run into trouble I'll find out what the reason ist. For
> now, just give my documentation a try.
>
> Chris
>
>
> 2011/4/14 tombc <[email protected]>:
>> This discussion continues
>> http://groups.google.com/group/flex-mojos/browse_thread/thread/3a71e6b552cd1183/0bdf658dd90d93a1?lnk=gst&q=code+127#0bdf658dd90d93a1
>>
>> My headless built on Ubuntu 8.0.4 runs into the 127 return code
>> problem described in the other thread:
>>
>>
>> [INFO] Running tests /tmp/codebank-flex-trunk/target/test-classes/
>> TestRunner.swf
>> [WARNING] [LAUNCHER] Using xvfb-run to launch headless tests
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Tests run: 0, Failures: 0, Errors: 0, Time Elapsed: 0 sec
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 39.783s
>> [INFO] Finished at: Thu Apr 14 12:05:30 CEST 2011
>> [INFO] Final Memory: 15M/194M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal org.sonatype.flexmojos:flexmojos-maven-
>> plugin:3.9:test-run (default-test-run) on project codebank-flex:
>> Unexpected return code 127/tmp/codebank-flex-trunk/target/test-classes/
>> TestRunner.swf -> [Help 1]
>>
>>
>> When starting the TestRunnter.swf with flashplayer directly, I get the
>> following (partially truncated) result:
>>
>>
>> byteconsult@ubuntu:/tmp/codebank-flex-trunk$ /usr/bin/xvfb-run /tmp/
>> flash_player_10_linux_dev/standalone/debugger/flashplayer target/test-
>> classes/TestRunner.swf
>> Property canClose set to false
>> Testing [class TestButtonGroup]
>> Testing [class TestListCollectionView45]
>> Testing [class TestWrappingListCollectionView]
>> Testing [class TestLocaleDate]
>> Testing [class TestDictionaryMap]
>> Testing [class TestMultiLevelDictionary]
>> Running tests using Flexunit4
>> FlexUnit4: Test testProperties in
>> de.byteconsult.codebank.datetime.TestLocaleDate started
>> FlexUnit4: Test testProperties in
>> de.byteconsult.codebank.datetime.TestLocaleDate finished
>> (many more of these lines)...
>> Running 47 tests
>> FlexUnit4: Test testArrayOperatorAccess in
>> de.byteconsult.codebank.collections.TestListCollectionView45 finished
>> FlexUnit4: Test testCreateCursor in
>> de.byteconsult.codebank.collections.TestListCollectionView45 started
>> (many more of these lines)...
>> FlexUnit4: Test testProductsAdd in
>> de.byteconsult.codebank.collections.TestWrappingListCollectionView
>> started
>> FlexUnit4: Test testProductsAdd in
>> de.byteconsult.codebank.collections.TestWrappingListCollectionView
>> finished
>> FlexUnit4: Test testRemoveItemAt in
>> de.byteconsult.codebank.collections.TestWrappingListCollectionView
>> started
>> Error #2044: Unhandled IOErrorEvent:. text=Error #2031: Socket Error.
>>        at org.sonatype.flexmojos.unitestingsupport::ControlSocket/
>> connect()[/home/nexus/flexmojos/3.x/target/checkout/flexmojos-testing/
>> flexmojos-unittest-support/src/main/flex/org/sonatype/
>> flexmojos/                           unitestingsupport/
>> ControlSocket.as:46]
>>        at org.sonatype.flexmojos.unitestingsupport::TestApplication/
>> runTests()[/home/nexus/flexmojos/3.x/target/checkout/flexmojos-testing/
>> flexmojos-unittest-support/src/main/flex/org/sonatype/
>> flexmoj                           os/unitestingsupport/
>> TestApplication.as:52]
>>        at flash.events::EventDispatcher/dispatchEventFunction()
>>        at flash.events::EventDispatcher/dispatchEvent()
>>        at mx.core::UIComponent/dispatchEvent()[C:\autobuild
>> \3.5.0\frameworks\projects\framework\src\mx\core\UIComponent.as:9440]
>>        at mx.core::UIComponent/set initialized()[C:\autobuild
>> \3.5.0\frameworks\projects\framework\src\mx\core\UIComponent.as:1168]
>>        at mx.managers::LayoutManager/doPhasedInstantiation()[C:
>> \autobuild\3.5.0\frameworks\projects\framework\src\mx\managers
>> \LayoutManager.as:718]
>>        at Function/http://adobe.com/AS3/2006/builtin::apply()
>>        at mx.core::UIComponent/callLaterDispatcher2()[C:\autobuild
>> \3.5.0\frameworks\projects\framework\src\mx\core\UIComponent.as:8744]
>>        at mx.core::UIComponent/callLaterDispatcher()[C:\autobuild
>> \3.5.0\frameworks\projects\framework\src\mx\core\UIComponent.as:8684]
>>
>>
>> While the test case where it starts to fail changes from run to run,
>> its always the case that a test is started, and then runs into the
>> IOErrorEvent.
>>
>> Could you give me some help based on this?
>>
>> Thanks a million
>> Tom
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Flex Mojos" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]
>> For more options, visit this group at
>> http://groups.google.com/group/flex-mojos
>>
>> http://flexmojos.sonatype.org/
>>
>

-- 
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos

http://flexmojos.sonatype.org/

Reply via email to