-
Notifications
You must be signed in to change notification settings - Fork 722
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jdk_container_0_FAILED jdk/internal/platform/docker/TestDockerCpuMetrics.java NPE at TestDockerCpuMetrics.main(TestDockerCpuMetrics.java:77) #16462
Comments
The test seems bogus as it can only run inside a docker environment. The NPE is caused by jdk.internal.platform.Metrics.systemMetrics() returning null. This is expected unless the JVM is running under docker. The test checks if docker is available on the machine, by running |
@JasonFengJ9 I expect this should be excluded everywhere it fails until it's working. |
A docker-enabled machine label is required, this test along with other docker test friends can be excluded if the framework support is going to take a while. |
Since they are new, we do not yet have all the data on all versions/platforms. I do not see any valid Test_openjdk8_j9_dev.openjdk_aarch64_linux test builds at Adoptium. But the same test passed on s390 at Adoptium https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_dev.openjdk_s390x_linux/7/ |
I also noticed the pipeline issue on platforms that do not have |
JDK17 0.36 build(
|
Failure link
From an internal build(
ub18-aarch64-4
):Rerun in Grinder - Change TARGET to run only the failed test targets.
Optional info
Failure output (captured from console output)
100x grinder
The text was updated successfully, but these errors were encountered: