-
Bug
-
Resolution: Fixed
-
P4
-
21, 22, 23
-
b12
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8357114 | 21.0.8 | Goetz Lindenmaier | P4 | Resolved | Fixed | b04 |
| JDK-8357125 | 17.0.16 | Goetz Lindenmaier | P4 | Resolved | Fixed | b04 |
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::lock: 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.
java.lang.RuntimeException: VM output should contain exactly one RTM locking statistics entry for method compiler.rtm.locking.TestRTMTotalCountIncrRate$Test::lock: 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.
- backported by
-
JDK-8357114 [test] improve assertEquals failure output
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk/9b1f1e52
-
Commit(master)
openjdk/jdk17u-dev/27c553e5
-
Commit(master)
openjdk/jdk21u-dev/e83e1383
-
Review
openjdk/jdk/17952
-
Review(master)
openjdk/jdk17u-dev/3574
-
Review(master)
openjdk/jdk21u-dev/1787
(3 links to)