sikuli-driver team mailing list archive

Thread
Date

[Question #250119]: How can I turn on debugging in a JUnit test?

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: Rainer Klute <question250119@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 11 Jun 2014 21:41:26 -0000
Reply-to: question250119@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

New question #250119 on Sikuli:
https://answers.launchpad.net/sikuli/+question/250119

Running a JUnit test case I get the following error message:

[error] ResourceLoader: loadLib: Fatal Error 110: loading: libVisionProxy.so
[error] ResourceLoader: loadLib: Since native library was found, it might be a problem with needed dependent libraries
Expecting an absolute path of the library: libVisionProxy.so
[error] RunSetup: Problem with SikuliX libs folder - see error log
[error] Terminating SikuliX after a fatal error(110)! Sorry, but it makes no sense to continue!
If you do not have any idea about the error cause or solution, run again
with a Debug level of 3. You might paste the output to the Q&A board.

How can I set the debug level to 3 in order to dive deeper into the problem? How is the libVisionProxy.so looked up anyway? I couldn't find that in the docs. What's that absolute path in "Expecting an absolute path of the library: libVisionProxy.so"? Regarding "see error log", I don't have any error log besides what I pasted above.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.