Issue metadata
Sign in to add a comment
|
5.8%-23% regression in browser_tests at 447702:448233 |
||||||||||||||||||||
Issue descriptionVirtually impossible to bisect, since the blamelists are huge. WebRTC: https://chromium.googlesource.com/external/webrtc/trunk/webrtc/+log/7d5b2665b5c6a37ebad6c6bcbf5f4a9ee8408c65..b3f36e7e138c4198f0e06ed3829206654804938d/?s=cf356c61b63caffcda1098275413a85a33e3a6dc The weird thing is that the point before the regression was run on February 1, but picked up a WebRTC rev from January 19. Assigning to kjellander@ to figure out if something needs checking there. For the regression itself, I think we will have to let that go.
,
Feb 8 2017
Yeah, this is unfortunate. The Mac Builder bot in chromium.webrtc.fyi was down first Jan 13-18 then Jan 19-Feb 6 before it was fixed. When expanding the scale longer back in time, it seems it's back at where it was in October 2016, and the comment regarding the cause of bug 689915 seems to tell that's intentional. This pattern looks similar from revision 448728 and forward, so I suggest we just close this. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by hlundin@chromium.org
, Feb 8 2017