adoptium / adoptium/aqa-tests

jdk17+ tools/jlink/JLinkTest.java failed on window32, arm-linux

Open
#2,857 2 comments 0 reactions 0 assignees View on GitHub
JBS
Dominant language
HTML
Stars
155
Forks
346
Avg merge
2d 9h
Merged PRs (30d)
36

Description

jdk17+ tools/jlink/JLinkTest.java failed on window32

```
jlink options: --output E:\workspace\grinder_sandbox_new\aqa-tests\TKG\output_16313003152445\jdk_custom_2\work\scratch\0\images\bug8240349.image --add-modules java.base --module-path E:\workspace\grinder_sandbox_new\openjdkbinary\j2sdk-image\jmods;E:\workspace\grinder_sandbox_new\aqa-tests\TKG\output_16313003152445\jdk_custom_2\work\scratch\0\jmods;E:\workspace\grinder_sandbox_new\aqa-tests\TKG\output_16313003152445\jdk_custom_2\work\scratch\0\jars;E:\workspace\grinder_sandbox_new\aqa-tests\TKG\output_16313003152445\jdk_custom_2\work\scratch\0\explodedmods\classes --vm=client

java.lang.AssertionError: Failure expected: E:\workspace\grinder_sandbox_new\aqa-tests\TKG\output_16313003152445\jdk_custom_2\work\scratch\0\images\bug8240349.image
at tests.Result.assertFailure(Result.java:58)
at JLinkTest.main(JLinkTest.java:378)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
```
https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk17_hs_extended.openjdk_x86-32_windows_testList_0/lastCompletedBuild/testReport/junit/tools_jlink_JLinkTest/java/JLinkTest/

The failure test was recently committed by https://bugs.openjdk.java.net/browse/JDK-8240349
https://github.com/openjdk/jdk17/commit/4d1cf51b1d4a5e812c9f78b0104e40fbc4883a6c#diff-9081f35054af34efdb5ecadf6bf9fb1269c92ec643d94d6fc7ae3af1ffdb47e8, which might not work for windows 32.

Contributor guide

Open the contributing guide

Research direction

Start with tools/jlink/JLinkTest.java, especially JLinkTest.main at line 378, and inspect tests.Result.assertFailure in Result.java line 58. Reproduce the failure from the linked Windows 32-bit CI report, then compare the test introduced by JDK-8240349 and check the reported arm-linux configuration. Done means the test behaves correctly on the affected platforms and the relevant test run passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
operating-systems, testing
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.