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

Issue 713076 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

2355.5%-7114.4% regression in thread_times.key_idle_power_cases at 465266:465372

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

Comment 1 by alexclarke@chromium.org, Apr 19 2017 

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

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


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

android-webview-nexus6
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       : thread_total_all_cpu_time_per_second/set-timeout.html

Revision             Result                  N
chromium@465265      20.1368 +- 3.55167      21      good
chromium@465372      20.2401 +- 2.53594      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 thread_times.key_idle_power_cases

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

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


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

Status: WontFix (was: Untriaged)
This appears to be a false alert, the graph reverted to the prevailing mean.
Project Member

Comment 6 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       : thread_total_all_cpu_time_per_second/set-timeout.html

Revision             Result                  N
chromium@465265      20.1368 +- 3.55167      21      good
chromium@465372      20.2401 +- 2.53594      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 thread_times.key_idle_power_cases

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

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


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

Revision             Result                  N
chromium@465265      20.1368 +- 3.55167      21      good
chromium@465372      20.2401 +- 2.53594      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 thread_times.key_idle_power_cases

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

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


| 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 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/css-animation.html

Revision             Result                  N
chromium@465265      20.1368 +- 3.55167      21      good
chromium@465372      20.2401 +- 2.53594      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=css.animation.html thread_times.key_idle_power_cases

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

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


| 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