We've set up a bunch of flexmojo configured projects in our CI tool. When two projects are built concurrently on the same build server we occasionally see a build fail with the following error...
[INFO] Running tests C:\PATH_TO_PROJECT\core-util\target\test-classes \TestRunner.swf [WARNING] [LAUNCHER] Using regular flashplayer tests [INFO] ------------------------------------------------------------------------ [INFO] Tests run: 0, Failures: 0, Errors: 0, Time Elapsed: 0 sec [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Address already in use: JVM_BindC:\PATH_TO_PROJECT\core-util \target\test-classes\TestRunner.swf This is caused by the two builds using the same ports to connect to the flashplayer running the unit tests. In theory we could configure each project with a unique set of testPort and testControlPort configurations, but this would get ugly as we'd have to insure each project had it's own unique values. A more flexible approach would be set a range of ports for all projects. The unit test runner could then attempt to bind to a random value within this range, and automatically retry if that port is not available. Regards Andy -- 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/
