some tests (e.g. stress test) are supposed to work long period of time and have time limitation mechanism inside their own logic. having timeout specified on jtreg level is obstructing for such types of tests. currently we can workaround it by specifying very big value, however it's not very nice solution. on the other hand, JavaTest harness supports actions w/o timeout, and we can use that in jtreg too.
so we are proposing changing jtreg to treat /timeout=0 as actions w/o timeout
so we are proposing changing jtreg to treat /timeout=0 as actions w/o timeout