Hi Raphael, I searched all the test cases and found that , "Tester.sleep()" is used in all the GUI test cases, "Thread.sleep()" is used in UNO test cases. I think the slow PC only failed GUI test cases, and UNO test case will not be affected. (If you find "sleep()" in one test case, the sleep() actuall is "Tester.sleep()". )
So I think modify setting "sleep.factor" will solve your problem. On Fri, Jan 4, 2013 at 12:33 PM, Raphael Bircher <[email protected]> wrote: > Hi Linyi Li > > Thanks for the answare > > Am 04.01.2013 03:00, schrieb Linyi Li: > > Hi Raphael, >> >> There is a setting "sleep.factor". You can find it in Tester.java. >> Changing it from "1.0" to "2.0" or larger numbers, you can slow down the >> tests. >> >> But there may be a problem that I am not sure all the test cases useing >> "Tester.sleep()". You can try it to see the result. >> > Yes, exactly that's the case. In this file sleep() is used and not > Tester.sleep() > > Greetings Raphael > -- Best wishes. Linyi Li
