SimpleCache: Port (unsequenced) use of SequencedWorkerPool over to TaskScheduler
This is what it does behind scenes in Chrome anyway, but always using the scheduler in tests as well is helpful since it means a single TaskScheduler::FlushForTesting() call rather than needing both TaskScheduler and SequencedWorkerPool versions of FlushForTesting() as separate calls, which causes trouble when control jumps back and forth between the two. Bug: 766221 Change-Id: Iab6a49cad86f1fd5a31c66c50d25e2962c538d53 Reviewed-on: https://chromium-review.googlesource.com/697925Reviewed-by:Asanka Herath <asanka@chromium.org> Reviewed-by:
Scott Graham <scottmg@chromium.org> Commit-Queue: Maks Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#506395}
Showing
Please register or sign in to comment