From fe0b499634d354e891912ead914426f56087d62d Mon Sep 17 00:00:00 2001 From: Philipp Hancke Date: Fri, 22 Mar 2019 09:00:50 +0100 Subject: [PATCH] legacy stats: update timestamp on localcandidate/remotecandidate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit updates the timestamp on the local and remote candidate stats for consistency with other places. This also makes the graphs on chrome://webrtc-internals work (even though most values don't update so showing graphs is not meaningful) BUG=chromium:937833 Change-Id: I3267dd7a5f5a887dcd0756137077b8f02c201905 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/128765 Reviewed-by: Henrik Boström Reviewed-by: Steve Anton Commit-Queue: Steve Anton Cr-Commit-Position: refs/heads/master@{#27248} --- pc/stats_collector.cc | 1 + 1 file changed, 1 insertion(+) diff --git a/pc/stats_collector.cc b/pc/stats_collector.cc index 03eb59cf64..6bfce676ca 100644 --- a/pc/stats_collector.cc +++ b/pc/stats_collector.cc @@ -737,6 +737,7 @@ StatsReport* StatsCollector::AddCandidateReport( report->AddString(StatsReport::kStatsValueNameCandidateTransportType, candidate.protocol()); } + report->set_timestamp(stats_gathering_started_); if (local && candidate_stats.stun_stats.has_value()) { const auto& stun_stats = candidate_stats.stun_stats.value();