New issue
Advanced search Search tips

Issue 849188 link

Starred by 1 user
Status: WontFix
Owner:
ssilkin@chromium.org
Closed: Jul 9
Cc:
asapersson@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 25% regression in webrtc_perf_tests at 23447:23447

Project Member Reported by asapersson@chromium.org, Jun 4 2018 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jun 4 2018 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=849188

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=80f2215bc0819742b7adc88e1e14b080b0dfe30bee0a6688705eba629deb59f7


Bot(s) for this bug's original alert(s):

webrtc-linux-large-tests
webrtc-win-large-tests

Comment 2 by asapersson@chromium.org, Jun 4 2018

Owner: ssilkin@chromium.org

Comment 3 by ssilkin@chromium.org, Jul 9

Status: WontFix (was: Untriaged)
dropped_frames increased from 0 to 1. This is not something we should worry about. It actually further increased in the following revisions and currently equal to 3 frames on average, which is still not an issue.
►

Sign in to add a comment