Bug 177204
Summary: | stress/regress-159779-2.js.ftl-eager-no-cjit is timing out | ||
---|---|---|---|
Product: | WebKit | Reporter: | Matt Lewis <jlewis3> |
Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED WONTFIX | ||
Severity: | Normal | CC: | ryanhaddad, saam, ysuzuki |
Priority: | P2 | ||
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Matt Lewis
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
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Ryan Haddad
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.
Ryan Haddad
Skipped test on debug in https://trac.webkit.org/changeset/222780/webkit
Saam Barati
Matt, what do you mean by a flaky failure here? The things you linked to are dead links.
Saam Barati
(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.
Saam Barati
(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.