> 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 ------------- Changes: - all: https://git.openjdk.org/jdk/pull/28178/files - new: https://git.openjdk.org/jdk/pull/28178/files/18203dab..f9b48b19 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=28178&range=04 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=28178&range=03-04 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/28178.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/28178/head:pull/28178 PR: https://git.openjdk.org/jdk/pull/28178
