New issue
Advanced search Search tips

Issue 672082 link

Starred by 0 users
Status: WontFix
Owner:
juncai@chromium.org
Closed: Dec 2016
Cc:
tdres...@chromium.org
juncai@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

14.5% regression in blink_perf.parser at 434856:435481

Project Member Reported by tdres...@chromium.org, Dec 7 2016 
See the link to graphs below.

Comment 1 by tdres...@chromium.org, Dec 7 2016 

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Dec 7 2016 


===== 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  1.70238  0.299395  25  good
chromium@435481  1.68986  0.150007  25  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 672082

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser
Test Metric: url-parser/url-parser
Relative Change: 0.74%

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


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

| 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, Dec 7 2016 


===== 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  1.64282  0.223472  25  good
chromium@435481  1.67584  0.153947  25  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 672082

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser
Test Metric: url-parser/url-parser
Relative Change: 2.01%

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


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

| 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, Dec 7 2016 


===== 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@434400  1.65691  0.424684  25  good
chromium@435700  1.68442  0.271436  25  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 672082

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser
Test Metric: url-parser/url-parser
Relative Change: 1.66%

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


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

| 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 8 by tdres...@chromium.org, Dec 8 2016

Status: WontFix (was: Untriaged)
The ref build moves a bit later - I think this is probably just something to do with the bot.
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Dec 9 2016 


===== 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  1.6835   0.370951  25  good
chromium@435481  1.71143  0.237916  25  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 672082

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser
Test Metric: url-parser/url-parser
Relative Change: 1.66%

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


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

| 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 12 by 42576172...@developer.gserviceaccount.com, Dec 16 2016

Cc: juncai@chromium.org
Owner: juncai@chromium.org

=== PERF REGRESSION ===


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

Hi juncai@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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


===== SUSPECTED CL(s) =====
Subject : Use new wrapper types for web_bluetooth.mojom
Author  : juncai
Commit description:
  
This CL modified code to use new wrapper types for web_bluetooth.mojom.
Also changed all instances of mojo::Array, mojo::String to std::vector,
std::string since mojo::Array, mojo::String have been deprecated.

BUG= 597053 

Review-Url: https://codereview.chromium.org/2506813003
Cr-Commit-Position: refs/heads/master@{#434892}
Commit  : 1ef7dd4b548d9ccd5e573bf053043ab79070ae08
Date    : Tue Nov 29 04:31:49 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N   Good?
chromium@434855  1.62425  0.340779  30  good
chromium@434875  1.63121  0.248038  30  good
chromium@434885  1.56367  0.3159    30  good
chromium@434890  1.53578  0.278284  30  good
chromium@434891  1.53799  0.236089  25  good
chromium@434892  1.67106  0.331886  30  bad    <--
chromium@434893  1.68979  0.312935  30  bad
chromium@434895  1.68451  0.272566  25  bad
chromium@434934  1.69246  0.322811  30  bad
chromium@435012  1.71325  0.201686  30  bad
chromium@435168  1.69449  0.198177  30  bad
chromium@435481  1.70787  0.211409  30  bad

Bisect job ran on: android_nexus5X_perf_bisect
Bug ID: 672082

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.parser
Test Metric: url-parser/url-parser
Relative Change: 5.15%

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


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

| 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