Hi,
Also, should it not be the case that running with -Xcomp should increase
the timeout factor
to avoid such issues? I'm not sure how that can be assured though.
Roger
On 5/1/2017 3:47 PM, Brent Christian wrote:
On 5/1/17 12:41 PM, Mandy Chung wrote:
Looks like this test execs a new VM for 66 times to exhaust the
combination of with and without security manager, with a valid or
malformed policy, client & custom loader in unnamed, named, automatic
module.
Right.
I think we could take out the automatic module case as named
module would verify it.
OK, I can do that. I'm pretty sure an increase to the timeout will
still be needed, though.
One refactor you can consider by separating
them in several @run actions. The timeout will apply to each action
but that does not help shorten the test execution time.
I had the same thought, and concluded that without a reduction in
overall execution time, the benefit of such a refactor is pretty limited.
Thanks,
-Brent
