New issue
Advanced search Search tips

Issue 606340 link

Starred by 0 users
Status: WontFix
Owner:
holmer@chromium.org
Closed: Apr 2016
Cc:
sprang@chromium.org
peah@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

13.9% regression in webrtc_perf_tests at 12457:12469

Project Member Reported by peah@chromium.org, Apr 25 2016 
13.9# regression in the bitrate_stats_min_transmit_bitrate/bitrate_kbps webrtc_perf_test

Comment 1 by peah@chromium.org, Apr 25 2016 

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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5KyxsAoM


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

webrtc-android-tests-nexus9

Comment 2 by peah@chromium.org, Apr 25 2016

Cc: peah@chromium.org
Owner: sprang@chromium.org
A possible CL causing this could be https://codereview.webrtc.org/1903553003
@sprang: Could you please take a look if that could be the one?

Comment 3 by sprang@chromium.org, Apr 25 2016

Cc: sprang@chromium.org
Owner: holmer@chromium.org
No, that CL just changes the default parameters (used if you don't specify any on the command line) in the stand-alone screenshare_loopback. 

A more likely culprit, but that is technically one revision outside of the blame range reported, is this one: https://chromium.googlesource.com/external/webrtc/+/fb8fc5391e097dc4c2f89b3a38724f5fa109d8f9

Stefan, could you have a look?

Comment 4 by holmer@chromium.org, Apr 25 2016 

Expected that these stats change a bit with my CL.

Comment 5 by holmer@chromium.org, Apr 25 2016

Status: WontFix (was: Assigned)
►

Sign in to add a comment