On Wed, 21 Dec 2022 17:25:20 GMT, Harshitha Onkar <hon...@openjdk.org> wrote:
>> test/jdk/TEST.ROOT line 36: >> >>> 34: com/sun/net/httpserver/simpleserver \ >>> 35: java/awt \ >>> 36: javax/swing >> >> Hello Harshitha, I don't have any knowledge of the client area, but I see >> that there are a large number of tests that are present in >> `test/jdk/java/awt` and `test/jdk/javax/swing`. Adding these 2 directories >> to `exclusiveAccess.dirs` would mean that none of the tests in `java/awt` >> will be run when any other test in `java/awt` is currently in progress. Same >> with the `javax/swing` directory. So it could increase the duration of the >> tiers in which these tests run. Is there a CI run which shows if this >> changes the test run duration drastically? > > @jaikiran Thank you for the details. I'll check if the duration of run > differed drastically. I thought all the client tests run in non-concurrent > mode by default or does this differ for headful and headless test? *Headful* tests are not supposed concurrently: they display UI and often use Robot to send input events to the UI. Running such tests concurrently leads to obscure failures. In our CI system, `JTREG_JOBS=1` is passed to `make` when running headful tests. There's a set of *headless* tests which can be run concurrently. Such tests will be affected if they're run concurrently. ------------- PR: https://git.openjdk.org/jdk/pull/11747