summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authordglazkov@chromium.org <dglazkov@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-12 19:02:54 +0000
committerdglazkov@chromium.org <dglazkov@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-01-12 19:02:54 +0000
commited86a70901c4a9082fc0b29e8c4665487e094575 (patch)
tree9092a3613c3194a23bc49f233632f097ad739586
parent1225c9cdd78365e114fb2b063161494dfdab7575 (diff)
downloadchromium_src-ed86a70901c4a9082fc0b29e8c4665487e094575.zip
chromium_src-ed86a70901c4a9082fc0b29e8c4665487e094575.tar.gz
chromium_src-ed86a70901c4a9082fc0b29e8c4665487e094575.tar.bz2
Consolidate mask-related failures under one bug
TBR=gdk TEST=none BUG=3244 Review URL: http://codereview.chromium.org/542033 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@36026 0039d316-1c4b-4281-b951-d872f2087c98
-rw-r--r--webkit/tools/layout_tests/test_expectations.txt26
1 files changed, 12 insertions, 14 deletions
diff --git a/webkit/tools/layout_tests/test_expectations.txt b/webkit/tools/layout_tests/test_expectations.txt
index 31e3070..88297994 100644
--- a/webkit/tools/layout_tests/test_expectations.txt
+++ b/webkit/tools/layout_tests/test_expectations.txt
@@ -981,15 +981,6 @@ BUG10296 LINUX : LayoutTests/svg/W3C-SVG-1.1/pservers-grad-14-b.svg = FAIL
// No anti-aliasing on the text.
BUG10298 LINUX : LayoutTests/svg/custom/use-on-disallowed-foreign-object-3.svg = FAIL
-// Marking this again as failed. This test failed even after rebaseline due to
-// the fact that the font is not specified in the test and it seems that the
-// test falls back on a different font locally than on the buildbot so the
-// baseline is invalid. This might indicate a failure in our font fallback code
-// or might be expected and that we should either go with the buildbot output
-// or change the test upstream to specify explicitly what font to use.
-// The mask part of this test is totally wrong.
-BUG3244 LINUX WIN : LayoutTests/fast/backgrounds/svg-as-background-6.html = FAIL
-
// The failures listed below have never passed in Chromium and need to be
// investigated, categorized, and (one hopes) fixed.
@@ -1052,6 +1043,18 @@ BUG3244 LINUX WIN : LayoutTests/fast/backgrounds/svg-as-mask.html = FAIL
BUG3244 WIN DEBUG : LayoutTests/fast/backgrounds/animated-svg-as-mask.html = FAIL
BUG3244 SLOW WIN RELEASE : LayoutTests/fast/backgrounds/animated-svg-as-mask.html = FAIL
BUG3244 LINUX : LayoutTests/fast/backgrounds/animated-svg-as-mask.html = FAIL
+// More tests that fail because of masks not working properly.
+// New tests. We should fix these, but they don't need to block the current release
+BUG3244 WIN LINUX : LayoutTests/fast/backgrounds/mask-composite.html = FAIL
+BUG3244 WIN LINUX : LayoutTests/fast/backgrounds/repeat/mask-negative-offset-repeat.html = FAIL
+// Marking this again as failed. This test failed even after rebaseline due to
+// the fact that the font is not specified in the test and it seems that the
+// test falls back on a different font locally than on the buildbot so the
+// baseline is invalid. This might indicate a failure in our font fallback code
+// or might be expected and that we should either go with the buildbot output
+// or change the test upstream to specify explicitly what font to use.
+// The mask part of this test is totally wrong.
+BUG3244 LINUX WIN : LayoutTests/fast/backgrounds/svg-as-background-6.html = FAIL
BUG10302 LINUX : LayoutTests/svg/W3C-SVG-1.1/pservers-grad-10-b.svg = FAIL
@@ -1168,11 +1171,6 @@ BUG22700 LINUX WIN : LayoutTests/fast/canvas/canvas-getImageData.html = FAIL
// and gif, which is a low priority.
BUG10318 WIN LINUX : LayoutTests/fast/canvas/toDataURL-supportedTypes.html = FAIL
-// More tests that fail because of masks not working properly.
-// New tests. We should fix these, but they don't need to block the current release
-BUG10319 WIN LINUX : LayoutTests/fast/backgrounds/mask-composite.html = FAIL
-BUG10319 WIN LINUX : LayoutTests/fast/backgrounds/repeat/mask-negative-offset-repeat.html = FAIL
-
// This test finishes while in the middle of a CSS animation. This is
// intentional, but it makes pixel results unreliable.
// http://bugs.webkit.org/show_bug.cgi?id=21491