Disable browser hit testing tests on Android

Disable browser hit testing tests on Android

Browser process hit testing was enabled on Android in r455559, along
with the appropriate browser tests. Unfortunately on some builders these
tests fail, due to coordinates being off skewed from expectations. The
tests attempt to account for scale factor rounding error on Android that
does not exist on other platforms, due to differently treatment of DSF,
but apparently the variance can be quite high across devices. We need
to investigate a way to work around this in browser tests.

BUG=700007
TBR=creis@chromium.org

Review-Url: https://codereview.chromium.org/2743733002
Cr-Commit-Position: refs/heads/master@{#455766}
Committed: https://chromium.googlesource.com/chromium/src/+/6bc574cbc64fb6b9b29ac1bc8ea71e19ff327c41

[kenrb, 2017-03-09 15:57:39]

Description was changed from

==========
Disable browser hit testing tests on Android

Browser process hit testing was enabled on Android in r455559, along
with the appropriate browser tests. Unfortunately on some builders these
tests fail, due to coordinates being off skewed from expectations. The
tests attempt to account for scale factor rounding error on Android that
does not exist on other platforms, due to differently treatment of DSF,
but apparently the variance can be quite high across devices. We need
to investigate a way to work around this in browser tests.

BUG=700007
TBR=creis@chromium.org
==========

to

==========
Disable browser hit testing tests on Android

Browser process hit testing was enabled on Android in r455559, along
with the appropriate browser tests. Unfortunately on some builders these
tests fail, due to coordinates being off skewed from expectations. The
tests attempt to account for scale factor rounding error on Android that
does not exist on other platforms, due to differently treatment of DSF,
but apparently the variance can be quite high across devices. We need
to investigate a way to work around this in browser tests.

BUG=700007
TBR=creis@chromium.org
==========

[kenrb, 2017-03-09 15:57:54]

The CQ bit was checked by kenrb@chromium.org

[commit-bot: I haz the power, 2017-03-09 15:58:28]

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, 2017-03-09 16:40:00]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1489075074631650, "parent_rev":
"32a58c7e9cf5f455eb07420587efec657b1409ba", "commit_rev":
"6bc574cbc64fb6b9b29ac1bc8ea71e19ff327c41"}

[commit-bot: I haz the power, 2017-03-09 16:41:48]

Description was changed from

==========
Disable browser hit testing tests on Android

Browser process hit testing was enabled on Android in r455559, along
with the appropriate browser tests. Unfortunately on some builders these
tests fail, due to coordinates being off skewed from expectations. The
tests attempt to account for scale factor rounding error on Android that
does not exist on other platforms, due to differently treatment of DSF,
but apparently the variance can be quite high across devices. We need
to investigate a way to work around this in browser tests.

BUG=700007
TBR=creis@chromium.org
==========

to

==========
Disable browser hit testing tests on Android

Browser process hit testing was enabled on Android in r455559, along
with the appropriate browser tests. Unfortunately on some builders these
tests fail, due to coordinates being off skewed from expectations. The
tests attempt to account for scale factor rounding error on Android that
does not exist on other platforms, due to differently treatment of DSF,
but apparently the variance can be quite high across devices. We need
to investigate a way to work around this in browser tests.

BUG=700007
TBR=creis@chromium.org

Review-Url: https://codereview.chromium.org/2743733002
Cr-Commit-Position: refs/heads/master@{#455766}
Committed:
https://chromium.googlesource.com/chromium/src/+/6bc574cbc64fb6b9b29ac1bc8ea7...
==========

[commit-bot: I haz the power, 2017-03-09 16:41:50]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/6bc574cbc64fb6b9b29ac1bc8ea7...

[Charlie Reis, 2017-03-09 17:05:20]

LGTM, assuming this doesn't mean we have similar problems for real users.  (If
so, let's file a bug.)