infrastructure
infrastructure copied to clipboard
System unavailable: test-aws-rhel8-x64-1
-
Please put the system name in the title of this issue. machine link
-
Link to any log file showing the problem: https://ci.adoptopenjdk.net/job/Test_openjdk16_j9_extended.openjdk_x86-64_linux/14/ (Hit timeout)
-
Please describe the issue: Looks to be locked ports on the machine. Have Re-run at https://ci.adoptopenjdk.net/job/Test_openjdk16_j9_extended.openjdk_x86-64_linux/15/ and marked the machine offline for now
Multiple processes from a run of Test_openjdk8_corretto_sanity
were left around. I have removed them and re-enabled the machine (Although it still needs a permanent fix to https://github.com/adoptium/infrastructure/issues/1829)
Running test at https://ci.adoptopenjdk.net/job/Grinder/1024/
Previous Grinder failed (likely because the parameters to Grinder have changed, or because of the repo move) so I have kicked off another JDK16/J9 extended.openjdk on this machine at https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk16_j9_extended.openjdk_x86-64_linux/33/
Job re-running at https://ci.adoptopenjdk.net/view/Test_openjdk/job/Test_openjdk16_j9_extended.openjdk_x86-64_linux/39/ since the previous one is now lost.
Running at https://ci.adoptopenjdk.net/job/Test_openjdk17_j9_extended.openjdk_x86-64_linux/30/
Running at https://ci.adoptopenjdk.net/job/Test_openjdk17_j9_extended.openjdk_x86-64_linux/30/
That failed with some connection issue on the machine, therefore re-running at https://ci.adoptopenjdk.net/job/Test_openjdk17_j9_extended.openjdk_x86-64_linux/33
Running the specific subset of tests for HotSpot listed in https://github.com/adoptium/infrastructure/issues/2360 as failing at https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_linux/38/
Running again at https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_linux/50 and hopefully I'll remember to look at the output this time :-)
Running again at https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_linux/102 (without dynamic parallel) and hopefully I'll remember to look at the output this time :-)
It worked without any port issues but failed a number of tests in sun/security/pkcs11
https://ci.adoptopenjdk.net/job/Test_openjdk17_hs_extended.openjdk_x86-64_linux/102/testReport/ - will raise this as a separate issue.