RFR: 8259954: gc/shenandoah/mxbeans tests fail with -Xcomp
Eric Liu
github.com+10482586+therealeliu at openjdk.java.net
Thu Jan 21 09:59:54 UTC 2021
On Thu, 21 Jan 2021 09:09:22 GMT, Aleksey Shipilev <shade at openjdk.org> wrote:
> See the bug report for initial observation. The key thing is that the asynchronous GC notifications can arrive late, and they do arrive late with `-Xcomp`, because all that code is now waiting for compilation. The answer is to wait a bit smarter.
>
> Additional testing:
> - [x] `gc/shenandoah/mxbeans` default mode
> - [x] `gc/shenandoah/mxbeans` with `-Xcomp`
> - [x] `gc/shenandoah/mxbeans` with `-Xint`
test/hotspot/jtreg/gc/shenandoah/mxbeans/TestChurnNotifications.java line 167:
> 165: Thread.sleep(1000);
> 166: }
> 167: Thread.sleep(5000);
I was wandering if it's necessary to handle the timeout by the code itself instead of delegating to jtreg? In the worst case, that's a really long time about 960000ms.
-------------
PR: https://git.openjdk.java.net/jdk/pull/2179
More information about the shenandoah-dev
mailing list