JDK-8255855 : appcds/jigsaw/NewModuleFinderTest.java test failed due to unexpected NPE
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 16
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2020-11-03
  • Updated: 2020-12-09
  • Resolved: 2020-11-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 16
16 b23Fixed
Related Reports
Relates :  
JDK-8254876 - (fs) NullPointerException not thrown when first argument to Path.of or Paths.get is null
Sub Tasks
JDK-8255893 :  
Problemlist runtime/cds/appcds/jigsaw/NewModuleFinderTest.java - Resolved
Description
 stderr: [Exception in thread "main" java.lang.ExceptionInInitializerError
	at NewModuleFinderTest$Helper.main(NewModuleFinderTest.java:81)
Caused by: java.lang.NullPointerException
	at java.base/java.util.Objects.requireNonNull(Objects.java:208)
	at java.base/sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:260)
	at java.base/java.nio.file.Path.of(Path.java:147)
	at java.base/java.nio.file.Paths.get(Paths.java:69)
	at NewModuleFinderTest.<clinit>(NewModuleFinderTest.java:48)
	... 1 more
]
 exitValue = 1

java.lang.RuntimeException: Expected to get exit value of [0]

	at jdk.test.lib.process.OutputAnalyzer.shouldHaveExitValue(OutputAnalyzer.java:457)
	at NewModuleFinderTest.main(NewModuleFinderTest.java:75)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:564)
	at com.sun.javatest.regtest.agent.MainActionHelper$AgentVMRunnable.run(MainActionHelper.java:298)
	at java.base/java.lang.Thread.run(Thread.java:832)

JavaTest Message: Test threw exception: java.lang.RuntimeException
JavaTest Message: shutting down test

result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Expected to get exit value of [0]
Comments
The failure has not occurred after the fix was integrated. Marking it as "verified".
09-12-2020
[~iklam] Yes I see that now. Thanks.
05-11-2020
[~dholmes] -Dtest.src is not null when the test is invoked by jtreg, but the test launches a child process that runs itself. Inside this child process, test.src is null.
04-11-2020
Changeset: 5348298f Author: Calvin Cheung <ccheung@openjdk.org> Date: 2020-11-04 17:17:46 +0000 URL: https://github.com/openjdk/jdk/commit/5348298f
04-11-2020
It shouldn't be null: -Dtest.src=/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-16+23-1428/src.full/open/test/hotspot/jtreg/runtime/cds/appcds/jigsaw
04-11-2020
Long standing bug that Path.of(null, "foo") didn't throw NPE. It looks like TEST_SRC may be null in this test.
04-11-2020
Bumped to P2 as this is causing a lot of noise in the CI in tiers 2, 3 and 4. Either fix immediately or else ProblemList it. Thanks.
04-11-2020
This could be a side-effect of the fix for https://bugs.openjdk.java.net/browse/JDK-8254876
03-11-2020