predictors: Wait for the cache cleaning synchronously.

predictors: Wait for the cache cleaning synchronously.

chrome::ClearCache() is asynchronous so there was possibility that cache is
cleared after prefetching causing flakiness.
This problem was almost hidden by that fact that the last navigation (after
prefetching) also caused prefetching. So the probability that cache is cleared
after the second prefetching was even less.
This CL also changes command line flag to disable the second prefetching because
it only tangles the tests.

BUG=650253
Committed: https://crrev.com/f15203e94ad5245c9ab50fbc0e1385ef403d0903
Cr-Commit-Position: refs/heads/master@{#440379}

[alexilin, 2016-12-21 17:26:40]

Description was changed from

==========
predictors: Wait for the cache cleaning synchronously.

chrome::ClearCache() is asynchronous so there was possibility that cache is
cleared after prefetching causing flakiness.
This problem was almost hidden by that fact that the last navigation (after
prefetching) also causes prefetching. So the probability that cache is cleared
after the second prefetching was even less.
This CL also changes command line flag to disable the second prefetching because
it only tangles the tests.

BUG=650253
==========

to

==========
predictors: Wait for the cache cleaning synchronously.

chrome::ClearCache() is asynchronous so there was possibility that cache is
cleared after prefetching causing flakiness.
This problem was almost hidden by that fact that the last navigation (after
prefetching) also caused prefetching. So the probability that cache is cleared
after the second prefetching was even less.
This CL also changes command line flag to disable the second prefetching because
it only tangles the tests.

BUG=650253
==========

[alexilin, 2016-12-21 17:28:34]

alexilin@chromium.org changed reviewers:
+ lizeb@chromium.org

[alexilin, 2016-12-21 17:28:34]

I created one more flaky test (yay!)
This is the fix...

[Benoit L, 2016-12-22 10:18:04]

lgtm, thanks.

[alexilin, 2016-12-22 10:33:00]

The CQ bit was checked by alexilin@chromium.org

[commit-bot: I haz the power, 2016-12-22 10:33:08]

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-12-22 11:09:37]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1482402780217760, "parent_rev":
"24f45ac60440a1b560f954facab4bc94d475f966", "commit_rev":
"0cc3e60d6a67632d14ba17ed57663faffe94a4c8"}

[commit-bot: I haz the power, 2016-12-22 11:10:05]

Description was changed from

==========
predictors: Wait for the cache cleaning synchronously.

chrome::ClearCache() is asynchronous so there was possibility that cache is
cleared after prefetching causing flakiness.
This problem was almost hidden by that fact that the last navigation (after
prefetching) also caused prefetching. So the probability that cache is cleared
after the second prefetching was even less.
This CL also changes command line flag to disable the second prefetching because
it only tangles the tests.

BUG=650253
==========

to

==========
predictors: Wait for the cache cleaning synchronously.

chrome::ClearCache() is asynchronous so there was possibility that cache is
cleared after prefetching causing flakiness.
This problem was almost hidden by that fact that the last navigation (after
prefetching) also caused prefetching. So the probability that cache is cleared
after the second prefetching was even less.
This CL also changes command line flag to disable the second prefetching because
it only tangles the tests.

BUG=650253

Review-Url: https://codereview.chromium.org/2596893002
==========

[commit-bot: I haz the power, 2016-12-22 11:10:06]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-22 11:12:36]

Description was changed from

==========
predictors: Wait for the cache cleaning synchronously.

chrome::ClearCache() is asynchronous so there was possibility that cache is
cleared after prefetching causing flakiness.
This problem was almost hidden by that fact that the last navigation (after
prefetching) also caused prefetching. So the probability that cache is cleared
after the second prefetching was even less.
This CL also changes command line flag to disable the second prefetching because
it only tangles the tests.

BUG=650253

Review-Url: https://codereview.chromium.org/2596893002
==========

to

==========
predictors: Wait for the cache cleaning synchronously.

chrome::ClearCache() is asynchronous so there was possibility that cache is
cleared after prefetching causing flakiness.
This problem was almost hidden by that fact that the last navigation (after
prefetching) also caused prefetching. So the probability that cache is cleared
after the second prefetching was even less.
This CL also changes command line flag to disable the second prefetching because
it only tangles the tests.

BUG=650253

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

[commit-bot: I haz the power, 2016-12-22 11:12:37]

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