JDK-8249395 : (macos) jpackage tests timeout on MacPro5_1 systems
  • Type: Bug
  • Component: tools
  • Sub-Component: jpackage
  • Affected Version: 16,17
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: os_x
  • CPU: x86_64
  • Submitted: 2020-07-14
  • Updated: 2025-01-24
  • Resolved: 2021-05-14
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 17
17 b23Fixed
Related Reports
Duplicate :  
JDK-8265294 - tools/jpackage/share/AppImagePackageTest.java failed with "Exit code: 134"
Relates :  
JDK-8236282 - [macos] Find permanent solution to macOS test timeout problem JDK-8235738
Description
The following test timed out in the JDK16 CI:

tools/jpackage/share/IconTest.java

Typically when jpackage tests timeout we see some error in the
logs but that's not the case with this sighting. One thing I did
notice is that this test failure happened on a MacPro5_1 system.

The following test timed out in the JDK16 CI:

tools/jpackage/share/EmptyFolderPackageTest.java

The logs for this failure also do not show any errors for this
sighting. One thing I did notice is that this test failure happened
on a MacPro5_1 system.
Comments
Changeset: 28f1c7ac Author: Alexander Matveev <almatvee@openjdk.org> Date: 2021-05-14 23:00:59 +0000 URL: https://git.openjdk.java.net/jdk/commit/28f1c7ac4dfcf1df7df4eb94d270292b76baee12
14-05-2021
Looks like it is similar to JDK-8236282, except for "hdiutil create". Based on call stack below taking from hanging test we launched "hdiutil create" and waiting for it to terminate while reading output from it. However, based on process dump from machine which reproduces this issue, hdiutil no longer runs and existed long time ago. java.lang.Thread.State: RUNNABLE at java.io.FileInputStream.readBytes(java.base@17-ea/Native Method) at java.io.FileInputStream.read(java.base@17-ea/FileInputStream.java:271) at java.io.BufferedInputStream.read1(java.base@17-ea/BufferedInputStream.java:282) at java.io.BufferedInputStream.read(java.base@17-ea/BufferedInputStream.java:343) - locked <0x0000000700a17e90> (a java.lang.ProcessImpl$ProcessPipeInputStream) at sun.nio.cs.StreamDecoder.readBytes(java.base@17-ea/StreamDecoder.java:270) at sun.nio.cs.StreamDecoder.implRead(java.base@17-ea/StreamDecoder.java:313) at sun.nio.cs.StreamDecoder.read(java.base@17-ea/StreamDecoder.java:188) - locked <0x0000000700a1ec18> (a java.io.InputStreamReader) at java.io.InputStreamReader.read(java.base@17-ea/InputStreamReader.java:177) at java.io.BufferedReader.fill(java.base@17-ea/BufferedReader.java:162) at java.io.BufferedReader.readLine(java.base@17-ea/BufferedReader.java:329) - locked <0x0000000700a1ec18> (a java.io.InputStreamReader) at java.io.BufferedReader.readLine(java.base@17-ea/BufferedReader.java:396) at java.io.BufferedReader$1.hasNext(java.base@17-ea/BufferedReader.java:571) at java.util.Iterator.forEachRemaining(java.base@17-ea/Iterator.java:132) at java.util.Spliterators$IteratorSpliterator.forEachRemaining(java.base@17-ea/Spliterators.java:1801) at java.util.stream.AbstractPipeline.copyInto(java.base@17-ea/AbstractPipeline.java:484) at java.util.stream.AbstractPipeline.wrapAndCopyInto(java.base@17-ea/AbstractPipeline.java:474) at java.util.stream.AbstractPipeline.evaluate(java.base@17-ea/AbstractPipeline.java:550) at java.util.stream.AbstractPipeline.evaluateToArrayNode(java.base@17-ea/AbstractPipeline.java:260) at java.util.stream.ReferencePipeline.toArray(java.base@17-ea/ReferencePipeline.java:616) at java.util.stream.ReferencePipeline.toArray(java.base@17-ea/ReferencePipeline.java:622) at java.util.stream.ReferencePipeline.toList(java.base@17-ea/ReferencePipeline.java:627) at jdk.jpackage.internal.Executor.execute(jdk.jpackage@17-ea/Executor.java:151) at jdk.jpackage.internal.Executor.executeExpectSuccess(jdk.jpackage@17-ea/Executor.java:88) at jdk.jpackage.internal.IOUtils.exec(jdk.jpackage@17-ea/IOUtils.java:205) at jdk.jpackage.internal.IOUtils.exec(jdk.jpackage@17-ea/IOUtils.java:166) at jdk.jpackage.internal.MacDmgBundler.buildDMG(jdk.jpackage@17-ea/MacDmgBundler.java:328) at jdk.jpackage.internal.MacDmgBundler.bundle(jdk.jpackage@17-ea/MacDmgBundler.java:88) at jdk.jpackage.internal.MacDmgBundler.execute(jdk.jpackage@17-ea/MacDmgBundler.java:567) at jdk.jpackage.internal.Arguments.generateBundle(jdk.jpackage@17-ea/Arguments.java:676) at jdk.jpackage.internal.Arguments.processArguments(jdk.jpackage@17-ea/Arguments.java:550) at jdk.jpackage.main.Main.execute(jdk.jpackage@17-ea/Main.java:91) at jdk.jpackage.main.Main.main(jdk.jpackage@17-ea/Main.java:52) java.lang.Thread.State: BLOCKED (on object monitor) at java.lang.ProcessImpl$ProcessPipeInputStream.processExited(java.base@17-ea/ProcessImpl.java:592) - waiting to lock <0x0000000700a17e90> (a java.lang.ProcessImpl$ProcessPipeInputStream) at java.lang.ProcessImpl.lambda$initStreams$1(java.base@17-ea/ProcessImpl.java:370) at java.lang.ProcessImpl$$Lambda$486/0x0000000800cd6c00.apply(java.base@17-ea/Unknown Source) at java.util.concurrent.CompletableFuture.uniHandle(java.base@17-ea/CompletableFuture.java:934) at java.util.concurrent.CompletableFuture$UniHandle.tryFire(java.base@17-ea/CompletableFuture.java:911) at java.util.concurrent.CompletableFuture.postComplete(java.base@17-ea/CompletableFuture.java:510) at java.util.concurrent.CompletableFuture.complete(java.base@17-ea/CompletableFuture.java:2147) at java.lang.ProcessHandleImpl$1.run(java.base@17-ea/ProcessHandleImpl.java:171) at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17-ea/ThreadPoolExecutor.java:1135) at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17-ea/ThreadPoolExecutor.java:635) at java.lang.Thread.run(java.base@17-ea/Thread.java:831)
14-05-2021
Adding [~tbell] since there might be something wrong with these MacPro5_1 systems.
15-07-2020