external test jacoco_test failed with jdk17 (passed with jdk11)

[sophia-guo]

external test jacoco_test failed with jdk17 (passed with jdk11)
jdk11: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/456/ passed
jdk17: https://ci.adoptopenjdk.net/view/work-in-progress/job/grinder_sandbox_new/449/console

17:54:39  /jacoco/org.jacoco.build
17:54:39  Compile and run jacoco tests
17:54:39  Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8 -Djava.security.egd=file:/dev/./urandom
17:54:40  [�[1;31mERROR�[m] Error executing Maven.
17:54:40  [�[1;31mERROR�[m] java.lang.IllegalStateException: Unable to load cache item
17:54:40  [�[1;31mERROR�[m] Caused by: Unable to load cache item
17:54:40  [�[1;31mERROR�[m] Caused by: Could not initialize class com.google.inject.internal.cglib.core.$MethodWrapper
17:54:40  Build jacoco completed
17:54:40  Test results copied
17:54:41  
17:54:41  jacoco_test_0_FAILED

[sophia-guo]

We currently are not using the latest stable build which appears to be https://github.com/jacoco/jacoco/releases/tag/v0.8.7. We likely should switch to using it by updating tag_version="v0.8.7" to the jacoco/test.properties file.

We may still see the issue being reported, but at least we are pulling a stable build (otherwise we are just pulling from master/main branch).

The comment of https://github.com/jacoco/jacoco/releases/tag/v0.8.7
JaCoCo now officially supports Java 15 and 16 (GitHub jacoco/jacoco#1094, jacoco/jacoco#1097, jacoco/jacoco#1176).
Experimental support for Java 17 class files (GitHub jacoco/jacoco#1132).

The failure with jdk17 might be expected.

[yinggzz]

I would like to work on this issue

[yinggzz]

external test jacoco_test with jdk17 after updating tag_version = "v0.8.7": https://ci.adoptopenjdk.net/job/Grinder/3766/console
@sophia-guo Hi Sophia, can I get some clarification on what next step I should take?

[sophia-guo]

Test passed with jdk11 and failed with jdk17. So might not be the test environment setting issue. The failure is similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980467, which suggests the issue is with maven and jdk17. The specific maven version doesn't work with jdk17. I can see same failure with #3382 and believe there are other tests got the same failures. Could you please print the maven version by command mvn -v ? Thanks.

[sophia-guo]

@yinggzz please see the comment #3390 (comment)

[yinggzz]

Grinder link: https://ci.adoptopenjdk.net/job/Grinder/3842/ (passed?)

maven version 3.6.3

output of command mvn-v:

11:58:22  Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8 -Djava.security.egd=file:/dev/./urandom
11:58:22  �[1mApache Maven 3.6.3�[m
11:58:22  Maven home: /usr/share/maven
11:58:22  Java version: 17.0.3-beta, vendor: Eclipse Adoptium, runtime: /opt/java/openjdk
11:58:22  Default locale: en_US, platform encoding: UTF8
11:58:22  OS name: "linux", version: "4.4.0-204-generic", arch: "amd64", family: "unix"

[sophia-guo]

It passed because your change will only run mvn -v command, no tests will run. If your branch 3390 is used to commit some tag update, you will need to reverse that change.

[smlambert]

This has found an interesting defect, given that there were errors and it still shows as passed.

11:58:23  The directory in the external.sh is jacoco
11:58:23  Error: No such container: jacoco-test

[sophia-guo]

same error happened to netty.

[sophia-guo]

re #3390 (comment)

The error message is expected, similar to the error message when doing the image clean at the build step. We explicitly remove the container no matter it exist or not, which should not affect the build status.

11:57:24  clean_image:
11:57:24       [echo] Executing external.sh --clean --dir jacoco --tag nightly --version 17 --impl hotspot 
11:57:24       [exec] The test here is jacoco
11:57:24       [exec] The directory in the external.sh is jacoco
11:57:24       [exec] Error: No such container: jacoco-test
11:57:24       [exec] Result: 1