[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Integrated: 8327505: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.j
From:       Kevin Walls <kevinw () openjdk ! org>
Date:       2024-03-28 9:09:35
Message-ID: tlkDBaY_F1z-M28di8fbTQvTDMyX2VEyl7FHtXU7nTU=.40a46e3e-5ca3-45b4-aca1-33856e013f38 () github ! com
[Download RAW message or body]

On Tue, 19 Mar 2024 16:23:27 GMT, Kevin Walls <kevinw@openjdk.org> wrote:

> 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.

This pull request has now been integrated.

Changeset: 2b79c22c
Author:    Kevin Walls <kevinw@openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/2b79c22c43a2de0815e77c9aa71f010906be8670
                
Stats:     7 lines in 1 file changed: 3 ins; 0 del; 4 mod

8327505: Test com/sun/jmx/remote/NotificationMarshalVersions/TestSerializationMismatch.java \
fails

Reviewed-by: lmesnik, stuefe

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

PR: https://git.openjdk.org/jdk/pull/18381


[prev in list] [next in list] [prev in thread] [next in thread]