> 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: Fix copyright dates ------------- Changes: - all: https://git.openjdk.org/jdk/pull/28178/files - new: https://git.openjdk.org/jdk/pull/28178/files/0ae487b8..e05864db Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=28178&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=28178&range=01-02 Stats: 2 lines in 2 files changed: 0 ins; 0 del; 2 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
