Hi Alex, Well it Needs this, only if you want to have automated FlexUnit or whatsoever Unit tests running in your build. If you only want to build a Flex/Air application, you don't Need it.
Chris ________________________________________ Von: Alex Harui <[email protected]> Gesendet: Dienstag, 7. Januar 2014 18:22 An: [email protected] Betreff: Re: AW: Running unit tests with flashplayer under wine Just curious: why does flexmojos need the flash player to run at all during a build? On 1/7/14 7:41 AM, "wim.deblauwe" <[email protected]> wrote: >I just did a test with xvfb. I now get a "broken pipe" error: > >Xvfb starting$ Xvfb :1 -screen 0 1024x768x24 -fbdir >/var/lib/jenkins/2014-01-07_16-27-521847713838354367507xvfb >.... > >[INFO] --- flexmojos-maven-plugin:6.0.1:test-run (default-test-run) @ >client-domain --- >[INFO] Flexmojos 6.0.1 >[INFO] GPL License - Version 2.0 (NO WARRANTY) - See COPYRIGHT file >[DEBUG] Found 1 test runners: >[TestRunner.swf] >[DEBUG] Using test port '43627' and test control port '40158' >[DEBUG] Flexmojos test port: 43627 - control: 40158 >[INFO] Running tests >/var/lib/jenkins/jobs/Flux/workspace/client-domain/target/test-classes/Tes >tRunner.swf >[DEBUG] [net.flexmojos.oss.test.monitor.AsVmPing] opened server socket on >port 40158 >[DEBUG] [LAUNCHER] ASVmLauncher starting >[DEBUG] [LAUNCHER] exec: [flashplayer] - >/var/lib/jenkins/jobs/Flux/workspace/client-domain/target/test-classes/Tes >tRunner.swf >[DEBUG] [LAUNCHER] Creating process >[WARNING] [LAUNCHER] Using regular flashplayer tests >[DEBUG] [LAUNCHER] Executing command: [flashplayer, >/var/lib/jenkins/jobs/Flux/workspace/client-domain/target/test-classes/Tes >tRunner.swf] >[DEBUG] [net.flexmojos.oss.test.monitor.ResultHandler] opened server >socket >on port 43627 >[DEBUG] [LAUNCHER] Process created java.lang.UNIXProcess@d6a6acb >[DEBUG] [MOJO] launcher STARTED >[DEBUG] [MOJO] pinger STARTED >[DEBUG] [MOJO] resultHandler STARTED >[DEBUG] [LAUNCHER] Output pumpers ON >[DEBUG] [LAUNCHER] Waiting for flashplayer termination >[DEBUG] [SYSOUT]: Starting flashplayer using WINE >[DEBUG] [SYSOUT]: DISPLAY=:1 >[DEBUG] [MOJO] launcher RUNNING >[DEBUG] [MOJO] pinger STARTED >[DEBUG] [MOJO] resultHandler STARTED >[DEBUG] [SYSERR]: p11-kit: couldn't load module: >/usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: >/usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object >file: No such file or directory >[DEBUG] [MOJO] launcher RUNNING >[DEBUG] [MOJO] pinger STARTED >[DEBUG] [MOJO] resultHandler STARTED >[DEBUG] [SYSERR]: libGL: OpenDriver: trying >/usr/lib/i386-linux-gnu/dri/tls/swrast_dri.so >[DEBUG] [SYSERR]: libGL: OpenDriver: trying >/usr/lib/i386-linux-gnu/dri/swrast_dri.so >[DEBUG] [SYSERR]: fixme:thread:start_thread Started native thread 0000002c >[DEBUG] [SYSERR]: fixme:thread:start_thread Started native thread 0000002b >[DEBUG] [SYSERR]: fixme:d3d:wined3d_guess_card No card selector available >for card vendor 0000 (using GL_RENDERER "Gallium 0.4 on llvmpipe (LLVM >3.3, >128 bits)"). >[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]: fixme:win:EnumDisplayDevicesW >((null),0,0x33dd48,0x00000000), stub! >[DEBUG] [SYSERR]: fixme:win:EnumDisplayDevicesW >((null),0,0x33ce24,0x00000000), stub! >[DEBUG] [SYSERR]: fixme:win:EnumDisplayDevicesW >((null),0,0x33e0e8,0x00000000), stub! >[DEBUG] [SYSERR]: fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not >officially supported by the wine project >[DEBUG] [SYSERR]: fixme:winediag:AUDDRV_GetAudioEndpoint For sound related >feedback and support, please visit >http://ubuntuforums.org/showthread.php?t=1960599 >[DEBUG] [MOJO] launcher RUNNING >[DEBUG] [MOJO] pinger STARTED >[DEBUG] [MOJO] resultHandler STARTED >[DEBUG] [net.flexmojos.oss.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] [MOJO] launcher RUNNING >[DEBUG] [MOJO] pinger ERROR >[DEBUG] [MOJO] resultHandler STARTED >[DEBUG] [LAUNCHER] process has not been finished, destroying >[INFO] >------------------------------------------------------------------------ >[INFO] Tests run: 0, Failures: 0, Errors: 0, Time Elapsed: 0 sec >[ERROR] Broken pipe - >/var/lib/jenkins/jobs/Flux/workspace/client-domain/target/test-classes/Tes >tRunner.swf >net.flexmojos.oss.test.TestRunnerException: Broken pipe - >/var/lib/jenkins/jobs/Flux/workspace/client-domain/target/test-classes/Tes >tRunner.swf >at net.flexmojos.oss.test.DefaultTestRunner.run(DefaultTestRunner.java:84) >at net.flexmojos.oss.plugin.test.TestRunMojo.runTest(TestRunMojo.java:407) >at net.flexmojos.oss.plugin.test.TestRunMojo.runTest(TestRunMojo.java:374) >at >net.flexmojos.oss.plugin.test.TestRunMojo.runTests(TestRunMojo.java:432) >at net.flexmojos.oss.plugin.test.TestRunMojo.run(TestRunMojo.java:310) >at >net.flexmojos.oss.plugin.test.TestRunMojo.execute_aroundBody0(TestRunMojo. >java:262) >at >net.flexmojos.oss.plugin.test.TestRunMojo.execute_aroundBody1$advice(TestR >unMojo.java:41) >at >net.flexmojos.oss.plugin.test.TestRunMojo.execute_aroundBody2(TestRunMojo. >java:249) >at >net.flexmojos.oss.plugin.test.TestRunMojo.execute_aroundBody3$advice(TestR >unMojo.java:34) >at net.flexmojos.oss.plugin.test.TestRunMojo.execute(TestRunMojo.java:1) >at >org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuild >PluginManager.java:106) >at >org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java >:208) >at >org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java >:153) >at >org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java >:145) >at >org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Li >fecycleModuleBuilder.java:84) >at >org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Li >fecycleModuleBuilder.java:59) >at >org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(L >ifecycleStarter.java:183) >at >org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStar >ter.java:161) >at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:317) >at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152) >at >org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java >:132) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: >57) >at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm >pl.java:43) >at java.lang.reflect.Method.invoke(Method.java:606) >at >org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher. >java:330) >at >org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238 >) >at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) >at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >at >sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: >57) >at >sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm >pl.java:43) >at java.lang.reflect.Method.invoke(Method.java:606) >at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) >at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) >at hudson.remoting.UserRequest.perform(UserRequest.java:118) >at hudson.remoting.UserRequest.perform(UserRequest.java:48) >at hudson.remoting.Request$2.run(Request.java:328) >at >hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorSer >vice.java:72) >at java.util.concurrent.FutureTask.run(FutureTask.java:262) >at >java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java: >1145) >at >java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java >:615) >at java.lang.Thread.run(Thread.java:744) >Caused by: java.net.SocketException: Broken pipe >at java.net.SocketOutputStream.socketWrite0(Native Method) >at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) >at java.net.SocketOutputStream.write(SocketOutputStream.java:159) >at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) >at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) >at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) >at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) >at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) >at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:216) >at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:474) >at org.codehaus.plexus.util.IOUtil.copy(IOUtil.java:461) >at net.flexmojos.oss.test.monitor.AsVmPing.handleRequest(AsVmPing.java:66) >at >net.flexmojos.oss.test.monitor.AbstractSocketThread.run(AbstractSocketThre >ad.java:61) >... 1 more >[DEBUG] [LAUNCHER] Flashplayer closed >[DEBUG] [LAUNCHER] Unexpected return code 143 > >regards, > >Wim > > > >2014/1/7 Christofer Dutz [via Apache Flex Users] < >[email protected]> > >> An alternative would be xvfb ... I remember that I invested days and >>even >> weeks in trying to get a Flexmojos CI build up and running on a Linux >> machine: >> >> >> >>https://dev.c-ware.de/confluence/display/PUBLIC/Building+Flexmojos+on+a+H >>eadless+64Bit+Ubuntu+10.04+CI-Server >> >> After getting the virtual Screen stuff up and running, I ran into loads >>of >> Problems with the Linux FlashPlayer and finally gave up renting a >>Windows >> Amazon EC2 Node because I would rather pay a few bucks for the Windows >> Machine than ruin my sanity by getting the FlashPlayer up and running on >> Linux by my headless CI Server ;-) >> >> Chris >> >> ________________________________________ >> Von: wim.deblauwe <[hidden >>email]<http://user/SendEmail.jtp?type=node&node=4381&i=0>> >> >> Gesendet: Dienstag, 7. Januar 2014 12:29 >> An: [hidden email] <http://user/SendEmail.jtp?type=node&node=4381&i=1> >> Betreff: Re: AW: Running unit tests with flashplayer under wine >> >> VNC is there because I run jenkins as a service on Ubuntu, so there is >>no >> graphical display available. >> >> >> 2014/1/7 Tom Chiverton [via Apache Flex Users] < >> [hidden email] <http://user/SendEmail.jtp?type=node&node=4381&i=2>> >> >> > Wow, complicated. >> > >> > Are you trying to work around the fact your Jenkins machine is >>headless >> > ? Or something else ? Basically, why is VNC here at all ? >> > >> > Tom >> > >> > On 07/01/2014 09:23, wim.deblauwe wrote: >> > >> > > I am not totally in the clear yet. I don't have it working through >> > jenkins >> > > yet. >> > > >> > > * I have installed vnc4server package (sudo apt-get install >> vnc4server) >> > and >> > > the vnc plugin in jenkins. >> > > * I have set the option in the build settings of my project to start >> > vnc. >> > > * I can connect using vinagre to this desktop >> > > * I have checked that the DISPLAY variable is set in a pre-build >>step >> by >> > > running: echo $DISPLAY >> > > * If I start vncserver manually, set the DISPLAY manually and then >>run >> > my >> > > 'flashplayer' script, I see the flashplayer starting in the remote >> > desktop. >> > > >> > > I have the feeling that wine does not seem to pick up the display >> > variable >> > > for some reason. >> > > >> > > All ideas welcome! >> > > >> > > regards, >> > > >> > > Wim >> > > >> > > >> > > >> > > -- >> > > View this message in context: >> > >> >>http://apache-flex-users.2333346.n4.nabble.com/Running-unit-tests-with-fl >>ashplayer-under-wine-tp4284p4374.html >> > >> > > Sent from the Apache Flex Users mailing list archive at Nabble.com. >> > > >> > > >>______________________________________________________________________ >> > > This email has been scanned by the Symantec Email Security.cloud >> > service. >> > > For more information please visit http://www.symanteccloud.com >> > > >>______________________________________________________________________ >> > > >> > > >> > >> > >> > >> > ------------------------------ >> > If you reply to this email, your message will be added to the >> discussion >> > below: >> > >> > >> >>http://apache-flex-users.2333346.n4.nabble.com/Running-unit-tests-with-fl >>ashplayer-under-wine-tp4284p4375.html >> > To unsubscribe from Running unit tests with flashplayer under wine, >> click >> > here< >> >> > . >> > NAML< >> >>http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet.jtp?m >>acro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml. >>namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble >>.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble% >>3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21na >>bble%3Aemail.naml> >> >> > >> >> >> >> >> -- >> View this message in context: >> >>http://apache-flex-users.2333346.n4.nabble.com/Running-unit-tests-with-fl >>ashplayer-under-wine-tp4284p4380.html >> >> Sent from the Apache Flex Users mailing list archive at Nabble.com. >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the >>discussion >> below: >> >> >>http://apache-flex-users.2333346.n4.nabble.com/Running-unit-tests-with-fl >>ashplayer-under-wine-tp4284p4381.html >> To unsubscribe from Running unit tests with flashplayer under wine, >>click >> >>here<http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet. >>jtp?macro=unsubscribe_by_code&node=4284&code=d2ltLmRlYmxhdXdlQGdtYWlsLmNv >>bXw0Mjg0fDExMzA2NTE5NDc=> >> . >> >>NAML<http://apache-flex-users.2333346.n4.nabble.com/template/NamlServlet. >>jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble. >>naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-n >>abble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21na >>bble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email >>%21nabble%3Aemail.naml> >> > > > > >-- >View this message in context: >http://apache-flex-users.2333346.n4.nabble.com/Running-unit-tests-with-fla >shplayer-under-wine-tp4284p4383.html >Sent from the Apache Flex Users mailing list archive at Nabble.com.
