DeviceUtils.ForceStop: no-op if the app isn't running

DeviceUtils.ForceStop: no-op if the app isn't running

am force-stop takes > 1 second, so it's worth checking the app is even
running first.

BUG=540857
Committed: https://crrev.com/491f8007366e6505f46e98cef46283b366637202
Cr-Commit-Position: refs/heads/master@{#353876}

[agrieve, 2015-10-08 01:15:15]

agrieve@chromium.org changed reviewers:
+ jbudorick@chromium.org

[agrieve, 2015-10-08 01:15:19]

On 2015/10/08 01:15:15, agrieve wrote:
> mailto:agrieve@chromium.org changed reviewers:
> + mailto:jbudorick@chromium.org

[agrieve, 2015-10-08 01:15:23]

The CQ bit was checked by agrieve@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2015-10-08 01:15:33]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1398613002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1398613002/1

[commit-bot: I haz the power, 2015-10-08 04:21:30]

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

[commit-bot: I haz the power, 2015-10-08 04:21:31]

Dry run: This issue passed the CQ dry run.

[jbudorick, 2015-10-08 14:36:46]

lgtm pending the resolution of the RunShellCommand shell variables comment in
the other review.

[agrieve, 2015-10-08 15:46:06]

On 2015/10/08 14:36:46, jbudorick wrote:
> lgtm pending the resolution of the RunShellCommand shell variables comment in
> the other review.

Not sure we can come up with a solution that would simplify using variables
within script snippets. For script snippets, I think it's better to handle on a
case-by-case. Will wait till we resolve the other one though.

[agrieve, 2015-10-09 18:11:58]

On 2015/10/08 15:46:06, agrieve wrote:
> On 2015/10/08 14:36:46, jbudorick wrote:
> > lgtm pending the resolution of the RunShellCommand shell variables comment
in
> > the other review.
> 
> Not sure we can come up with a solution that would simplify using variables
> within script snippets. For script snippets, I think it's better to handle on
a
> case-by-case. Will wait till we resolve the other one though.

ok to go ahead with this?

[jbudorick, 2015-10-12 13:04:06]

On 2015/10/09 18:11:58, agrieve wrote:
> On 2015/10/08 15:46:06, agrieve wrote:
> > On 2015/10/08 14:36:46, jbudorick wrote:
> > > lgtm pending the resolution of the RunShellCommand shell variables comment
> in
> > > the other review.
> > 
> > Not sure we can come up with a solution that would simplify using variables
> > within script snippets. For script snippets, I think it's better to handle
on
> a
> > case-by-case. Will wait till we resolve the other one though.
> 
> ok to go ahead with this?

Yeah, still lgtm

[agrieve, 2015-10-13 15:12:47]

The CQ bit was checked by agrieve@chromium.org

[commit-bot: I haz the power, 2015-10-13 15:18:39]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1398613002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1398613002/1

[commit-bot: I haz the power, 2015-10-13 15:24:59]

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

[commit-bot: I haz the power, 2015-10-13 15:24:59]

Try jobs failed on following builders:
  ios_dbg_simulator_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_gn_rel on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_gn_r...)
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
  win8_chromium_ng on tryserver.chromium.win (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_ng/...)

[agrieve, 2015-10-13 19:36:57]

The CQ bit was checked by agrieve@chromium.org

[agrieve, 2015-10-13 19:36:57]

The patchset sent to the CQ was uploaded after l-g-t-m from
jbudorick@chromium.org
Link to the patchset: https://codereview.chromium.org/1398613002/#ps20001
(title: "rebase")

[commit-bot: I haz the power, 2015-10-13 19:41:58]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1398613002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1398613002/20001

[commit-bot: I haz the power, 2015-10-13 22:25:16]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-10-13 22:26:42]

Patchset 2 (id:??) landed as
https://crrev.com/491f8007366e6505f46e98cef46283b366637202
Cr-Commit-Position: refs/heads/master@{#353876}