On Tue, 21 Apr 2026 05:16:15 GMT, Yasumasa Suenaga <[email protected]> wrote:
>> test/hotspot/jtreg/serviceability/sa/ClhsdbLauncher.java line 157:
>>
>>> 155: if (!allowStderrOutput) {
>>> 156: oa.stderrShouldBeEmptyIgnoreVMWarnings();
>>> 157: }
>>
>> We need to be careful here. I think the reason for by default allowing
>> stderr output is because it can sometimes appear, but is not necessarily
>> indicative of bug. For example, sometimes during the stack dump an active
>> thread can produce an exception because it is not in a consistent state, but
>> the thread we care about (like SteadyStateThread) produces what we are
>> looking for, so the test should pass. I worry that this change is going to
>> produce a lot of intermittent failures.
>
> Indeed the thread might have inconsistent state because they would be stopped
> by signal or `ptrace()`.
> So is it better to check `*Exception: ` and `*Error: ` in stderr?
But that is what my concern is. We can see exceptions on stderr that we want to
ignore.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/30808#discussion_r3121454067
