sikuli-driver team mailing list archive
-
sikuli-driver team
-
Mailing list archive
-
Message #34410
[Bug 1489809] Re: [1.1.0] run sikuli script with jenkins
It seems, that when SikuliX starts up, it thinks it runs on a 64-Bit
system (and hence works with a 64-Bit libs folder), but the concrete
environment forces Windows to access the 32-Bit stuff (SysWOW64), which
does not fit of course.
So check your runtime environment.
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1489809
Title:
[1.1.0] run sikuli script with jenkins
Status in Sikuli:
Opinion
Bug description:
I'm working with sikuli 1.1.0, in a windows server 64-bits.
Where i have install jenkins, when I create a job to run an example
Test Case from jenkins I have this error:
======================================================================================================
c:\dcip\workspace\vdc\example>C:\sikulix\runsikulix.cmd -r C:\example.sikuli
+++ running this Java
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
+++ trying to run SikuliX
+++ using: -Xms64M -Xmx512M -Dfile.encoding=UTF-8 -Dsikuli.FromCommandLine -jar C:\sikulix\sikulix.jar -r C:\example.sikuli
Exception in thread "main" java.lang.UnsatisfiedLinkError: org.sikuli.util.SysJNA$WinKernel32.GetEnvironmentVariableW(Lorg/bridj/Pointer;Lorg/bridj/Pointer;I)I
at org.sikuli.util.SysJNA$WinKernel32.GetEnvironmentVariableW(Native Method)
at org.sikuli.util.SysJNA$WinKernel32.getEnvironmentVariable(SysJNA.java:53)
at org.sikuli.script.RunTime.addToWindowsSystemPath(RunTime.java:997)
at org.sikuli.script.RunTime.libsExport(RunTime.java:959)
at org.sikuli.script.RunTime.init(RunTime.java:715)
at org.sikuli.script.RunTime.get(RunTime.java:291)
at org.sikuli.ide.SikuliIDE.run(SikuliIDE.java:177)
at org.sikuli.ide.Sikulix.main(Sikulix.java:21)
# BridJ: LoadLibrary error when loading C:\Windows\SysWOW64\kernel32.dll : %1 is not a valid Win32 application.
# BridJ: LoadLibrary error when loading C:\Windows\SysWOW64\kernel32.dll : %1 is not a valid Win32 application.
# BridJ: LoadLibrary error when loading C:\Windows\SysWOW64\kernel32.dll : %1 is not a valid Win32 application.
Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE
======================================================================================================
but when I tried to execute from the cmd, the same command works well
To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1489809/+subscriptions
References