[system health] Compute power and clock sync latency metrics

[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
NOTRY=true

Committed: https://crrev.com/7c742ced7137db2e6785822d2a2f8299178b3537
Cr-Commit-Position: refs/heads/master@{#424536}

[charliea (OOO until 10-5), 2016-09-14 18:10:37]

Description was changed from

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

BUG=637158
==========

to

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

BUG=637158
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[charliea (OOO until 10-5), 2016-09-14 18:12:21]

Description was changed from

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

BUG=637158
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[charliea (OOO until 10-5), 2016-09-14 18:13:34]

charliea@chromium.org changed reviewers:
+ nednguyen@google.com

[nednguyen, 2016-09-14 18:41:30]

lgtm

[nednguyen, 2016-09-15 00:38:37]

Description was changed from

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[nednguyen, 2016-09-15 00:39:14]

On 2016/09/14 18:41:30, nednguyen wrote:
> lgtm

+Kouhei, Ksakamoto: later once loading_metric support multiple renderer process,
we can also enable loadingMetric for this benchmark

[charliea (OOO until 10-5), 2016-09-15 20:23:23]

The CQ bit was checked by charliea@chromium.org

[commit-bot: I haz the power, 2016-09-15 20:23:49]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-16 02:33:10]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-16 02:33:12]

Try jobs failed on following builders:
  android_s5_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no build
URL)

[nednguyen, 2016-09-16 11:46:03]

On 2016/09/16 02:33:12, commit-bot: I haz the power wrote:
> Try jobs failed on following builders:
>   android_s5_perf_cq on master.tryserver.chromium.perf (JOB_TIMED_OUT, no
build
> URL)

The mac failure are blocked on https://codereview.chromium.org/2342303002/

[charliea (OOO until 10-5), 2016-09-21 14:32:48]

The CQ bit was checked by charliea@chromium.org

[commit-bot: I haz the power, 2016-09-21 14:33:08]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-21 17:12:43]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-21 17:12:44]

Try jobs failed on following builders:
  linux_perf_cq on master.tryserver.chromium.perf (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_cq/bu...)

[nednguyen, 2016-09-28 14:01:14]

Description was changed from

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
==========

[nednguyen, 2016-09-28 14:01:18]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2016-09-28 14:01:52]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-28 14:09:20]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-28 14:09:21]

Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[nednguyen, 2016-09-28 14:11:48]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2016-09-28 14:11:57]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-28 14:14:16]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-28 14:14:17]

Try jobs failed on following builders:
  android_compile_dbg on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/android_comp...)

[nednguyen, 2016-09-28 14:14:59]

The CQ bit was checked by nednguyen@google.com

[commit-bot: I haz the power, 2016-09-28 14:15:28]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-09-28 14:17:49]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-09-28 14:17:51]

Try jobs failed on following builders:
  linux_chromium_chromeos_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_compile_dbg_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[charliea (OOO until 10-5), 2016-10-11 13:48:56]

Description was changed from

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
==========

to

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

[charliea (OOO until 10-5), 2016-10-11 13:49:05]

The CQ bit was checked by charliea@chromium.org

[charliea (OOO until 10-5), 2016-10-11 13:49:05]

The patchset sent to the CQ was uploaded after l-g-t-m from nednguyen@google.com
Link to the patchset: https://codereview.chromium.org/2338343002/#ps40001
(title: "Synced to head")

[commit-bot: I haz the power, 2016-10-11 13:49:20]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-11 14:01:26]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-11 14:01:27]

Try jobs failed on following builders:
  ios-device on master.tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)

[charliea (OOO until 10-5), 2016-10-11 20:32:57]

Description was changed from

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq
==========

to

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
NOTRY=true
==========

[charliea (OOO until 10-5), 2016-10-11 20:33:17]

Have to add NOTRY=true because several builders on the CQ are flaky

[charliea (OOO until 10-5), 2016-10-11 20:33:21]

The CQ bit was checked by charliea@chromium.org

[commit-bot: I haz the power, 2016-10-11 20:33:49]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-11 20:41:53]

Description was changed from

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
NOTRY=true
==========

to

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
NOTRY=true
==========

[commit-bot: I haz the power, 2016-10-11 20:41:54]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-10-11 20:43:48]

Description was changed from

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
NOTRY=true
==========

to

==========
[system health] Compute power and clock sync latency metrics

I added the "common system health benchmark" (i.e. non-memory
benchmark), but forgot to have it compute any metrics. This fixes that.

I also removed the old system health loading stories from the "battor"
benchmark set. Eventually, I imagine that this set will go away
completely as BattOr metrics are computed in other benchmarks.

BUG=637158
NOTRY=true

Committed: https://crrev.com/7c742ced7137db2e6785822d2a2f8299178b3537
Cr-Commit-Position: refs/heads/master@{#424536}
==========

[commit-bot: I haz the power, 2016-10-11 20:43:50]

Patchset 3 (id:??) landed as
https://crrev.com/7c742ced7137db2e6785822d2a2f8299178b3537
Cr-Commit-Position: refs/heads/master@{#424536}