RFR: JDK-8326389: [test] improve assertEquals failure output [v2]
Matthias Baesken
mbaesken at openjdk.org
Thu Feb 22 14:57:05 UTC 2024
> 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.lib.Asserts.fail(Asserts.java:634)
> at jdk.test.lib.Asserts.assertEquals(Asserts.java:205)
>
> (I don't think we really expected that for some reason 0 equals 1)
> This should be improved.
Matthias Baesken has updated the pull request incrementally with one additional commit since the last revision:
Adjust COPYRIGHT year info
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/17952/files
- new: https://git.openjdk.org/jdk/pull/17952/files/d7b4de35..09989d25
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=17952&range=01
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=17952&range=00-01
Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod
Patch: https://git.openjdk.org/jdk/pull/17952.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/17952/head:pull/17952
PR: https://git.openjdk.org/jdk/pull/17952
More information about the core-libs-dev
mailing list