Bug 61918
Summary: | [GTK] SVG zoom tests randomly failing because of 16px difference | ||
---|---|---|---|
Product: | WebKit | Reporter: | Mario Sanchez Prada <mario> |
Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | aroben |
Priority: | P2 | Keywords: | Gtk |
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Linux |
Mario Sanchez Prada
The following tests were observed failing randomly in the GTK bots, and whenever they failed, they always did because of an exact difference of 16px rendering:
svg/zoom/page/zoom-svg-through-object-with-absolute-size-2.xhtml
svg/zoom/page/zoom-svg-through-object-with-absolute-size.xhtml
svg/zoom/page/zoom-svg-through-object-with-huge-size.xhtml
svg/zoom/page/zoom-svg-through-object-with-override-size.html
svg/zoom/page/zoom-svg-through-object-with-percentage-size.xhtml
svg/zoom/page/zoom-svg-through-object-with-text.xhtml
See pretty diffs at:
http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r87883%20%2822992%29/svg/zoom/page/zoom-svg-through-object-with-absolute-size-2-pretty-diff.html
http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r87883%20%2822992%29/svg/zoom/page/zoom-svg-through-object-with-absolute-size-pretty-diff.html
http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r87883%20%2822992%29/svg/zoom/page/zoom-svg-through-object-with-huge-size-pretty-diff.html
http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r87883%20%2822992%29/svg/zoom/page/zoom-svg-through-object-with-override-size-pretty-diff.html
http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r87883%20%2822992%29/svg/zoom/page/zoom-svg-through-object-with-percentage-size-pretty-diff.html
http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r87883%20%2822992%29/svg/zoom/page/zoom-svg-through-object-with-text-pretty-diff.html
Skipping in GTK for now...
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Adam Roben (:aroben)
*** This bug has been marked as a duplicate of bug 63186 ***