On Thu, 6 Nov 2025 16:22:41 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. @dfuch, could replacing `1ms` sleeps in `RawChannelTest` with `1ns` be a solution too? ------------- Marked as reviewed by vyazici (Committer). PR Review: https://git.openjdk.org/jdk/pull/28178#pullrequestreview-3435397100
