Help with flex4unit ant build.xml: Socket timeout waiting for flexunit report

Question

I'm having trouble setting up ant to build and test my project locally and I'm not sure what the next step is.
Info:
Running on XP/Cygwin.
All of the files that FlexUnit4 references when used in Flash Builder are in my '${basename}/libs' folder (eg FlexUnit4_1.0.swc).
I've placed the flexunit4 task in my ant/libs folder.
I'm getting two errors...
I don't think I've set up the 'socket' stuff right for the tests. It just sits and waits then dies...
[flexunit] Waiting for client connection ...
(about a minute later)
[flexunit] Stopping server ...
[flexunit] End of test data reached, sending acknowledgement to player ...
[flexunit] Closing client connection ...
[flexunit] Closing server on port [1024] ...
BUILD FAILED
java.util.concurrent.ExecutionException: Socket timeout waiting for flexunit report
Plus this is the error I get from the flash player:
ReferenceError: Error #1065: Variable mx.skins.spark::BorderSkin is not defined.
I don't know why it's complaining about Borderskin as I think I have included all the flex4 libs I could find. I suspect this second error is causing the first error?
Any help appreciated. I think I'm just setting it up all wrong.
Screencap of errors:
http://twitpic.com/l7ay8
build.xml:
http://gist.github.com/20804

Answer 1

Finally got everything working using the files from the CI Example which what i probably should have done in the first place.
So a rough guide for anyone just starting out with this:
Download the Flex 4 'workspace' from the digital primates hudson server . This appears to contain flexunit library and examples in various stages of development.
I used Flex Builder 4 Beta 2 to set up my Test Suite and Test Cases.
I then loaded the libs folder from:
workspace.zip\workspace\project\FlexUnit4SampleCIProject
into my flex project's libs folder:
this includes:
FlexUnit4.swc
FlexUnit4CIListener.swc
flexUnit4UIRunner.swc
flexTasks.jar
flexUnitTasks.jar
I didn't need to remove the FlexUnit4 stuff that is 'referenced' automatically by flash builder when you start adding flexunit4 tests/suites.
Then I used a modified version of the TestRunner.mxml found in:
workspace.zip\workspace\project\FlexUnit4SampleCIProject\src\test\flex
The lines to pay attention to are the ones that look like:
static public function currentRunTestSuite():Array {
    var testsToRun:Array = new Array();
    testsToRun.push(packagename.TestSuiteName);
    testsToRun.push(packagename.TestClassName);
    return testsToRun;
Just make sure you update this list to include all of the test suites &/or individual tests you want to run.
I made this a static function and modified the code in the "FlexUnitApplication.mxml" file to use this function so i'd only need to update one list of suites/tests.
FlexUnitApplication.mxml is generated automatically when you run FlexUnit4 tests in the Flash Builder 4 Beta 2 IDE.
This is the build.xml file I'm using in the project:
http://gist.github.com/208211
Change the name of the project from "Flare" to whatever and adjust the other path settings where required (though you might want to write this from scratch at least once so you understand roughly what is going on).
The Debug Flash Player must be installed on the server otherwise you'll get a:
java.util.concurrent.ExecutionException: Socket timeout waiting for flexunit report
...while it waits for the non-existant debugger to attach. (This is obvious but I did forget and was a bit bewildered for a moment)
Need to also ensure the environment variable:FLEX_HOME is set to the location you installed the flex sdk...by editing your .bashrc setting the environment variable the in the Hudson Configuration.
You'll need to point Hudson at your ant installation and your jdk installation. If you downloaded he sdk, be aware you might need to point it to the jdk folder inside the place you installed the sdk.
And I think that's all the problems I had. Hope it's useful to someone... if anyone who actually knows what they are doing can point out any potential issues/better ways of doing things, feel free to comment.
Thanks to Brian (legrosb) and Mike (mlabriola) for their assistance!