RFR: 8377433: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java failed

Kevin Walls kevinw at openjdk.org
Fri Feb 20 11:16:15 UTC 2026


On Thu, 19 Feb 2026 19:48:05 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:

>> Test timeout: update to use timeout factor.  
>> 
>> The timeout that fails is short, and failing runs have a test.timeout.factor of 10 or 16 (Xcomp and low threshold) .  Timeout was bumped from 30 to 60 seconds in a previous change, it's better revert that and apply the timeout.
>
> test/jdk/com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java line 38:
> 
>> 36:  * @library /test/lib
>> 37:  * @build jdk.test.lib.Utils
>> 38:  *
> 
> Q: Why this is needed now? Did this test work before?

Thanks Serguei - I think it's just a variation in something which Xcomp makes really slow already, and occasionally times out.  This test has timed out with Xcomp sometimes over the years.  If there is a genuine failure we should fail with the longer adjusted timeout.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/29813#discussion_r2832697177


More information about the serviceability-dev mailing list