adoptium / adoptium/aqa-systemtest
Modularity tests for implied readability fails
- Dominant language
- Java
- Stars
- 27
- Forks
- 70
- PR merge metrics
- No merged PRs in 30d
Description
Modularity tests for implied readability fails on on both hotspot and openj9 with following error. Likely the Modularity access rules have changed since the test was developed. Need investigation. Test should be disabled for the time being.
```
10:58:08 T4 1) test2(net.adoptopenjdk.test.modularity.junit.TestImpliedReadability)
10:58:08 T4 java.lang.IllegalAccessError: class net.adoptopenjdk.test.modularity.junit.TestImpliedReadability (in module com.test) cannot access class org.hamcrest.CoreMatchers (in module hamcrest.core) because module com.test does not read module hamcrest.core
10:58:08 T4 at com.test/net.adoptopenjdk.test.modularity.junit.TestImpliedReadability.test2(TestImpliedReadability.java:66)
10:58:08 T4 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
10:58:08 T4 at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
10:58:08 T4 at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
10:58:08 T4 at java.base/java.lang.reflect.Method.invoke(Method.java:566)
10:58:08 T4 at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
10:58:08 T4 at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
10:58:08 T4 at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
10:58:08 T4 at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
10:58:08 T4 at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
10:58:08 T4 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
10:58:08 T4 at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
10:58:08 T4 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
10:58:08 T4 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
10:58:08 T4 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
10:58:08 T4 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
10:58:08 T4 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
10:58:08 T4 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
10:58:08 T4 at org.junit.runners.Suite.runChild(Suite.java:128)
10:58:08 T4 at org.junit.runners.Suite.runChild(Suite.java:27)
10:58:08 T4 at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
10:58:08 T4 at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
10:58:08 T4 at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
10:58:08 T4 at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
10:58:08 T4 at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
10:58:08 T4 at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
10:58:08 T4 at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
10:58:08 T4 at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
10:58:08 T4 at org.junit.runner.JUnitCore.runMain(JUnitCore.java:77)
10:58:08 T4 at org.junit.runner.JUnitCore.main(JUnitCore.java:36)
10:58:08 T4
```
https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/479/console
Contributor guide
Research direction
Start with net.adoptopenjdk.test.modularity.junit.TestImpliedReadability, especially test2 at line 66, and review the linked Grinder/479 console output. Investigate the module-readability failure, then disable this test as requested. Done means the modularity test run no longer fails on the reported access error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100