RESOLVED WORKSFORME 75276
[Chromium] REGRESSION(r98596?): fast/repaint/shadow-multiple-horizontal.html, shadow-multiple-strict-horizontal.html, and shadow-multiple-strict-vertical.html are failing
https://bugs.webkit.org/show_bug.cgi?id=75276
Summary [Chromium] REGRESSION(r98596?): fast/repaint/shadow-multiple-horizontal.html,...
Ryosuke Niwa
Reported 2011-12-27 16:00:43 PST
The following 3 tests regressed presumably due to r98596: fast/repaint/shadow-multiple-horizontal.html fast/repaint/shadow-multiple-strict-horizontal.html fast/repaint/shadow-multiple-strict-vertical.html There are multiple vertical lines now.
Attachments
screenshot of 18.0.995 (100.22 KB, image/png)
2012-01-03 08:35 PST, Mike Reed
no flags
actual Webkit Win results from flakiness dashboard (20.80 KB, image/png)
2012-01-03 08:55 PST, epoger
no flags
Mike Reed
Comment 1 2012-01-03 08:32:51 PST
I don't see any vertical lines, running 18.0.995 on win7. Can you attach a screen-shot?
Mike Reed
Comment 2 2012-01-03 08:35:35 PST
Created attachment 120951 [details] screenshot of 18.0.995 here is a screen shot of win7 running 18.0.995. Does it illustrate the bug?
epoger
Comment 3 2012-01-03 08:55:16 PST
Created attachment 120954 [details] actual Webkit Win results from flakiness dashboard My guess is that Ryosuke was looking at the flakiness dashboard and saw results like the one attached here. (Is that right, Ryosuke?) You can see more like this at http://test-results.appspot.com/dashboards/flakiness_dashboard.html#showLargeExpectations=true&showExpectations=true&tests=fast%2Frepaint%2Fshadow
Ryosuke Niwa
Comment 4 2012-01-03 10:59:22 PST
(In reply to comment #3) > Created an attachment (id=120954) [details] > actual Webkit Win results from flakiness dashboard > > My guess is that Ryosuke was looking at the flakiness dashboard and saw results like the one attached here. (Is that right, Ryosuke?) Yes.
Peter Kasting
Comment 5 2013-03-22 11:45:55 PDT
The only test expectations about this now are for Android, and I'm removing those.
Note You need to log in before you can comment on or make changes to this bug.