-
Type:
Bug
-
Resolution: Fixed
-
Priority:
P3
-
Affects Version/s: 15
-
Component/s: core-svc
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8271211 | 11.0.13 | Martin Doerr | P3 | Resolved | Fixed | b01 |
| JDK-8286426 | openjdk8u342 | Xin Liu | P3 | Resolved | Fixed | b02 |
| JDK-8353110 | shenandoah8u342 | Xin Liu | P3 | Resolved | Fixed | b02 |
serviceability/attach/RemovingUnixDomainSocketTest.java
fails in debug builds with "stderr was not empty"
The code that was pushed has:
+ out.stderrShouldBeEmptyIgnoreVMWarnings()
+ .stderrShouldBeEmpty();
which initially allows for warnings (as it should) but then will fail anyway.
- backported by
-
JDK-8271211 serviceability/attach/RemovingUnixDomainSocketTest.java fails "stderr was not empty"
-
- Resolved
-
-
JDK-8286426 serviceability/attach/RemovingUnixDomainSocketTest.java fails "stderr was not empty"
-
- Resolved
-
-
JDK-8353110 serviceability/attach/RemovingUnixDomainSocketTest.java fails "stderr was not empty"
-
- Resolved
-
- relates to
-
JDK-8235211 serviceability/attach/RemovingUnixDomainSocketTest.java fails with AttachNotSupportedException: Unable to open socket file
-
- Resolved
-
- links to
-
Commit
openjdk/jdk8u-dev/1067c545
-
Commit
openjdk/jdk11u-dev/133eca0a
-
Review
openjdk/jdk8u-dev/32
-
Review
openjdk/jdk11u-dev/153