Re: JavaFX on headless Jenkins

[Tom Eugelink]

Jenkins does that for me.


On 2014-1-7 21:13, Matthieu BROUILLARD wrote:

For JFXtras build on travis.org , I just followed some docs 
pages to setup xvfb, sorry I am not a linux/unix expert and don't know how to help 
more.

/[Stupid linux user mode activated]/
If you do not have the  /etc/init.d/xvfb script, can't you launch the program 
itself in background?
/[/Stupid linux user mode activated]/

Matthieu

Re: JavaFX on headless Jenkins

[Matthieu BROUILLARD]

For JFXtras build on travis.org, I just followed some docs pages to setup
xvfb, sorry I am not a linux/unix expert and don't know how to help more.

*[Stupid linux user mode activated]*
If you do not have the  /etc/init.d/xvfb script, can't you launch the
program itself in background?
*[/Stupid linux user mode activated]*

Matthieu

Re: JavaFX on headless Jenkins

[Tom Eugelink]

Nope, Xvfb has the same problem...

Xvfb starting$ /usr/bin/Xvfb :2 -screen 0 1024x768x24 -fbdir 
/var/lib/jenkins/2014-01-07_19-17-242962656246439721545xvfb

...

:*test*
Executing task ':test' (up-to-date check took 0.051 secs) due to:
  No history is available.
Starting process 'Gradle Worker 1'. Working directory: 
/var/lib/jenkins/workspace/JFXtrasLabs8.0 Command: 
/usr/lib/jvm/jdk1.8.0-ea/bin/java 
-Djava.security.manager=jarjar.org.gradle.process.internal.child.BootstrapSecurityManager
 -Dfile.encoding=UTF-8 -ea -cp 
/var/lib/jenkins/.gradle/caches/1.9/workerMain/gradle-worker.jar 
jarjar.org.gradle.process.internal.launcher.GradleWorkerMain
Successfully started process 'Gradle Worker 1'
Gradle Worker 1 executing tests.

jfxtras.labs.scene.control.test.ListSpinnerEditableTest > 
enterSelectValueByTyping STANDARD_ERROR
Graphics Device initialization failed for :  es2, sw
Error initializing QuantumRenderer: no suitable pipeline found
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing 
QuantumRenderer: no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:300)
at 
com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:244)
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:179)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: 
no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:98)
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:128)
... 1 more
Exception in thread "Thread-4" java.lang.RuntimeException: No toolkit found
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:191)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)

jfxtras.labs.scene.control.test.ListSpinnerEditableTest > 
enterSelectValueByTyping FAILED
java.lang.RuntimeException: Unable to show stage

Caused by:
java.util.concurrent.TimeoutException: Timeout waiting for task.



But I can start both the xvnc and Xvfb manually as user Jenkins, for example 
Xvfb:

/jenkins@leah:~$ /usr/bin/Xvfb :2 -screen 0 1024x768x24 -fbdir /tmp//
//SELinux: Disabled on system, not enabling in X server//
//[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, 
removing from list!/

Then I need to ^C to terminate Xvfb.
But it does seem that your Travis environments indeed has run the tests:
https://travis-ci.org/JFXtras/jfxtras-labs/builds/15810910

So the question is: how did Travis do that (since both approaches are 
identical)? One thing I notice is that it starts Xfvb as a service, not as an 
application.
sh -e /etc/init.d/xvfb start

But that script is not available on my Linux after installing Xvfb...

Tom


On 2014-1-7 6:58, Tom Eugelink wrote:

Ok. I saw xfvb passing by, but most blogs talked about xvnc, I'll give that a 
spin. Thanks.

Tom

BTW: the Travis environment keeps reporting errors; it has trouble downloading 
one of the supporting jar from maven.


On 2014-1-6 23:49, Matthieu BROUILLARD wrote:

On the linux nodes on travis.org  xvfb is used to mimic a 
GUI environment on headless nodes.
Have a look at : 
http://about.travis-ci.org/docs/user/gui-and-headless-browsers/ you might be 
probably able to do something like that on your linux box.

Matthieu

Re: JavaFX on headless Jenkins

[David Hill]

On 1/6/14, Jan 6, 3:13 PM, Tom Eugelink wrote:


Yes please, I've got Jenkins setup so it starts a vncserver and it runs on 
linux, so I'm interesting in the option you mention (as long as it doesn't 
require too many hoops I need to jump through).


This will take me a day of so. It would appear that I have not touched this 
since the gradle switchout :-(

Dave

Tom


On 2014-1-6 17:36, David Hill wrote:

On 1/4/14, Jan 4, 3:57 PM, Tom Eugelink wrote:

I'm trying to run JavaFX UI tests using TestFX on a headless Jenkins server (Ubuntu / 
Debian). I've gotten to the point where the UI is actually started by Jenkins, but then 
the test fail with a "no suitable pipeline found". Any suggestions how to fix 
that?


This has long been a challenge with FX. I even modified Glass/Lens to get a 
headless with a VNC option working on Linux & Mac (Windows probably needed a 
little porting). This has never been a priority though, only a casual hobby.

Daniel is working on a refresh of Glass/Lens that may make it even easier to do 
headless (as a side effect).

If there is any interest, I can provide more information on the current 
Glass/Lens headless.

Dave


:*test*
Executing task ':test' (up-to-date check took 0.054 secs) due to:
  No history is available.
Starting process 'Gradle Worker 1'. Working directory: 
/var/lib/jenkins/workspace/JFXtras8.0 Command: 
/usr/lib/jvm/jdk1.8.0-ea/bin/java 
-Djava.security.manager=jarjar.org.gradle.process.internal.child.BootstrapSecurityManager
 -Dfile.encoding=UTF-8 -ea -cp 
/var/lib/jenkins/.gradle/caches/1.9/workerMain/gradle-worker.jar 
jarjar.org.gradle.process.internal.launcher.GradleWorkerMain
Successfully started process 'Gradle Worker 1'
Gradle Worker 1 executing tests.

jfxtras.labs.scene.control.test.ListSpinnerEditableTest > 
enterSelectValueByTyping STANDARD_ERROR
Graphics Device initialization failed for :  es2, sw
Error initializing QuantumRenderer: no suitable pipeline found
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing 
QuantumRenderer: no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:300)
at 
com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:244)
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:179)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: 
no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:98)
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:128)
... 1 more
Exception in thread "Thread-4" java.lang.RuntimeException: No toolkit found
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:191)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)











--
David Hill 
Java Embedded Development

"Basic research is what I am doing when I don't know what I am doing."
-- Wernher von Braun (1912 - 1977)

Re: JavaFX on headless Jenkins

[Tom Eugelink]

Ok. I saw xfvb passing by, but most blogs talked about xvnc, I'll give that a 
spin. Thanks.

Tom

BTW: the Travis environment keeps reporting errors; it has trouble downloading 
one of the supporting jar from maven.


On 2014-1-6 23:49, Matthieu BROUILLARD wrote:

On the linux nodes on travis.org  xvfb is used to mimic a 
GUI environment on headless nodes.
Have a look at : 
http://about.travis-ci.org/docs/user/gui-and-headless-browsers/ you might be 
probably able to do something like that on your linux box.

Matthieu

Re: JavaFX on headless Jenkins

[Matthieu BROUILLARD]

On the linux nodes on travis.org xvfb is used to mimic a GUI environment on
headless nodes.
Have a look at :
http://about.travis-ci.org/docs/user/gui-and-headless-browsers/ you might
be probably able to do something like that on your linux box.

Matthieu

Re: JavaFX on headless Jenkins

[Tom Eugelink]

Yes please, I've got Jenkins setup so it starts a vncserver and it runs on 
linux, so I'm interesting in the option you mention (as long as it doesn't 
require too many hoops I need to jump through).

Tom


On 2014-1-6 17:36, David Hill wrote:

On 1/4/14, Jan 4, 3:57 PM, Tom Eugelink wrote:

I'm trying to run JavaFX UI tests using TestFX on a headless Jenkins server (Ubuntu / 
Debian). I've gotten to the point where the UI is actually started by Jenkins, but then 
the test fail with a "no suitable pipeline found". Any suggestions how to fix 
that?


This has long been a challenge with FX. I even modified Glass/Lens to get a 
headless with a VNC option working on Linux & Mac (Windows probably needed a 
little porting). This has never been a priority though, only a casual hobby.

Daniel is working on a refresh of Glass/Lens that may make it even easier to do 
headless (as a side effect).

If there is any interest, I can provide more information on the current 
Glass/Lens headless.

Dave


:*test*
Executing task ':test' (up-to-date check took 0.054 secs) due to:
  No history is available.
Starting process 'Gradle Worker 1'. Working directory: 
/var/lib/jenkins/workspace/JFXtras8.0 Command: 
/usr/lib/jvm/jdk1.8.0-ea/bin/java 
-Djava.security.manager=jarjar.org.gradle.process.internal.child.BootstrapSecurityManager
 -Dfile.encoding=UTF-8 -ea -cp 
/var/lib/jenkins/.gradle/caches/1.9/workerMain/gradle-worker.jar 
jarjar.org.gradle.process.internal.launcher.GradleWorkerMain
Successfully started process 'Gradle Worker 1'
Gradle Worker 1 executing tests.

jfxtras.labs.scene.control.test.ListSpinnerEditableTest > 
enterSelectValueByTyping STANDARD_ERROR
Graphics Device initialization failed for :  es2, sw
Error initializing QuantumRenderer: no suitable pipeline found
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing 
QuantumRenderer: no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:300)
at 
com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:244)
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:179)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: 
no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:98)
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:128)
... 1 more
Exception in thread "Thread-4" java.lang.RuntimeException: No toolkit found
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:191)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)

Re: JavaFX on headless Jenkins

[Kevin Rushforth]

The headless toolkit mentioned by David and Richard is one possible 
approach, and may be the best long term approach depending on what you 
are trying to test (e.g., it won't test rendering, but might be fine for 
most of your tests), but as Richard notes, it isn't there yet.


If you prefer not to wait for that, one possible solution would be to 
set up a Jenkinks slave to be headful (may need to be hooked up to a 
keyboard/mouse or a display). You could then take a look at the system 
tests in rt/tests/system for examples of how we run headful tests. I 
don't know how feasible this would be for you.


Still another option is to use the oft-maligned StubToolkit (it stubs 
out all of Quantum and Prism), which all of our tests in the graphics 
and controls modules in JavaFX use. This isn't distributed (see 
https://javafx-jira.kenai.com/browse/RT-35010), but can easily be built 
from source.


-- Kevin


Richard Bair wrote:

Hi Tom!

On Jan 4, 2014, at 12:57 PM, Tom Eugelink  wrote:

  

I'm trying to run JavaFX UI tests using TestFX on a headless Jenkins server (Ubuntu / 
Debian). I've gotten to the point where the UI is actually started by Jenkins, but then 
the test fail with a "no suitable pipeline found". Any suggestions how to fix 
that?



This was one of my long-standing TODO items: have a “headless” glass that would 
allow us to run quantum / prism tests headless. However for running scene graph 
or UI control tests, you should be using the “StubToolkit” instead of 
QuantumToolkit. The StubToolkit is located in Graphics/src/test, so for using 
it for 3rd party tests (like JFXtras) you would need to jar up the classes 
produced during a test run of FX. Then just specify the stub toolkit via 
-Djavafx.toolkit=com.sun.javafx.pgstub.StubToolkit

Now, longer term I wanted to nuke the StubToolkit. If we had a headless Glass 
then we could test with Prism/Quantum directly instead of the stubs. But this 
isn’t straightforward so it hasn’t been attempted yet.

Hope that helps.
Richard

  

:*test*
Executing task ':test' (up-to-date check took 0.054 secs) due to:
 No history is available.
Starting process 'Gradle Worker 1'. Working directory: 
/var/lib/jenkins/workspace/JFXtras8.0 Command: 
/usr/lib/jvm/jdk1.8.0-ea/bin/java 
-Djava.security.manager=jarjar.org.gradle.process.internal.child.BootstrapSecurityManager
 -Dfile.encoding=UTF-8 -ea -cp 
/var/lib/jenkins/.gradle/caches/1.9/workerMain/gradle-worker.jar 
jarjar.org.gradle.process.internal.launcher.GradleWorkerMain
Successfully started process 'Gradle Worker 1'
Gradle Worker 1 executing tests.

jfxtras.labs.scene.control.test.ListSpinnerEditableTest > 
enterSelectValueByTyping STANDARD_ERROR
   Graphics Device initialization failed for :  es2, sw
   Error initializing QuantumRenderer: no suitable pipeline found
   java.lang.RuntimeException: java.lang.RuntimeException: Error initializing 
QuantumRenderer: no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:300)
at 
com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:244)
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:179)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)
   Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: 
no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:98)
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:128)
... 1 more
   Exception in thread "Thread-4" java.lang.RuntimeException: No toolkit found
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:191)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)





  

Re: JavaFX on headless Jenkins

[Richard Bair]

Hi Tom!

On Jan 4, 2014, at 12:57 PM, Tom Eugelink  wrote:

> I'm trying to run JavaFX UI tests using TestFX on a headless Jenkins server 
> (Ubuntu / Debian). I've gotten to the point where the UI is actually started 
> by Jenkins, but then the test fail with a "no suitable pipeline found". Any 
> suggestions how to fix that?

This was one of my long-standing TODO items: have a “headless” glass that would 
allow us to run quantum / prism tests headless. However for running scene graph 
or UI control tests, you should be using the “StubToolkit” instead of 
QuantumToolkit. The StubToolkit is located in Graphics/src/test, so for using 
it for 3rd party tests (like JFXtras) you would need to jar up the classes 
produced during a test run of FX. Then just specify the stub toolkit via 
-Djavafx.toolkit=com.sun.javafx.pgstub.StubToolkit

Now, longer term I wanted to nuke the StubToolkit. If we had a headless Glass 
then we could test with Prism/Quantum directly instead of the stubs. But this 
isn’t straightforward so it hasn’t been attempted yet.

Hope that helps.
Richard

> 
> :*test*
> Executing task ':test' (up-to-date check took 0.054 secs) due to:
>  No history is available.
> Starting process 'Gradle Worker 1'. Working directory: 
> /var/lib/jenkins/workspace/JFXtras8.0 Command: 
> /usr/lib/jvm/jdk1.8.0-ea/bin/java 
> -Djava.security.manager=jarjar.org.gradle.process.internal.child.BootstrapSecurityManager
>  -Dfile.encoding=UTF-8 -ea -cp 
> /var/lib/jenkins/.gradle/caches/1.9/workerMain/gradle-worker.jar 
> jarjar.org.gradle.process.internal.launcher.GradleWorkerMain
> Successfully started process 'Gradle Worker 1'
> Gradle Worker 1 executing tests.
> 
> jfxtras.labs.scene.control.test.ListSpinnerEditableTest > 
> enterSelectValueByTyping STANDARD_ERROR
>Graphics Device initialization failed for :  es2, sw
>Error initializing QuantumRenderer: no suitable pipeline found
>java.lang.RuntimeException: java.lang.RuntimeException: Error initializing 
> QuantumRenderer: no suitable pipeline found
>   at 
> com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:300)
>   at 
> com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:244)
>   at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:179)
>   at 
> com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
>   at 
> com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
>   at 
> com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
>   at 
> com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
>   at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
>   at java.lang.Thread.run(Thread.java:744)
>Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: 
> no suitable pipeline found
>   at 
> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:98)
>   at 
> com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:128)
>   ... 1 more
>Exception in thread "Thread-4" java.lang.RuntimeException: No toolkit found
>   at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:191)
>   at 
> com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
>   at 
> com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
>   at 
> com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
>   at 
> com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
>   at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
>   at java.lang.Thread.run(Thread.java:744)
> 
> 

Re: JavaFX on headless Jenkins

[David Hill]

On 1/4/14, Jan 4, 3:57 PM, Tom Eugelink wrote:

I'm trying to run JavaFX UI tests using TestFX on a headless Jenkins server (Ubuntu / 
Debian). I've gotten to the point where the UI is actually started by Jenkins, but then 
the test fail with a "no suitable pipeline found". Any suggestions how to fix 
that?


This has long been a challenge with FX. I even modified Glass/Lens to get a 
headless with a VNC option working on Linux & Mac (Windows probably needed a 
little porting). This has never been a priority though, only a casual hobby.

Daniel is working on a refresh of Glass/Lens that may make it even easier to do 
headless (as a side effect).

If there is any interest, I can provide more information on the current 
Glass/Lens headless.

Dave


:*test*
Executing task ':test' (up-to-date check took 0.054 secs) due to:
  No history is available.
Starting process 'Gradle Worker 1'. Working directory: 
/var/lib/jenkins/workspace/JFXtras8.0 Command: 
/usr/lib/jvm/jdk1.8.0-ea/bin/java 
-Djava.security.manager=jarjar.org.gradle.process.internal.child.BootstrapSecurityManager
 -Dfile.encoding=UTF-8 -ea -cp 
/var/lib/jenkins/.gradle/caches/1.9/workerMain/gradle-worker.jar 
jarjar.org.gradle.process.internal.launcher.GradleWorkerMain
Successfully started process 'Gradle Worker 1'
Gradle Worker 1 executing tests.

jfxtras.labs.scene.control.test.ListSpinnerEditableTest > 
enterSelectValueByTyping STANDARD_ERROR
Graphics Device initialization failed for :  es2, sw
Error initializing QuantumRenderer: no suitable pipeline found
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing 
QuantumRenderer: no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:300)
at 
com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:244)
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:179)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: 
no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:98)
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:128)
... 1 more
Exception in thread "Thread-4" java.lang.RuntimeException: No toolkit found
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:191)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)





--
David Hill 
Java Embedded Development

"On a clear disk, you can seek forever."

JavaFX on headless Jenkins

[Tom Eugelink]

I'm trying to run JavaFX UI tests using TestFX on a headless Jenkins server (Ubuntu / 
Debian). I've gotten to the point where the UI is actually started by Jenkins, but then 
the test fail with a "no suitable pipeline found". Any suggestions how to fix 
that?

:*test*
Executing task ':test' (up-to-date check took 0.054 secs) due to:
  No history is available.
Starting process 'Gradle Worker 1'. Working directory: 
/var/lib/jenkins/workspace/JFXtras8.0 Command: 
/usr/lib/jvm/jdk1.8.0-ea/bin/java 
-Djava.security.manager=jarjar.org.gradle.process.internal.child.BootstrapSecurityManager
 -Dfile.encoding=UTF-8 -ea -cp 
/var/lib/jenkins/.gradle/caches/1.9/workerMain/gradle-worker.jar 
jarjar.org.gradle.process.internal.launcher.GradleWorkerMain
Successfully started process 'Gradle Worker 1'
Gradle Worker 1 executing tests.

jfxtras.labs.scene.control.test.ListSpinnerEditableTest > 
enterSelectValueByTyping STANDARD_ERROR
Graphics Device initialization failed for :  es2, sw
Error initializing QuantumRenderer: no suitable pipeline found
java.lang.RuntimeException: java.lang.RuntimeException: Error initializing 
QuantumRenderer: no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer.getInstance(QuantumRenderer.java:300)
at 
com.sun.javafx.tk.quantum.QuantumToolkit.init(QuantumToolkit.java:244)
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:179)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.RuntimeException: Error initializing QuantumRenderer: 
no suitable pipeline found
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.init(QuantumRenderer.java:98)
at 
com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run(QuantumRenderer.java:128)
... 1 more
Exception in thread "Thread-4" java.lang.RuntimeException: No toolkit found
at com.sun.javafx.tk.Toolkit.getToolkit(Toolkit.java:191)
at 
com.sun.javafx.application.PlatformImpl.startup(PlatformImpl.java:210)
at 
com.sun.javafx.application.LauncherImpl.startToolkit(LauncherImpl.java:653)
at 
com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:678)
at 
com.sun.javafx.application.LauncherImpl.access$000(LauncherImpl.java:56)
at com.sun.javafx.application.LauncherImpl$1.run(LauncherImpl.java:158)
at java.lang.Thread.run(Thread.java:744)