Created attachment 76854 [details] Patch

I've not actually run this (since I don't have a copy of webkit built), but the cq will build and run the tests for me. This should make it easier to solve bug 51102.

The commit-queue encountered the following flaky tests while processing attachment 76854 [details]: fast/workers/storage/use-same-database-in-page-and-workers.html bug 50995 (author: dumi@chromium.org) java/argument-to-object-type.html bug 51102 (author: ap@webkit.org) The commit-queue is continuing to process your patch.

Comment on attachment 76854 [details] Patch Rejecting attachment 76854 [details] from commit-queue. Failed to run "['./WebKitTools/Scripts/webkit-patch', '--status-host=queues.webkit.org', '--bot-id=abarth-cq-sl', 'build-and-test', '--no-clean', '--no-update', '--test', '--non-interactive']" exit_code: 2 Last 500 characters of output: ......................................................................................................................................................................... inspector ................................................................................. java . java/argument-to-object-type.html -> failed Exiting early after 1 failures. 17897 tests run. 292.72s total testing time 17896 test cases (99%) succeeded 1 test case (<1%) had incorrect layout 8 test cases (<1%) had stderr output Full output: http://queues.webkit.org/results/7290011

The failure can be seen here: https://bugs.webkit.org/attachment.cgi?id=76861 I guess that's why we didn't shouldBeEqualToSTring.

Eric, has this been rolled out?

It was never rolled in. :)

Oh, ok. I was looking at <https://bug-51102-attachments.webkit.org/attachment.cgi?id=76861>, and didn't realize that it was from a failed attempt to commit this change.

Yeah. It's slightly concerning that the queue thought that the failed attempt was a flaky test. Calls our flaky test detection into question. But as far as I know this was never committed. Looks like our flaky test detection code will report a constant failure as a flaky test if another test happens to flake at the same time: http://trac.webkit.org/browser/trunk/WebKitTools/Scripts/webkitpy/tool/bot/commitqueuetask.py#L171 Notice how if first_failing_tests is non-empty, we run the tests again, if a different set of tests fail, we report them all as flaky (which is wrong!). I'll file a separate bug to fix.

Filed bug 51272 about the flaky test detection code being wrong.