New issue
Advanced search Search tips

Issue 635888 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 632644
Owner:
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.2%-6.1% regression in indexeddb_perf at 407919:408831

Project Member Reported by rmcilroy@chromium.org, Aug 9 2016

Issue description

See the link to graphs below.
 

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


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@408196  23662.3  467.389  12  good
chromium@408216  23923.1  544.558  12  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 635888

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.basic_oopif
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 2.89%
Score: 0

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


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

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

Mergedinto: 632644
Status: Duplicate (was: Assigned)

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


===== SUSPECTED CL(s) =====
Subject : [Android] Roll support lib to 24.1.1
Author  : ianwen
Commit description:
  
This is the second attempt to roll the support library. The first
attempt was https://codereview.chromium.org/2175513002 and it was
reverted in https://codereview.chromium.org/2175763003 due to downstream
bots failure.

BUG=629768

Review-Url: https://codereview.chromium.org/2185133002
Cr-Commit-Position: refs/heads/master@{#408211}
Commit  : c8ba82433d4b45be103fc3f3b0005d6df5c82a64
Date    : Wed Jul 27 19:18:31 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@408196  32517.2  57.5387  5  good
chromium@408206  32541.8  50.4747  5  good
chromium@408209  32523.8  58.666   5  good
chromium@408210  32570.0  57.0307  5  good
chromium@408211  32311.8  53.4107  5  bad    <--
chromium@408216  32346.3  68.7038  8  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 635888

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.basic_oopif
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 0.47%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2005
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004720692888457248


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

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


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


===== SUSPECTED CL(s) =====
Subject : [Android] Roll support lib to 24.1.1
Author  : ianwen
Commit description:
  
This is the second attempt to roll the support library. The first
attempt was https://codereview.chromium.org/2175513002 and it was
reverted in https://codereview.chromium.org/2175763003 due to downstream
bots failure.

BUG=629768

Review-Url: https://codereview.chromium.org/2185133002
Cr-Commit-Position: refs/heads/master@{#408211}
Commit  : c8ba82433d4b45be103fc3f3b0005d6df5c82a64
Date    : Wed Jul 27 19:18:31 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@408184  28229.2  49.126   6  good
chromium@408210  28255.0  32.871   5  good
chromium@408211  28556.6  31.3417  5  bad    <--
chromium@408212  28542.4  23.2013  5  bad
chromium@408214  28559.8  40.7701  5  bad
chromium@408217  28562.2  50.2613  5  bad
chromium@408223  28586.2  40.7333  5  bad
chromium@408236  28579.2  35.6539  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 635888

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests page_cycler.intl_hi_ru
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 1.25%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2451
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004720681617012272


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

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

Sign in to add a comment