Did you tried 3.6-SNAPSHOT?

VELO

On Wed, Mar 10, 2010 at 10:13 PM, cholm <[email protected]> wrote:

> The debug output for test-run on the flex unit sample (with mojos
> 3.5.0 and flex unit version changed to 0.90, although the same result
> with 0.85) is below.  I have seen something similar on a thread here,
> where we don't run any tests and get the same invalid state error
> message, however in that case the issue was upgrading from FlexUnit
> 0.90 to 4 (none of the tests had the [Test] metadata, and thus
> FlexUnit 4 didn't recognize them as tests as I understand it), whereas
> I am using FlexUnit 0.90 with naming convention recognized tests.
> Again, hope this is helpful at all, if anyone has a look and would
> like any more info please let me know
>
> [INFO] [flexmojos:test-run]
> [INFO] Flexmojos 3.5.0
> [INFO]   Apache License - Version 2.0 (NO WARRANTY) - See COPYRIGHT
> file
> [INFO] Running tests /usr/local/hudson/jobs/flexmojos-test/workspace/
> flexunit-example/target/test-classes/TestRunner.swf
> [DEBUG] [org.sonatype.flexmojos.test.monitor.AsVmPing] opened server
> socket on port 13540
> [DEBUG] [org.sonatype.flexmojos.test.monitor.ResultHandler] opened
> server socket on port 13539
> [DEBUG] [LAUNCHER] ASVmLauncher starting
> [DEBUG] [LAUNCHER] exec: flashplayer - /usr/local/hudson/jobs/
> flexmojos-test/workspace/flexunit-example/target/test-classes/
> TestRunner.swf
> [DEBUG] [LAUNCHER] Creating process
> [WARNING] [LAUNCHER] Using xvfb-run to launch headless tests
> [DEBUG] [LAUNCHER] Process created java.lang.unixproc...@3514a9dc
> [DEBUG] [MOJO] launcher RUNNING
> [DEBUG] [MOJO] pinger STARTED
> [DEBUG] [MOJO] resultHandler STARTED
> [DEBUG] [LAUNCHER] Output pumpers ON
> [DEBUG] [LAUNCHER] Waiting for flashplayer termination
> [DEBUG] [MOJO] launcher RUNNING
> [DEBUG] [MOJO] pinger STARTED
> [DEBUG] [MOJO] resultHandler STARTED
> [DEBUG] [MOJO] launcher RUNNING
> [DEBUG] [MOJO] pinger STARTED
> [DEBUG] [MOJO] resultHandler STARTED
> [DEBUG] [MOJO] launcher RUNNING
> [DEBUG] [MOJO] pinger STARTED
> [DEBUG] [MOJO] resultHandler STARTED
> [DEBUG] [SYSERR]: /usr/bin/xvfb-run: line 168: 11771 Segmentation
> fault      DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE "$@" 2>&1
> [DEBUG] [LAUNCHER] Flashplayer closed
> [DEBUG] [LAUNCHER] Flashplayer exit as expected
> [DEBUG] [MOJO] launcher DONE
> [DEBUG] [MOJO] pinger STARTED
> [DEBUG] [MOJO] resultHandler STARTED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Tests run: 0, Failures: 0, Errors: 0, Time Elapsed: 0 sec
> [HUDSON] Archiving /usr/local/hudson/jobs/flexmojos-test/workspace/
> flexunit-example/pom.xml to /usr/local/hudson/jobs/flexmojos-test/
> modules/com.adobe.samples$calculator-api/builds/2010-03-10_18-08-12/
> archive/com.adobe.samples/calculator-api/1.0-SNAPSHOTpom.xml
> [HUDSON] Archiving /usr/local/hudson/jobs/flexmojos-test/workspace/
> flexunit-example/target/calculator-api-1.0-SNAPSHOT.swc to /usr/local/
> hudson/jobs/flexmojos-test/modules/com.adobe.samples$calculator-api/
> builds/2010-03-10_18-08-12/archive/com.adobe.samplescalculator-api/1.0-
> SNAPSHOT/calculator-api-1.0-SNAPSHOT.swc
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Invalid state: the flashplayer is closed, but the sockets still
> running...
>
> [INFO]
> ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Invalid state:
> the flashplayer is closed, but the sockets still running...
>         at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 584)
>        at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:
> 500)
>        at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:
> 479)
>        at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:
> 331)
>        at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:
> 292)
>        at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:
> 142)
>        at
>
> org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:
> 65)
>        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
>        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
>        at org.apache.maven.cli.MavenCli.main(MavenCli.java:301)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> 39)
>        at
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> 25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>        at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:
> 315)
>        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>        at hudson.maven.agent.Main.launch(Main.java:165)
>        at hudson.maven.MavenBuilder.call(MavenBuilder.java:159)
>        at hudson.maven.MavenModuleSetBuild
> $Builder.call(MavenModuleSetBuild.java:584)
>        at hudson.maven.MavenModuleSetBuild
> $Builder.call(MavenModuleSetBuild.java:530)
>        at hudson.remoting.UserRequest.perform(UserRequest.java:103)
>        at hudson.remoting.UserRequest.perform(UserRequest.java:47)
>        at hudson.remoting.Request$2.run(Request.java:236)
>        at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:
> 441)
>        at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
>        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
>        at java.util.concurrent.ThreadPoolExecutor
> $Worker.runTask(ThreadPoolExecutor.java:886)
>        at java.util.concurrent.ThreadPoolExecutor
> $Worker.run(ThreadPoolExecutor.java:908)
>        at java.lang.Thread.run(Thread.java:619)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Invalid
> state: the flashplayer is closed, but the sockets still running...
>         at
> org.sonatype.flexmojos.test.FlexUnitMojo.tearDown(FlexUnitMojo.java:
> 302)
>        at
> org.sonatype.flexmojos.test.FlexUnitMojo.execute(FlexUnitMojo.java:
> 152)
>        at
>
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:
> 453)
>        at
>
> hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:
> 182)
>        at
>
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:
> 559)
>        ... 28 more
> Caused by: org.sonatype.flexmojos.test.TestRunnerException: Invalid
> state: the flashplayer is closed, but the sockets still running...
>         at
> org.sonatype.flexmojos.test.DefaultTestRunner.run(DefaultTestRunner.java:
> 83)
>        at org.sonatype.flexmojos.test.FlexUnitMojo.run(FlexUnitMojo.java:
> 266)
>        at
> org.sonatype.flexmojos.test.FlexUnitMojo.execute(FlexUnitMojo.java:
> 151)
>        ... 31 more
>
> On Mar 10, 6:03 pm, cholm <[email protected]> wrote:
> > Update in case anyone has a look...
> >
> > So I've managed to manifest a different issue, which I have only seen
> > referenced with regards to FlexUnit 4 here (I am using 0.90).  My
> > project sets flash player 10 as the target version, we had a
> > standalone 9 player on the CentOS box, so I put version 10 on the
> > machine.  Now, for both my project and the flex unit sample, I get:
> >
> > with FlexMojos 3.5.0 I get an 'Invalid state: the flashplayer is
> > closed, but the sockets still running...' error message.
> >
> > with FlexMojos 3.4.2 an error code 139
> >
> > I'm sure this isn't very helpful, but wanted to throw it out there in
> > case it is relevant.
> >
> > On Mar 10, 4:45 pm, cholm <[email protected]> wrote:
> >
> > > I know there is a whole lot here and on the wiki regarding unit
> > > testing on headless linux boxes, as well as working with CI tools, so
> > > my apologies if this is covered elsewhere... I have spent about the
> > > last hour trying to track something down, hopefully I didn't overlook
> > > anything.  I tried all of the tips from the wiki without success.
> >
> > > I am using flex mojos 3.5.0 and Flex SDK 3.4, CI is Hudson on a CentOS
> > > box.
> >
> > > Anyway, I will try to keep this as simple as possible and provide
> > > detail as needed.  I ran into trouble with a project, so I added a
> > > Hudson job to build the FlexUnit sample project referenced on the unit
> > > testing wiki page, and got the same results with the sample project; I
> > > can pull the code down and build it (mvn clean install) manually as
> > > root without any problems, however when Hudson (which runs all of its
> > > jobs as root) runs the same command the test-run phase hangs
> > > indefinitely (or at least for 15 or so minutes, as long as I waited).
> >
> > > The debug output for the test-run phase is:
> >
> > > [INFO] [flexmojos:test-run]
> > > [INFO] Flexmojos 3.5.0
> > > [INFO]   Apache License - Version 2.0 (NO WARRANTY) - See COPYRIGHT
> > > file
> > > [INFO] Running tests /usr/local/hudson/jobs/flexmojos-test/workspace/
> > > flexunit-example/target/test-classes/TestRunner.swf
> > > [DEBUG] [org.sonatype.flexmojos.test.monitor.AsVmPing] opened server
> > > socket on port 13540
> > > [DEBUG] [org.sonatype.flexmojos.test.monitor.ResultHandler] opened
> > > server socket on port 13539
> > > [DEBUG] [LAUNCHER] ASVmLauncher starting
> > > [DEBUG] [LAUNCHER] exec: flashplayer - /usr/local/hudson/jobs/
> > > flexmojos-test/workspace/flexunit-example/target/test-classes/
> > > TestRunner.swf
> > > [DEBUG] [LAUNCHER] Creating process
> > > [WARNING] [LAUNCHER] Using xvfb-run to launch headless tests
> > > [DEBUG] [LAUNCHER] Process created java.lang.unixproc...@670d6e40
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger STARTED
> > > [DEBUG] [MOJO] resultHandler STARTED
> > > [DEBUG] [LAUNCHER] Output pumpers ON
> > > [DEBUG] [LAUNCHER] Waiting for flashplayer termination
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger STARTED
> > > [DEBUG] [MOJO] resultHandler STARTED
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger STARTED
> > > [DEBUG] [MOJO] resultHandler STARTED
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger STARTED
> > > [DEBUG] [MOJO] resultHandler STARTED
> > > [DEBUG] [org.sonatype.flexmojos.test.monitor.AsVmPing] accepting data
> > > from client
> > > [DEBUG] [CONTROL] AsVmControl handleRequest
> > > [DEBUG] [CONTROL] query status
> > > [DEBUG] [CONTROL] received status
> > > [DEBUG] [CONTROL] status is: <policy-file-request/>
> > > [DEBUG] [CONTROL] query status
> > > [DEBUG] [CONTROL] received status
> > > [DEBUG] [CONTROL] status is: null
> > > [DEBUG] [CONTROL] query status
> > > [DEBUG] [org.sonatype.flexmojos.test.monitor.ResultHandler] accepting
> > > data from client
> > > [DEBUG] [RESULT] Recivied data: <policy-file-request/>
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger DONE
> > > [DEBUG] [MOJO] resultHandler RUNNING
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger DONE
> > > [DEBUG] [MOJO] resultHandler RUNNING
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger DONE
> > > [DEBUG] [MOJO] resultHandler RUNNING
> > > [DEBUG] [RESULT] Socket buffer
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger DONE
> > > [DEBUG] [MOJO] resultHandler DONE
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger DONE
> > > [DEBUG] [MOJO] resultHandler DONE
> > > [DEBUG] [MOJO] launcher RUNNING
> > > [DEBUG] [MOJO] pinger DONE
> > > [DEBUG] [MOJO] resultHandler DONE
> >
> > > and loops like this indefinitely.
> >
> > > I hope this is enough information, please let me know if anything else
> > > would be helpful (pom files etc).
>
> --
> 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]<flex-mojos%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos?hl=en?hl=en
>
> 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?hl=en?hl=en

http://flexmojos.sonatype.org/

Reply via email to