-
Sub-task
-
Resolution: Fixed
-
P4
-
25
-
b04
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8351707 | 24-pool | Unassigned | P4 | New | Unresolved | |
| JDK-8351709 | 21-pool-oracle | Unassigned | P4 | New | Unresolved | |
| JDK-8351708 | 17-pool-oracle | Unassigned | P4 | New | Unresolved | |
| JDK-8351710 | 11-pool-oracle | Unassigned | P4 | New | Unresolved | |
| JDK-8351711 | 8-pool | Unassigned | P4 | New | Unresolved |
The test/jdk/java/util/zip/EntryCount64k.java test launches an application through "java -jar" and then expects the message written out by the application's main method to be available in the STDOUT output of the launched process. The check however is a bit too strict and doesn't allow additional messages to be present on the STDOUT of the process.
JDK-8346834 has shown that the JVM can sometimes log a warning message on STDOUT. The EntryCount64k.java test can be improved to handle that situation better.
- backported by
-
-
- New
-
-
-
- New
-
-
-
- New
-
-
-
- New
-
-
-
- New
-
- links to
-
Commit(master)
openjdk/jdk/24c5ff7b
-
Review(master)
openjdk/jdk/22892
(2 links to)