Make rtc::TimestampWrapAroundHandler handle backwards wrapping

Make rtc::TimestampWrapAroundHandler handle backwards wrapping

Also fix a timestamp issue in video analyzer test.

BUG=webrtc:5637, webrtc:5537
Committed: https://crrev.com/1b3530b4df1dc5ef3a6c16b41d86dd910d24c573
Cr-Commit-Position: refs/heads/master@{#11938}

[sprang_webrtc, 2016-03-09 14:49:22]

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

[mflodman, 2016-03-09 15:01:57]

https://codereview.webrtc.org/1779773002/diff/1/webrtc/base/timeutils.cc
File webrtc/base/timeutils.cc (right):

https://codereview.webrtc.org/1779773002/diff/1/webrtc/base/timeutils.cc#newc...
webrtc/base/timeutils.cc:205: return ts + ((num_wrap_ -1) << 32);
Functionality LG, but can this be written in an easy way to still only have one
return for this method?

To have better readability and logic.

[sprang_webrtc, 2016-03-09 15:40:30]

https://codereview.webrtc.org/1779773002/diff/1/webrtc/base/timeutils.cc
File webrtc/base/timeutils.cc (right):

https://codereview.webrtc.org/1779773002/diff/1/webrtc/base/timeutils.cc#newc...
webrtc/base/timeutils.cc:205: return ts + ((num_wrap_ -1) << 32);
On 2016/03/09 15:01:57, mflodman wrote:
> Functionality LG, but can this be written in an easy way to still only have
one
> return for this method?
> 
> To have better readability and logic.

Not without duplicating "last_ts = ts" or adding an ugly temporary for num_wrap
I agree it's a little hard to follow, but the alternatives are pretty messy too.
Otherwise I could rewrite it entirely in a more verbose way.

[mflodman, 2016-03-09 16:29:15]

Thanks for the extra test!

LGTM

[sprang_webrtc, 2016-03-09 16:29:36]

The CQ bit was checked by sprang@webrtc.org

[commit-bot: I haz the power, 2016-03-09 16:29:47]

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

[commit-bot: I haz the power, 2016-03-09 16:53:19]

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

[commit-bot: I haz the power, 2016-03-09 16:53:20]

Try jobs failed on following builders:
  win_baremetal on tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/win_baremetal/builds/9587)

[pbos-webrtc, 2016-03-09 18:43:38]

The CQ bit was checked by pbos@webrtc.org

[commit-bot: I haz the power, 2016-03-09 18:43:42]

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

[commit-bot: I haz the power, 2016-03-09 19:10:39]

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

[commit-bot: I haz the power, 2016-03-09 19:10:40]

Try jobs failed on following builders:
  win_baremetal on tryserver.webrtc (JOB_FAILED,
http://build.chromium.org/p/tryserver.webrtc/builders/win_baremetal/builds/9595)

[sprang_webrtc, 2016-03-10 08:35:17]

The CQ bit was checked by sprang@webrtc.org

[commit-bot: I haz the power, 2016-03-10 08:35:25]

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

[commit-bot: I haz the power, 2016-03-10 09:32:58]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-03-10 09:33:09]

Description was changed from

==========
Make rtc::TimestampWrapAroundHandler handle backwards wrapping

Also fix a timestamp issue in video analyzer test.

BUG=webrtc:5637, webrtc:5537
==========

to

==========
Make rtc::TimestampWrapAroundHandler handle backwards wrapping

Also fix a timestamp issue in video analyzer test.

BUG=webrtc:5637, webrtc:5537

Committed: https://crrev.com/1b3530b4df1dc5ef3a6c16b41d86dd910d24c573
Cr-Commit-Position: refs/heads/master@{#11938}
==========

[commit-bot: I haz the power, 2016-03-10 09:33:10]

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