P4
Hi,
The test for dropping messages have started to fail on aarch64 fast debug on Linux only (seeJDK-8352568). 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.
Fail if the asynchronous mode isn't "drop" (the test makes no sense with stalling mode)
Print the entirety of the log file produced if no missing messages are found
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 the bug.
The test for dropping messages have started to fail on aarch64 fast debug on Linux only (see
Fail if the asynchronous mode isn't "drop" (the test makes no sense with stalling mode)
Print the entirety of the log file produced if no missing messages are found
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 the bug.
- relates to
-
JDK-8352568 Test gtest/AsyncLogGtest.java failed at droppingMessage_vm
-
- Resolved
-
- links to
-
Review(master)
openjdk/jdk/24411