On Fri, Jun 29, 2012 at 9:00 AM, Balazs Kelemen <kbal...@webkit.org> wrote: > I think this is just the default, WebKitTestRunner has a --timeout that > should control this if given. If that's not the case than it seems like a > bug for me. On the other hand, I don't think run-webkit-tests supports > setting custom timeout for a particular test. >
Correct, neither old-run-webkit-tests nor new-run-webkit-tests supports per-test custom timeouts. new-run-webkit-tests does support the concept of "slow" tests (i.e., two timeouts), but we generally use this to reduce the default value (i.e., chromium runs with 6 and 12 seconds). As Brady said, the test needs to be redesigned or broken up if it takes that long to run. -- Dirk _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
