Bug 229743
Summary: | [ iOS Release ] svg/W3C-SVG-1.1/struct-dom-06-b.svg is flaky text failing | ||
---|---|---|---|
Product: | WebKit | Reporter: | ayumi_kojima |
Component: | SVG | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | bfulgham, sabouhallawa, webkit-bot-watchers-bugzilla, webkit-bug-importer, zimmermann |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | iPhone / iPad | ||
OS: | Unspecified |
ayumi_kojima
svg/W3C-SVG-1.1/struct-dom-06-b.svg
Is a flaky text failure on iOS-14-Simulator-WK2-Tests-EWS.
The failure is showing up in the open source directory: https://results.webkit.org/?suite=layout-tests&test=svg/W3C-SVG-1.1/struct-dom-06-b.svg
Diff:
--- /Volumes/Data/worker/iOS-14-Simulator-WK2-Tests-EWS/build/layout-test-results/svg/W3C-SVG-1.1/struct-dom-06-b-expected.txt
+++ /Volumes/Data/worker/iOS-14-Simulator-WK2-Tests-EWS/build/layout-test-results/svg/W3C-SVG-1.1/struct-dom-06-b-actual.txt
@@ -3,7 +3,7 @@
layer at (0,0) size 480x360
RenderSVGRoot {svg} at (0,0) size 480x360
RenderSVGContainer {g} at (50,185) size 149x19
- RenderSVGRect {rect} at (0,0) size 0x0 [fill={[type=SOLID] [color=#FF0000]}] [x=0.00] [y=0.00] [width=0.00] [height=0.00]
+ RenderSVGRect {rect} at (0,0) size 450x360 [fill={[type=SOLID] [color=#FF0000]}] [x=0.00] [y=0.00] [width=0.00] [height=0.00]
RenderSVGText {text} at (50,185) size 149x19 contains 1 chunk(s)
RenderSVGInlineText {#text} at (0,0) size 149x18
chunk 1 text run 1 at (50.00,200.00) startOffset 0 endOffset 20 width 148.89: "DOM API is supported"
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/82601796>
ayumi_kojima
Marked test expectation: https://trac.webkit.org/changeset/281833/webkit
ayumi_kojima
I was not able to reproduce the failure locally using: run-webkit-tests --iterations 500 --exit-after-n-failures 1 --ios-simulator --force svg/W3C-SVG-1.1/struct-dom-06-b.svg
ayumi_kojima
Though, I was not able to reproduce the failure, it seems to have started recently with the first one at r281701 according to the history.
Brent Fulgham
Robert Jenner confirmed this is no longer an issue (5/3/2022).