Bug 191047
| Summary: | REGRESSION (r237479-237484): [ MacOS ] Layout Test svg/animations/svglength-element-removed-crash.svg is failing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Truitt Savell <tsavell> |
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | fpizlo, jlewis3, lforschler, ryanhaddad, sabouhallawa, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=173178 | ||
Truitt Savell
The following layout test is failing on Mojave and High Sierra
svg/animations/svglength-element-removed-crash.svg
Probable cause:
Problem is a recent regression. I was able to reproduce it with:
run-webkit-tests --root testbuild-237484 svg/animations/svglength-element-removed-crash.svg --iterations 500 -f
due to several revisions being built together this left me with a range of possible revisions between r237479-237484.
Flakiness Dashboard:
https://webkit-test-results.webkit.org/dashboards/flakiness_dashboard.html#showAllRuns=true&tests=svg%2Fanimations%2Fsvglength-element-removed-crash.svg
Diff:
--- /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/svg/animations/svglength-element-removed-crash-expected.txt
+++ /Volumes/Data/slave/mojave-release-tests-wk2/build/layout-test-results/svg/animations/svglength-element-removed-crash-actual.txt
@@ -1 +1 @@
-PASS x = 10
+FAIL: -150 extra live node(s) x = 10
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/45653754>
Matt Lewis
This test was already marked as skip at one point due to being a frequent flake in:
https://bugs.webkit.org/show_bug.cgi?id=173178
While the diffs are different, they seem to be very similar.
Said Abou-Hallawa
This should be fixed by removing the SVG tear-off object. https://bugs.webkit.org/show_bug.cgi?id=191237
*** This bug has been marked as a duplicate of bug 191237 ***