The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/e2737cd317c5d95c395cedfc4e4d9a54bea7ea67

commit e2737cd317c5d95c395cedfc4e4d9a54bea7ea67
Author: Benjamin Gordon <bmgordon@chromium.org>
Date: Wed Oct 31 19:42:30 2018

power: Run a command after each suspend_stress_test iteration

When debugging suspend problems, it is useful to run some command to
examine the state of the system after each iteration.  This can be done
by running a command in a loop in a separate shell, but it's simpler and
more synchronized to just let suspend_stress_test do it.

Example usage:

$ suspend_stress_test --post_resume_command='grep MemFree /proc/meminfo' -c 2
Running 2 iterations with:
  suspend: 5-10 seconds
  wake: 5-10 seconds
  backup_rtc: false
  errors_fatal: true
  fw_errors_fatal: true
  bugs fatal:  true
  warnings fatal:  false
  crcs fatal:  true
  suspend command: powerd_dbus_suspend --delay=0
  wakeup source to ignore: none
  record_dmesg_dir:
  pm_print_times:  true
powerd start/running, process 19861
tlsdated stop/waiting
Suspend     1 of 2: sleep for  7 seconds...running grep MemFree /proc/meminfo
MemFree:          260824 kB
 wake for  6 seconds...
Suspend     2 of 2: sleep for  8 seconds...running grep MemFree /proc/meminfo
MemFree:          245292 kB

powerd start/running, process 20533
tlsdated start/running, process 20557

Finished 2 iterations.
Suspend_failures: 0
Firmware log errors: 0

BUG= chromium:898535 
TEST=ran suspend_stress_test

Change-Id: Ie1e2e6a332122c05a6996077da290f67f798a2b5
Reviewed-on: https://chromium-review.googlesource.com/1299758
Commit-Ready: Benjamin Gordon <bmgordon@chromium.org>
Tested-by: Benjamin Gordon <bmgordon@chromium.org>
Reviewed-by: Dan Erat <derat@chromium.org>
Reviewed-by: Martin Roth <martinroth@chromium.org>

[modify] https://crrev.com/e2737cd317c5d95c395cedfc4e4d9a54bea7ea67/power_manager/tools/suspend_stress_test