RESOLVED FIXED 98729
REGRESSION (r130699): 5 various fast/ tests started failing
https://bugs.webkit.org/show_bug.cgi?id=98729
Summary REGRESSION (r130699): 5 various fast/ tests started failing
Zan Dobersek
Reported 2012-10-09 01:29:55 PDT
Attachments
Patch (3.46 KB, patch)
2012-10-09 12:25 PDT, Martin Robinson
no flags
Patch (3.77 KB, patch)
2012-10-09 15:12 PDT, Martin Robinson
xan.lopez: review+
webkit.review.bot: commit-queue-
Zan Dobersek
Comment 1 2012-10-09 01:40:46 PDT
Narrowing down the offending revision was done through the help of EFL buildbots since the GTK ones were failing at the compilation step. The flakiness dashboard has that data.
Zan Dobersek
Comment 2 2012-10-09 02:06:14 PDT
Also adding svg/custom/object-data-href.html under this bug, though I'm not 100% the failure stems from this commit. The EFL port doesn't seem to fail this test.
Zan Dobersek
Comment 3 2012-10-09 02:10:19 PDT
... and 4 tests timing out as well. These are failing on EFL as well. http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20webkit.org&tests=fast%2Fevents%2Fattribute-listener fast/events/attribute-listener-cloned-from-frameless-doc-context.html fast/events/attribute-listener-cloned-from-frameless-doc-context-2.html fast/events/attribute-listener-extracted-from-frameless-doc-context.html fast/events/attribute-listener-extracted-from-frameless-doc-context-2.html
Raphael Kubo da Costa (:rakuco)
Comment 4 2012-10-09 02:45:23 PDT
I have skipped these tests for the EFL port in <http://trac.webkit.org/changeset/130745>. Perhaps we should roll the commit out later today if there's no fix in sight?
Zan Dobersek
Comment 5 2012-10-09 03:51:19 PDT
(In reply to comment #4) > I have skipped these tests for the EFL port in <http://trac.webkit.org/changeset/130745>. > > Perhaps we should roll the commit out later today if there's no fix in sight? I'd say we should wait for a response from Martin and Kov. They'll make it clear whether they can get to fixing the regressions soon or whether to just rollout this patch (and all the other fixes following it) and fixing it outside of trunk.
Martin Robinson
Comment 6 2012-10-09 08:01:51 PDT
Do you mind skipping the tests for now and I'll try to fix them?
Zan Dobersek
Comment 7 2012-10-09 08:03:18 PDT
(In reply to comment #6) > Do you mind skipping the tests for now and I'll try to fix them? Already done shortly after reporting the bug. Happy fixing.
Martin Robinson
Comment 8 2012-10-09 12:25:09 PDT
Dan Winship
Comment 9 2012-10-09 13:05:12 PDT
Comment on attachment 167816 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=167816&action=review > Source/WebCore/platform/network/soup/ResourceRequestSoup.cpp:129 > + // Data URLs don't have fragment identifiers. That's not true. The data: URLs in those tests are syntactically incorrect. "#" isn't a valid character in the <data> part of a data: URL; they need "%23". (And presumably KURL is broken if the other ports *aren't* failing those tests...) https://bugzilla.mozilla.org/show_bug.cgi?id=308590 suggests several SVG features can't work on SVGs loaded from data: URLs unless you deal with fragments on them correctly.
Martin Robinson
Comment 10 2012-10-09 13:12:50 PDT
(In reply to comment #9) > (From update of attachment 167816 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=167816&action=review > > > Source/WebCore/platform/network/soup/ResourceRequestSoup.cpp:129 > > + // Data URLs don't have fragment identifiers. > > That's not true. The data: URLs in those tests are syntactically incorrect. "#" isn't a valid character in the <data> part of a data: URL; they need "%23". (And presumably KURL is broken if the other ports *aren't* failing those tests...) Other ports do not try to remove the fragment identifier from Data URLs, as far as I know. This is a work-around for soup behavior. See: http://trac.webkit.org/changeset/52305 I can change the comment to: // KURL does not yet properly handle fragment identifiers in Data URLs, so don't even try. > https://bugzilla.mozilla.org/show_bug.cgi?id=308590 suggests several SVG features can't work on SVGs loaded from data: URLs unless you deal with fragments on them correctly.
Martin Robinson
Comment 11 2012-10-09 13:13:36 PDT
(In reply to comment #10) > Other ports do not try to remove the fragment identifier from Data URLs, as far as I know. This is a work-around for soup behavior. See: http://trac.webkit.org/changeset/52305 This would be more accurately stated as "Other ports do not try to remove the fragment identifier from *any* URLs."
Dan Winship
Comment 12 2012-10-09 13:50:23 PDT
ok, bug 68089 says this parsing behavior is intentional. IRC discussion led to the suggestion that ResourceRequestSoup should translate "#" to "%23" in data: URLs, so that it continues to match this behavior regardless of what libsoup does.
Martin Robinson
Comment 13 2012-10-09 15:12:55 PDT
Dan Winship
Comment 14 2012-10-10 05:42:00 PDT
yeah, that looks right to me
Xan Lopez
Comment 15 2012-10-18 11:30:08 PDT
Comment on attachment 167857 [details] Patch OK!
Martin Robinson
Comment 16 2012-10-18 11:36:17 PDT
Thanks for the review!
WebKit Review Bot
Comment 17 2012-10-18 11:39:14 PDT
Comment on attachment 167857 [details] Patch Rejecting attachment 167857 [details] from commit-queue. Failed to run "['/mnt/git/webkit-commit-queue/Tools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '-..." exit_code: 2 Last 500 characters of output: 1 with fuzz 3. patching file Source/WebCore/platform/network/soup/ResourceRequestSoup.cpp patching file LayoutTests/ChangeLog Hunk #1 succeeded at 1 with fuzz 3. patching file LayoutTests/platform/gtk/TestExpectations Hunk #1 FAILED at 1387. 1 out of 1 hunk FAILED -- saving rejects to file LayoutTests/platform/gtk/TestExpectations.rej Failed to run "[u'/mnt/git/webkit-commit-queue/Tools/Scripts/svn-apply', u'--force', u'--reviewer', u'Xan Lopez']" exit_code: 1 cwd: /mnt/git/webkit-commit-queue Full output: http://queues.webkit.org/results/14463081
Martin Robinson
Comment 18 2012-10-19 14:02:30 PDT
Note You need to log in before you can comment on or make changes to this bug.