The following layout test is timing out on Chromium Linux Debug canaries: fast/js/dfg-osr-entry-hoisted-clobbered-structure-check.html Probable cause: http://trac.webkit.org/changeset/124404 (see http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=fast%2Fjs%2Fdfg-osr-entry-hoisted-clobbered-structure-check.html for the reference). I'm suppressing the failure for now.
...and on SnowLeopard, too.
(In reply to comment #0) > The following layout test is timing out on Chromium Linux Debug canaries: > > fast/js/dfg-osr-entry-hoisted-clobbered-structure-check.html > > Probable cause: http://trac.webkit.org/changeset/124404 > (see http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=fast%2Fjs%2Fdfg-osr-entry-hoisted-clobbered-structure-check.html for the reference). > > I'm suppressing the failure for now. This is a test whose run-time crosses just above the timeout threshold that Chromium sets, but it's within the timeout threshold that other WebKit ports use (30 sec). Suppressing the failure on Chromium but leaving it alone for other platforms is likely to be the right solution here. It would be hard to make the test run faster while still covering the specific case that it's meant to cover.
(In reply to comment #1) > ...and on SnowLeopard, too. SL Chromium or SL something else?
Assigning back to Alexander. Chromium timeouts are not my domain.
I'm not sure about the right resolution. Perhaps we might want to leave it as is.
The test was marked DEBUG SLOW in r124415. Per conversation on IRC and comment 2, it's not really possible to make the test faster. So it doesn't look like there's more to be done here.