Happy to vounteer for sponsorship duties. Been following this from the
sidelines.
-Rob
On 22/10/13 20:01, Alan Bateman wrote:
On 18/10/2013 17:00, Ivan Gerasimov wrote:
Thank you Martin for the references.
I've implemented passing the limitation to the application in a
similar manner.
The timeout value is passed to the test through the CloseRaceTimeout
system property.
If the property wasn't set, the default value of 2 minutes is used.
When the application creates its child process, this value is passed
through the argument list.
In any ways this test should be run by jtreg harness, since it uses
'testlibrary' for dealing with the child process.
However, when run by hands, there's a way to specify for how long it
should work.
Ivan - do you have a sponsor for this one? It would be good to get
this out of the way before ZBB.
On the default timeout in the test then I'd prefer it to be something
like 20s or 30s rather than 2 minutes. The reason is that we don't
currently have any distinction between stress tests and other types of
tests and so people tend to just run all the tests for an area (hence
2 minutes is a long time as we need the tests to execute as quickly as
possible).
-Alan.
