New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 911094 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

12.9%-41.6% improvement in browser_tests at 611865:612146

Project Member Reported by ilnik@chromium.org, Dec 3

Issue description

Browser tests webrtc stats changed a lot.

There were no webrtc roll at the time.


This commit looks like most probable cause:
https://chromium.googlesource.com/chromium/src/+/c2227ae1467d525c15802d8dd6ddbe309c432515

cduvall, PTAL
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=911094

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


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

chromium-webrtc-rel-mac
Cc: cduvall@chromium.org
Owner: phoglund@chromium.org
It seems pretty unlikely that my change caused this, since the only difference is to a test that only runs with NetworkService enabled, and the change only prevents that test from running when NetworkService is in-process (a configuration we don't currently run browser tests for).

I'm wondering if it could be related to the recent change of running webrtc browser tests on luci: http://crrev.com/c/1354001

Assigning to Patrik to see if he thinks it could be related.

Sign in to add a comment