jmx-dev RFR: 8327505: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java fails
Kevin Walls
kevinw at openjdk.org
Tue Mar 19 17:55:28 UTC 2024
Client.java has a fixed 30-second timeout on the CountDownLatch to wait for 10 notifications.
If it fails, you can't tell if CountDownLatch.await threw, or returned false and the app threw InterruptedException, due to the way Client.java handles these.
Seems most likely the 30 second wait expired, as we are dealing with -Xcomp failures in a debug build. Passing runs can take a few seconds, but can be 25 seconds.
Increasing the timeout and tidying up the handling so we can see the specific reason in future.
-------------
Commit messages:
- 8327505: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java fails
Changes: https://git.openjdk.org/jdk/pull/18381/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=18381&range=00
Issue: https://bugs.openjdk.org/browse/JDK-8327505
Stats: 7 lines in 1 file changed: 3 ins; 0 del; 4 mod
Patch: https://git.openjdk.org/jdk/pull/18381.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/18381/head:pull/18381
PR: https://git.openjdk.org/jdk/pull/18381
More information about the jmx-dev
mailing list