You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the problem or enhancement request:
Enviroment that works JMockit+Jacoco+JDK8, when upgraded to JDK11 causes ArrayIndexOutOfBoundException during test execution. There have been some related defects raised around this issue (and possibly partially fixed?) (ArrayIndexOutOfBounds while creating mocks #664) (ArrayIndexOutOfBoundsException while initializing mocks #615) but I am still seeing issues in the latest versions. I am including a stripped down example to illustrate as that seems to have been requested
I am using:
Jmockit 1.49 (current latest)
Jacoco 0.8.5 (current latest)
AdoptOpenJDK 11.0.8 hotspot (in contrast to AdoptOpenJDK 1.8.0_262)
As an experiment, I changed jacoco 0.8.5->0.8.3 and tests run. This may be a potential work-around for people affected pending an update (from jmockit?). Supposedly, the jacoco folks have switched to using 'condy' in their latest versions (e.g. 0.8.5), but earlier version (0.8.3) does not have condy. Per that discussion (#664) (#615), jmockit needs to properly support latest-jacoco-using-condy (I am paraphrasing based on what I think I read).
Please provide the following information:
Version of JMockit that was used: 1.49
Description of the problem or enhancement request:
Enviroment that works JMockit+Jacoco+JDK8, when upgraded to JDK11 causes ArrayIndexOutOfBoundException during test execution. There have been some related defects raised around this issue (and possibly partially fixed?) (ArrayIndexOutOfBounds while creating mocks #664) (ArrayIndexOutOfBoundsException while initializing mocks #615) but I am still seeing issues in the latest versions. I am including a stripped down example to illustrate as that seems to have been requested
I am using:
see attached zip
example.zip
build.log
buildDebug.log
The text was updated successfully, but these errors were encountered: