LayoutTests/media/event-queue-crash.html produces a console message that, due to a race condition apparently caused by asynchronously loading a video resource, appears after testRunner.notifyDone() has been called and hence may appear in the output of the next test. See flakiness dashboard for media/fallback.html: http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=media%2Ffallback.html Here's an excerpt from http://build.chromium.org/p/chromium.webkit/builders/Webkit%20Mac10.6/builds/23776/steps/webkit_tests/logs/stdio 07:27:30.225 1138 worker/2 media/event-queue-crash.html passed 07:27:30.229 1136 worker/1 media/W3C/video/src/src_removal_does_not_trigger_loadstart.html passed 07:27:30.232 1135 worker/0 ietestcenter/Javascript/15.4.4.21-8-c-3.html passed 07:27:30.248 1116 [19314/25469] fallback.html failed unexpectedly (text diff) 07:27:30.244 1138 worker/2 media/fallback.html failed I've tried to see whether the event-queue-crash.html actually crashes when reverting http://trac.webkit.org/changeset/124843, but couldn't reproduce the crash. So I'm going to skip in on chromium for the time being so as to reduce flakiness.
(In reply to comment #0) > LayoutTests/media/event-queue-crash.html produces a console message that, due to a race condition apparently caused by asynchronously loading a video resource, appears after testRunner.notifyDone() has been called and hence may appear in the output of the next test. It sounds like this is caused by a bug in the testing infrastructure, not by any one test.