RFR: 8352568: Test gtest/AsyncLogGtest.java failed at droppingMessage_vm

Leonid Mesnik lmesnik at openjdk.org
Thu Apr 3 19:32:47 UTC 2025


On Thu, 3 Apr 2025 10:35:29 GMT, Johan Sjölen <jsjolen at openjdk.org> wrote:

> Hi,
> 
> The test for dropping messages have started to fail on aarch64 fast debug on Linux only. It's currently unclear why this occurs. To figure out why, I've extended the test to do emit more diagnostic information if it fails.
> 
> 1. Fail if the asynchronous mode isn't "drop" (the test makes no sense with stalling mode)
> 2. Print the entirety of the log file produced if no missing messages are found
> 3. If the thread running the test is unattached, then async UL will emit log messages in synchronous mode. Therefore, if the thread is unattached, the test now fails with an error message.
> 
> With these changes integrated, I hope to be able to find the actual culprit of this bug.
> 
> I have attempted to reproduce this bug on both mainline and with this patch, but I have been unable to do so.

Changes looks reasonable.
However it should be another issue, the bug is not fixed, thus should still be open and GK should continue to link bugs to it.

-------------

Marked as reviewed by lmesnik (Reviewer).

PR Review: https://git.openjdk.org/jdk/pull/24411#pullrequestreview-2740937806


More information about the hotspot-runtime-dev mailing list