ReReland ServiceWorkerCacheStorage::Keys function

ReReland ServiceWorkerCacheStorage::Keys function

Suppression (error hash=#E226F7559AD360E7#):
For more info on using suppressions see http://dev.chromium.org/developers/tree-sheriffs/sheriff-details-chromium/memory-sheriff#TOC-Suppressing-memory-reports
{
<insert_a_suppression_name_here>
Memcheck:Leak
fun:_Znw*
fun:_ZN4base8internal20PostTaskAndReplyImpl16PostTaskAndReplyERKN15tracked_objects8LocationERKNS_8CallbackIFvvEEESA_
fun:_ZN4base10TaskRunner16PostTaskAndReplyERKN15tracked_objects8LocationERKNS_8CallbackIFvvEEES9_
fun:_ZN10disk_cache15SimpleEntryImpl13CloseInternalEv
fun:_ZN10disk_cache15SimpleEntryImpl24RunNextOperationIfNeededEv
fun:_ZN10disk_cache15SimpleEntryImpl21DoomOperationCompleteERKN4base8CallbackIFviEEENS0_5StateEi
}
Original CL: https://codereview.chromium.org/477973002/
Reland: https://codereview.chromium.org/528233003/

The SimpleCache backend wasn't given a chance to finish up a close operation before the IO messageloop closed at the end of functions.  The tests now run the loop in TearDown.

The original patch is PatchSet1 and the fix is PatchSet3.

BUG=392621
Committed: https://crrev.com/bbfe6ce49b8e99b190085dffbf446b474c5f07ff
Cr-Commit-Position: refs/heads/master@{#294090}

[jkarlin, 2014-09-09 15:44:20]

Patchset #4 (id:60001) has been deleted

[jkarlin, 2014-09-09 21:11:04]

Patchset #3 (id:40001) has been deleted

[jkarlin, 2014-09-09 21:11:13]

Patchset #3 (id:80001) has been deleted

[jkarlin, 2014-09-09 21:11:22]

Patchset #3 (id:100001) has been deleted

[jkarlin, 2014-09-09 21:11:31]

Patchset #3 (id:120001) has been deleted

[jkarlin, 2014-09-09 21:15:24]

jkarlin@chromium.org changed reviewers:
+ horo@chromium.org, michaeln@chromium.org

[jkarlin, 2014-09-09 21:15:25]

michaeln@chromium.org: Please review changes in all

horo@chromium.org: Please review changes in all

Thanks so much!

[michaeln, 2014-09-09 21:53:48]

lgtm

[jkarlin, 2014-09-09 22:18:03]

The CQ bit was checked by jkarlin@chromium.org

[commit-bot: I haz the power, 2014-09-09 22:19:36]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jkarlin@chromium.org/543093003/140001

[commit-bot: I haz the power, 2014-09-10 00:58:16]

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

[commit-bot: I haz the power, 2014-09-10 00:58:17]

Try jobs failed on following builders:
  win_chromium_rel_swarming on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_...)

[jkarlin, 2014-09-10 02:06:56]

The CQ bit was checked by jkarlin@chromium.org

[commit-bot: I haz the power, 2014-09-10 02:10:10]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jkarlin@chromium.org/543093003/140001

[commit-bot: I haz the power, 2014-09-10 03:28:21]

Committed patchset #3 (id:140001) as 6352acb3779bdb6ea6ba5e46c2a3e8067489c037

[commit-bot: I haz the power, 2014-09-10 03:58:44]

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

[jkarlin, 2014-09-10 09:31:31]

On 2014/09/10 03:58:44, I haz the power (commit-bot) wrote:
> Patchset 3 (id:??) landed as
> https://crrev.com/bbfe6ce49b8e99b190085dffbf446b474c5f07ff
> Cr-Commit-Position: refs/heads/master@{#294090}

Looks like linux valgrind now passes but chromium valgrind still doesn't. 
Reverting once again.

[jkarlin, 2014-09-10 09:32:56]

A revert of this CL (patchset #3 id:140001) has been created in
https://codereview.chromium.org/562613002/ by jkarlin@chromium.org.

The reason for reverting is: Linux Valgrind now passes but ChromeOS Valgrind
doesn't.  Looks like I need to do more on TearDown..