Don't WaitForNavigate in memory.blink_memory_mobile benchmark.

Don't WaitForNavigate in memory.blink_memory_mobile benchmark.

Since https://codereview.chromium.org/2400123002 has landed, the navigate step
waits for an additional frame before returning. I suspect the redirect
navigations happen in that frame so when the page calls WaitForNavigate it'll
timeout.

BUG=655627
Committed: https://crrev.com/7319aef904a71aba9f710482b8372434b8227df6
Cr-Commit-Position: refs/heads/master@{#426480}

[bokan, 2016-10-19 17:43:27]

Description was changed from

==========
Don't WaitForNavigate in memory.blink_memory_mobile benchmark.

Since https://codereview.chromium.org/2400123002 has landed, the navigate step
waits for an additional frame before returning. I suspect the redirect
navigations happen in that frame so when the page calls WaitForNavigate it'll
timeout.

BUG=655627
==========

to

==========
Don't WaitForNavigate in memory.blink_memory_mobile benchmark.

Since https://codereview.chromium.org/2400123002 has landed, the navigate step
waits for an additional frame before returning. I suspect the redirect
navigations happen in that frame so when the page calls WaitForNavigate it'll
timeout.

BUG=655627
==========

[bokan, 2016-10-19 17:43:28]

bokan@chromium.org changed reviewers:
+ bashi@chromium.org

[bokan, 2016-10-19 17:46:02]

bashi@, you wrote this so I hope you're the right reviewer. The NavigateAction
now waits an additional frame which means the navigations complete before we
call WaitForNavigate so it'll time out. I think the right thing to do is just
remove the call, the test seems to work consistently for me when I do that.
WDYT?

Thanks.

[bashi, 2016-10-19 23:35:15]

non-owner lgtm

[bokan, 2016-10-20 14:25:52]

bokan@chromium.org changed reviewers:
+ nednguyen@google.com

[bokan, 2016-10-20 14:25:52]

+nednguyen@ for OWNER

[nednguyen, 2016-10-20 14:28:44]

lgtm

[bokan, 2016-10-20 14:29:01]

The CQ bit was checked by bokan@chromium.org

[commit-bot: I haz the power, 2016-10-20 14:29:15]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-20 15:26:25]

Description was changed from

==========
Don't WaitForNavigate in memory.blink_memory_mobile benchmark.

Since https://codereview.chromium.org/2400123002 has landed, the navigate step
waits for an additional frame before returning. I suspect the redirect
navigations happen in that frame so when the page calls WaitForNavigate it'll
timeout.

BUG=655627
==========

to

==========
Don't WaitForNavigate in memory.blink_memory_mobile benchmark.

Since https://codereview.chromium.org/2400123002 has landed, the navigate step
waits for an additional frame before returning. I suspect the redirect
navigations happen in that frame so when the page calls WaitForNavigate it'll
timeout.

BUG=655627
==========

[commit-bot: I haz the power, 2016-10-20 15:26:26]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-10-21 13:18:25]

Description was changed from

==========
Don't WaitForNavigate in memory.blink_memory_mobile benchmark.

Since https://codereview.chromium.org/2400123002 has landed, the navigate step
waits for an additional frame before returning. I suspect the redirect
navigations happen in that frame so when the page calls WaitForNavigate it'll
timeout.

BUG=655627
==========

to

==========
Don't WaitForNavigate in memory.blink_memory_mobile benchmark.

Since https://codereview.chromium.org/2400123002 has landed, the navigate step
waits for an additional frame before returning. I suspect the redirect
navigations happen in that frame so when the page calls WaitForNavigate it'll
timeout.

BUG=655627

Committed: https://crrev.com/7319aef904a71aba9f710482b8372434b8227df6
Cr-Commit-Position: refs/heads/master@{#426480}
==========

[commit-bot: I haz the power, 2016-10-21 13:18:26]

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