[Webkit-unassigned] [Bug 148569] REGRESSION(r188639): [GTK] Several inspector tests started to time out in GTK+ bots after r188639

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Sep 28 09:24:29 PDT 2015


https://bugs.webkit.org/show_bug.cgi?id=148569

--- Comment #9 from Brian Burg <bburg at apple.com> ---
(In reply to comment #8)
> There are still some tests timing out in the bots, but I think they are just
> slow. I've tried some of them, for example
> inspector/css/createStyleSheet.html never times out for me, however
> inspector/css/stylesheet-events-basic.html fails for me when run with
> run-webkit-tests and passes when using WTR directly. It also pass when
> running run-webkit-tests with --no-timeout, the test is a lot slower when
> using run-webkit-tests for some reason. The thing is that I'm not sure if
> the slowness is somehow expected or a bug specific to the GTK+ port. It
> seems to me that the inspector tests actually run multiple test cases per
> test, so it's probably expected to be slow. Should we mark inspector tests
> as slow to use a higher timeout?

We have been seeing similar issues for some Mac bots, with tests having high variance and taking several times longer to complete than when running locally, even on very old hardware (2008 MacBook runs tests in ~3s, bots can take up to 40s+). However, I  have not noticed differences between run-webkit-tests and direct WKTR execution. If you are able to find anything out, do file a bug.

<https://webkit.org/b/148636> tracks general flakiness in inspector tests.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150928/2e69a7bb/attachment-0001.html>


More information about the webkit-unassigned mailing list