On Thu, 13 Nov 2025 13:14:25 GMT, Daniel Fuchs <[email protected]> wrote:
>> Nothing looks wrong with the test or the code. The failure happens rarely -
>> probably when the machine is under load: this test tries to saturate the
>> socket buffers and is resource consuming.
>>
>> The proposed fix is just to double the jtreg timeout for this test from 120
>> to 240.
>
> Daniel Fuchs has updated the pull request incrementally with one additional
> commit since the last revision:
>
> Copyright years
Marked as reviewed by djelinski (Reviewer).
test/jdk/java/net/httpclient/whitebox/java.net.http/jdk/internal/net/http/RawChannelTest.java
line 166:
> 164: writeStall.countDown(); // signal send buffer is
> full
> 165: } catch (IOException e) {
> 166: print("OP_RIGHT failed: " + e);
Suggestion:
print("OP_WRITE failed: " + e);
-------------
PR Review: https://git.openjdk.org/jdk/pull/28178#pullrequestreview-3459737196
PR Review Comment: https://git.openjdk.org/jdk/pull/28178#discussion_r2523422595
