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

Issue 659652 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression

Blocked on:
issue 659658



Sign in to add a comment

5.2%-15% regression in thread_times.key_silk_cases at 427466:427517

Project Member Reported by alexclarke@chromium.org, Oct 26 2016

Issue description

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

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


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

android-nexus5
android-nexus6
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 26 2016

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4291
Failure reason: the build has failed due to infrastructure failure.

Blockedon: 659658
Status: WontFix (was: Untriaged)
These regressions happened before M56 branch. M56 is now in stable. These regressions made it to the stable channel. Marking wontfix.
Labels: Performance-Responsiveness
Project Member

Comment 8 by 42576172...@developer.gserviceaccount.com, Apr 10 2017

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4843
Failure reason: the build has failed due to infrastructure failure.

Sign in to add a comment