touch-packages team mailing list archive

[Paul Larson <paul.larson@xxxxxxxxxxxxx>]

Public bug reported:

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.

For upowerd, we see quite a lot more file IO and syncs than it did in
trusty. Here are the results from the latest run at: Results from a
recent test run can be seen at
http://ci.ubuntu.com/smokeng/utopic/touch/mako/204:20140822:20140811.1/9853
/health-check/

process: upowerd
PASSED: 0.09 >= 0.086667: health-check.cpu-load.cpu-load-total.system-cpu-percent
FAILED: 0.02 < 0.136667: health-check.cpu-load.cpu-load-total.total-cpu-percent
PASSED: 0.06 >= 0.05: health-check.cpu-load.cpu-load-total.user-cpu-percent
FAILED: 0.016666667 < 3.189998: health-check.file-access.file-access-total.access-count-total-rate
FAILED: 0.016666667 < 1.063333: health-check.file-io-operations.file-io-operations-total.close-call-total-rate
FAILED: 0.016666667 < 1.063333: health-check.file-io-operations.file-io-operations-total.open-call-total-rate
FAILED: 0.016666667 < 1.049999: health-check.file-io-operations.file-io-operations-total.read-call-total-rate
FAILED: 0.016666667 < 0.026667: 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
FAILED: 0.0 < 0.013333: 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: 256.0 >= 0.0: health-check.network-connections.network-connections-total.receive-total-rate
PASSED: 256.0 >= 0.0: health-check.network-connections.network-connections-total.send-total-rate
PASSED: 0.25 >= 0.01: health-check.wakeup-events.wakeup-events-total.wakeup-total-rate

** Affects: upower (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: health-check

** Tags added: health-check

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1360368

Title:
  upowerd health check failures

Status in “upower” package in Ubuntu:
  New

Bug description:
  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.

  For upowerd, we see quite a lot more file IO and syncs than it did in
  trusty. Here are the results from the latest run at: Results from a
  recent test run can be seen at
  http://ci.ubuntu.com/smokeng/utopic/touch/mako/204:20140822:20140811.1/9853
  /health-check/

  process: upowerd
  PASSED: 0.09 >= 0.086667: health-check.cpu-load.cpu-load-total.system-cpu-percent
  FAILED: 0.02 < 0.136667: health-check.cpu-load.cpu-load-total.total-cpu-percent
  PASSED: 0.06 >= 0.05: health-check.cpu-load.cpu-load-total.user-cpu-percent
  FAILED: 0.016666667 < 3.189998: health-check.file-access.file-access-total.access-count-total-rate
  FAILED: 0.016666667 < 1.063333: health-check.file-io-operations.file-io-operations-total.close-call-total-rate
  FAILED: 0.016666667 < 1.063333: health-check.file-io-operations.file-io-operations-total.open-call-total-rate
  FAILED: 0.016666667 < 1.049999: health-check.file-io-operations.file-io-operations-total.read-call-total-rate
  FAILED: 0.016666667 < 0.026667: 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
  FAILED: 0.0 < 0.013333: 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: 256.0 >= 0.0: health-check.network-connections.network-connections-total.receive-total-rate
  PASSED: 256.0 >= 0.0: health-check.network-connections.network-connections-total.send-total-rate
  PASSED: 0.25 >= 0.01: health-check.wakeup-events.wakeup-events-total.wakeup-total-rate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1360368/+subscriptions