On Wed, Dec 17, 2008 at 8:50 AM, codebeneath <[email protected]> wrote:
> On the topic of this thread, I see the same problem with the flexunit
> timeout in hudson.  Command line works as expected, but hudson gets
> stuck as you describe for continuum.  I worked great with version
> 2.0M9 and around the time 2.0M10 came out, it stop working.  Plugging
> back 2.0M9 back into the poms did not fix the problem.  (the maven
> download of 2.0M10 and its transitive dependencies may need to be
> cleared from the local maven repo... have not had time to try that
> yet)

Is your Hudson running on Windows or Linux? Our Linux Hudson
installation is running fine, so I'd like to find out more details.

Can you change your Hudson config to add -X to the maven command. That
will show the debugging output from trying to launch the tests to
determine the issue.

We have one other issue I remember now, but not sure if it's Linux or
Hudson. If one of our tests pops up a Flash Player error dialog due to
an unhandled error event, the Hudson build just stops, instead of
timing out and failing the test.

Logan

--~--~---------~--~----~------------~-------~--~----~
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?hl=en?hl=en

http://blog.flex-mojos.info/
-~----------~----~----~----~------~----~------~--~---

Reply via email to