On Tue, 3 Mar 2026 10:40:59 GMT, Daniel Jeliński <[email protected]> wrote:
>> Raise the QUIC connection timeout in the H3MultipleConnectionsToSameHost >> test above the jtreg timeout. >> >> The test failed with a QUIC connection timeout, but the reason for the >> timeout was not found in the logs. This kind of failure is usually caused by >> one of: >> - packet loss; when that happens, the congestion controller slows down the >> sending rate until the connection times out, >> - threading issues like races / deadlocks >> - overloaded machine; the threads might not get enough CPU time to respond >> before the timeout expires. >> >> Increasing the QUIC connection timeout should mitigate the packet loss and >> CPU issues, and will provide additional information like thread / core dumps >> to help with diagnosing threading issues. > > Daniel Jeliński has updated the pull request with a new target base due to a > merge or a rebase. The pull request now contains two commits: > > - Merge remote-tracking branch 'origin/master' into h3-timeout > - Raise QUIC connection timeout above jtreg timeout Thanks for the reviews! ------------- PR Comment: https://git.openjdk.org/jdk/pull/29993#issuecomment-3996415604
