MarketSquare / MarketSquare/robotframework-SikuliLibrary
"java.lang.ExceptionInInitializerError: null" at all Click keywords by X86 Enviroments
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 163
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
we have found a problem for 32-bit machines. When we want to use the SikuliLibrary for this we get an ExceptionInInitializerError exception.
Testing Enviroment -> 21H1 Windows 10 X86

Here we initialize Sikuli with the New Mode during a test suite start and finish it.
```
*** Settings ***
Suite Setup Init Sikuli Lib
Suite Teardown Stop Sikuli Lib
*** Keywords ***
Init Sikuli Lib
${_path}= Normalize Path ${CURDIR}/../Img
Start Sikuli Process
SikuliLibrary.Add Image Path ${_path}
Stop Sikuli Lib
Stop Sikuli
```
I have installed a wide variety of 32-bit Java runtimes and they all had the same initialization error.
* Java SE Runtime Environment 8u291 by Oracle does not work
* OpenJDK Runtime Enviroment AdoptOpenJDK-11.0.11+9 does not work
However, if I run the same code on a 64 bit architecture with a 64 bit installation, the library works without problems.
* OpenJDK Runtime Enviroment AdoptOpenJDK-11.0.11+9 works
I found already some issues by this Exception type:
https://github.com/rainmanwy/robotframework-SikuliLibrary/issues/108
https://github.com/rainmanwy/robotframework-SikuliLibrary/issues/122
Does the Sikuli library support the 32-bit Java runtimes to execute test runs on X86 systems?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from SikuliLibrary initialization and the reported Suite Setup sequence, then reproduce the ExceptionInInitializerError on the listed 32-bit Windows and Java runtimes. Compare the failing 32-bit execution with the working 64-bit environment; done means establishing whether 32-bit Java is supported and documenting or addressing the compatibility result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100