adoptium / adoptium/aqa-tests

jdk18: compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestResolvedJavaType.java failed on multiple platforms

Open
#3,873 4 comments 0 reactions 0 assignees View on GitHub
release triage triage required
Dominant language
HTML
Stars
155
Forks
346
Avg merge
2d 9h
Merged PRs (30d)
36

Description

jdk18: compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestResolvedJavaType.java failed on multiple platforms.

```
11:09:49 STDOUT:
11:09:49 STDERR:
11:09:49 JavaTest Message: JUnit Failure: internalNameTest(jdk.vm.ci.runtime.test.TestResolvedJavaType): expected:<...dJavaType$$Lambda$42[.]0x0000000800d437c0> but was:<...dJavaType$$Lambda$42[/]0x0000000800d437c0>
11:09:49 org.junit.ComparisonFailure: expected:<...dJavaType$$Lambda$42[.]0x0000000800d437c0> but was:<...dJavaType$$Lambda$42[/]0x0000000800d437c0>
11:09:49 at org.junit.Assert.assertEquals(Assert.java:117)
```

https://ci.adoptopenjdk.net/job/Test_openjdk18_hs_extended.openjdk_x86-64_mac_testList_1/44/console

jdk18 jvm support jvmci specific. Jdk17, jdk11 works fine.

Contributor guide

Open the contributing guide

Research direction

Start with compiler/jvmci/jdk.vm.ci.runtime.test/src/jdk/vm/ci/runtime/test/TestResolvedJavaType.java and the referenced CI console output. Reproduce the internalNameTest failure on JDK 18 and compare its expected and actual names with the behavior on JDK 17 and JDK 11. Done means the affected JDK 18 platform tests pass without regressing the other versions.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
compilers, testing-qa
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.