-
Bug
-
Resolution: Unresolved
-
P4
-
14
Test that failed: test/hotspot/jtreg/containers/docker/TestJcmdWithSideCar.java
This can be container related, or not.
Frequency: Somewhat intermittent, fails about 1 in 4 times in CI
Scenario:
The observed JVM (target of jhsdb jinfo command) runs in container A (pid=1, normal when running in container), while the 'jhsdb jinfo' runs in a 'sidecar' container B. The containers are 'friendly' to each other, sharing process namespace, /tmp directories and signals. The PTRACE capability is enabled on the target container. It usually works, but in this instance it fails.
See the relevant log section in the comments below:
This can be container related, or not.
Frequency: Somewhat intermittent, fails about 1 in 4 times in CI
Scenario:
The observed JVM (target of jhsdb jinfo command) runs in container A (pid=1, normal when running in container), while the 'jhsdb jinfo' runs in a 'sidecar' container B. The containers are 'friendly' to each other, sharing process namespace, /tmp directories and signals. The PTRACE capability is enabled on the target container. It usually works, but in this instance it fails.
See the relevant log section in the comments below:
- relates to
-
JDK-8228904 Problemlist docker/TestJcmdWithSideCar.java until JDK-8228850 and JDK-8228960 are fixed
-
- Resolved
-