Open pshipton opened 6 months ago
@mpirvu fyi
Just an observation: the output from the failed test shows:
[ERR] /home/jenkins/workspace/Test_openjdk8_j9_sanity.functional_s390x_linux_Nightly_testList_0/aqa-tests/TKG/../../jvmtest/functional/cmdLineTests/jitserver/jitserverconfig.sh: line 30: lsof: command not found
So, the machine does not have lsof
installed and the test harness will not be able to tell which ports are busy. This may result in "port is in use" type of errors, but this error here is different.
Another observation:
[ERR] JITServer is currently a technology preview. Its use is not yet supported.
I though we deleted those messages on all platforms.
The diagnostic info shows that the client cannot connect to the server for compilation requests:
[ERR] #FAILURE: JITServer::StreamFailure: Connect failed: Connection refused for sun/reflect/Reflection.getCallerClass()Ljava/lang/Class; @ cold
....
[ERR] #JITServer: t= 50 Could not connect to a server. Next attempt in 2000 ms.
[ERR] #JITServer: t= 50 Resetting activation policy to AGGRESSIVE because client has lost connection to server
[ERR] #JITServer: JITServer StreamFailure (server unreachable before the termination message was sent): Connect failed: Connection refused
The test fails because the output finds "Connection refused". It's not clear whether the health port is also refusing connections. Probably not. The server is still active, or at least it didn't crash because we can read its PID after the client finishes.
https://openj9-jenkins.osuosl.org/job/Test_openjdk8_j9_sanity.functional_s390x_linux_Nightly_testList_0/758 testJitserverArguments_0