GitLab

Bug: 835950
Change-Id: I47800b90b1ec6b684d1d5f602b0beb84cb0919df
Reviewed-on: https://chromium-review.googlesource.com/1034208Reviewed-by: Michael Moss <mmoss@chromium.org>
Commit-Queue: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555244}

Previously, ParentLocalSurfaceIdAllocator would default to an invalid
LocalSurfaceId. A new LSI had to be explicitly allocated before the
normal behavior could use it.

With ParentLocalSurfaceIdAllocator now default initializing a valid LSI,
the various call sites no longer need to explicitly check for the
uninitialized state.

Blink's platform/graphics have some of those call sites.

BUG=837030

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: Ie8ec4f6d09e357e9433e583e0a79abb72de73385
Reviewed-on: https://chromium-review.googlesource.com/1038140Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Chris Blume <cblume@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555243}

R=abdulsyed@chromium.org

Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I746e2523b8735082fcb1cf14c3660908e918a3b7
Reviewed-on: https://chromium-review.googlesource.com/1038805Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555242}

Some users complain that the fullscreen exit UI (FAB X) doesn't go away
when they move their cursor to the top of the screen. This is a common
scenario where people play video or present slides and they just want
to keep their cursor on the top.

To fix this use case, this CL adds a 3s timeout to the exit UI. After
the UI times out, the user needs to move the cursor away from the
buffer area then move it back to the top to re-trigger the UI.

Bug: 835223
Change-Id: I43a652d83ffb539a89f9a0bcb81987c62d439edf
Reviewed-on: https://chromium-review.googlesource.com/1033483
Commit-Queue: Yuwei Huang <yuweih@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555241}

A fuchsia-specific change landed that caused webkit_lint to
fail on windows when it tried to instantiate a Fuchsia configuration.

This CL fixes a number of small issues that caused that failure,
so that things will work correctly in the same situation in the future.

R=jbudorick@chromium.org, kmarshall@chromium.org
BUG=838703

Change-Id: I796ff68b5138e4c31d56121e9a7fa751ade48543
Reviewed-on: https://chromium-review.googlesource.com/1038570Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555240}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/4973c626..fa6b64e1

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,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I9b238238ab208158bc60a469549f81b03fe675ff
Reviewed-on: https://chromium-review.googlesource.com/1038543Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555239}

This would help reduce the size of XML POST update check requests generated
by the update client. Without this change, the update client may generate
requests exceeding the size limit of the update server.

Bug: 722942
Change-Id: I1453e615a2271b8fd376b0706574b22b1d36e26d
Reviewed-on: https://chromium-review.googlesource.com/1033539
Commit-Queue: Minh Nguyen <mxnguyen@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555238}

https://chromium.googlesource.com/catapult.git/+log/4e78157a8a47..faa15b5e1038

$ git log 4e78157a8..faa15b5e1 --date=short --no-merges --format='%ad %ae %s'
2018-05-01 dtu [pinpoint] Ability to pin a Job to a commit and/or patch.

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-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=sullivan@chromium.org

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

The parameters construction order may be different as listed.
This avoids crash on Windows.

Bug: 782270
Change-Id: Ib318c3dc433e4bd5f7a58067acf92b7f500dec07
Reviewed-on: https://chromium-review.googlesource.com/1038143
Commit-Queue: Jinho Bang <zino@chromium.org>
Reviewed-by: Jinho Bang <zino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555236}

These tests needed to be marked as failing for the new virtual test
suite for video-surface-layer and it seemed as good to simply fix them.

Bug: 821025
Change-Id: I4e350f15a937bfcea80b61340573534ccada8022
Reviewed-on: https://chromium-review.googlesource.com/1035268
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555235}

The CVC fix flow ran from M62-M64 on Desktop (just M64 on Mac) but was
disabled in M65 with the launch of Partial Data Project, and can now be
removed entirely.

Bug: 812696
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I555d6ac0996e514702a21d39b0046c85681f4682
Reviewed-on: https://chromium-review.googlesource.com/1034103Reviewed-by: Sebastien Seguin-Gagnon <sebsg@chromium.org>
Reviewed-by: Rachel Blum <groby@chromium.org>
Reviewed-by: Evan Stade <estade@chromium.org>
Reviewed-by: John Wu <jzw@chromium.org>
Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Commit-Queue: Jared Saul <jsaul@google.com>
Cr-Commit-Position: refs/heads/master@{#555234}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/8b6d412457ea..4736430a2b1c

$ git log 8b6d41245..4736430a2 --date=short --no-merges --format='%ad %ae %s'
2018-05-01 chrome-bot Update config settings by config-updater.
2018-05-01 chrome-bot Update config settings by config-updater.
2018-04-28 dgarrett build_summary: Values can be string or int, handle both.
2018-04-23 levarum Reland: Copy ndk-translation artifacts when uprevving android
2018-04-19 guocb gs: support streaming cat a remote file

Created with:
  roll-dep src/third_party/chromite
BUG=chromium:837928,chromium:824580


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: Ib68f53f4e620c60580f627305744c1215c640935
Reviewed-on: https://chromium-review.googlesource.com/1038054Reviewed-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@{#555233}

Add UI integration tests for:
 - testScrollPageToTrigger
 - testShadowVisibleOnScroll
 - testInProductHelp
 - testMultiInstanceMode

And updated testEnterAndExitTabSwitcher.

BUG=835450

Change-Id: Ife58a7ba6dde69687d652f81fd2657cecdf5cb61
Reviewed-on: https://chromium-review.googlesource.com/1036795Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555232}

In interfaces that are used for sharing buffer handles, which currently can only be handles for SharedMemory, use a union struct media::mojom::VideoBufferHandle to allow the handle to be either for SharedMemory or for MailboxHolders.

Affected interfaces are:
video_capture::mojom::Receiver
media::VideoFrameReceiver
content::VideoCaptureControllerEventHandler
media::mojom::VideoCaptureObserver

Note: No update to interface media::VideoCaptureDevice::Client at this point,
because we are for now limiting this to virtual devices instead of also
including real webcams.

Design Doc: https://docs.google.com/document/d/1Vt8ME9foAR7vs9azwTP0mAQYUxAEbA1SOQ7hzrcXxP8/edit?usp=sharing

Bug: 834478
Change-Id: Iaabcbe54face7290ea6ee3dab058c10e11c69728
Reviewed-on: https://chromium-review.googlesource.com/1022175Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Yuri Wiitala <miu@chromium.org>
Reviewed-by: Olga Sharonova <olka@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Commit-Queue: Christian Fremerey <chfremer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555231}

BUG=

Change-Id: I89ccf891aa0673c49474e97c6b40781c798d1d5f
Reviewed-on: https://chromium-review.googlesource.com/1036479Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555230}

This test was failing on iOS devices.

TBR=vabr@chromium.org
NOTRY=true
NOPRESUBMIT=true

Bug: 838685
Change-Id: Ia394f3d1c1bd53057d03d0504088f2040b5e6c05
Reviewed-on: https://chromium-review.googlesource.com/1038606
Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org>
Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555229}

This was changed by r554983, which really should have only changed the
android OS check, as Linux builds also need to support NaCl toolchains
where current_os != "linux".

Bug: 822034
Change-Id: I5ca924516158bdd6228b947f32db6b614d1caacd
Reviewed-on: https://chromium-review.googlesource.com/1038430Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555228}

In the startup trace log from perf dashboard, there is some empty space
(~8 ms) between WebViewChromiumFactoryProvider.startYourEngines() and
WebViewChromium.ContentSettingsAdapter().

https://chromeperf.appspot.com/report?sid=5ae87c41efb3d436419396e0551577a6e5bb1dc9544c55bf0e2881db28ed54be

This is not reproducible in a local trace benchmark run.

checkThread() and WebViewContentsClientAdapter's constructor seem to be
the only methods that are called in between, but checkThread() doesn't
look like a culprit, so adding trace to the constructor to verify it.

BUG=817644

Change-Id: I80da1b0ea74e2c7f005398a0a54bde1d38296222
Reviewed-on: https://chromium-review.googlesource.com/1038225Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Changwan Ryu <changwan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555227}

Without this change, we're doing color transforms on
the multiplied-in alpha values, which is wrong.

Bug: 835322
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: I30a9533837f8d6392394eab9d859968cec93e4da
Reviewed-on: https://chromium-review.googlesource.com/1036618Reviewed-by: Fredrik Hubinette <hubbe@chromium.org>
Reviewed-by: ccameron <ccameron@chromium.org>
Commit-Queue: Fredrik Hubinette <hubbe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555226}

There are two different implementations of PlatformServiceBridge, both
called PlatformServiceBridgeImpl. (One is downstream.) This CL excludes
the class from the "multiple definitions" presubmit warning.

Bug: 838493
Change-Id: Iaef896f4f04c203497638af01d40f4aaee930919
Reviewed-on: https://chromium-review.googlesource.com/938305Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555225}

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I29acd26d754c1f79335090cae958d995ec691a3e
Reviewed-on: https://chromium-review.googlesource.com/1038575Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555224}

After https://codereview.chromium.org/1411203010, the RenderViewHost now
contains a pointer to RenderWidgetHost.

Bug: 419087
Change-Id: I5bf5d0ee5d434db478abb945afac0dc202176fa7
Reviewed-on: https://chromium-review.googlesource.com/1014305Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555223}

- Shelf stays with SHELF_AUTO_HIDE_ALWAYS_HIDDEN in tablet mode when
  running in a kiosk session;
- App window keeps the immersive mode disabled when entering tablet
  mode in a kiosk session;

Bug: 834058
Test: ash_unittests ShelfControllerAppModeTest.AutoHideBehavior and browser_tests ChromeNativeAppWindowViewsAuraAshBrowserTest.NoImmersiveModeWhenForcedFullscreen
Change-Id: I57cf9ac08fdc48c433dcb0d5c3f7c561041431c3
Reviewed-on: https://chromium-review.googlesource.com/1035522Reviewed-by: James Cook <jamescook@chromium.org>
Reviewed-by: Ben Wells <benwells@chromium.org>
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555222}

Monochrome.apk_Dex
        +2 entries fields
        +5 entries methods
        +1 entries types
        +1 entries strings
Monochrome.apk_Breakdown (+1,932 bytes)
        -2 bytes Zip Overhead
      +228 bytes Non-compiled Android resources size
       +76 bytes Package metadata size
      +126 bytes Java code size
    +1,504 bytes Compiled Android resources size
Monochrome.apk_Specifics
    +2,324 bytes normalized apk size
        +1 zip entries file count
      +392 bytes main dex size

Change-Id: I5ddb2a71e54303188cd651a029c383f950785f80
Reviewed-on: https://chromium-review.googlesource.com/1038346Reviewed-by: Filip Gorski <fgorski@chromium.org>
Commit-Queue: Sky Malice <skym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555221}

The mustash team is deprecating the current implementation of mus mode
(mojo window service on a background thread in the browser process).
We don't need to test this configuration any more.

Later CLs will clean up the test suite C++ code.

Bug: 838597
Change-Id: I1198adcb6e105f3c326f47356b5551221663ad0f
Reviewed-on: https://chromium-review.googlesource.com/1037663Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555220}

Store RTT observation buffers together in an array.
This makes it easier to combine various methods which will be
done in the next CL.

This CL does not change any functionality.

Change-Id: Iaa54895778b078640e6155f833d90903d733f391
Bug: 834119
Reviewed-on: https://chromium-review.googlesource.com/1034391
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555219}

Previously, ParentLocalSurfaceIdAllocator would default to an invalid
LocalSurfaceId. A new LSI had to be explicitly allocated before the
normal behavior could use it.

With ParentLocalSurfaceIdAllocator now default initializing a valid LSI,
the various call sites no longer need to explicitly check for the
uninitialized state.

LocalSurfaceIdProvider is one of those call sites.

BUG=837030

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: Ifec19249e74d2a705b54fec4d5d350ee435d87b0
Reviewed-on: https://chromium-review.googlesource.com/1036794
Commit-Queue: Chris Blume <cblume@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555218}

This cl sends a GFS with zero velocity in |OnAutoscrollStart| to make sure
that the GFC sent in |onAutoscrollEnd| doesn't get filtered. Processing the
GFC will generate a GSE with ends the current scroll sequence.

Bug: 829794
Test: WheelScrollingWorksAfterAutoscrollCancel
Change-Id: I929e473018f3de9ecf8fafb1f7b2e8e6a9adfd2f
Reviewed-on: https://chromium-review.googlesource.com/1026454
Commit-Queue: Sahel Sharifymoghaddam <sahel@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Reviewed-by: Sahel Sharifymoghaddam <sahel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555217}

This hides the flag from showing up in chrome://flags if the platform
itself does not have VM support. VM support is indicated by the
'Crostini' feature flag being passed into Chrome.

Bug: None
Test: Verified experimental-ui flag shows/hides based on Crostini flag
Change-Id: Ibebc731628e7f05efbbcc586fde923b7c0d30388
Reviewed-on: https://chromium-review.googlesource.com/1037915Reviewed-by: James Hawkins <jhawkins@chromium.org>
Reviewed-by: Nicholas Verne <nverne@chromium.org>
Commit-Queue: Jeffrey Kardatzke <jkardatzke@google.com>
Cr-Commit-Position: refs/heads/master@{#555216}

The new ServiceDirectory can be used to publish services for other
processes to consumer.
Also refactored GN templates in fuchsia-sdk to allow building FIDL
interfaces defined outside of the SDK and added a unittest that verifies
that a service published in ServicesDirectory can be consumed in
ComponentContext.

TBR=jam@chromium.org

Bug: 831384
Change-Id: Ie82e8cd6ff7c02a791ec8b5534f55a527b08a571
Reviewed-on: https://chromium-review.googlesource.com/1027126
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555215}

https://pdfium.googlesource.com/pdfium.git/+log/4bbbca4880fd..9294ffdf371f

$ git log 4bbbca488..9294ffdf3 --date=short --no-merges --format='%ad %ae %s'
2018-05-01 hnakashima Start at today's date in XFA Month Calendar.

Created with:
  roll-dep src/third_party/pdfium


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: Iaa9cb61af696dd11e77add3c1ac485e787ecdfda
Reviewed-on: https://chromium-review.googlesource.com/1038344
Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#555214}

Change-Id: I8b2889ac52df0e59413590002416c97434ca3cfb
Reviewed-on: https://chromium-review.googlesource.com/1036797
Commit-Queue: Matt Mueller <mattm@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555213}

Android component builds have .cr.so in library names.
Make the test for library name less strict by checking only for
substring match.

BUG=838544

Change-Id: If7958fdc70e8429e93aff098fcb8baca2ff6c456
Reviewed-on: https://chromium-review.googlesource.com/1038228Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555212}

In previous versions, the vibration feature was enabled with the
GamepadExtensions runtime feature flag. This CL splits the vibration
functionality into a separate flag that is enabled by default. This
allows the vibration feature to be enabled independently of other
features that use the same runtime flag.

BUG=749295

Change-Id: Ia8017e8b0ecd9df4490e8b205ecd1f49509c687b
Reviewed-on: https://chromium-review.googlesource.com/1027996Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Commit-Queue: Matt Reynolds <mattreynolds@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555211}

The configure scripts, used to generate many of the files in
source/config, have been removed from libaom in favor of cmake scripts.

Modify generate_gni.sh and BUILD.gn to accomodate.

However, the library is not ready to be updated yet, so keep these in
limbo.

Change-Id: I187c7877b3f3a5eadffb3d0055d9e3abf9d17b2a
Reviewed-on: https://chromium-review.googlesource.com/1038437
Commit-Queue: Johann Koenig <johannkoenig@google.com>
Reviewed-by: James Zern <jzern@google.com>
Cr-Commit-Position: refs/heads/master@{#555210}

Removing 622 unnecessary includes and adding 14 missing includes.

Script used @ https://crbug.com/825327#c155 (tweaked from https://crbug.com/825327#c151)

R=fdoray@chromium.org
TBR=jam@chromium.org

Bug: 825327
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_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;master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_mojo;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I943b9cd10d3c4ee7fb096c648a618a9a7032684c
Reviewed-on: https://chromium-review.googlesource.com/1035788
Commit-Queue: Gabriel Charette <gab@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555209}

Show the navigation time mark on the timeline.

Change-Id: I1d8d832f40b17094f84ef1b1ae366beabe6016ec
Reviewed-on: https://chromium-review.googlesource.com/1036619Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555208}

Also adds chrome_cleaner_unittests to run the added unit tests (only
enabled on the FYI bot for now). This is a separate test suite because
it will have Chrome Cleaner specific setup added to it as more tests
are added.

Bug: 830892
Change-Id: I33181ac5ad6bba893594838bf1cb77c83cfc69c5
Reviewed-on: https://chromium-review.googlesource.com/1024972
Commit-Queue: Joe Mason <joenotcharles@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Chris Sharp <csharp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555207}

https://chromium.googlesource.com/angle/angle.git/+log/41529e5e0f66..57d9cbb67f2d

$ git log 41529e5e0..57d9cbb67 --date=short --no-merges --format='%ad %ae %s'
2018-04-27 jmadill Sync individual attachments in RenderTargetCache.
2018-04-27 jmadill Vulkan: Add framework for internal shaders.

Created with:
  roll-dep src/third_party/angle


The AutoRoll server is located here: https://angle-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.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_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
TBR=cwallez@chromium.org

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

crrev.com/555016 changed the C++ browser-test-side code to use the name
LaunchExtension(), rather than InstallExtension(). Change the test code
JS command similarly, use launchProviderExtension.

Also make launchProviderExtension a separate getSetupSteps step because
chrome test.sendMessage always has a reply. We should await it and then
do the next step: setup that next step to call setupAndWaitUntilReady()
as before.

Covered by existing tests: Provider/FileManagerBrowserTest/Test.*

Bug: 833834,668680
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I0cffa47ae94e46699fd1e92d69dea946686d6ad1
Reviewed-on: https://chromium-review.googlesource.com/1036747Reviewed-by: Stuart Langley <slangley@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#555205}