Skip to content
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

jdk14: JlmRemote testcases failing, unsure why...? #10156

Closed
andrew-m-leonard opened this issue Jul 14, 2020 · 4 comments
Closed

jdk14: JlmRemote testcases failing, unsure why...? #10156

andrew-m-leonard opened this issue Jul 14, 2020 · 4 comments

Comments

@andrew-m-leonard
Copy link
Contributor

andrew-m-leonard commented Jul 14, 2020

https://ci.adoptopenjdk.net/job/Test_openjdk14_j9_sanity.system_x86-64_linux_xl/145/consoleFull
test-scaleway-ubuntu1604-x64-1

01:43:17 FAILED test targets:
01:43:17 TestJlmRemoteClassNoAuth_0
01:43:17 TestJlmRemoteMemoryAuth_0
01:43:17 TestJlmRemoteMemoryNoAuth_0
01:43:17 TestIBMJlmRemoteClassAuth_0
01:43:17 TestIBMJlmRemoteClassNoAuth_0
01:43:17 TestIBMJlmRemoteMemoryAuth_0
01:43:17 TestIBMJlmRemoteMemoryNoAuth_0

00:06:20  STF 23:06:16.340 - Heartbeat: Process LT1 is still running
00:06:39  CL1 j> 2020/07/13 23:06:35.635 Monitored VM not ready at Jul 13, 2020, 11:06:35 PM (attempt 6).
00:06:39  CL1 j> 2020/07/13 23:06:35.635 Wait 10 secs and trying again...
00:06:39  CL1 j> 2020/07/13 23:06:35.636 Trying to connect using JMXConnectorFactory
00:09:02  CL1 j> 2020/07/13 23:08:53.065 Monitored VM not ready at Jul 13, 2020, 11:08:53 PM (attempt 7).
00:09:02  CL1 j> 2020/07/13 23:08:53.066 Wait 10 secs and trying again...
00:09:02  CL1 j> 2020/07/13 23:08:53.066 Trying to connect using JMXConnectorFactory
00:11:25  CL1 j> 2020/07/13 23:11:10.504 Monitored VM not ready at Jul 13, 2020, 11:11:10 PM (attempt 8).
00:11:25  CL1 j> 2020/07/13 23:11:10.505 Wait 10 secs and trying again...
00:11:25  CL1 j> 2020/07/13 23:11:10.505 Trying to connect using JMXConnectorFactory
00:11:25  STF 23:11:16.003 - Heartbeat: Process CL1 is still running
00:13:34  CL1 j> 2020/07/13 23:13:27.824 Monitored VM not ready at Jul 13, 2020, 11:13:27 PM (attempt 9).
00:13:34  CL1 j> 2020/07/13 23:13:27.826 Wait 10 secs and trying again...
00:13:34  CL1 j> 2020/07/13 23:13:27.827 Trying to connect using JMXConnectorFactory
00:15:57  CL1 j> 2020/07/13 23:15:45.225 Monitored VM not ready at Jul 13, 2020, 11:15:45 PM (attempt 10).
00:15:57  CL1 j> 2020/07/13 23:15:45.225 Wait 10 secs and trying again...
00:15:57  CL1 j> 2020/07/13 23:15:45.226 Trying to connect using JMXConnectorFactory
00:16:17  STF 23:16:16.269 - Heartbeat: Process LT1 is still running
00:16:30  STF 23:16:28.367 - **FAILED** Process LT1 has ended unexpectedly

No clear reason why

@pshipton
Copy link
Member

pshipton commented Jul 14, 2020

Some kind of network problem on the machine?
1.LT1.stdout

22:13:47.264 - Completed 100.0%. Number of tests started=260268 (+3437)
...
22:13:54.985 - Thread completed. Suite=0 thread=21
22:13:55.055 - Thread completed. Suite=0 thread=12
22:13:55.121 - Test stopped due to reaching runtime limit
22:13:55.122 - Load test completed
22:13:55.122 -   Ran     : 260268
22:13:55.123 -   Passed  : 260268
22:13:55.123 -   Failed  : 0
22:13:55.124 -   Result  : PASSED
3XMTHREADINFO      "RMI RenewClean-[10.8.206.67:42327]" J9VMThread:0x00007FEF78601B00, omrthread_t:0x00007FEF785F54B8, java/lang/Thread:0x00007FEF7585BED8, state:R, prio=5
3XMJAVALTHREAD            (java/lang/Thread getId:0x1A, isDaemon:true)
3XMTHREADINFO1            (native thread ID:0x9FC, native priority:0x5, native policy:UNKNOWN, vmstate:R, vm thread flags:0x000000a1)
3XMTHREADINFO2            (native stack address range from:0x00007FEF4D32F000, to:0x00007FEF4D370000, size:0x41000)
3XMCPUTIME               CPU usage total: 0.003284840 secs, current category="Application"
3XMHEAPALLOC             Heap bytes allocated since last GC cycle=12240 (0x2FD0)
3XMTHREADINFO3           Java callstack:
4XESTACKTRACE                at sun/nio/ch/Net.connect0(Native Method)
4XESTACKTRACE                at sun/nio/ch/Net.connect(Net.java:503)
4XESTACKTRACE                at sun/nio/ch/Net.connect(Net.java:492)
4XESTACKTRACE                at sun/nio/ch/NioSocketImpl.connect(NioSocketImpl.java:588)
4XESTACKTRACE                at java/net/SocksSocketImpl.connect(SocksSocketImpl.java:333(Compiled Code))
4XESTACKTRACE                at java/net/Socket.connect(Socket.java:648)
4XESTACKTRACE                at java/net/Socket.connect(Socket.java:597)
4XESTACKTRACE                at java/net/Socket.<init>(Socket.java:520)
4XESTACKTRACE                at java/net/Socket.<init>(Socket.java:294)
4XESTACKTRACE                at sun/rmi/transport/tcp/TCPDirectSocketFactory.createSocket(TCPDirectSocketFactory.java:40)
4XESTACKTRACE                at sun/rmi/transport/tcp/TCPEndpoint.newSocket(TCPEndpoint.java:617)
4XESTACKTRACE                at sun/rmi/transport/tcp/TCPChannel.createConnection(TCPChannel.java:209)
4XESTACKTRACE                at sun/rmi/transport/tcp/TCPChannel.newConnection(TCPChannel.java:196)

@adamfarley
Copy link
Contributor

I think this could be a duplicate of adoptium/aqa-systemtest#246

@lumpfish
Copy link
Contributor

This is different to the failures seen in adoptium/aqa-systemtest#246 (and similar issues) which was fixed by adoptium/aqa-systemtest#246.

As @pshipton suggests above there appears to be some issue with the test machine preventing the test processes connecting.

adoptium/infrastructure#1627 has been raised at AdoptOpenJDK.

@pshipton
Copy link
Member

Since we have the issue raised at Adopt, I'll close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants