New issue
Advanced search Search tips

Issue 660167 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

4.1% regression in system_health.memory_mobile at 427620:427667

Project Member Reported by m...@chromium.org, Oct 27 2016

Issue description

See the link to graphs below.
 

Comment 1 by m...@chromium.org, Oct 27 2016

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

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


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

android-nexus5X
Project Member

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


===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N   Good?
chromium@427619  751803  10755.5  12  good

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 660167

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background_tools/background_tools_gmail
Relative Change: 0.78%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/808
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997614052240025584


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5907415856316416

| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Tests>AutoBisect.  Thank you!

Comment 5 by m...@chromium.org, Oct 28 2016

Infra failure in last bisect run, re-running...
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Oct 28 2016

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

Comment 7 by m...@chromium.org, Oct 29 2016

Cc: sullivan@chromium.org
Labels: Performance-Sheriff-BotHealth
Cannot proceed on this due to infra failure (bisect attempts failed, and there are too many candidates in rev ranges to suspect individual changes).
Owner: dtu@chromium.org
Dave, can you take a look at the failed bisects as part of your bug triage rotation?

Comment 9 by benhenry@google.com, Dec 20 2016

Status: Assigned (was: Untriaged)

Comment 10 by dtu@chromium.org, Feb 8 2017

Status: Archived (was: Assigned)

Sign in to add a comment