Bug 177204 - stress/regress-159779-2.js.ftl-eager-no-cjit is timing out
Summary: stress/regress-159779-2.js.ftl-eager-no-cjit is timing out
Status: RESOLVED WONTFIX
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: 2017-09-19 15:26 PDT by Matt Lewis
Modified: 2017-10-04 12:56 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Matt Lewis 2017-09-19 15:26:01 PDT 
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
Comment 1 Ryan Haddad 2017-10-02 09:22:16 PDT 
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.
Comment 2 Ryan Haddad 2017-10-03 09:17:08 PDT 
Skipped test on debug in https://trac.webkit.org/changeset/222780/webkit
Comment 3 Saam Barati 2017-10-04 12:50:57 PDT 
Matt, what do you mean by a flaky failure here? The things you linked to are dead links.
Comment 4 Saam Barati 2017-10-04 12:52:56 PDT 
(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.
Comment 5 Saam Barati 2017-10-04 12:56:56 PDT 
(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.