Bug 104023

Summary: fast/dom/HTMLTemplateElement/inertContents.html is flaky
Product: WebKit Reporter: Emil A Eklund <eae>
Component: Tools / TestsAssignee: Adam Klein <adamk>
Status: RESOLVED FIXED    
Severity: Normal CC: adamk, dglazkov, eric, rafaelw, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
URL: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=fast%2Fdom%2FHTMLTemplateElement%2FinertContents.html
Bug Depends on:    
Bug Blocks: 103547    
Attachments:
Description Flags
Patch none

Emil A Eklund
Reported 2012-12-04 11:36:28 PST
Flaky on mac debug since r136472 or earlier
Attachments
Patch (4.79 KB, patch)
2012-12-14 13:24 PST, Adam Klein
no flags
Adam Klein
Comment 1 2012-12-07 13:43:58 PST
FYI, just happened to find this bug by searching. When gardening please CC _someone_ even if there's not an obvious culprit (say, the author of the flaky test). For this test in particular, it was a new test added in r136467. Assigning appropriately.
Adam Klein
Comment 2 2012-12-07 15:13:40 PST
I'm guessing that this test is flaky due to the preload scanner, but I haven't verified that.
Adam Klein
Comment 3 2012-12-14 13:24:35 PST
Eric Seidel (no email)
Comment 4 2012-12-14 13:33:50 PST
Comment on attachment 179526 [details] Patch Can you just listen to the onload to get your desired image testing?
Adam Klein
Comment 5 2012-12-14 13:55:43 PST
(In reply to comment #4) > (From update of attachment 179526 [details]) > Can you just listen to the onload to get your desired image testing? Rather than using dumpResourceLoadCallbacks? I hope so. But that will still be flaky until we stop the preload scanner from processing <img>s inside <template>s.
WebKit Review Bot
Comment 6 2012-12-14 14:12:20 PST
Comment on attachment 179526 [details] Patch Clearing flags on attachment: 179526 Committed r137769: <http://trac.webkit.org/changeset/137769>
WebKit Review Bot
Comment 7 2012-12-14 14:12:24 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.