ThreadInfo's that should be equal are detected as different

[pshipton]

https://openj9-jenkins.osuosl.org/job/Test_openjdk17_j9_sanity.functional_s390x_linux_Nightly_testList_1/656 JLM_Tests_class_0

00:51:47  FAILED: testThreadMXBeanProxy
00:51:47  java.lang.AssertionError: expected:<"main" prio=5 Id=1 RUNNABLE
00:51:47  > but was:<"main" prio=5 Id=1 RUNNABLE
00:51:47  >
00:51:47  	at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
00:51:47  	at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
00:51:47  	at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
00:51:47  	at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88)
00:51:47  	at org.openj9.test.java.lang.management.TestManagementFactory.testThreadMXBeanProxy(TestManagementFactory.java:1304)

[pshipton]

@r30shah @hzongaro fyi. Not sure if this is a very rare occurrence or related to some recent change. Or even what platforms are affected.

[hzongaro]

Looking at TestManagementFactory.testThreadMXBeanProxy I think it's actually ThreadInfo objects that are being tested for equality rather than Strings.

[pshipton]

Ah ok, thanks for checking. The equality check looks at many other fields which aren't reflected in the String output. I'll monitor this and if it occurs again modify the test to provide more info about the failure.

[pshipton]

Internal build [linux_390-64_cmprssptrs] SE80_GIT JLM_Tests_class_SE80

FAILED: testThreadMXBeanProxy
java.lang.AssertionError: expected:<"main" Id=1 RUNNABLE
> but was:<"main" Id=1 RUNNABLE
>
	at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
	at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
	at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
	at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:88)
	at org.openj9.test.java.lang.management.TestManagementFactory.testThreadMXBeanProxy(TestManagementFactory.java:1304)

[pshipton]

A new failure occurred with partial debug output. waitedCount ti1: 0 ti2: 4