Remove non-monotonic clock support

Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) for timed waits, but that should be less of an issue than actual
timestamps.

BUG=webrtc:5452
Committed: https://crrev.com/e791ffd63873739b47a2633531f4ac2f12e6951d
Cr-Commit-Position: refs/heads/master@{#11375}

[sprang_webrtc, 2016-01-21 15:43:58]

Description was changed from

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

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

to

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) but that should be less of an issue than actual timestamps.

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

[sprang_webrtc, 2016-01-21 15:43:58]

sprang@webrtc.org changed reviewers:
+ pbos@webrtc.org

[sprang_webrtc, 2016-01-21 15:44:35]

Description was changed from

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) but that should be less of an issue than actual timestamps.

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

to

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) for timed waits, but that should be less of an issue than actual
timestamps.

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

[pbos-webrtc, 2016-01-21 15:49:50]

pbos@webrtc.org changed reviewers:
+ tommi@webrtc.org

[pbos-webrtc, 2016-01-21 15:49:50]

+R tommi@, since this is a big across-the-everything change, do you have any
concerns?

[tommi, 2016-01-21 16:05:32]

is there a bug with some more information?  I can rs the change but I don't
understand well enough what sort of impact it will have or what specifically the
change fixes.

[sprang_webrtc, 2016-01-21 16:19:35]

Description was changed from

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) for timed waits, but that should be less of an issue than actual
timestamps.

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

to

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) for timed waits, but that should be less of an issue than actual
timestamps.

BUG=webrtc:5452
==========

[sprang_webrtc, 2016-01-25 18:59:52]

There is indeed a bug linked, as discussed offline as well.
Should be in a good state now.

[tommi, 2016-01-25 19:20:49]

lgtm % remove the below log

https://codereview.webrtc.org/1613013002/diff/140001/webrtc/video/video_captu...
File webrtc/video/video_capture_input.cc (right):

https://codereview.webrtc.org/1613013002/diff/140001/webrtc/video/video_captu...
webrtc/video/video_capture_input.cc:53: LOG(LS_WARNING) <<
"delta_ntp_internal_ms_ = " << delta_ntp_internal_ms_;
remove?

[sprang_webrtc, 2016-01-25 19:34:18]

https://codereview.webrtc.org/1613013002/diff/140001/webrtc/video/video_captu...
File webrtc/video/video_capture_input.cc (right):

https://codereview.webrtc.org/1613013002/diff/140001/webrtc/video/video_captu...
webrtc/video/video_capture_input.cc:53: LOG(LS_WARNING) <<
"delta_ntp_internal_ms_ = " << delta_ntp_internal_ms_;
On 2016/01/25 19:20:49, tommi-webrtc wrote:
> remove?

Oops! Right-o..

[sprang_webrtc, 2016-01-25 19:34:27]

The CQ bit was checked by sprang@webrtc.org to run a CQ dry run

[commit-bot: I haz the power, 2016-01-25 19:34:32]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1613013002/160001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1613013002/160001

[commit-bot: I haz the power, 2016-01-25 20:57:17]

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

[commit-bot: I haz the power, 2016-01-25 20:57:17]

Dry run: This issue passed the CQ dry run.

[sprang, 2016-01-26 09:51:35]

The CQ bit was checked by sprang@google.com

[sprang, 2016-01-26 09:51:35]

The patchset sent to the CQ was uploaded after l-g-t-m from tommi@webrtc.org
Link to the patchset: https://codereview.webrtc.org/1613013002/#ps160001 (title:
"Cleanup")

[commit-bot: I haz the power, 2016-01-26 09:51:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1613013002/160001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1613013002/160001

[commit-bot: I haz the power, 2016-01-26 09:53:22]

Description was changed from

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) for timed waits, but that should be less of an issue than actual
timestamps.

BUG=webrtc:5452
==========

to

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) for timed waits, but that should be less of an issue than actual
timestamps.

BUG=webrtc:5452
==========

[commit-bot: I haz the power, 2016-01-26 09:53:23]

Committed patchset #9 (id:160001)

[commit-bot: I haz the power, 2016-01-26 09:53:33]

Description was changed from

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) for timed waits, but that should be less of an issue than actual
timestamps.

BUG=webrtc:5452
==========

to

==========
Remove non-monotonic clock support

Real time clock may cause problems as they can move (even backwards) if
the clock is changed, eg updated by NTP.

Non-monotonic clocks still in use on some platform (I'm looking at you,
Apple) for timed waits, but that should be less of an issue than actual
timestamps.

BUG=webrtc:5452

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

[commit-bot: I haz the power, 2016-01-26 09:53:34]

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