Java: Running Sikuli scripts using ScriptRunner.runPython causes JVM to exit upon completion

[Stephen Christian]

Having gathered all of my individual, Sikuli-GUI-made unit tests into a single test suite and trying to run them sequentially I was hit by the incredible show-stopper bug of having the JVM shut down as soon as the first script finished. (Using X 1.0 rc2 "Maltese" on 64-bit Windows 7, but running 32-bit Java 1.6.0_23-b05)

The following code will never WOOGAH CHAKA:

final ScriptRunner sr = ScriptRunner.getInstance(new String[0]);
sr.runPython("testing/sikuli/InitialGuiLookTest.sikuli", new File("testing/sikuli/InitialGuiLookTest.sikuli/InitialGuiLookTest.py"));
System.out.println("WOOOGAH CHAKA");

[RaiMan (raimund-hocke)]

by design, when running a Sikuli script standalone (from Java or in the command line), the JVM, it is running in is exited.

I guess you have to put the "gathering" of your single scripts to the python level and use import or execfile for each of your test, so that on the Java level it is one Sikuli script.

Or you might try to call each scripts using a system command "java -jar sikuli-script.jar path to your script", hoping that gets it's own JVM.

[Stephen Christian (getefix)]

I am extremely interested in what prompted this design decision, as it appears to limit the utility of the script-runner considerably.

[RaiMan (raimund-hocke)]

I guess, the focus for the Python level, was not to run it from within Java, since the Sikuli features are available from within Java on the Java level (this is what most Java people use).

But we should wait for a comment of the developers ;-)