|Summary:||[mac-wk2 debug] LayoutTest js/function-call-aliased.html is a flaky timeout|
|Product:||WebKit||Reporter:||Ryan Haddad <ryanhaddad>|
|Component:||New Bugs||Assignee:||Nobody <webkit-unassigned>|
|Status:||RESOLVED CONFIGURATION CHANGED|
|Severity:||Normal||CC:||ap, jbedard, webkit-bug-importer|
|Version:||WebKit Nightly Build|
Description Ryan Haddad 2016-06-30 13:35:21 PDT
LayoutTest js/function-call-aliased.html is a flaky timeout Most recent timeout: https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/builds/6247 Flakiness dashboard: https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=js%2Ffunction-call-aliased.html
Comment 1 Alexey Proskuryakov 2016-07-01 23:55:22 PDT
This looks like it's not a real problem with this test - WebKitTestRunner doesn't even start loading the test when it times out. Some logic seems wrong in WebKitTestRunner: 12:51:39.850 89305 worker/4 js/function-call-aliased.html output stderr lines: 12:51:39.850 89305 Timed out waiting for initial response from web process 12:51:39.850 89305 #PROCESS UNRESPONSIVE - com.apple.WebKit.WebContent.Development (pid 92706) > Most recent timeout: > https://build.webkit.org/builders/Apple%20El%20Capitan%20Debug%20WK2%20(Tests)/builds/6247 In this run, the previous test was js/function-apply.html. Perhaps it's doing something very slow after claiming to have succeeded.
Comment 4 Alexey Proskuryakov 2016-07-14 17:35:31 PDT
Changed ProcessType on bot162 and bot165 to see if that makes any change. Should undo that once done with the experiment.
Comment 5 Alexey Proskuryakov 2016-07-15 12:18:44 PDT
Looks like this hasn't happened in a while (last timeout that I see was on July 7).
Comment 6 Alexey Proskuryakov 2016-07-18 09:50:20 PDT
Comment on attachment 283701 [details] Patch Clearing review flag, as Jonathan is trying a different approach in bug 159827.
Comment 7 Jonathan Bedard 2016-09-16 11:26:27 PDT
This has stopped happening in the last few months. It appears that this is no longer an issue.