Assert event timestamp to be monotonic and not from future

Assert event timestamp to be monotonic and not from future.

Add assert in Blink Platform and Core Event type to ensure that timestamp is
never larger than current monotonic clock. This helps catch any cases where we
incorrectly pass wall clock timestamp.

EventSender provides the ability to leap forward the time. In the past we only
advance the event timestamp and left Blink monotonic clock untouched. This is no
longer a viable solution given the added assumption. A better approach is to
advance Blink time. Appropriate plumbing has been added to achieve this.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2

[majidvp, 2016-05-02 23:52:02]

Description was changed from

==========
Assert for timestamp to be monotonic

Add asserts in platform and core Event type for timestamp to help prevent new
regressions to be introduced.

BUG=
==========

to

==========
Assert for event timestamp to be monotonic and not from future.

Add assert in Blink Platform and Core Event type to ensure that timestamp is
never larger than current monotonic clock. This helps catch any cases where we
incorrectly pass wall clock timestamp.

EventSender provides the ability to leap forward the time. In the past we only
advance the event timestamp and left Blink monotonic clock untouched. This is no
longer a viable solution given the added assumption. A better approach is to
advance Blink time. Appropriate plumbing has been added to achieve this.

BUG=
==========

[majidvp, 2016-05-02 23:52:53]

Description was changed from

==========
Assert for event timestamp to be monotonic and not from future.

Add assert in Blink Platform and Core Event type to ensure that timestamp is
never larger than current monotonic clock. This helps catch any cases where we
incorrectly pass wall clock timestamp.

EventSender provides the ability to leap forward the time. In the past we only
advance the event timestamp and left Blink monotonic clock untouched. This is no
longer a viable solution given the added assumption. A better approach is to
advance Blink time. Appropriate plumbing has been added to achieve this.

BUG=
==========

to

==========
Assert event timestamp to be monotonic and not from future.

Add assert in Blink Platform and Core Event type to ensure that timestamp is
never larger than current monotonic clock. This helps catch any cases where we
incorrectly pass wall clock timestamp.

EventSender provides the ability to leap forward the time. In the past we only
advance the event timestamp and left Blink monotonic clock untouched. This is no
longer a viable solution given the added assumption. A better approach is to
advance Blink time. Appropriate plumbing has been added to achieve this.
==========

[majidvp, 2016-05-03 16:24:34]

majidvp@chromium.org changed reviewers:
+ dtapuska@chromium.org

[dtapuska, 2016-05-12 02:02:52]

On 2016/05/03 16:24:35, majidvp wrote:

lgtm % tests passing.

[majidvp, 2016-10-11 13:25:12]

Description was changed from

==========
Assert event timestamp to be monotonic and not from future.

Add assert in Blink Platform and Core Event type to ensure that timestamp is
never larger than current monotonic clock. This helps catch any cases where we
incorrectly pass wall clock timestamp.

EventSender provides the ability to leap forward the time. In the past we only
advance the event timestamp and left Blink monotonic clock untouched. This is no
longer a viable solution given the added assumption. A better approach is to
advance Blink time. Appropriate plumbing has been added to achieve this.
==========

to

==========
Assert event timestamp to be monotonic and not from future.

Add assert in Blink Platform and Core Event type to ensure that timestamp is
never larger than current monotonic clock. This helps catch any cases where we
incorrectly pass wall clock timestamp.

EventSender provides the ability to leap forward the time. In the past we only
advance the event timestamp and left Blink monotonic clock untouched. This is no
longer a viable solution given the added assumption. A better approach is to
advance Blink time. Appropriate plumbing has been added to achieve this.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
==========

[majidvp, 2016-10-11 13:25:19]

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

[commit-bot: I haz the power, 2016-10-11 13:25:32]

Dry run: 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-10-11 13:28:30]

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

[commit-bot: I haz the power, 2016-10-11 13:28:31]

Dry run: Try jobs failed on following builders:
  chromeos_daisy_chromium_compile_only_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_chromeos_compile_dbg_ng on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_layout_tests_slimming_paint_v2 on master.tryserver.chromium.linux
(JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_layout_te...)
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
  mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)