177204 2017-09-19 15:26:01 -0700 stress/regress-159779-2.js.ftl-eager-no-cjit is timing out 2017-10-04 12:56:56 -0700 1 1 1 Unclassified WebKit JavaScriptCore WebKit Nightly Build Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 1 jlewis3 webkit-unassigned ryanhaddad saam ysuzuki oldest_to_newest 1350542 0 jlewis3 2017-09-19 15:26:01 -0700 stress/regress-159779-2.js.ftl-eager-no-cjit has been a flaky failure on the debug JSC testers; it fails more often than it passes. The first build I found the failure in when going through the archive is: https://build.webkit.org/builders/Apple%20Sierra%20Debug%20JSC%20%28Tests%29/builds/972 https://build.webkit.org/builders/Apple%20Sierra%20Debug%20JSC%20%28Tests%29/builds/972/steps/jscore-test/logs/stdio it looks as though the failure started after this revision: https://trac.webkit.org/changeset/221783/webkit 1355247 1 ryanhaddad 2017-10-02 09:22:16 -0700 Here is a new link since the bots have been moved to High Sierra: https://build.webkit.org/builders/Apple%20High%20Sierra%20Debug%20JSC%20%28Tests%29/builds/1 This test is timing out on every run. 1355850 2 ryanhaddad 2017-10-03 09:17:08 -0700 Skipped test on debug in https://trac.webkit.org/changeset/222780/webkit 1356595 3 saam 2017-10-04 12:50:57 -0700 Matt, what do you mean by a flaky failure here? The things you linked to are dead links. 1356598 4 saam 2017-10-04 12:52:56 -0700 (In reply to Saam Barati from comment #3) > Matt, what do you mean by a flaky failure here? The things you linked to are > dead links. Oops, I missed Ryan's comments. Looking at logs now. 1356602 5 saam 2017-10-04 12:56:56 -0700 (In reply to Ryan Haddad from comment #2) > Skipped test on debug in https://trac.webkit.org/changeset/222780/webkit Skipping this test in debug mode is totally OK behavior. These fuzzing tests can run for a really long time in debug, especially with eager compilation mode.