New issue
Advanced search Search tips

Issue 665954 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 662398



Sign in to add a comment

42.3% regression in system_health.memory_mobile at 430308:430399

Project Member Reported by benjhayden@chromium.org, Nov 16 2016

Issue description

Not sure if this is a real regression, since it is returning to levels as seen before 4 Nov.

+perezju, Do you happen to know of any temporary changes to the benchmark that might have temporarily improved this metric?
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=665954

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


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

android-one
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Nov 16 2016

Cc: ericrk@chromium.org
Owner: ericrk@chromium.org

=== Auto-CCing suspected CL author ericrk@chromium.org ===

Hi ericrk@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Fix locked/unlocked in SW IDC memory dumps.
Author  : ericrk
Commit description:
  
Refactored this incorrectly in the last CL.

R=vmpstr
BUG=661948
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/2485573004
Cr-Commit-Position: refs/heads/master@{#430396}
Commit  : 4ce5368e828e3aaabbede4a684fdc705288b48c9
Date    : Mon Nov 07 22:25:46 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev   N  Good?
chromium@430307  21552820  0.0       5  good
chromium@430353  21552820  0.0       5  good
chromium@430376  21552820  0.0       5  good
chromium@430388  21552820  0.0       5  good
chromium@430393  21552820  0.0       5  good
chromium@430395  21552820  0.0       5  good
chromium@430396  30303514  10115801  5  bad    <--
chromium@430399  31595393  9536006   5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 665954

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.facebook.photos system_health.memory_mobile
Test Metric: memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_media/browse_media_facebook_photos
Relative Change: 46.60%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1808
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995813885644724544


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

| 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!
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Nov 17 2016


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


=== Bisection aborted ===
The bisect was aborted because Infra Failure: Step('device_status (3)') returned 1
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@430307  21552820  0.0      5  good
chromium@430353  21552820  0.0      5  good
chromium@430376  21552820  0.0      3  unknown
chromium@430399  28893671  3254753  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 665954

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:cc:effective_size_avg/browse_media/browse_media_facebook_photos
Relative Change: 34.06%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1807
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8995813912802763168


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

| 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!
Blockedon: 662398

Comment 7 by ericrk@chromium.org, Nov 17 2016

Status: WontFix (was: Untriaged)
This is expected, should have added a note to the cl.we previously checked in a bug which stopped logging some items in memory infra, causing the value to decrease. This regards them.

Sign in to add a comment