> Several tests from test/jdk/sun/tools/jstatd are intermittent. > > Port clashes when run at the same time on the same machine have been a > problem. > The RMI error "no such object in table" can mean a reference on the RMI > server has been GC'd. > Either way, jstatd fails to startup and and the test fails. > > These both have jstatd reporting "Could not bind" which should be recognised > and retried, as we already do for (some) port in use problems. i.e. > JstatdTest.java: the isJstadReady() method (will correct that typo also) > checks for "Port already in use", which can be printed by TCPTransport.java. > > Should update its test to check for "Could not bind". > Should limit the retries also.
Kevin Walls has updated the pull request incrementally with one additional commit since the last revision: Modernisation ------------- Changes: - all: https://git.openjdk.org/jdk/pull/15414/files - new: https://git.openjdk.org/jdk/pull/15414/files/67fd896d..35199a6d Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=15414&range=02 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=15414&range=01-02 Stats: 3 lines in 1 file changed: 2 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/15414.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/15414/head:pull/15414 PR: https://git.openjdk.org/jdk/pull/15414
