On Thu, 7 Sep 2023 16:22:18 GMT, Soumadipta Roy wrote:
>> test/jdk/java/util/concurrent/tck/JSR166TestCase.java line 45:
>>
>>> 43: * @modules java.management
>>> 44: * @run junit/othervm/timeout=1000 JSR166TestCase
>>> 45: * @run junit/othervm/timeout=1000 -Djava.security.manager=allow
>>>
On Thu, 7 Sep 2023 16:08:16 GMT, Martin Buchholz wrote:
> Hello Soumadipta - pleased to "meet" you.
>
> If the intent is to split the tests into relatively more and less important
> variants for placing into separate tiers, that should be clear from the
> @summary's in the tests.
Hi @Martin-B
On Thu, 7 Sep 2023 15:58:26 GMT, Martin Buchholz wrote:
>> Soumadipta Roy has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Remove extra new line
>
> test/jdk/java/util/concurrent/tck/JSR166TestCase.java line 45:
>
>> 43: * @modules java
On Thu, 7 Sep 2023 14:10:20 GMT, Soumadipta Roy wrote:
>> This test is running in tier1, and takes about 400 seconds to complete.
>> Thus, it drags the execution time of tier1 on large machines. The commit
>> includes changing the sequential run of test cases in
>> java/util/concurrent/tck/JSR
On Thu, 7 Sep 2023 14:10:20 GMT, Soumadipta Roy wrote:
>> This test is running in tier1, and takes about 400 seconds to complete.
>> Thus, it drags the execution time of tier1 on large machines. The commit
>> includes changing the sequential run of test cases in
>> java/util/concurrent/tck/JSR
> This test is running in tier1, and takes about 400 seconds to complete. Thus,
> it drags the execution time of tier1 on large machines. The commit includes
> changing the sequential run of test cases in
> java/util/concurrent/tck/JSR166TestCase.java to the best possible combination
> of paral
