Disable UserInputTracker DCHECK which is firing in unit tests.

Disable UserInputTracker DCHECK which is firing in unit tests.

UserInputTracker::OnInputEvent has a DCHECK to make sure that any
WebInputEvent received has a timeStampSeconds that isn't in the future.
The dcheck only fires in cases where we have a high resolution clock,
as high resolution clocks are guaranteed to be system-wide monotonic
across all processes (whereas the windows non-high res monotonic clock
can skew between processes).

This dcheck recently started firing in unit tests. For now, we just
disable the dcheck since the broken tests is causing issues for
other devs, but the real fix is to figure out why the input events have
timestamps in the future and fix that.

BUG=678093
Review-Url: https://codereview.chromium.org/2611943004
Cr-Commit-Position: refs/heads/master@{#441664}
Committed: https://chromium.googlesource.com/chromium/src/+/ec1a7d3712848ad33ca4adf21950877624d44ee0

[Bryan McQuade, 2017-01-05 15:10:53]

The CQ bit was checked by bmcquade@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-01-05 15:10:59]

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

[Bryan McQuade, 2017-01-05 15:15:19]

bmcquade@chromium.org changed reviewers:
+ csharrison@chromium.org

[Bryan McQuade, 2017-01-05 15:15:51]

PTAL. The commit queue is apparently borked until this lands, so we need to
disable the dcheck and then dig into figuring out why we receive events with
timestamps in the future.

[Charlie Harrison, 2017-01-05 15:22:24]

lgtm

[commit-bot: I haz the power, 2017-01-05 15:51:12]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-01-05 15:51:13]

Dry run: This issue passed the CQ dry run.

[Bryan McQuade, 2017-01-05 16:00:00]

The CQ bit was checked by bmcquade@chromium.org

[commit-bot: I haz the power, 2017-01-05 16:00: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, 2017-01-05 16:05:32]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1483632000835510, "parent_rev":
"cff22de0743ef3de687e55c376b9733a0ff560a7", "commit_rev":
"ec1a7d3712848ad33ca4adf21950877624d44ee0"}

[commit-bot: I haz the power, 2017-01-05 16:06:03]

Description was changed from

==========
Disable UserInputTracker DCHECK which is firing in unit tests.

UserInputTracker::OnInputEvent has a DCHECK to make sure that any
WebInputEvent received has a timeStampSeconds that isn't in the future.
The dcheck only fires in cases where we have a high resolution clock,
as high resolution clocks are guaranteed to be system-wide monotonic
across all processes (whereas the windows non-high res monotonic clock
can skew between processes).

This dcheck recently started firing in unit tests. For now, we just
disable the dcheck since the broken tests is causing issues for
other devs, but the real fix is to figure out why the input events have
timestamps in the future and fix that.

BUG=678093
==========

to

==========
Disable UserInputTracker DCHECK which is firing in unit tests.

UserInputTracker::OnInputEvent has a DCHECK to make sure that any
WebInputEvent received has a timeStampSeconds that isn't in the future.
The dcheck only fires in cases where we have a high resolution clock,
as high resolution clocks are guaranteed to be system-wide monotonic
across all processes (whereas the windows non-high res monotonic clock
can skew between processes).

This dcheck recently started firing in unit tests. For now, we just
disable the dcheck since the broken tests is causing issues for
other devs, but the real fix is to figure out why the input events have
timestamps in the future and fix that.

BUG=678093

Review-Url: https://codereview.chromium.org/2611943004
Cr-Commit-Position: refs/heads/master@{#441664}
Committed:
https://chromium.googlesource.com/chromium/src/+/ec1a7d3712848ad33ca4adf21950...
==========

[commit-bot: I haz the power, 2017-01-05 16:06:03]

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