Bug 59166

Summary: new svg tests timing out in chromium win/linux debug builds
Product: WebKit Reporter: Dirk Pranke <dpranke>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WONTFIX    
Severity: Normal CC: jamesr, kbr, krit, reed
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   

Dirk Pranke
Reported 2011-04-21 19:26:13 PDT
The new svg tests introduced in http://trac.webkit.org/browser/?rev=84522 appear to be timing out in chromium win/linux debug: Regressions: Unexpected tests timed out : (13) svg/dynamic-updates/SVGFEDropShadowElement-dom-dx-attr.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-dom-dy-attr.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-dom-in-attr.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-dom-shadow-color-attr.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-dom-shadow-opacity-attr.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-dom-stdDeviation-attr.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-svgdom-dx-prop.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-svgdom-dy-prop.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-svgdom-in-prop.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-svgdom-shadow-color-prop.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-svgdom-shadow-opacity-prop.html = TIMEOUT svg/dynamic-updates/SVGFEDropShadowElement-svgdom-stdDeviation-prop.html = TIMEOUT svg/filters/feDropShadow.svg = TIMEOUT
Attachments
Dirk Schulze
Comment 1 2011-04-21 22:08:01 PDT
Are there any further animation? I wonder that svg/filters/feDropShadow.svg timeouts as well. Can't debug Chromium here :-(
Dirk Schulze
Comment 2 2011-04-21 22:29:21 PDT
(In reply to comment #1) > Are there any further animation? I wonder that svg/filters/feDropShadow.svg timeouts as well. Can't debug Chromium here :-( s/animation/information/ :-P
Stephen Chenney
Comment 3 2013-04-09 16:10:45 PDT
LayoutTest failures for Chromium are being marked WontFix. The Bug is still accessible and referenced from TestExpectations.
Note You need to log in before you can comment on or make changes to this bug.