112598 2013-03-18 11:07:14 -0700 [chromium] http/tests/security/mixedContent/insecure-audio-video-in-main-frame.html is flaky because of console output 2013-04-08 16:54:00 -0700 1 1 1 Unclassified WebKit Tools / Tests 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 1 kbr mkwst abarth japhet mkwst schenney tsepez oldest_to_newest 857326 0 kbr 2013-03-18 11:07:14 -0700 The test http/tests/security/mixedContent/insecure-audio-video-in-main-frame.html is flaky on all platforms because occasionally the console output attributes the error message to a line number. See http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20chromium.org&showExpectations=true&tests=http%2Ftests%2Fsecurity%2FmixedContent%2Finsecure-audio-video-in-main-frame.html . Marking this test as flaky. 859288 1 mkwst 2013-03-20 05:57:19 -0700 (In reply to comment #0) > The test http/tests/security/mixedContent/insecure-audio-video-in-main-frame.html is flaky on all platforms because occasionally the console output attributes the error message to a line number. See http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20chromium.org&showExpectations=true&tests=http%2Ftests%2Fsecurity%2FmixedContent%2Finsecure-audio-video-in-main-frame.html . > > Marking this test as flaky. For some reason, "document->parsing()" is periodically returning true when the onload event is triggered. This causes PageConsole::addMessage to check whether the scriptableDocumentParser isWaitingForScripts or isExecutingScripts. Neither is true, so we grab the line number, believing it to be a message tied to something in parsing. I'll dig a bit deeper. 859330 2 mkwst 2013-03-20 06:25:03 -0700 (In reply to comment #1) > (In reply to comment #0) > > The test http/tests/security/mixedContent/insecure-audio-video-in-main-frame.html is flaky on all platforms because occasionally the console output attributes the error message to a line number. See http://test-results.appspot.com/dashboards/flakiness_dashboard.html#group=%40ToT%20-%20chromium.org&showExpectations=true&tests=http%2Ftests%2Fsecurity%2FmixedContent%2Finsecure-audio-video-in-main-frame.html . > > > > Marking this test as flaky. > > For some reason, "document->parsing()" is periodically returning true when the onload event is triggered. This causes PageConsole::addMessage to check whether the scriptableDocumentParser isWaitingForScripts or isExecutingScripts. Neither is true, so we grab the line number, believing it to be a message tied to something in parsing. > > I'll dig a bit deeper. I think this is happening because we defer loading of media sources via 'HTMLMediaElement::scheduleDelayedAction(LoadMediaResource)'. This means that the mixed content and CSP checks (among others) will happen at some indeterminate point; perhaps before the onload event, perhaps after. This is different from what we do for images, for instance: those checks happen synchronously (via ImageLoader::updateFromElement()), which makes it possible to pull a line number directly from the parser. I'll have to think a bit about how to address this. Nothing brilliant is coming to mind. :/ 859527 3 kbr 2013-03-20 10:15:28 -0700 Thanks for investigating. Maybe it's necessary to live with the flakiness. Your call. Assigning to you.