Bug 58421 - svg/W3C-SVG-1.1-SE/svgdom-over-01-f.svg has different output on Windows
Summary: svg/W3C-SVG-1.1-SE/svgdom-over-01-f.svg has different output on Windows
Status: RESOLVED DUPLICATE of bug 57334
Alias: None
Product: WebKit
Classification: Unclassified
Component: SVG (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nikolas Zimmermann
URL: http://build.webkit.org/results/Windo...
Keywords:
Depends on: 52543
Blocks:
  Show dependency tree / graph
 
Reported: 2011-04-13 02:21 PDT by Nikolas Zimmermann
Modified: 2011-04-13 06:49 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolas Zimmermann 2011-04-13 02:21:03 PDT 
svg/W3C-SVG-1.1-SE/svgdom-over-01-f.svg has different output on Windows.
From http://build.webkit.org/results/Windows%207%20Release%20(Tests)/r83710%20(11563)/svg/W3C-SVG-1.1-SE/svgdom-over-01-f-pretty-diff.html:
The following statement is missing "Blocked access to external URL http://example.org/image.jpg".

Anyone aware of this win difference?
Comment 1 Nikolas Zimmermann 2011-04-13 02:23:12 PDT 
Skipped test in r83712.
Comment 2 Adam Roben (:aroben) 2011-04-13 06:46:45 PDT 
FYI, we normally check in expected-failure results rather than skip the test in cases like this.

*** This bug has been marked as a duplicate of bug 57334 ***
Comment 3 Adam Roben (:aroben) 2011-04-13 06:49:25 PDT 
(In reply to comment #2)
> FYI, we normally check in expected-failure results rather than skip the test in cases like this.

Specifically, we prefer to check in expected-failure results if:

1) The test fails the same way every time.
2) The test is not timing out or crashing.

http://article.gmane.org/gmane.os.opendarwin.webkit.devel/10017 has some of the thinking behind this.

This is definitely not a universally-applied policy, but I think it's a good one to keep in mind.