GitLab

A previous CL addressed the inconsistency in how throttleable
outstanding requests were counted when transistioning between life cycle
states. This caused memory perf tests to regress because more low/medium
requests were throttled due to high priority requests being counted.

While the change made the counting scheme more consistent, it likely
should be reverted and re-landed behind a field trial of some sort.

Bug: 862365
Change-Id: I525058198ccf5b65aa8c754aca776c74295351e6
Reviewed-on: https://chromium-review.googlesource.com/1132471Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574025}

Bug: 856530
Change-Id: I8da043903712003379603b443ad2c584ebc1c244
Reviewed-on: https://chromium-review.googlesource.com/1131022Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574024}

This benchmark is no longer necessary now that we are no longer using
ground-truth power in our integration testing.

Bug: 859514
Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi
Change-Id: I9d9fd8d5a629d903e38a9ad5d5e03a2fda58c650
Reviewed-on: https://chromium-review.googlesource.com/1130008
Commit-Queue: Charlie Andrews <charliea@chromium.org>
Reviewed-by: Emily Hanley <eyaich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574023}

This migrates SyncEngine from using

net::NetworkChangeNotifier to content::NetworkConnectionTracker, which

works with the network service enabled.

Bug: 859139
Change-Id: I8ec4d755c0a6ec854403f66d89ad22a6be47f467
Reviewed-on: https://chromium-review.googlesource.com/1123712
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Reviewed-by: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574022}

Fixes two broken WebXR tests that verify the Daydream controller's app
button behavior. The condition that they checked after pressing the
button was not changed as part of the AR test patch, so they always
failed.

TBR=mthiesse@chromium.org

Change-Id: Ibbee773352e18ea65018101057be08adc6ba190a
Reviewed-on: https://chromium-review.googlesource.com/1132563Reviewed-by: Brian Sheedy <bsheedy@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574021}

Change-Id: I53f92d7b6f9b7dfc7f698018896c6a28703e10b1
Reviewed-on: https://chromium-review.googlesource.com/1132481
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574020}

The reported bug uncovered an issue about non-full-width overlay panel
having a wrong, full width when toggling (or resizing while in)
multi-window mode. The new panel width calculated from the new size
should have been used, but the raw, full width value was passed to
resizing logic of the content layer. This is a new corner case where
non-full-width overlay panel is preserved across size change.

This CL fixes it to ensure that the right values from
|OverlayPanelBase.getContentView{Width|Height}Px()| are used.
Also did a cleanup removing some dup'ed codes and combined WebContents/
native backing size updates as they are always done together.


Bug: 855386
Change-Id: I0a982dd21a083bbec7b9e0d5838a866ebcce31cb
Reviewed-on: https://chromium-review.googlesource.com/1127918Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574019}

Aligns with other service_worker directories.

Change-Id: I19396e65af847d38acf82f6a29ea4a302d12dd7a
Reviewed-on: https://chromium-review.googlesource.com/1131042
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574018}

This is the subpage for the multidevice settings UI. It will contain a
toggle for each individual feature in addition to some feature-specific
infrastructure (e.g. setup button, learn more link, password protection
of features). I will also have a toggle to disable all multidevice
features and a button to forget phone already set up on the account
(the subpage is only reached if there is a phone set).

Note that if the phone is not yet verified for multidevice features,
then individual feature toggles will not be shown.

Bug: 824568
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I29e8f9aa3d2801fb898eabf02adc2e79bd43ef5e
Reviewed-on: https://chromium-review.googlesource.com/1128334
Commit-Queue: Jordy Greenblatt <jordynass@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574017}

When navigating page inside the same renderer with browser-side
navigation, we are too late with unpausing the Page.

As a result, the page still considers itself paused and hits
a DCHECK in DocumentLoader::FinishedLoading.

R=dgozman

Change-Id: I0998b94c4a379c23bd44d56a6cb7c9fb4aa3bb5c
Reviewed-on: https://chromium-review.googlesource.com/1132378
Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574016}

Following up on r573982, looks like these tests are flaky on Linux Asan
as well. According to FindIt, the flakes are likely caused by
https://crrev.com/c/1131219 (r573789), so we should be able to revert
that CL and then revert this and r573982.

TBR=dtapuska@chromium.org, oysteine@chromium.org
BUG=862414

Change-Id: I88791155467f7808ca608a585fa8268a9f1afee0
Reviewed-on: https://chromium-review.googlesource.com/1132562Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574015}

Use Emulation.setDocumentCookieDisabled protocol method instead.

Change-Id: I0fa3832f1203e94d68159dd0e0100d7b77da04d9
Reviewed-on: https://chromium-review.googlesource.com/1132477
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574014}

Marked fixed in May, still in expectations as failing.

R: ikilpatrick@chromium.org
Bug: 443615
Change-Id: Id891ed123179388c392ba19fa1f52055c846e55e
Reviewed-on: https://chromium-review.googlesource.com/1132253Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Peter Mayo <petermayo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574013}

Move classes to anonymous namespace to make them local and avoid name
collision.

Bug: b/111212020
Test: Ran test on device and ensured correctness
Change-Id: I0250f294705eb24cc77c86d74b7d0991d0995757
Reviewed-on: https://chromium-review.googlesource.com/1132078Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Daniel Nicoara <dnicoara@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574012}

This is currently required (eg, because we depend on mailbox to surface
bridge).

Bug: 861866
Change-Id: Ie9d6a76a2f19d8645d25463d64c338f40554e56b
Reviewed-on: https://chromium-review.googlesource.com/1132392Reviewed-by: Bill Orr <billorr@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574011}

AudioPostProcessor2Shlib_Create is the new create function for V2 post
processors. The post processor name and header are defined in BUILD.gn.

Also add a function to check if a .so is a post processor library.
This will be used by TuningManager to query the available post
processors on a device.

Bug: internal b/109845931
Test: Tested on Joplin.
Change-Id: I3a75ae208c0275d7106392950d7a4eabf90d1de1
Reviewed-on: https://chromium-review.googlesource.com/1095128Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Chinyue Chen <chinyue@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574010}

This CL makes CronetURLRequestContext available to run network tasks in assigned
task runner instead of self-creating network thread.

Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ie6d3acf826313640c05ea63fe356dbc92487c7fc
Reviewed-on: https://chromium-review.googlesource.com/1122139Reviewed-by: Misha Efimov <mef@chromium.org>
Commit-Queue: Shenghuai Ji <shenghuai@google.com>
Cr-Commit-Position: refs/heads/master@{#574009}

The structure that tracks global binder overrides is not thread-safe.
This is fine because these overrides should be static for the life of
the browser. Some tests however configured these overrides after the
browser threads were started which the thread sanitizer complains about.

Bug: 853907
Change-Id: Ibf282aa403be37639261dab66c9c73a99b6fb767
Reviewed-on: https://chromium-review.googlesource.com/1121588Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574008}

We won't be able to preserve current implementation with network
service (although we could have a new one if needed).

Change-Id: I14ac498f0bf128b9d654ef781648aacc4349c63a
Reviewed-on: https://chromium-review.googlesource.com/1132326Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574007}

Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: If5cf7d3dcda8dc411c6c90de31885dca683354d8
Reviewed-on: https://chromium-review.googlesource.com/1130656Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574006}

By not including the entire svg sets from iron-icons/ the resulting
md_extensions/vulcanized.html file size reduced from 232.8 kB to
144.4 kB.

As a side clean-up thing, the "store" icon is removed from the icons.html
since it's no longer used.

Bug: 855205
Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Ia19bd8b61425cbff0e3d70cc08a1201856fe0276
Reviewed-on: https://chromium-review.googlesource.com/1123164
Commit-Queue: Scott Chen <scottchen@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574005}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/d07c1948..1fb73122

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I0489d7d416f3a55471063690969953f95b517c1f
Reviewed-on: https://chromium-review.googlesource.com/1132252Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#574004}

There are 3 changes make in hover-during-scroll.html:

1. update tests to use testharness.js
2. call rAFs before start input
3. use promise_test and gpuBenchmarking events

This should fix the hover-during-scroll.html flaky on virtual/threaded
test suites.

Bug: 841567
Change-Id: Idc46e81a3974e97478a871dc976af3acf7493269
Reviewed-on: https://chromium-review.googlesource.com/1130013Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Jianpeng Chao <chaopeng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574003}

- Add a clone method on DecryptConfig.
- This is required for later patches for decoders and CodecPictures to
  copy and own DecryptConfigs.

Bug: 820192
Change-Id: I5ae0826e86781d876af09509a9168e8a8e5be8a6
Reviewed-on: https://chromium-review.googlesource.com/1123767Reviewed-by: John Rummell <jrummell@chromium.org>
Commit-Queue: Rintaro Kuroiwa <rkuroiwa@chromium.org>
Cr-Commit-Position: refs/heads/master@{#574002}

This turns the existing WebAuthenticationTouchId feature into a
chrome://flags flag.

Bug: 678128
Change-Id: I8741f1d66409bdf636645c79cfb2145d679cb8d9
Reviewed-on: https://chromium-review.googlesource.com/1130699Reviewed-by: Kim Paulhamus <kpaulhamus@chromium.org>
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Cr-Commit-Position: refs/heads/master@{#574001}

Bug: 757933
Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi
Change-Id: Ifde7ff385e21fe71a6f19476109e5a53bc3e64c8
Reviewed-on: https://chromium-review.googlesource.com/1131222Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#574000}

These tests seem to be often missed once disabled, but they show
up as unexpected passes.

Bug: 626703
Change-Id: Ife2ea06ab41a5a6665b27101d98bebdb9978d1ab
Reviewed-on: https://chromium-review.googlesource.com/1131820Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Peter Mayo <petermayo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573999}

This migrates ForceSigninVerifier from using
net::NetworkChangeNotifier to content::NetworkConnectionTracker, which
works with the network service enabled.

Bug: 859136
Change-Id: I59bda75125f09664c5611fbebed89beb175ecc71
Reviewed-on: https://chromium-review.googlesource.com/1123695Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573998}

In order to assert |WorkerGlobalScope::url_| is non-empty
when referenced (which will be needed when Issue 861564 is
applied for module workers),
this CL removes cases where |url_| can be empty in unit tests.

Bug: 861564
Change-Id: I983f334ab866495a13a15e42805998359748b907
Reviewed-on: https://chromium-review.googlesource.com/1128518
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573997}

* Add RunnerImpl for servicing Runner FIDL requests.
* Add ComponentController class for managing the lifetime of connected
  Runner clients, and servicing ViewProvider::CreateView() calls.
* Add "runner" package, deployment scripts, etc.
* Modify ScopedServiceBinding to support multiple clients.

Bug: 856416
Change-Id: I1b3fd00e868f5eed6842f711986a13c0296a4c07
Reviewed-on: https://chromium-review.googlesource.com/1114377Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573996}

Bug: 844016
Change-Id: Ia1d3238506ff95c565a2bcf309d94da7b527e490
Reviewed-on: https://chromium-review.googlesource.com/1132519
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573995}

Bug: none
Change-Id: I759a442c973f85bd0363e1342d0e4ecfb9cf0fdc
Reviewed-on: https://chromium-review.googlesource.com/1132486Reviewed-by: Bret Sepulveda <bsep@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573994}

This reverts commit 764f213c.

Reason for revert:

Findit (https://goo.gl/kROfz5) identified CL at revision 573986 as the
culprit for failures in the build cycles as shown on:
https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzc2NGYyMTNjZGY2NWI2YWVhMTBmMmZkMjA4Yzg2NjEyZjk2MzkzMGEM

Sample Failed Build: https://ci.chromium.org/buildbot/chromium.linux/Linux%20Builder%20%28dbg%29%2832%29/84783

Sample Failed Step: compile

Original change's description:
> Implemented headless compositor protocol tests for basic rAF, GIF and CSS animations.
> 
> Browser flags that are required for BeginFrameControl are now set only
> for compositor specific tests thus preventing virtual time flakyness.
> 
> Change-Id: I79c1326fab0b4e90e35b12bdf31c665cdeeb0ec2
> Reviewed-on: https://chromium-review.googlesource.com/1132467
> Commit-Queue: Peter Kvitek <kvitekp@chromium.org>
> Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#573986}

Change-Id: I880408504b16822e278140a6f668220a6077455e
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/1131964
Cr-Commit-Position: refs/heads/master@{#573993}

https://android.googlesource.com/platform/external/perfetto.git/+log/5571a97fd12b..8049055c4260


git log 5571a97fd12b..8049055c4260 --date=short --no-merges --format='%ad %ae %s'
2018-07-10 michaschwab@google.com Create Canvas Controller


Created with:
  gclient setdep -r src/third_party/perfetto@8049055c4260

The AutoRoll server is located here: https://perfetto-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:111101128
TBR=perfetto-bugs@google.com

Change-Id: Ic4688114220b89684c9e9b73bc2355cac7d2099b
Reviewed-on: https://chromium-review.googlesource.com/1132434
Reviewed-by: <perfetto-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: <perfetto-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#573992}

* Move tests from http/tests/locks to external/wpt/web-locks
* Name with '.tentative' infix since this is still just a proposal
* Name most tests with '.https' infix since feature is [SecureContext]
   (and remove redirect-to-secure-host logic in tests)
* Consolidate window/worker interfaces test with '.any.js' variant
* Update paths to service worker helpers

Bug: 857265
Change-Id: Iaf254c5d53ff5b6bb65de4516df85307ad3a6519
Reviewed-on: https://chromium-review.googlesource.com/1118764
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573991}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/f9d85d8779cf..0664f1210277


git log f9d85d8779cf..0664f1210277 --date=short --no-merges --format='%ad %ae %s'
2018-07-10 dgarrett@google.com chrome_committer: Remove committer email argument.


Created with:
  gclient setdep -r src/third_party/chromite@0664f1210277

The AutoRoll server is located here: https://chromite-chromium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: Icbba1b121627de66e41ead1d98732a2255280b54
Reviewed-on: https://chromium-review.googlesource.com/1131962Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#573990}

This CL replaces base::Timer with its subclasses.
As base::Timer changes its behavior subject to its construction time
flags, that makes hard to see the actual timer behavior, especially
it's unclear when a timer is injected from other components.
Also, that OnceCallback support of base::Timer is hard to implement on
the dynamically determined invocation pattern.

Bug: 850247
Change-Id: If83f289ad4c284f21d297b813d7ad25e68a2dd5b
Reviewed-on: https://chromium-review.googlesource.com/1130561Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573989}

https://pdfium.googlesource.com/pdfium.git/+log/416cbeab1d93..144107d3ca6d


git log 416cbeab1d93..144107d3ca6d --date=short --no-merges --format='%ad %ae %s'
2018-07-10 hnakashima@chromium.org Create API for adding content marks and setting their params.


Created with:
  gclient setdep -r src/third_party/pdfium@144107d3ca6d

The AutoRoll server is located here: https://pdfium-roll.skia.org

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=dsinclair@chromium.org

Change-Id: I4f5b910fe1cebaddc6aaabcb61dd0ac768204d8d
Reviewed-on: https://chromium-review.googlesource.com/1132355Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#573988}

BUG=none
TEST=comment only change

Change-Id: Ie6f5d38f4d582f0f0bf580e9f73f3b0d96e18ce7
Reviewed-on: https://chromium-review.googlesource.com/1132463
Commit-Queue: Scott Violet <sky@chromium.org>
Commit-Queue: Michael Wasserman <msw@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573987}

Browser flags that are required for BeginFrameControl are now set only
for compositor specific tests thus preventing virtual time flakyness.

Change-Id: I79c1326fab0b4e90e35b12bdf31c665cdeeb0ec2
Reviewed-on: https://chromium-review.googlesource.com/1132467
Commit-Queue: Peter Kvitek <kvitekp@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573986}