commit 88c1d2bc0f8468f04cb05a536c5194f9bb9d0e50
author terelius <terelius@webrtc.org> Mon Aug 01 05:20:33 2016 -0700
committer Commit bot <commit-bot@chromium.org> Mon Aug 01 12:20:39 2016 +0000
tree 6e20dc309f664bb0e5a6b60cd9c53d475fe80c9a
parent 1a518fc4e3a185329770e9ac8f3654c7068e38ec

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

Review-Url: https://codereview.webrtc.org/2176663002
Cr-Commit-Position: refs/heads/master@{#13585}

webrtc/tools/event_log_visualizer/analyzer.cc

diff --git a/webrtc/tools/event_log_visualizer/analyzer.cc b/webrtc/tools/event_log_visualizer/analyzer.cc
index 26be553..ba92da7 100644
--- a/webrtc/tools/event_log_visualizer/analyzer.cc
+++ b/webrtc/tools/event_log_visualizer/analyzer.cc
@@ -137,7 +137,9 @@
     if (event_type != ParsedRtcEventLog::VIDEO_RECEIVER_CONFIG_EVENT &&
         event_type != ParsedRtcEventLog::VIDEO_SENDER_CONFIG_EVENT &&
         event_type != ParsedRtcEventLog::AUDIO_RECEIVER_CONFIG_EVENT &&
-        event_type != ParsedRtcEventLog::AUDIO_SENDER_CONFIG_EVENT) {
+        event_type != ParsedRtcEventLog::AUDIO_SENDER_CONFIG_EVENT &&
+        event_type != ParsedRtcEventLog::LOG_START &&
+        event_type != ParsedRtcEventLog::LOG_END) {
       uint64_t timestamp = parsed_log_.GetTimestamp(i);
       first_timestamp = std::min(first_timestamp, timestamp);
       last_timestamp = std::max(last_timestamp, timestamp);