RESOLVED FIXED 104848
sandboxed iframe attribute parsing layout tests are flaky
https://bugs.webkit.org/show_bug.cgi?id=104848
Summary sandboxed iframe attribute parsing layout tests are flaky
Adam Klein
Reported 2012-12-12 15:01:03 PST
The following layout test is flaky on most Chromium platforms: fast/frames/sandboxed-iframe-attribute-parsing.html fast/frames/sandboxed-iframe-parsing-space-characters.html This does not seem to be a recent occurrence. See: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=fast/frames/sandboxed-iframe-attribute-parsing.html,fast/frames/sandboxed-iframe-parsing-space-characters.html
Attachments
Patch (39.17 KB, patch)
2012-12-27 07:33 PST, Mike West
no flags
Mike West
Comment 1 2012-12-27 06:48:57 PST
I suspect this is the same issue we saw when adding detail to the multi-iframe CSP tests: the iframes load in an indeterminate order, meaning that the console messages are sometimes generated in a different order than expected. We solved it for CSP by chaining the iframe loads; I'd like to not do that here, as it's quite slow. A different option would be to break these test into multiple tests, each with only a single iframe present. That makes things a bit more difficult to maintain, but would be consistent.
Mike West
Comment 2 2012-12-27 07:33:14 PST
Adam Barth
Comment 3 2013-01-02 11:22:38 PST
Comment on attachment 180800 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=180800&action=review Thanks. > LayoutTests/fast/frames/resources/sandboxed-iframe-attribute-test.js:5 > +var frames = 0; /* number of allowed frames that called back */ We usually use C++ style comments, but it doesn't really matter.
WebKit Review Bot
Comment 4 2013-01-02 11:29:11 PST
Comment on attachment 180800 [details] Patch Clearing flags on attachment: 180800 Committed r138625: <http://trac.webkit.org/changeset/138625>
WebKit Review Bot
Comment 5 2013-01-02 11:29:14 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.