-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 18, 19
-
b10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8284434 | 18.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b03 |
| JDK-8283251 | 17.0.4 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
STDOUT:
STDERR:
java.lang.RuntimeException: Too few tlab objects allocated: expected 50 >= 80
at jdk.test.lib.Asserts.fail(Asserts.java:594)
at jdk.test.lib.Asserts.assertGreaterThanOrEqual(Asserts.java:288)
at jdk.jfr.event.allocation.TestObjectAllocationInNewTLABEvent.main(TestObjectAllocationInNewTLABEvent.java:78)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
at java.base/java.lang.reflect.Method.invoke(Method.java:577)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:828)
I think the test makes questionably assumptions about the size of byte array allocated, which fail on 32-bit platforms.
- backported by
-
JDK-8283251 Improve jfr/event/allocation tests reliability
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
JDK-8281638 jfr/event/allocation tests fail with release VMs after JDK-8281318 due to lack of -XX:+UnlockDiagnosticVMOptions
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk17u-dev/cf2a7abc
-
Commit
openjdk/jdk18u/b50949a5
-
Commit
openjdk/jdk/65831eb2
-
Review
openjdk/jdk17u-dev/240
-
Review
openjdk/jdk18u/42
-
Review
openjdk/jdk/7365