New issue
Advanced search Search tips

Issue 877905 link

Starred by 1 user
Status: Fixed
Owner:
ilnik@chromium.org
Closed: Aug 27
Cc:
srte@chromium.org
ilnik@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

3.6%-775.1% regression in webrtc_perf_tests at 24379:24383

Project Member Reported by ilnik@chromium.org, Aug 27
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Aug 27 

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

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


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

webrtc-android-tests-nexus4-lollipop
webrtc-linux-large-tests

Comment 2 by srte@chromium.org, Aug 27 

Note: The task posting cl shouldn't be able to affect this since the TaskQueue based congestion controller is not enabled for any performance tests yet.

Comment 3 by ilnik@chromium.org, Aug 27 

Another, most probable culprit:
https://webrtc.googlesource.com/src/+/206b77f7ad183d125107113410c9925b5c1a527e

srte@ do you think it could've caused these? The most noticeable change is 0 ramp-up-rtx-padding-sent for all the bots.

Comment 4 by ilnik@chromium.org, Aug 27 

Is it also disabled everywhere?

Comment 5 by ilnik@chromium.org, Aug 27 

Ok, It's probably my commit.

Comment 6 by ilnik@chromium.org, Aug 27

Status: Fixed (was: Assigned)
Revert returned all the graphs.
►

Sign in to add a comment