RESOLVED DUPLICATE of bug 10374487772
svg/dom/viewspec-parser-*.html are slow and text output mismatches
https://bugs.webkit.org/show_bug.cgi?id=87772
Summary svg/dom/viewspec-parser-*.html are slow and text output mismatches
Rafael Weinstein
Reported 2012-05-29 13:20:45 PDT
The original test was broken into five parts by the previous chromium gardener, but each part is now timing out. Are these tests really this slow, or is this a bug?
Attachments
Nikolas Zimmermann
Comment 1 2012-05-29 13:25:31 PDT
These tests was splitted in r87726. Are there still problems after the split? Marcus should know about this.
Rafael Weinstein
Comment 2 2012-05-29 13:30:46 PDT
Yes. All five splits are still timing out.
Rafael Weinstein
Comment 3 2012-05-29 13:53:22 PDT
marked as TIMEOUT in r118829
Ojan Vafai
Comment 4 2012-05-29 13:56:41 PDT
Chromium has a shorter timeout than other WebKit ports (6 seconds on release and 12 on debug). We could mark these tests SLOW in the test_expectations.txt file and that would give them 30/60 seconds respectively. Testing locally, they complete at that point, but fail with a text diff. Looking at http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=svg%2Fdom%2Fviewspec-parser- these tests are slow on all ports. Taking up to 19 seconds on GTK debug and 30 seconds on Lion Release with a high variance. Is there any way we can make these tests faster? More importantly, why are we running fuzzer tests as part of the layout test suite? I realize that the randomization is deterministic, but this still doesn't seem appropriate in principle for layout testing. We run a fuzzer to find problems and then create dedicated reduced test-cases for those.
Simon Fraser (smfr)
Comment 5 2012-09-20 13:33:07 PDT
Ojan Vafai
Comment 6 2012-09-20 14:09:10 PDT
Jussi Kukkonen (jku)
Comment 7 2012-12-03 04:08:12 PST
I missed this bug report, please see bug 103744 for my patch.
Dirk Schulze
Comment 8 2012-12-03 04:17:33 PST
*** This bug has been marked as a duplicate of bug 103744 ***
Note You need to log in before you can comment on or make changes to this bug.