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

Issue 714288 link

Starred by 1 user
Status: Duplicate
Merged: issue 714497
Owner:
█ paezagon@chromium.org
Email to this user bounced
Closed: Apr 2017
Cc:
martiniss@chromium.org
█ paezagon@chromium.org
nedngu...@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

170.6% regression in page_cycler_v2.tough_layout_cases at 464923:464949

Project Member Reported by nedngu...@google.com, Apr 21 2017 
There is no change to this benchmark. Wonder whether this is due to a device swap.

Comment 1 by nedngu...@google.com, Apr 21 2017 

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

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


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

android-nexus6

Comment 3 by nedngu...@google.com, Apr 21 2017

Cc: martiniss@chromium.org
Components: Speed>Benchmarks>Waterfall
Project Member

Comment 5 by 42576172...@developer.gserviceaccount.com, Apr 21 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                      N
chromium@464922      0.0506119 +- 0.0179521      21      good
chromium@464949      0.0489868 +- 0.0198141      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=benchmark.duration page_cycler_v2.tough_layout_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8981667161025577872

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5816118486237184


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 7 by 42576172...@developer.gserviceaccount.com, Apr 21 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                      N
chromium@464922      0.0506119 +- 0.0179521      21      good
chromium@464949      0.0489868 +- 0.0198141      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=benchmark.duration page_cycler_v2.tough_layout_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8981662045033715664

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5816118486237184


| 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 Speed>Bisection.  Thank you!

Comment 8 by nedngu...@google.com, Apr 22 2017

Owner: simonhatch@chromium.org
+Simon seems like the nexus 6 bisect bot is failing?
Project Member

Comment 10 by 42576172...@developer.gserviceaccount.com, Apr 23 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                      N
chromium@464922      0.0496648 +- 0.0213437      21      good
chromium@464949      0.0494344 +- 0.0189344      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=benchmark.duration page_cycler_v2.tough_layout_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8981570463256259360

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5816118486237184


| 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 Speed>Bisection.  Thank you!

Comment 12 by simonhatch@chromium.org, Apr 24 2017 

Rekicked this bisect, guessing that if you want to bisect on benchmark duration you don't want to supply a story filter.
Project Member

Comment 13 by 42576172...@developer.gserviceaccount.com, Apr 25 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                   N
chromium@464922      14.6189 +- 0.639905      21      good
chromium@464949      14.6759 +- 1.2981        21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.tough_layout_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8981423185856876736

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5898030491893760


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 15 by 42576172...@developer.gserviceaccount.com, Apr 25 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                  N
chromium@464922      13.3994 +- 5.22171      21      good
chromium@464949      13.5569 +- 0.81519      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.tough_layout_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8981380073384321536

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5898030491893760


| 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 Speed>Bisection.  Thank you!

Comment 17 by nedngu...@google.com, Apr 25 2017

Mergedinto: 714497
Status: Duplicate (was: Untriaged)
Project Member

Comment 19 by 42576172...@developer.gserviceaccount.com, Apr 27 2017

Cc: paezagon@chromium.org
Owner: paezagon@chromium.org

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

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


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : paezagon
  Commit : ae360640e5b0475e52f8cee25d755ce484faf6e4
  Date   : Mon Apr 17 17:49:09 2017
  Subject: Working on making context menu display the number of bookmarks that will be opened by by Open All.

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : benchmark_duration/benchmark_duration
  Change       : 2.39% | 14.7507624904 -> 14.3987812224

Revision             Result                   N
chromium@464922      14.7508 +- 0.453432      21      good
chromium@464936      14.8684 +- 1.15515       21      good
chromium@464943      14.7814 +- 0.301628      14      good
chromium@464946      14.8637 +- 0.200109      6       good
chromium@464948      14.8856 +- 0.698457      9       good
chromium@464949      14.3988 +- 3.68308       14      bad       <--

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.tough_layout_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8981244287448465792

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5898030491893760


| 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 Speed>Bisection.  Thank you!
Project Member

Comment 21 by 42576172...@developer.gserviceaccount.com, Apr 30 2017 


=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : page_cycler_v2.tough_layout_cases
  Metric       : benchmark_duration/benchmark_duration

Revision             Result                   N
chromium@464922      13.6284 +- 0.764554      21      good
chromium@464949      13.5545 +- 0.543683      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests page_cycler_v2.tough_layout_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980930211023908192

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5816118486237184


| 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 Speed>Bisection.  Thank you!
►

Sign in to add a comment