03 дек. 2013 г., в 14:11, Tim Horton <[email protected]> написал(а):
> It would be ideal if you could figure out *why* the test is flaky. What state > are the tests that run before it setting that isn’t getting reset? Can you > narrow it down to a pair of tests? One way to do this is to run accessibility tests with "--child-processes=1 --verbose" options, and to start bisecting if that makes the issue reliable. Another useful approach is to make the tests run multiple times with "--child-processes=1 --verbose —repeat-each=10". - WBR, Alexey Proskuryakov _______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
