On 17/09/2014 7:45 AM, Paul Sandoz wrote:

Hi,

Please see below for a patch to disable concurrent execution of the stream tests by jtreg.

A number of our smaller systems may not be able to handle running these tests concurrently regardless, so I think removing the concurrency is a good thing regardless of F/J changes. So looks good to me. Thanks, David

Due to recent f/j changes some stream tests are now timing out. This is because the tests are running concurrently and parallel stream execution in one process is competing for resources with parallel stream execution in another process. This was actually always the case, but the recent f/j changes appear to be more sensitive to OS scheduling effects on some platforms and there is not much we can do about that at the moment.

This is unlikely to increase the overall execution time of the JDK tests by much.

Paul.

diff -r aabb503ab6de test/TEST.ROOT --- a/test/TEST.ROOT Tue Sep 16 23:16:01 2014 +0200 +++ b/test/TEST.ROOT Tue Sep 16 23:26:11 2014 +0200 @@ -8,7 +8,7 @@ othervm.dirs=java/awt java/beans javax/accessibility javax/imageio javax/sound javax/print javax/management com/sun/awt sun/awt sun/java2d sun/pisces

# Tests that cannot run concurrently -exclusiveAccess.dirs=java/rmi/Naming java/util/prefs sun/management/jmxremote sun/tools/jstatd sun/security/mscapi +exclusiveAccess.dirs=java/rmi/Naming java/util/prefs sun/management/jmxremote sun/tools/jstatd sun/security/mscapi java/util/stream

# Group definitions groups=TEST.groups [closed/TEST.groups]