-
Bug
-
Resolution: Fixed
-
P4
-
25, 26
-
master
-
generic
-
linux
On Linux ppc64le RHEL 8, we have such a docker version :
docker --version
Docker version v25.0.3, build 4debf41
Unfortunately, the leading 'v' is not expected in ContainerRuntimeVersionTestUtils fromVersionString so we get an exception.
Probably we should simply skip the leading 'v' .
Also the appended build info has to be considered.
Example :
TEST: jdk/internal/platform/docker/TestDockerMemoryMetricsSubgroup.java
TEST RESULT: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Failed to parse container runtime version: Docker version v25.0.3, build 4debf41
docker --version
Docker version v25.0.3, build 4debf41
Unfortunately, the leading 'v' is not expected in ContainerRuntimeVersionTestUtils fromVersionString so we get an exception.
Probably we should simply skip the leading 'v' .
Also the appended build info has to be considered.
Example :
TEST: jdk/internal/platform/docker/TestDockerMemoryMetricsSubgroup.java
TEST RESULT: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: Failed to parse container runtime version: Docker version v25.0.3, build 4debf41
- caused by
-
JDK-8352926 New test TestDockerMemoryMetricsSubgroup.java fails
-
- Resolved
-
- links to
-
Commit(master) openjdk/jdk/97ec9d3e
-
Review(master) openjdk/jdk/25996