Re: RFR: JDK-8326389: [test] improve assertEquals failure output [v4]

2024-02-28 Thread Matthias Baesken
On Tue, 27 Feb 2024 16:48:05 GMT, Matthias Baesken wrote: >> Currently assertEquals has in the failure case sometimes confusing output >> like : >> >> java.lang.RuntimeException: VM output should contain exactly one RTM locking >> statistics entry for method >> compiler.rtm.locking.TestRTMTot

Re: RFR: JDK-8326389: [test] improve assertEquals failure output [v4]

2024-02-27 Thread Christoph Langer
On Tue, 27 Feb 2024 16:48:05 GMT, Matthias Baesken wrote: >> Currently assertEquals has in the failure case sometimes confusing output >> like : >> >> java.lang.RuntimeException: VM output should contain exactly one RTM locking >> statistics entry for method >> compiler.rtm.locking.TestRTMTot

Re: RFR: JDK-8326389: [test] improve assertEquals failure output [v4]

2024-02-27 Thread Jaikiran Pai
On Tue, 27 Feb 2024 16:48:05 GMT, Matthias Baesken wrote: >> Currently assertEquals has in the failure case sometimes confusing output >> like : >> >> java.lang.RuntimeException: VM output should contain exactly one RTM locking >> statistics entry for method >> compiler.rtm.locking.TestRTMTot

Re: RFR: JDK-8326389: [test] improve assertEquals failure output [v4]

2024-02-27 Thread Matthias Baesken
> Currently assertEquals has in the failure case sometimes confusing output > like : > > java.lang.RuntimeException: VM output should contain exactly one RTM locking > statistics entry for method > compiler.rtm.locking.TestRTMTotalCountIncrRate$Test:🔒 expected 0 to equal 1 >at jdk.test.