GitLab

In my previous attemp to disable this here:
https://chromium-review.googlesource.com/c/chromium/src/+/1026155, there
was a typo and causes compile failure. I have a full build with this CL
and it works fine.

TBR=thestig@chromium.org
NOTRY=true

Bug: 836289
Change-Id: I92df34158b417b87adf48e9b8460d10171594a3e
Reviewed-on: https://chromium-review.googlesource.com/1024603
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553209}

This only contains the UI skeleton.

Bug: 835029
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I98f22b71dd3ab0a51e2f13ab96c54a011897a15d
Reviewed-on: https://chromium-review.googlesource.com/1016083
Commit-Queue: Yue Cen <rsgingerrs@chromium.org>
Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553208}

Bug: 836238
Change-Id: Ibec5500a6d9348a30009d3d6d97a51c38a8e64ef
Reviewed-on: https://chromium-review.googlesource.com/1026051Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553207}

These changes were scripted as part of the effort to restrict exposure of the
raw MessageLoop*.

Note that many static methods exposed on MessageLoopCurrent are also deprecated
so it is very well possible that this is migrating to an already deprecated
method.

The goal of this pass is to reduce usage of MessageLoop::current() (and
ultimately make it impossible to obtain the MessageLoop* statically).

As such I will not edit this CL unless the script did something logically wrong.
I defer to owners to fix highlighted usage of already deprecated APIs.

Possible script screw ups / things to look out for in this review:
 - Storing MessageLoopCurrent in a MessageLoop* variable or comparing it against
   one (I will go over that in a separate pass).

Includes should have been stripped if that was the last usage of message_loop.h
in that file.

Please CQ if LGTY

This CL was uploaded by git cl split.

R=vakh@chromium.org

Bug: 825327
Change-Id: Ic8c07068f4f567da6191716241a39fb3a68e6647
Reviewed-on: https://chromium-review.googlesource.com/1024318
Commit-Queue: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553206}

ChromeLauncherControllerTests have been updated to manifest v2.
Remove the allowance for manifest v1 extensions.

Bug: 816679
Change-Id: Ibe3aba811e68240bd5338aef9268af83bd611acc
Reviewed-on: https://chromium-review.googlesource.com/1026084Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553205}

Otherwise loads started right after calling abort() won't work.

Also simplify the watching logic in MojoBlobReader, to prevent hitting
DCHECKs in OnResponseBodyStreamReady.

Bug: 835928
Change-Id: I45eec517ccaf5f830101b6a02fce2fdcf696d17b
Reviewed-on: https://chromium-review.googlesource.com/1024315
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553204}

Bug:790520
Change-Id: If94cb97263cd69486ce25a63078739338d46ff5e

TBR=hzl@chromium.org
TBR=jbudorick@chromium.org

Change-Id: If94cb97263cd69486ce25a63078739338d46ff5e
Reviewed-on: https://chromium-review.googlesource.com/1026254
Commit-Queue: Zhiling Huang <hzl@chromium.org>
Reviewed-by: Zhiling Huang <hzl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553203}

Remove debug-build aslr policy-set test.  It's been failing all along,
but this is the first time we've turned on a debug Win bot.

Follow-up work / cleanup expected to follow.  Ref: crbug/834907

BUG=833648
TEST=sbox_integration_tests.exe, ProcessMitigationsTest.CheckWin8AslrPolicySuccess

Change-Id: I5bd538a1be03020b3dd4e355a3ebbd0a066adf7d
Reviewed-on: https://chromium-review.googlesource.com/1020153Reviewed-by: James Forshaw <forshaw@chromium.org>
Commit-Queue: Penny MacNeil <pennymac@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553202}

Otherwise it will trigger a gl_factory.cc assertion.

BUG=831168
TEST=chrome --in-process-gpu
R=oetuaho@nvidia.com

Change-Id: Ib50dd4350619d516d88bb30412d84a0f2644f1d5
Reviewed-on: https://chromium-review.googlesource.com/1024859Reviewed-by: Chris Blume <cblume@chromium.org>
Commit-Queue: Zhenyao Mo <zmo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553201}

And wires it up for WindowService on top of Aura. Another option is to
add a function to EnvObserver that is called anytime the mouse
location changes, but it didn't seem worth the extra complexity.

BUG=none
TEST=covered by tests

Change-Id: I83c426935b7c618351f5d5a786b8f9c4fc75fd59
Reviewed-on: https://chromium-review.googlesource.com/1024722
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553200}

Elements are possibly visible only if they ran the opacity computation
step.

BUG=835445
R=mthiesse

Change-Id: Ib45d933c36d509a8d0f224a1d2080fc88de78412
Reviewed-on: https://chromium-review.googlesource.com/1026071Reviewed-by: Michael Thiessen <mthiesse@chromium.org>
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553199}

Bug: 829697
Change-Id: Id67192084d36f8a730d05c9e0213893c7776ae6f
Reviewed-on: https://chromium-review.googlesource.com/1026194Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553198}

We trigger the Download Home IPH bubble as a callback on the IPH
initialization path.  However if the Activity is destroyed while we're
initializing, we end up accessing destroyed state, which ends up being
null.

This patch puts a guard in place to early-out if we get the
initialization callback and ChromeTabbedActivity is destroyed.

BUG=833747

Change-Id: I1824250f5ffae4c1232b8b04786214a37e1bc10b
Reviewed-on: https://chromium-review.googlesource.com/1022083Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553197}

Removes dynamic lib dependencies from clang, and shouldn't regress
functionality anyone uses.

Bug: none
Change-Id: I4f46af0364a8c6fb90a591c46a50e373e287ae5d
Reviewed-on: https://chromium-review.googlesource.com/1025648Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553196}

This reverts commit be5a2a38.

Reason for revert:

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

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

Sample Failed Step: compile

Original change's description:
> [cr-buildbucket] Clear 'cores' dimension for ios-* builders.
> 
> ios-* builders may run on a mix of VMs with cores:8 and Mac Mini's with cores:4.
> 
> Bug: 731546
> Change-Id: I056fbb5bd80ca50ef8005aa8bb99643853acd923
> Reviewed-on: https://chromium-review.googlesource.com/1024729
> Reviewed-by: Vadim Shtayura <vadimsh@chromium.org>
> Reviewed-by: Nodir Turakulov <nodir@chromium.org>
> Commit-Queue: Sergey Berezin <sergeyberezin@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#553160}

Change-Id: I0c984c1aae350b8ab59954d6602b7a689ffa40f1
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 731546
Reviewed-on: https://chromium-review.googlesource.com/1025284
Cr-Commit-Position: refs/heads/master@{#553195}

This CL is similar to https://codereview.chromium.org/2521793002. In order to
run this test on bots, we use base::LaunchUnitTestsSerially as a test runner.

Bug: 828176
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
Change-Id: I49f6331f04168b998edf5504a5c9b39c31e78784
Reviewed-on: https://chromium-review.googlesource.com/1023112
Commit-Queue: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Kuang-che Wu <kcwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553194}

Introduce BrowserContext::UniqueId() method that returns
a string, uniquely identifying the browser context.

This patch:
- re-pursposes BrowserContext's media_device_id_salt_ into the
  unique_id
- exposes the id as BrowserContext::UniqueId
- moves headless browser contexts to use BrowserContext::UniqueId()

BrowserContext::UniqueId() will be exposed in DevTools protocol to
support browser context management for the automation needs.

BUG=836272

Change-Id: Ic721d5b06aab555d9c3d47043f49ab02506f2b0b
Reviewed-on: https://chromium-review.googlesource.com/1025269Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Andrey Lushnikov <lushnikov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553193}

Fixed on https://crrev.com/551279

Tbr: yamaguchi-san
Bug: 836254,701922
Change-Id: I428256f41b8ac7c6119bf0e4ff209dbffdd8cb01
Reviewed-on: https://chromium-review.googlesource.com/1025853Reviewed-by: Noel Gordon <noel@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553192}

TBR=thestig@chromium.org
NOTRY=true

Bug: 836300
Change-Id: I7a60fad866a74518b2cd2bbd2921354bac5c22ea
Reviewed-on: https://chromium-review.googlesource.com/1024829Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553191}

https://skia.googlesource.com/skia.git/+log/af88ec371248..f50c283f0b53

$ git log af88ec371..f50c283f0 --date=short --no-merges --format='%ad %ae %s'
2018-04-24 angle-skia-autoroll Roll third_party/externals/angle2/ b3474d9d7..66410530a (1 commit)
2018-04-24 mtklein disable skcms on Android framework builds

Created with:
  roll-dep src/third_party/skia


The AutoRoll server is located here: https://autoroll.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=master.tryserver.blink:linux_trusty_blink_rel;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=stani@chromium.org

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

BUG=chromium:826527

Change-Id: I710b1712e016cd482c233fb930264128016c88bd
Reviewed-on: https://chromium-review.googlesource.com/1025102Reviewed-by: Ned Nguyen <nednguyen@google.com>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553189}

When it calls ReadFileToString() and fails, log the name of the file it
is trying to read.

BUG=826408

Change-Id: I546977b985c71cbd631820e7d7950b7f7449faba
Reviewed-on: https://chromium-review.googlesource.com/1024743Reviewed-by: Julia Tuttle <juliatuttle@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553188}

Also makes a small change to the GetWarmupURL() function in order to
allow this testing to work by preserving existing query params.

Cleans up a bit of whitespace in bypass.py

Bug: 724704
Change-Id: Ia84d1199911725684c00538f9ef651a427a9d279
Reviewed-on: https://chromium-review.googlesource.com/1024727
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553187}

See https://crrev.com/c/1024646 for the V8 side of this change.

Change-Id: I7638ff7ee0b8469be704a71b6e6968b35d2e855b
Reviewed-on: https://chromium-review.googlesource.com/1025181Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Eric Holk <eholk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553186}

This reverts commit 0b61ff47.

Reason for revert: <INSERT REASONING HERE>

Original change's description:
> Disable DeleteActiveSession on Win
> 
> TBR=thestig@chromium.org
> NOTRY=true
> 
> Bug: 836289
> Change-Id: I669edb4d3ec8af8e144e5fac812ed0b1422e5e55
> Reviewed-on: https://chromium-review.googlesource.com/1026155
> Commit-Queue: Xida Chen <xidachen@chromium.org>
> Reviewed-by: Xida Chen <xidachen@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#553165}

TBR=thestig@chromium.org,xidachen@chromium.org

Change-Id: I6b1f989a749c7cbda554d5d8b4ccee735ded64e7
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 836289
Reviewed-on: https://chromium-review.googlesource.com/1026132Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553185}

The URL bar color should animate when switching to and from incognito
mode.

BUG=836236
R=asimjour

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.chromium.linux:linux_vr
Change-Id: I4bd0eda60d5bc0852dfc739e5fd20c5b6c970291
Reviewed-on: https://chromium-review.googlesource.com/1025955Reviewed-by: Amirhossein Simjour <asimjour@chromium.org>
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553184}

The LSI allocators previously did not store a copy of the last generated
LSI. As a result, many call sites would have to keep their own copies.

Now that the LSI allocators have their own copies, the call sites can be
updated to no longer store a separate copy.

DirectLayerTreeFrameSink is one such call site.

BUG=759031

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

Animating multiple effects is not fully supported yet (tracked via
crbug.com/767043). For origin trial we should log a warning when an
array with multiple effects is passed to the WorkletAnimation
constructor.

Bug: 834456
Change-Id: Ie0a37e0d36464e595b54f140d2e3f3331280dd61
Reviewed-on: https://chromium-review.googlesource.com/1024952
Commit-Queue: Yi Gu <yigu@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553182}

Bug: b/78182827
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester
Change-Id: If2a6eea9db1b80c15e05ff0e33767367e1e472e5
Reviewed-on: https://chromium-review.googlesource.com/1025642Reviewed-by: Andrei Kapishnikov <kapishnikov@chromium.org>
Commit-Queue: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553181}

Reland https://crrev.com/c/1000487.

Remove HttpStreamFactory interface, also rename HttpStreamFactoryImpl to
HttpStreamFactory.

Bug: 829429
Change-Id: I298879817785174d1d7290520f889f0252074e14
Reviewed-on: https://chromium-review.googlesource.com/1023321
Commit-Queue: Bence Béky <bnc@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553180}

This reverts commit 89dbe1f8.

Reason for revert: This needs to be merged together with upstream rolldeps

Original change's description:
> Fix build errors with upstream libassistant change
> 
> Test: build locally with upreved libassistant
> Bug: None
> Change-Id: I3db67f5a77824fcf0831447f353baba6167b0801
> Reviewed-on: https://chromium-review.googlesource.com/1025268
> Reviewed-by: Muyuan Li <muyuanli@chromium.org>
> Commit-Queue: Muyuan Li <muyuanli@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#552972}

TBR=xiaohuic@chromium.org,muyuanli@chromium.org

Change-Id: I9b3b13b11381b3100203428343251d2522b1c638
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: None
Reviewed-on: https://chromium-review.googlesource.com/1026131Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553179}

TBR=thestig@chromium.org
NOTRY=true

Bug: 836297
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I775ed2b20cd8ffb4503505aa9e63290e8d92de1c
Reviewed-on: https://chromium-review.googlesource.com/1026160
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553178}

When the network service is restarted, the disk cache entry may be
not be recovered, for reasons that aren't completely clear (corruption?
disk contention?), which causes the test to flake.  This CL modifies
the test to not fail in that case.

Bug: 836073
Change-Id: I3eedeceae6145b1d386749125c8232d552be8308
Reviewed-on: https://chromium-review.googlesource.com/1025646
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553177}

Reason: they are flaky.

TBR=rouslan@chromium.org
NOTRY=true

Bug: 836027
Change-Id: I93d5903a0d2d4bd1cbed6257dd4887924b2a84fd
Reviewed-on: https://chromium-review.googlesource.com/1025775Reviewed-by: Egor Pasko <pasko@chromium.org>
Commit-Queue: Egor Pasko <pasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553176}

Remove prefs::kPasswordProtectionEnterpriseName and
~EnterpriseEmailDomain to eliminate the mis-configuration by admins.

Instead, deriving enterprise organization name from AccountInfo.email. If it
is not available, use generic term "your organization" instead.

This CL also simplifies the trigger logic by not comparing logged-in domain
with enterprise email domain, since the org name string derived from
logged-in account should be always correct.

Bug: 824501
Change-Id: Ie8c82940774d35783f14ce500742d1e3db74ff7d
Reviewed-on: https://chromium-review.googlesource.com/1022732Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: Nathan Parker <nparker@chromium.org>
Commit-Queue: Jialiu Lin <jialiul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553175}

https://chromium.googlesource.com/angle/angle.git/+log/b3474d9d77de..66410530a78d

$ git log b3474d9d7..66410530a --date=short --no-merges --format='%ad %ae %s'
2018-04-20 lucferron Vulkan: Textures mipmaps support

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=geofflang@chromium.org

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

The test fails in official builds (see bug). Probably this is due to
fieldtrial_testing_config.json not affecting official builds, and so
the feature needs to be explicitly enabled in the test fixture, perhaps
similarly to https://crrev.com/452026

Bug: 834010
Change-Id: If0909e90d03f05596cc44f3a1022a0f5eca66762
Reviewed-on: https://chromium-review.googlesource.com/1026113Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553173}

Removes usages of the stream for loading the main resource response
in the renderer process.

Other CLs:
  1) https://chromium-review.googlesource.com/c/chromium/src/+/1015005
* 2) https://chromium-review.googlesource.com/c/chromium/src/+/1021631
  3) https://chromium-review.googlesource.com/c/chromium/src/+/1022790
  4) https://chromium-review.googlesource.com/c/chromium/src/+/1024038

Bug: 705744
Change-Id: I2fa52775d24f12d16c71f615f0c9d7618d1edb1e
Reviewed-on: https://chromium-review.googlesource.com/1021631
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553172}

The listed test suites appear most frequently in the immediate history of bots
prior to windowserver deaths. See the linked bug for details.

Bug: 828031
Change-Id: I0f8a4937fff23a94a628493331dc51191de5b072
Reviewed-on: https://chromium-review.googlesource.com/1025638
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553171}

In skia, getTextureHandle is deprecated and this change moves to using the
new API.

Change-Id: I69b507744e21187cfa9da74a960e5394acb2b524
Reviewed-on: https://chromium-review.googlesource.com/1024370Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Commit-Queue: Greg Daniel <egdaniel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553170}