Quantcast
Channel: Adobe Community : Popular Discussions - FlexUnit
Viewing all articles
Browse latest Browse all 25673

FluxUnit 4 Task Fails on Server 2003 via Bamboo 2.6

$
0
0

Hi there,

 

I have a build file which includes tests, runs fine in my local dev environment via Flash Builder 4, and generates reports.  The test portion of the build fails however when executing on my CI server.  Some facts:

 

-CI box = Windows Server 2003 VM with Atlassian's Bamboo as the agent.

-flexUnit.cfg file exists and has the correct paths in it

-I've set the mime type correctly (executing a swf file opens the projector-player)

-I've copied over my flashplayer settings.sol to ensure security is set up the same

-Bamboo is set to run as Local System

-I have a CIListener and UIListener in my TestRunner.mxml file

-Headless mode = false

-The build log shows the following

 

03-Jun-2010 13:48:59[flexunit] Opening server socket on port  [1024].
03-Jun-2010 13:48:59[flexunit] Waiting for client connection ...
03-Jun-2010 13:49:59[flexunit]
03-Jun-2010 13:49:59[flexunit] Stopping server ...
03-Jun-2010 13:49:59[flexunit] End of test data reached, sending  acknowledgement to player ...
03-Jun-2010 13:49:59[flexunit] Closing client connection ...
03-Jun-2010 13:49:59[flexunit] Closing server on port [1024] ...

 


It appears that a connection can't be made to the player.  While I am remoted into the CI box, I can see a FlashPlayer process start up while the build is executing - nothing appears on the screen though. I noticed in a post someone mention that Server 2003 could run in  headless mode, however, when I have this set FlexUnitTasks throws an  error stating that headless mode isn't supported on windows.

 

Remember, everything works perfectly while running on my local machine, with the same build file, folder locations, and so on...

 

Any idea on what else I can try to made this work?


Viewing all articles
Browse latest Browse all 25673

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>