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

Issue 784304 link

Starred by 1 user
Status: WontFix
Owner:
hlundin@chromium.org
Closed: Nov 2017
Cc:
█ phoglund@chromium.org
grunell@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4% regression in browser_tests at 515253:515319

Project Member Reported by grunell@chromium.org, Nov 13 2017 
Can you take a look at this?
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 13 2017 

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

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


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

chromium-webrtc-trunk-tot-rel-win10

Comment 2 by hlundin@chromium.org, Nov 13 2017

Cc: phoglund@chromium.org
Labels: OS-Windows
Status: WontFix (was: Assigned)
I think this is specific to that bot. No other bots I looked at shows a similar shift.

Moreover, it happens simultaneously for Win10FYI and Win10. This implies that it is not a WebRTC change that caused this shift. However, looking at the corresponding Chrome CL range, nothing sticks out there either.

I think this is infra. Adding phoglund@ as FYI.

Comment 3 by phoglund@chromium.org, Nov 13 2017 

Could be cosmic rays / infra / aliens as usual, or a chrome change that had an unexpected effect. Either way, probably not related to WebRTC.
►

Sign in to add a comment