-
Bug
-
Resolution: Fixed
-
P3
-
18
-
b28
-
x86_64
-
os_x
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8278879 | 19 | Alexander Matveev | P3 | Resolved | Fixed | b03 |
JDK-8279721 | 18.0.1 | Alexander Matveev | P3 | Resolved | Fixed | b02 |
JDK-8289979 | 17.0.5-oracle | Alexander Matveev | P3 | Resolved | Fixed | b02 |
JDK-8290890 | 17.0.5 | Goetz Lindenmaier | P3 | Resolved | Fixed | b01 |
tools/jpackage/share/MultiNameTwoPhaseTest.java
The test run contains errors like this:
[11:45:37.245] Running /usr/bin/osascript
[11:51:07.189] Command [PID: 5566]:
/usr/bin/osascript /var/folders/93/pf04s4c922qcyb7v8xr1y5h8000_dc/T/jdk.jpackage4183342526789260831/config/Hello-dmg-setup.scpt
[11:51:07.190] Output:
/var/folders/93/pf04s4c922qcyb7v8xr1y5h8000_dc/T/jdk.jpackage4183342526789260831/config/Hello-dmg-setup.scpt:192:204: execution error: Finder got an error: AppleEvent timed out. (-1712)
[11:51:07.190] Returned: 1
[11:51:07.190] java.io.IOException: Command [/usr/bin/osascript, /var/folders/93/pf04s4c922qcyb7v8xr1y5h8000_dc/T/jdk.jpackage4183342526789260831/config/Hello-dmg-setup.scpt] exited with 1 code
at jdk.jpackage/jdk.jpackage.internal.Executor.executeExpectSuccess(Executor.java:90)
at jdk.jpackage/jdk.jpackage.internal.IOUtils.exec(IOUtils.java:215)
at jdk.jpackage/jdk.jpackage.internal.IOUtils.exec(IOUtils.java:193)
at jdk.jpackage/jdk.jpackage.internal.IOUtils.exec(IOUtils.java:172)
at jdk.jpackage/jdk.jpackage.internal.MacDmgBundler.buildDMG(MacDmgBundler.java:404)
at jdk.jpackage/jdk.jpackage.internal.MacDmgBundler.bundle(MacDmgBundler.java:90)
at jdk.jpackage/jdk.jpackage.internal.MacDmgBundler.execute(MacDmgBundler.java:579)
at jdk.jpackage/jdk.jpackage.internal.Arguments.generateBundle(Arguments.java:689)
at jdk.jpackage/jdk.jpackage.internal.Arguments.processArguments(Arguments.java:561)
at jdk.jpackage/jdk.jpackage.main.Main.execute(Main.java:91)
at jdk.jpackage/jdk.jpackage.main.Main.main(Main.java:52)
There are five runs of /usr/bin/osascript and
all have similar errors. I suspect that the issues with
/usr/bin/osascript are what caused the test run to
take so long.
The test did PASS while the timeout handler was running:
[12:03:44.970] [ OK ] MultiNameTwoPhaseTest.test([MultiNameTest, ](length=2)); checks=36
[12:03:44.970] [==========] 5 tests ran
[12:03:44.971] [ PASSED ] 5 tests
----------System.err:(1/15)----------
STATUS:Passed.
----------rerun:(39/8387)*----------
It could be that these /usr/bin/osascript errors are "normal"
and this test just needs a longer timeout.
- backported by
-
JDK-8278879 [macos] tools/jpackage tests timeout due to /usr/bin/osascript
- Resolved
-
JDK-8279721 [macos] tools/jpackage tests timeout due to /usr/bin/osascript
- Resolved
-
JDK-8289979 [macos] tools/jpackage tests timeout due to /usr/bin/osascript
- Resolved
-
JDK-8290890 [macos] tools/jpackage tests timeout due to /usr/bin/osascript
- Resolved
- relates to
-
JDK-8276837 [macos]: Error when signing the additional launcher
- Resolved
-
JDK-8248248 [macos] EmptyFolderPackageTest.java fails EmptyFolderPackageTest-dmg-setup.scpt exited with 134 code
- Resolved
- links to
-
Commit openjdk/jdk17u-dev/930be902
-
Commit openjdk/jdk18/918e3397
-
Review openjdk/jdk17u-dev/577
-
Review openjdk/jdk18/18