Bug 126166
| Summary: | REGRESSION: fast/js/dfg-* typed array tests frequently time out on debug bots | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
| Component: | JavaScriptCore | Assignee: | Nobody <webkit-unassigned> |
| Status: | REOPENED | ||
| Severity: | Normal | CC: | barraclough, fpizlo, ggaren, jbedard, koivisto, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Alexey Proskuryakov
http://webkit-test-results.appspot.com/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=js%2Fdfg-.*array.html
These tests were always slow, but bots very clearly claim that they became ~50% slower at around r160908 (lazy DOM tree creation patch). I know this doesn't seem related, but the numbers appear conclusive.
Even if not a true regression, we should do something to make these tests not time out on bots.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
It appears that these tests are over 30x slower in debug than in release - they don't show up on flakiness dashboard for release builds, which I believe means that they take under 1 second.
Skipped in http://trac.webkit.org/r162543 with Filip's blessing.
Radar WebKit Bug Importer
<rdar://problem/15883202>
Alexey Proskuryakov
This doesn't happen any more.
Jonathan Bedard
These tests remain slow, although they shouldn't time out.
Another possible approach, given that all of the tests in question generate large arrays and preform computations on them, would be to simply decrease the size of the arrays the tests use.