Use polling to test Physical Web upgrade path

Use polling to test Physical Web upgrade path

Our upgrade test is failing on some devices.  It could be a race
condition that makes waitForIdleSync insufficient.  If this is
indeed the issue, using CriteriaHelper should fix the problem.

BUG=597316
Committed: https://crrev.com/fe8947ed378f5a0ba7c602dbae38864d73a6b0f1
Cr-Commit-Position: refs/heads/master@{#393352}

[cco3, 2016-05-12 00:36:06]

cco3@chromium.org changed reviewers:
+ mattreynolds@chromium.org

[cco3, 2016-05-12 00:38:23]

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

[mattreynolds, 2016-05-12 00:50:35]

lgtm

[cco3, 2016-05-12 00:50:58]

cco3@chromium.org changed reviewers:
+ nyquist@chromium.org

[nyquist, 2016-05-12 20:03:34]

lgtm for now, but it'd be nice to know why this fails. have you been able to
repro it locally on those versions android / those devices?

[cco3, 2016-05-12 20:24:46]

On 2016/05/12 20:03:34, nyquist wrote:
> lgtm for now, but it'd be nice to know why this fails. have you been able to
> repro it locally on those versions android / those devices?

I have not been able to repro.  I've been trying with L on a nexus 4, but no
luck.

[cco3, 2016-05-12 20:31:33]

The CQ bit was checked by cco3@chromium.org

[commit-bot: I haz the power, 2016-05-12 20:31:59]

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

[commit-bot: I haz the power, 2016-05-12 21:04:59]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-12 21:06:01]

Description was changed from

==========
Use polling to test Physical Web upgrade path

Our upgrade test is failing on some devices.  It could be a race
condition that makes waitForIdleSync insufficient.  If this is
indeed the issue, using CriteriaHelper should fix the problem.

BUG=597316
==========

to

==========
Use polling to test Physical Web upgrade path

Our upgrade test is failing on some devices.  It could be a race
condition that makes waitForIdleSync insufficient.  If this is
indeed the issue, using CriteriaHelper should fix the problem.

BUG=597316

Committed: https://crrev.com/fe8947ed378f5a0ba7c602dbae38864d73a6b0f1
Cr-Commit-Position: refs/heads/master@{#393352}
==========

[commit-bot: I haz the power, 2016-05-12 21:06:02]

Patchset 1 (id:??) landed as
https://crrev.com/fe8947ed378f5a0ba7c602dbae38864d73a6b0f1
Cr-Commit-Position: refs/heads/master@{#393352}