P3
When running jpackage tests locally, the following issues were uncovered in jpackage test lib:
- LinuxHelper: a regression fromJDK-8354988. Before the JDK-8354988 fix, when a process started with Executor didn't write to stdout, Executor.executeAndGetFirstLineOfOutput() returned an empty string; after the fix, it throws an exception.
- EmptyFolderTest: when an MSI is installed, it can create empty directories. Empty directories are not created only when it is unpacked.
- PackageTest.Group works incorrectly when a test runs jpackage to produce both exe and msi packages, and when they are installed. This fails WinUpgradeUUIDTest.
Additionally (caught the eye in the test source code):
- PathGroupTest.testNullId() test case is missing @Test annotation.
- PListReaderTest: a typo - STRING_ARRY. Should be STRING_ARRAY.
- LinuxHelper: a regression from
- EmptyFolderTest: when an MSI is installed, it can create empty directories. Empty directories are not created only when it is unpacked.
- PackageTest.Group works incorrectly when a test runs jpackage to produce both exe and msi packages, and when they are installed. This fails WinUpgradeUUIDTest.
Additionally (caught the eye in the test source code):
- PathGroupTest.testNullId() test case is missing @Test annotation.
- PListReaderTest: a typo - STRING_ARRY. Should be STRING_ARRAY.
- caused by
-
JDK-8354988 Separate stderr and stdout in Executor class from jpackage test lib
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/cbbab07d
-
Review(master)
openjdk/jdk/24884