Bug 158133 - LayoutTest js/function-apply.html is a flaky timeout on mac debug wk2
Summary: LayoutTest js/function-apply.html is a flaky timeout on mac debug wk2
Status: RESOLVED DUPLICATE of bug 157990
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-26 15:58 PDT by Ryan Haddad
Modified: 2016-06-02 13:39 PDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Ryan Haddad 2016-05-26 16:03:08 PDT
Marked as flaky in <https://trac.webkit.org/r201437>
Comment 2 Alexey Proskuryakov 2016-05-29 17:40:29 PDT
It appears that this test times out for multiple reasons. It used to time out somewhat rarely. But it recently started to time out after 5 seconds a lot, which is undoubtedly a change in behavior induced by <http://trac.webkit.org/r201263>.

16:39:43.905 33037 worker/1 js/for-of-crash.html passed
16:39:46.370 33037 worker/1 js/function-apply-many-args.html passed
16:39:51.364 33037 com.apple.WebKit.WebContent.Development is unresponsive, pid = 33224
16:39:51.380 33037 "/usr/bin/sample 33224 10 10 -file /Volumes/Data/slave/yosemite-debug-tests-wk2/build/layout-test-results/com.apple.WebKit.WebContent.Development-33224-sample.txt" took 0.02s
16:39:51.381 33037 Unable to sample process:Failed to run "['/usr/bin/sample', 33224, 10, 10, '-file', '/Volumes/Data/slave/yosemite-debug-tests-wk2/build/layout-test-results/com.apple.WebKit.WebContent.Development-33224-sample.txt']" exit_code: 255
16:39:51.383 33037 worker/1 js/function-apply.html output stderr lines:
16:39:51.383 33037   TestController::resetStateToConsistentValues failed
16:39:51.383 33037   #PROCESS UNRESPONSIVE - com.apple.WebKit.WebContent.Development (pid 33224)
16:39:51.385 32989 [37355/42453] js/function-apply.html failed unexpectedly (test timed out)
Comment 3 Alexey Proskuryakov 2016-06-02 13:39:03 PDT

*** This bug has been marked as a duplicate of bug 157990 ***