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

Issue 639463 link

Starred by 2 users
Status: WontFix
Owner: ----
Closed: Mar 2017
Cc:
█ robert...@chromium.org
█ pras...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

10.2% regression in media.android.tough_video_cases at 412848:412892

Project Member Reported by chcunningham@google.com, Aug 19 2016 
Bump in vm_proportional_set_size_delta.

May be related to  Issue 639459 , but ranges seemingly don't overlap (close by though).

Comment 1 by chcunningham@google.com, Aug 19 2016 

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Aug 20 2016 


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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@412847  609.75   527.221  8  good
chromium@412853  676.5    322.132  8  good
chromium@412859  771.875  415.318  8  bad
chromium@412870  677.5    538.982  8  bad
chromium@412892  683.375  582.421  8  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 639463

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases
Test Metric: vm_proportional_set_size_delta/crowd.wav_gpu
Relative Change: 14.94%
Score: 0

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


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

| 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 4 by sheriffbot@chromium.org, Aug 20 2016

Labels: Hotlist-Google
Project Member

Comment 6 by 42576172...@developer.gserviceaccount.com, Aug 23 2016 


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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@412847  621.25   540.466  8  good
chromium@412853  829.25   38.7437  8  good
chromium@412856  784.0    16.2635  5  good
chromium@412859  883.125  38.5132  8  bad
chromium@412870  869.8    17.1085  5  bad
chromium@412892  887.4    26.073   5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 639463

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases
Test Metric: vm_proportional_set_size_delta/crowd.wav_gpu
Relative Change: 81.99%
Score: 0

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


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

| 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 8 by 42576172...@developer.gserviceaccount.com, Aug 23 2016 


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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@412847  621.25   540.466  8  good
chromium@412853  829.25   38.7437  8  good
chromium@412856  784.0    16.2635  5  good
chromium@412859  883.125  38.5132  8  bad
chromium@412870  869.8    17.1085  5  bad
chromium@412892  887.4    26.073   5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 639463

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases
Test Metric: vm_proportional_set_size_delta/crowd.wav_gpu
Relative Change: 81.99%
Score: 0

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


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

| 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 9 by chcunningham@chromium.org, Aug 23 2016

Cc: robert...@chromium.org pras...@chromium.org
@prasadv/robertocn - having trouble with this bisect too.
Project Member

Comment 11 by 42576172...@developer.gserviceaccount.com, Aug 24 2016 


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


===== SUSPECTED CL(s) =====
Subject : Use the process-level MojoShellConnection to connect to mojo:media.
Author  : slan
Commit description:
  
The interface provided by mojo:media, media::mojom::MediaService, is
registered in mojo_shell_context.cc on the browser process
MojoShellConnection. Use this ShellConnection to connect to this
interface (rather than the connection for the BrowserContext).

BUG=638950

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_site_isolation

Review-Url: https://codereview.chromium.org/2255223002
Cr-Commit-Position: refs/heads/master@{#412859}
Commit  : f78815009d7a7801126d30a76c71a2554ea86f93
Date    : Thu Aug 18 17:03:27 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@412847  503.0   655.828  5  good
chromium@412853  823.25  46.7172  8  good
chromium@412856  711.5   342.694  8  good
chromium@412858  808.6   24.4397  5  good
chromium@412859  879.8   23.9102  5  bad    <--
chromium@412870  885.4   30.8756  5  bad
chromium@412892  881.2   19.5371  5  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 639463

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests media.android.tough_video_cases
Test Metric: vm_proportional_set_size_delta/crowd.wav_gpu
Relative Change: 75.19%
Score: 0.0

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


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

| 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 12 by chcunningham@chromium.org, Aug 24 2016

Owner: s...@chromium.org
slan@, can you take a look at this metric and see if your change may have caused a regression?

Comment 13 by s...@chromium.org, Aug 24 2016

Owner: chcunningham@chromium.org
This change merely corrects an earlier bug that broke mojo:media on Android. I doubt it has anything to do with the perf regression. Though the bot tripped at my change, it looks like the mean value of the metric climbed steeply before it landed. 

Good luck!
Project Member

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/810
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.
Project Member

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/811
Failure reason: the build has failed.
Additional errors:
The metric was not found in the test output.
Either of the initial "good" or "bad" revisions failed to be tested or built.

Comment 18 by chcunningham@chromium.org, Nov 4 2016

Owner: robert...@chromium.org
Bisects not working here. Roberto, can you take a look or re-assign to bisect tool owner?
Project Member

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


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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: No values were found while testing the reference range.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean  Std Dev  N  Good?
chromium@412847  N/A   N/A      0  good
chromium@412892  N/A   N/A      0  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 639463

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=crowd.wav.gpu media.android.tough_video_cases
Test Metric: vm_proportional_set_size_delta/crowd.wav_gpu
Relative Change: None

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


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

| 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 21 by rbyers@chromium.org, Nov 18 2016

Labels: Performance

Comment 22 by robert...@chromium.org, Mar 17 2017

Owner: ----

Comment 23 by chcunningham@chromium.org, Mar 21 2017

Status: WontFix (was: Assigned)
Graphs have since recovered.
►

Sign in to add a comment