Disable flaky test OmniboxViewViewsTest.SelectionClipboard

Disable flaky test OmniboxViewViewsTest.SelectionClipboard

TBR=msw@chromium.org
BUG=676746
Committed: https://crrev.com/dea296de1bb5b61515994926d3ece3165274ffc2
Cr-Commit-Position: refs/heads/master@{#440586}

[Dan Beam, 2016-12-23 02:11:06]

The CQ bit was checked by dbeam@chromium.org

[commit-bot: I haz the power, 2016-12-23 02:11:19]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-23 02:46:51]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1482459066200480, "parent_rev":
"fa29d085d6467b78a4f3cc9d93500d72b3fd17a5", "commit_rev":
"2eea20f6b70b40c4489f0c8dc4aced33aa757fd0"}

[commit-bot: I haz the power, 2016-12-23 02:47:22]

Description was changed from

==========
Disable flaky test OmniboxViewViewsTest.SelectionClipboard

TBR=msw@chromium.org
BUG=676746
==========

to

==========
Disable flaky test OmniboxViewViewsTest.SelectionClipboard

TBR=msw@chromium.org
BUG=676746

Review-Url: https://codereview.chromium.org/2597403002
==========

[commit-bot: I haz the power, 2016-12-23 02:47:22]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-23 02:49:23]

Description was changed from

==========
Disable flaky test OmniboxViewViewsTest.SelectionClipboard

TBR=msw@chromium.org
BUG=676746

Review-Url: https://codereview.chromium.org/2597403002
==========

to

==========
Disable flaky test OmniboxViewViewsTest.SelectionClipboard

TBR=msw@chromium.org
BUG=676746

Committed: https://crrev.com/dea296de1bb5b61515994926d3ece3165274ffc2
Cr-Commit-Position: refs/heads/master@{#440586}
==========

[commit-bot: I haz the power, 2016-12-23 02:49:24]

Patchset 1 (id:??) landed as
https://crrev.com/dea296de1bb5b61515994926d3ece3165274ffc2
Cr-Commit-Position: refs/heads/master@{#440586}

[msw, 2016-12-23 04:06:54]

It seems this just started flaking today; is there any consistency in the
failure logs? Have you found any recent changes that might have introduced
flakiness here? In general, clipboard tests should be okay as
interactive_ui_tests.

[Dan Beam, 2016-12-26 00:44:29]

On 2016/12/23 04:06:54, msw wrote:
> It seems this just started flaking today; is there any consistency in the
> failure logs? Have you found any recent changes that might have introduced
> flakiness here? In general, clipboard tests should be okay as
> interactive_ui_tests.

i looked briefly at the logs but didn't see a smoking gun.  I mainly saw that it
was blocking CQs and that the bug filed by some sheriff bot said to revert it in
like 30m (and it has been flaking for 10-20m)