RESOLVED WONTFIX 81803
Layout Tests in platform/chromium/compositing/rubberbanding/ are flaky
https://bugs.webkit.org/show_bug.cgi?id=81803
Summary Layout Tests in platform/chromium/compositing/rubberbanding/ are flaky
Emil A Eklund
Reported 2012-03-21 10:46:22 PDT
The following layout tests are intermittently failing on mac platform/chromium/compositing/rubberbanding/transform-overhang-e.html platform/chromium/compositing/rubberbanding/transform-overhang-n.html platform/chromium/compositing/rubberbanding/transform-overhang-ne.html platform/chromium/compositing/rubberbanding/transform-overhang-nw.html platform/chromium/compositing/rubberbanding/transform-overhang-s.html platform/chromium/compositing/rubberbanding/transform-overhang-se.html platform/chromium/compositing/rubberbanding/transform-overhang-size-change.html platform/chromium/compositing/rubberbanding/transform-overhang-sw.html platform/chromium/compositing/rubberbanding/transform-overhang-w.html Probable cause: Unknown
Attachments
asvitkine
Comment 1 2012-12-19 14:05:28 PST
Sigh. It would be nice if you would cc a test's author when disabling tests - instead of me having to find out when I randomly notice the lines in the text expectations file or worse yet, when the feature gets broken because it's no longer being tested. Are there any links to the failures?
Emil A Eklund
Comment 2 2012-12-19 14:15:33 PST
(In reply to comment #1) > Sigh. It would be nice if you would cc a test's author when disabling tests - instead of me having to find out when I randomly notice the lines in the text expectations file or worse yet, when the feature gets broken because it's no longer being tested. Sorry about that, was a particularly bad day :( > Are there any links to the failures? Yeah, the url associated with the bug (shown above the keywords field above) has a link to the dashboard that shows that they still fail about one in ten runs.
Takashi Toyoshima
Comment 3 2013-02-19 02:20:15 PST
*** Bug 110182 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.