Open andrew-m-leonard opened 3 years ago
Seems like a machine problem, but @knn-k fyi.
@andrew-m-leonard Can you run a couple of grinders with the individual test (perhaps the hanging one and the previous one you're suspicious of) on the same same, and one other?
@andrew-m-leonard Job 102 on the "twin" machine from the same provider seemed to pass green (I'm assuming the same tests were in each)
Both tests on build-alibaba-ubuntu1804-armv8-1: https://ci.adoptopenjdk.net/job/Grinder/7632/console : HUNG Again Both tests on build-docker-ubuntu1804-armv8-3: https://ci.adoptopenjdk.net/job/Grinder/7633/console : Green
Tried just testJCMMXBeanRemote_SE80_1 on its own and still hangs on build-alibaba-ubuntu1804-armv8-1: https://ci.adoptopenjdk.net/job/Grinder/7650/consoleFull
@sxa looking like an issue on build-alibaba-ubuntu1804-armv8-1
and again but jdk-17 this time: https://ci.adoptopenjdk.net/job/Test_openjdk17_j9_extended.functional_aarch64_linux/17/console again on node build-alibaba-ubuntu1804-armv8-1 @pshipton fyi
@andrew-m-leonard if there is a JVM running you can try sending it a kill -QUIT <pid>
signal, and maybe get a javacore so we can see that it's doing. I'm guessing it's waiting on the network given that it's a remote beans test.
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_extended.functional_aarch64_linux/103/console Suspicious of the previous test testJCMMXBeanRemote_SE80_0 which failed...did that then cause the testJCMMXBeanRemote_SE80_1 one to hang? Node: build-alibaba-ubuntu1804-armv8-1