On 11/21/2013 2:08 AM, Alan Bateman wrote:
We have a number of test failures in agentvm mode that appear to be caused by tests changing the default TimeZone and not restoring it. These failures become very intermittently when running with concurrency as it is unpredictable as to the sequence of tests that a specific agent VM will execute from run to run.
If concurrent execution is a requirement, all tests changing default time zone and/or locale values need to run in "othervm"?
Masayoshi