New issue
Advanced search Search tips

Issue 640359 link

Starred by 1 user
Status: WontFix
Owner:
nisse@chromium.org
Closed: Oct 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

44.4% improvement in browser_tests at 413567:413577

Project Member Reported by peah@chromium.org, Aug 23 2016 
nisse@: Could these be caused by the revert you did on https://codereview.chromium.org/2244213002 ? In that case, is it expected that the values should not return to their former range?

Comment 1 by peah@chromium.org, Aug 23 2016 

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

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


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

chromium-webrtc-trunk-tot-rel-mac

Comment 2 by nisse@chromium.org, Sep 13 2016 

Not sure, needs a little investigation.

Comment 3 by peah@chromium.org, Oct 21 2016 

Any updates on this? Can it be closed?

Comment 4 by nisse@chromium.org, Oct 21 2016

Status: WontFix (was: Assigned)
I really have no idea why values didn't quite return to the former range. Closing, since I see nothing useful we can do about it.
►

Sign in to add a comment