NEW 179700
[ios-simulator] LayoutTest step intermittently times out before launching iPad simulators
https://bugs.webkit.org/show_bug.cgi?id=179700
Summary [ios-simulator] LayoutTest step intermittently times out before launching iPa...
Ryan Haddad
Reported 2017-11-14 15:58:53 PST
It appears that the LayoutTest step for iOS Simulator bots intermittently times out with no output at the point that it would be killing iPhone simulators to launch iPad simulators. A subsequent test run on the same bot will usually work without issue. Example failure: https://build.webkit.org/builders/Apple%20iOS%2011%20Simulator%20Release%20WK2%20%28Tests%29/builds/1280 Successful run on same bot: https://build.webkit.org/builders/Apple%20iOS%2011%20Simulator%20Release%20WK2%20%28Tests%29/builds/1282
Attachments
Radar WebKit Bug Importer
Comment 1 2017-11-14 15:59:13 PST
Jonathan Bedard
Comment 2 2017-11-17 08:13:54 PST
In order to debug this, we will need <https://bugs.webkit.org/show_bug.cgi?id=176393>. I also have a suspicion that this is related to the proposed fix <https://bugs.webkit.org/show_bug.cgi?id=178368>. This is one of the only places in webkitpy where we are waiting for something without a timeout.
Ryan Haddad
Comment 3 2018-01-08 13:27:54 PST
The following webkitpy tests also fails on runs that exhibit this behavior: [379/1691] webkitpy.layout_tests.controllers.layout_test_runner_unittest.LayoutTestRunnerTests.test_servers_started failed: Traceback (most recent call last): File "/Volumes/Data/slave/ios-simulator-11-release-tests-wk2/build/Tools/Scripts/webkitpy/layout_tests/controllers/layout_test_runner_unittest.py", line 178, in test_servers_started self.assertEqual(self.http_started, True) AssertionError: False != True New link since the original ones have expired: https://build.webkit.org/builders/Apple%20iOS%2011%20Simulator%20Release%20WK2%20%28Tests%29/builds/2308
Jonathan Bedard
Comment 4 2018-02-13 16:15:57 PST
We might be able to fix this by booting less iPad/iPhone 7 simulators.
Note You need to log in before you can comment on or make changes to this bug.