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

Issue 633946 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Aug 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

2% regression in system_health.memory_mobile at 409200:409247

Project Member Reported by petrcermak@chromium.org, Aug 3 2016

Issue description

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

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


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

android-nexus7v2
Cc: deadbeef@chromium.org
Owner: deadbeef@chromium.org

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

Hi deadbeef@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 : Roll src/third_party/usrsctp/usrsctplib/ c60ec8b35..9a3e5465e (180 commits).
Author  : deadbeef
Commit description:
  
https://chromium.googlesource.com/external/github.com/sctplab/usrsctp/+log/c60ec8b35c3f..9a3e5465e9d9

This roll includes a fix for a crash that was upstreamed:
https://github.com/sctplab/usrsctp/pull/93

Also replacing lally@ with pthatcher@ and deadbeef@ as owners of usrsctp, since Lally is no longer working on Chromium.

BUG= 622033 

Review-Url: https://codereview.chromium.org/2175453002
Cr-Commit-Position: refs/heads/master@{#409239}
Commit  : c259443691527968a5bcec022e41844fa606fd7e
Date    : Tue Aug 02 18:07:35 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@409199  1223066  3663.57  5  good
chromium@409223  1225523  5340.53  5  good
chromium@409235  1216512  2896.31  5  good
chromium@409238  1218970  2243.47  5  good
chromium@409239  1243546  2243.47  5  bad    <--
chromium@409240  1241088  2896.31  5  bad
chromium@409241  1242726  4670.16  5  bad
chromium@409247  1237811  4486.94  5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 633946

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_tools-memory:chrome:all_processes:reported_by_os:system_memory:ashmem:private_dirty_size_avg/load_tools_dropbox
Relative Change: 1.21%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3142
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005355145624270032


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

| 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!
Status: WontFix (was: Assigned)
Graph shows that this apparent regression is now recovered; closing.
Labels: SystemHealth-Sheriff
Labels: -Performance-Sheriff

Sign in to add a comment