Comment 0 for bug 1889183

RaiMan (raimund-hocke) wrote :

I have an issue where App.Open throws the following exception after an upgrade from Sikulix 1.1.4 to 2.0.4:

<type 'java.lang.IndexOutOfBoundsException'>:java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

I execute the code through jenkins via robot framework on a remote vm-machine, the only output given by the error is the following:

20200727 15:29:20.369 - INFO - +------ START KW: GyY7S.Sikuli Start Setup [ ${setup_path} ]
20200727 15:29:21.703 - FAIL - <type 'java.lang.IndexOutOfBoundsException'>:java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
20200727 15:29:21.703 - DEBUG - Traceback (most recent call last): None
20200727 15:29:21.704 - INFO - +------ END KW: GyY7S.Sikuli Start Setup (1334)

After this my test suite ends as RF get an obvious FAIL, however, sikulix DO start the application after the exception if I let the machine running for a bit.

Here's the python method, which is rather straight forward:

def sikuli_start_setup(self, exeName):
    self.Installer = Sikuli.App("C:\\Users\\user.user\\Desktop\\sikulix\\" + exeName)
    self.Installer.open()

exeName used in this case is "Setup_12345_1.0.0.exe".

This happens slightly under 7.5% of the times I execute the code and I've not been able recreate it by running the same code through the sikulix IDE at the local machine, or by executing the commands manually by using the robot remote.

It happens on different machines with different setup.
35 / 470 times

30 times on Windows 1903, java 8 191
2 time on Windows 1909, java 11
1 time on Windows Server 2016 java 11
2 time on Windows Server 2019 java 8 191

Sikulix 2.0.4
Jython 2.7.1

Any suggestions on how to be able to log more traces?