Testing a 32 bit Eclipse RCP Application on a 64 bit Windows machine

[wagner.w...@gmail.com]

Hi guys,

i´m new to robot framework and testautomation in general and after i have successfully evaluated it with selenium2library i´m now evaluating it for testing Eclipse RCP applications with the eclipselibrary and SWTBot. 

I have problems running the "installation_test_case" from [1] with a 32 bit Eclipse unter 64 bit Windows. No problem with 64 bit Eclipse on the same machine. 

The console output is [2].

The EclipseLibrary.log output is [3].

Any idea how to solve that?

Thanks in advance

Cheers,

Wlad

[1] https://code.google.com/p/robotframework-eclipselibrary/wiki/InstallationForEclipse     [/1]

[2] C:\robotfm\swt>eclipsebot RF-EclipseLibrary_installationtest.html

==============================================================================

RF-EclipseLibrary installationtest :: Test suite used to check robotframewo...

==============================================================================

Test Eclipse installation :: This test checks if all is installed ... .

Exception: java.lang.RuntimeException thrown from the UncaughtExceptionHandler i

n thread "Thread-1"

Test Eclipse installation :: This test checks if all is installed ... | FAIL |

RuntimeException

------------------------------------------------------------------------------

RF-EclipseLibrary installationtest :: Test suite used to check rob... | FAIL |

1 critical test, 0 passed, 1 failed

1 test total, 0 passed, 1 failed

==============================================================================

Debug:   C:\robotfm\swt\results\jybot.log

Output:  C:\robotfm\swt\results\output.xml

Log:     C:\robotfm\swt\results\log.html

Report:  C:\robotfm\swt\results\report.html

Exception in thread "MainThread" java.lang.SecurityException: Eclipse exit with

status=1, see log for detail and check StartEclipse keyword parameters

        at org.lcx.robotframework.eclipse.keyword.launch.EclipseLaunchingKeyword

s$3.checkExit(EclipseLaunchingKeywords.java:198)

        at java.lang.Runtime.exit(Runtime.java:105)

        at java.lang.System.exit(System.java:960)

        at org.robotframework.RobotFramework.main(RobotFramework.java:38)

C:\robotfm\swt>    [/2]

[3] INFO 2014/05/13 18:07:23,869 [MainThread] (LogKeywords.java:24) - Set EclipseLibrary log level to DEBUG

DEBUG 2014/05/13 18:07:23,879 [MainThread] (EclipseLibrary.java:51) - runKeyword:startEclipse

DEBUG 2014/05/13 18:07:23,879 [MainThread] (EclipseLibrary.java:52) - args:5

DEBUG 2014/05/13 18:07:23,880 [MainThread] (EclipseLibrary.java:55) - arg[0]:-install, of class=java.lang.String

DEBUG 2014/05/13 18:07:23,881 [MainThread] (EclipseLibrary.java:55) - arg[1]:file:/C:/eclipse32, of class=java.lang.String

DEBUG 2014/05/13 18:07:23,881 [MainThread] (EclipseLibrary.java:55) - arg[2]:-data, of class=java.lang.String

DEBUG 2014/05/13 18:07:23,882 [MainThread] (EclipseLibrary.java:55) - arg[3]:file:/C:/robotfm/swt/new_worskspace_blank, of class=java.lang.String

DEBUG 2014/05/13 18:07:23,883 [MainThread] (EclipseLibrary.java:55) - arg[4]:-consolelog -debug, of class=java.lang.String

DEBUG 2014/05/13 18:07:23,884 [MainThread] (EclipseLaunchingKeywords.java:54) - loading eclipse launcher jar

DEBUG 2014/05/13 18:07:23,884 [MainThread] (EclipseUtil.java:29) - Load Eclipse launcher jar

DEBUG 2014/05/13 18:07:23,885 [MainThread] (EclipseUtil.java:31) - pathToEclipse=file:/C:/eclipse32

DEBUG 2014/05/13 18:07:23,887 [MainThread] (EclipseUtil.java:36) - eclipseLauncherJar=C:\eclipse32\plugins\org.eclipse.equinox.launcher_1.2.0.v20110502.jar

DEBUG 2014/05/13 18:07:23,888 [MainThread] (EclipseUtil.java:74) - file:/C:/eclipse32/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar is loaded

DEBUG 2014/05/13 18:07:23,889 [MainThread] (EclipseLaunchingKeywords.java:62) - get the Main method

INFO 2014/05/13 18:07:23,932 [MainThread] (EclipseLaunchingKeywords.java:86) - Eclipse start is requested

DEBUG 2014/05/13 18:07:23,933 [Thread-1] (EclipseLaunchingKeywords.java:155) - requesting Main method of eclipse launcher jar

DEBUG 2014/05/13 18:07:27,185 [Thread-1] (EclipseLaunchingKeywords.java:160) - Error in internalLaunchEclipse

ERROR 2014/05/13 18:07:27,185 [Thread-1] (EclipseLaunchingKeywords.java:161) - java.lang.reflect.InvocationTargetException

ERROR 2014/05/13 18:07:27,185 [Thread-1] (EclipseLaunchingKeywords.java:162) - Eclipse exit with status=13, see log for detail and check StartEclipse keyword parameters

java.lang.SecurityException: Eclipse exit with status=13, see log for detail and check StartEclipse keyword parameters

at org.lcx.robotframework.eclipse.keyword.launch.EclipseLaunchingKeywords$3.checkExit(EclipseLaunchingKeywords.java:198)

at java.lang.Runtime.exit(Runtime.java:105)

at java.lang.System.exit(System.java:960)

at org.eclipse.equinox.launcher.Main.main(Main.java:1394)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:601)

at org.lcx.robotframework.eclipse.keyword.launch.EclipseLaunchingKeywords.internalLaunchEclipse(EclipseLaunchingKeywords.java:157)

at org.lcx.robotframework.eclipse.keyword.launch.EclipseLaunchingKeywords.access$100(EclipseLaunchingKeywords.java:23)

at org.lcx.robotframework.eclipse.keyword.launch.EclipseLaunchingKeywords$2.run(EclipseLaunchingKeywords.java:78)

at java.lang.Thread.run(Thread.java:722)      [/3]

 

 

[Laurent Carbonnaux]

Hello Wlad,

I'm not sure, but it seams it's more an eclipse problem :  Eclipse exit with status=13

I've found this "Make sure that the JVM version (32/64 bit) you use matches the eclipse version (32/64 bit)."

Does your eclipse 32 start normally out of rf?

regards,

Laurent

--
Vous recevez ce message, car vous êtes abonné au groupe Google Groupes "robotframework-eclipselibrary-users".
Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse robotframework-eclipsel...@googlegroups.com.
Pour obtenir davantage d'options, consultez la page https://groups.google.com/d/optout.

[Wladislaw Wagner]

Hi Laurent,

thanks for your quick reply. You pointed me in the right direction. I had several java versions installed on my corporate machine. Although i used a -vm option in the eclipse.ini of the 32 bit eclipse to force it to use 32 bit JVM i found later in the logs (configuration folder of eclipse) that 64 bit JVM was used. Then i messed up something with the enviroment variables in windows so that nothing worked at all and the day was over :)))

After work i did a new setup from scratch on my private pc ... almost everything worked, only some test steps of the installation test case failed. Will now try to do a setup from scratch on my corporate workstation and remove all the unnecessary JVMs in front.

Cheers,

Wlad

 

Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse robotframework-eclipselibrary-users+unsubscribe@googlegroups.com.

[Laurent Carbonnaux]

Happy it works!

Pour vous désabonner de ce groupe et ne plus recevoir d'e-mails le concernant, envoyez un e-mail à l'adresse robotframework-eclipsel...@googlegroups.com.

[Wladislaw Wagner]

Made it work on my corporate workstation, finally :))))

Noticed the following which might be interesting for others struggling with the same issue in the future:

When installing jython you are asked to chose a JRE/JDK which will be used to start jython. If you chose a 64 bit one you will NOT be able to run the example installation test case with a 32 bit eclipse IDE.

So if you are planning to do testautomation for a 32 bit eclipse RCP application you have to install jython with a 32 bit JRE / JDK to be able to drive it from RF + EclipseLibrary and vise versa - 64 bit JVM if you want to test a 64 bit RCP app. Please correct me if i told something wrong.

Of corse that might be something trivial and very basic but was not obvious for me, though. May be its worth to mention that in the documentation.

Cheers,

Wlad

[Laurent Carbonnaux]

Thanks for having shared this information

Good luck

Laurent

--