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

Issue 592290 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

6.2% regression in page_cycler.basic_oopif at 379174:379205

Project Member Reported by ericwilligers@chromium.org, Mar 7 2016

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=592290

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


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

linux-release
Cc: robert...@chromium.org pras...@chromium.org
Hmhh, the job kicked off by Tim was successful (https://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6319). Not sure why the bug didn't get updated.

+Prasad, Roberto?
"successful" but couldn't reproduce either time. I'm going to WontFix this since the bisector doesn't reproduce the regression and there is no ref build, but I filed  bug 598320  on the bisect not updating.
Status: WontFix (was: Assigned)
"Bisect failed to reproduce the regression with enough confidence."

Sign in to add a comment