Don't use LOG_END timestamp to compute RtcEventLog duration.

Don't use LOG_END timestamp to compute RtcEventLog duration.

The LOG_END time is incorrect if the event log is stopped
by the file size limit instead of a duration limit or a
manual stop. This makes the call appear to be very long
(10^13 seconds) in the analysis tool. This CL is a workaround
for that problem.

BUG=webrtc:6138
Committed: https://crrev.com/88c1d2bc0f8468f04cb05a536c5194f9bb9d0e50
Cr-Commit-Position: refs/heads/master@{#13585}

[terelius, 2016-07-22 14:16:00]

terelius@webrtc.org changed reviewers:
+ ivoc@webrtc.org, stefan@webrtc.org

[ivoc, 2016-07-27 09:18:47]

LGTM.

[terelius, 2016-07-29 15:34:33]

ping

[stefan-webrtc, 2016-08-01 11:04:43]

lgtm

[terelius, 2016-08-01 11:39:59]

The CQ bit was checked by terelius@webrtc.org

[commit-bot: I haz the power, 2016-08-01 11:40:07]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.webrtc.org/...

[commit-bot: I haz the power, 2016-08-01 12:20:36]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-08-01 12:20:47]

Description was changed from

==========
Don't use LOG_END timestamp to compute RtcEventLog duration.

The LOG_END time is incorrect if the event log is stopped
by the file size limit instead of a duration limit or a
manual stop. This makes the call appear to be very long
(10^13 seconds) in the analysis tool. This CL is a workaround
for that problem.

BUG=webrtc:6138
==========

to

==========
Don't use LOG_END timestamp to compute RtcEventLog duration.

The LOG_END time is incorrect if the event log is stopped
by the file size limit instead of a duration limit or a
manual stop. This makes the call appear to be very long
(10^13 seconds) in the analysis tool. This CL is a workaround
for that problem.

BUG=webrtc:6138

Committed: https://crrev.com/88c1d2bc0f8468f04cb05a536c5194f9bb9d0e50
Cr-Commit-Position: refs/heads/master@{#13585}
==========

[commit-bot: I haz the power, 2016-08-01 12:20:48]

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