New issue
Advanced search Search tips

Issue 670788 link

Starred by 0 users

Issue metadata

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



Sign in to add a comment

33.4% regression in indexeddb_perf at 434856:435481

Project Member Reported by qyears...@chromium.org, Dec 2 2016

Issue description

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

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


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

android-nexus5X

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@434855  30403.6  1217.95  27  good
chromium@435481  30527.9  1861.9   27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670788

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests indexeddb_perf
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 0.41%

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


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

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

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@434855  30537.8  1202.27  27  good
chromium@435481  30589.0  1994.65  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670788

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests indexeddb_perf
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 0.17%

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


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

| 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!
Note: Ref build results move at the same time, but not by the same amount.

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@434855  30411.9  1533.27  27  good
chromium@435481  30573.2  2092.29  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670788

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests indexeddb_perf
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 0.53%

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


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

| 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!
If the next bisect job fails to find a culprit, then this is likely nothing (note, see comment #7)

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


=== Bisection aborted ===
The bisect was aborted because Bisect cannot identify a culprit: Bisect failed to reproduce the regression with enough confidence.
Please contact the the team (see below) if you believe this is in error.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@434855  30452.3  1130.25  27  good
chromium@435481  30542.8  2029.62  27  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 670788

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests indexeddb_perf
Test Metric: vm_private_dirty_final_browser/vm_private_dirty_final_browser
Relative Change: 0.30%

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


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

| 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: Untriaged)
Closing after another failed bisect, see #10

Sign in to add a comment