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

Issue 713074 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

21.8%-51308.6% regression in thread_times.simple_mobile_sites at 465266:465372

Project Member Reported by alexclarke@chromium.org, Apr 19 2017 
See the link to graphs below.
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Apr 20 2017 


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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/set-timeout.html (Long Idle)

Revision             Result                  N
chromium@465265      1647.79 +- 280.162      21      good
chromium@465372      1645.52 +- 293.641      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html..Long.Idle. thread_times.key_idle_power_cases

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

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


| 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 5 by 42576172...@developer.gserviceaccount.com, Apr 21 2017 


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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : tasks_per_second_total_all/set-timeout.html (Long Idle)

Revision             Result                  N
chromium@465265      1647.79 +- 280.162      21      good
chromium@465372      1645.52 +- 293.641      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html..Long.Idle. thread_times.key_idle_power_cases

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

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


| 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 23 2017 


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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : thread_total_all_cpu_time_per_second/set-timeout.html (Long Idle)

Revision             Result                  N
chromium@465265      1647.79 +- 280.162      21      good
chromium@465372      1645.52 +- 293.641      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=set.timeout.html..Long.Idle. thread_times.key_idle_power_cases

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

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


| 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 alexclarke@chromium.org, Apr 24 2017

Status: WontFix (was: Untriaged)
Something landed but as reverted.  We can close this.
Project Member

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


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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_idle_power_cases
  Metric       : thread_total_all_cpu_time_per_second/animated-gif.html

Revision             Result                  N
chromium@465265      1647.79 +- 280.162      21      good
chromium@465372      1645.52 +- 293.641      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=animated.gif.html thread_times.key_idle_power_cases

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

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


| 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