mission-control-5 health-check failures

[Paul Larson]

We ran baselines of many processes on an idle nexus4 using health-check for the last trusty image, and some of those have regressed since then. These could be real regressions, or they could be something that's expected due to changes that happened since that image. We need someone to investigate these and report whether it requires a fix, or whether the thresholds need to be adjusted, and why.

Results from a recent test run can be seen at http://ci.ubuntu.com/smokeng/utopic/touch/mako/203:20140821.1:20140811.1/9847/health-check/1565353/

Occasionally with mission-control-5, we see it waking up more often than we expected from the idle case. It doesn't happen on every run though. Is there something that you can think of that would explain this behavior? any ideas how many wakups/s we should expect from it on an idle device?
process: mission-control-5
PASSED: 0.06 >= 0.043333: health-check.cpu-load.cpu-load-total.system-cpu-percent
PASSED: 0.08 >= 0.08: health-check.cpu-load.cpu-load-total.total-cpu-percent
PASSED: 0.05 >= 0.036667: health-check.cpu-load.cpu-load-total.user-cpu-percent
PASSED: 0.02 >= 0.0: health-check.file-access.file-access-total.access-count-total-rate
PASSED: 0.02 >= 0.0: health-check.file-io-operations.file-io-operations-total.close-call-total-rate
PASSED: 0.02 >= 0.0: health-check.file-io-operations.file-io-operations-total.open-call-total-rate
PASSED: 0.02 >= 0.0: health-check.file-io-operations.file-io-operations-total.read-call-total-rate
PASSED: 0.02 >= 0.0: health-check.file-io-operations.file-io-operations-total.write-call-total-rate
PASSED: 0.0 >= 0.0: health-check.file-system-syncs.sync-system-calls-total.fdatasync-call-count-total-rate
PASSED: 0.0 >= 0.0: health-check.file-system-syncs.sync-system-calls-total.fsync-call-count-total-rate
PASSED: 0.0 >= 0.0: health-check.file-system-syncs.sync-system-calls-total.sync-call-count-total-rate
PASSED: 0.0 >= 0.0: health-check.file-system-syncs.sync-system-calls-total.syncfs-call-count-total-rate
PASSED: 0.002777778 >= 0.0: health-check.heap-usage-via-brk.heap-usage-via-brk-total.brk-size-total-Kbytes-rate
PASSED: 0.002777778 >= 0.0: health-check.memory-usage-via-mmap.memory-usage-via-mmap-total.mmap-total-Kbytes-rate
PASSED: 128.0 >= 0.0: health-check.network-connections.network-connections-total.receive-total-rate
PASSED: 128.0 >= 0.0: health-check.network-connections.network-connections-total.send-total-rate
FAILED: 0.01 < 0.046667: health-check.wakeup-events.wakeup-events-total.wakeup-total-rate