GitLab

https://skia.googlesource.com/skia.git/+log/a05e199cd962..2f54f2c31572

$ git log a05e199cd..2f54f2c31 --date=short --no-merges --format='%ad %ae %s'
2018-04-18 angle-skia-autoroll Roll third_party/externals/angle2/ aed1b56aa..c90d4d38c (2 commits)

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

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

This hardens the zip parsing code in the crazy linker
library to avoid integer type and overflow problems.

- Defines packed struct types for various ZIP records,
  and helper functions to read their fields more
  easily.

- Provides a MemoryRangeReader convenience class to
  ensure parsing the file data doesn't try to read
  values out of bounds, and check offsets / ranges
  properly.

FYI, another CL adds unit-tests to the zip parser, but the
code was split since it required other non-trivial changes
to other classes. See https://chromium-review.googlesource.com/c/chromium/src/+/911408

BUG=543292
R=palmer@chromium.org,rsesek@chromium.org,agrieve@chromium.org,pasko@chromium.org,rmcilroy@chromium.org

Change-Id: Ic378c83396eb124b9ef8c605f21c5fa5dcc8139a
Reviewed-on: https://chromium-review.googlesource.com/910852
Commit-Queue: David Turner <digit@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Egor Pasko <pasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551611}

This reverts commit 96b9e995.

Reason for revert: introduces memory leak on youtube.com test

First failling here:

https://ci.chromium.org/buildbot/chromium.linux/Leak%20Detection%20Linux/4115

Original change's description:
> [Spellcheck] Enable cold mode idle time spellchecker in M68
> 
> As previously planned, we will enable cold mode checker as bug fix to
> the current spellchecker, and will monitor its performance.
> 
> Bug: 824030, 716642
> Change-Id: Ie37a08fb6d5562d2f2ff2c2ac84e8033b6ffb776
> Reviewed-on: https://chromium-review.googlesource.com/1015790
> Reviewed-by: Kent Tamura <tkent@chromium.org>
> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#551558}

TBR=yosin@chromium.org,tkent@chromium.org,xiaochengh@chromium.org

Change-Id: I03087aad24d41208a56aa1904eb55c719e771578
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 824030, 716642
Reviewed-on: https://chromium-review.googlesource.com/1015363Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551610}

Traffic annotation auditor's tester on FYI bot is updated to return more
gracefull output if auditor cannot produce any result.

Bug: 690323
Change-Id: If39c0cf092010c43d4c8a5b26a786172ba3cf937
TBR: msramek@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1015901Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551609}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/bde5be65..f70a4135

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: Ie74203b7ebe4b3793a93bf51a5721dcd63aded81
Reviewed-on: https://chromium-review.googlesource.com/1015144Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551608}

There are two ToRtcOptinlal functions in the same jumbo build group,
and it breaks jumbo builders.

Bug: 834162
Change-Id: Id37adc6bef5ce4d0e38b8e564f3998d27084a53d
Tbr: sergeyu@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1016217Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551607}

external/wpt/service-workers/service-worker/ServiceWorkerGlobalScope/update.https.html
http/tests/fetch/serviceworker-proxied/thorough/redirect-credentials-base-https-other-https.html
http/tests/fetch/serviceworker/thorough/redirect-credentials-base-https-other-https.html
http/tests/fetch/window/thorough/redirect-credentials-base-https-other-https.html
http/tests/fetch/workers/thorough/redirect-credentials-base-https-other-https.html
virtual/outofblink-cors/external/wpt/service-workers/service-worker/ServiceWorkerGlobalScope/update.https.html

TBR=dcheng@chromium.org
NOTRY=true

Bug: 834183, 834185
Change-Id: I6eb3d60775dc18aea2339f1be17358d9a00e5e97
Reviewed-on: https://chromium-review.googlesource.com/1016340Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551606}

When UI Refresh is enabled, it is possible to enter fullscreen mode
when scrolling a loading page.

Bug: 824929
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I18f724182dc25fe4827b7299d82cc1b350b7f31e
Reviewed-on: https://chromium-review.googlesource.com/1013930Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551605}

Suppress fast/peerconnection/RTCRtpSender-setParameters-crash.html
timeout for Windows.

Bug: 834177
Change-Id: I7fc2b96ca0329da34cbdd4f969ffc34b0a85142e
Tbr: orphis@chromium.org
Notry: true
Reviewed-on: https://chromium-review.googlesource.com/1016225
Commit-Queue: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551604}

Bug: 832192, 833049
Change-Id: I9e4816bbe1fe071a55791d706017ea5efa4e87fa
Reviewed-on: https://chromium-review.googlesource.com/1015337Reviewed-by: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551603}

This reverts commit 953fcf3f.

Reason for revert: We want to set envvar directly.

Original change's description:
> Add disable_goma for args.gn on win
>
> Switching use_goma causes full rebuild due to command line update in build.ninja.
> I added disable_goma to set GOMA_DISABLED on environment.{x86,x64}.
>
> If we specify disable_goma=true, GOMA_DISABLED env is passed to gomacc.
> Then gomacc executes given argument instead of sending args to goma daemon.
>
> This will help toolchain maintainer to check difference of build behavior w/wo goma without rebuilding everything.
>
> Bug:
> Change-Id: Ie58958b5484d57be1c40fbbca363f1eef4b55c7e
> Reviewed-on: https://chromium-review.googlesource.com/768549
> Reviewed-by: Dirk Pranke <dpranke@chromium.org>
> Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
> Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#518134}

TBR=dpranke@chromium.org,brucedawson@chromium.org,tikuta@chromium.org

Change-Id: Ia2d510f4149b30cff3f8dc6c0b89e37190c39368
Reviewed-on: https://chromium-review.googlesource.com/1015860Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551602}

RenderCoordinates is now a public interface backed by its impl class
within content layer (RenderCoordinatesImpl) and makes some of its methods
accessible by embedders, such as view/viewport dimension and scroll
offset which are necessary for Android container view to work.

Also deleted unused fields/methods, turned some methods to private
for RenderCoordinatesImpl.

Bug: 598880
Change-Id: Iee9983f9eb71d46e3318be6c2a37260352832c1e
Reviewed-on: https://chromium-review.googlesource.com/1013670Reviewed-by: Maria Khomenko <mariakhomenko@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551601}

To better support network S13N, expose the CT log information
directly via the //net API, rather than constructing
CTLogVerifiers. This is part of an overall cleanup of the
ct_known_logs as part of uplifting it out of //net.

BUG=702062

Change-Id: I6abb95351d3b7c6c32c8247a03da55776d80b817
Reviewed-on: https://chromium-review.googlesource.com/1015061
Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551600}

Previously, storage::ObfuscatedFileUtil used a custom timer
implementation (TimedTaskHelper). Crash involving this custom timer
implementation have been reported (e.g. http://crash/e2c6ff1ef4863460).
Therefore, we are moving all uses of TimedTaskHelper to the well
maintained base::Timer.

Note: The TaskRunner passed to the TimedTaskHelper in
storage::ObfuscatedFileUtil was always the one on which the
storage::ObfuscatedFileUtil was used (as proved by added sequence
checker), so there is no need to an explicit call to
base::Timer::SetTaskRunner in this CL.

Bug: 760326
Change-Id: Iee641ca876560a60c91ce17397dbcfb39a4bfc35
Reviewed-on: https://chromium-review.googlesource.com/1012519
Commit-Queue: François Doray <fdoray@chromium.org>
Reviewed-by: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551599}

A number of CertDatabaseNSSTests were changed in 2012 to test
the wrong thing, after a certificate expired, rather than to
DISABLE the test.

This updates all of the expectations to match what they were
intended to test, using regular test certificates that can
be easily updated.

BUG=111029

Change-Id: If7fcb67a20f52fe551da53ea809274ee5775a8bf
Reviewed-on: https://chromium-review.googlesource.com/1012452
Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551598}

This is a reland of 031b31c4

Original change's description:
> DevTools: fix interception for <a download='...'> downloads with network service
> 
> Bug: 721408
> 
> Change-Id: I60f0cf81a69d7826d2043aa8222d2e69ff9e406a
> Reviewed-on: https://chromium-review.googlesource.com/1006231
> Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
> Reviewed-by: Min Qin <qinmin@chromium.org>
> Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#550690}

Bug: 721408
Change-Id: Ia02958bcecb911f288c30699e4b265574c8807e3
Reviewed-on: https://chromium-review.googlesource.com/1015852Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551597}

Safe Browsing private extension API make key Safe Browsing events
observable by Enterprise Reporting Extension (go/ent-rep-ext-dd).
These proposed APIs do not add or facilitate new functionalities
in the browser.
go/safebrowsing-ext-api

Note that, this CL doesn't trigger this API. Follow-up CL(s) will
handle the triggering part.

Bug: 806112
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I1da2b643eb3d4c8c35dc68480e94c08cfb723fad
Reviewed-on: https://chromium-review.googlesource.com/1005975
Commit-Queue: Jialiu Lin <jialiul@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551596}

... because they have quite different file locations due to data
dependency restriction.

Bug: 734095
Change-Id: I737e7a9f7edc3fb12ef14ccd025ff0afc6688535
Reviewed-on: https://chromium-review.googlesource.com/1013096
Commit-Queue: Xi Cheng <chengx@chromium.org>
Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551595}

This makes it a lot easier to do code search for blink_perf benchmark

Change-Id: Ib1257088c4eb99d0f61ebb8fc6dc511d748459aa
Reviewed-on: https://chromium-review.googlesource.com/1013150
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Reviewed-by: Emily Hanley <eyaich@chromium.org>
Reviewed-by: Charlie Andrews <charliea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551594}

Once crostini is already installed, it needs to be restarted after
Chrome shuts down. These restart steps are all very fast in the case that
the default vm and container are already running. If not, there can be
a several second delay. Launching crostini apps always goes through this
flow and testing shows the impact is not user-noticeable when the
vm and container are running.

A future CL will add an observer to the
CrostiniRestarter class for this case.

Bug: 832509
Change-Id: I359e5a25c30664fad6425c218853dda204c605d9
Reviewed-on: https://chromium-review.googlesource.com/1013804
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Timothy Loh <timloh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551593}

Make a transparent window, and use a zero overlap in InitInsets and UpdateInsetsForWindow
to avoid the window beneath not rendering anything.

Bug: 826617
Change-Id: I9b5e8140a6b9a9c481caf92ef3d244ffc14b64d8
Reviewed-on: https://chromium-review.googlesource.com/1013444
Commit-Queue: Jianzhou Feng <jzfeng@chromium.org>
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551592}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/adc953f927bd..85c75025906a

$ git log adc953f92..85c750259 --date=short --no-merges --format='%ad %ae %s'
2018-04-17 brucedawson Teach autoninja.py to support GOMA_DISABLED env var

Created with:
  roll-dep src/third_party/depot_tools


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

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

- The final piece in the jigsaw of migrating notification methods
over to mojo.

- Note this is still behind the NotificationsWithMojo feature flag.

R=peter@chromium.org

Bug: 796991
Change-Id: Ic590154af590595b122f33ab200be22a628b1d67
Reviewed-on: https://chromium-review.googlesource.com/1014042
Commit-Queue: Anita Woodruff <awdf@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Oliver Chang <ochang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551590}

Using wpt-import in Chromium bc3cd02b.
With Chromium commits locally applied on WPT:
303956b6 "Enable WPT tests for the Generic Sensor classes"
afb472c0 "Try to fix crash when terminating a worker while it is XHR-ing to a blob."


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/15738

Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

TBR=raphael.kubo.da.costa@intel.com

No-Export: true
Change-Id: I3dc0da8ef963cb600fbaa5caf4b6b8a3262c61bf
Reviewed-on: https://chromium-review.googlesource.com/1015334
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551589}

Notable changes:
. Use the regular aura-path for setting the LocalSurfaceId for the
  compositor, instead of specially setting it from WindowTreeClient,
  when the window-server sets the LocalSurfaceId with a bounds-change.
  WindowTreeHost::SetBoundsInPixels() is changed to take LocalSurfaceId
  as an input-param to facilitate this.
. When the client itself changes the size, do not set the LocalSurfaceId
  on the compositor multiple times for the same size from various places
  (e.g. WindowTreeHostMus, WindowTreeClient etc.).
. Add validation checks for ui::Compositor that a new LocalSurfaceId is
  assigned whenever the size changes. This makes it easier to catch
  errors earlier in the pipeline.

BUG=821987

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel
Change-Id: Ic9703c57b7a7f9ef2b65b34fa38c8ec7de9e9f36
Reviewed-on: https://chromium-review.googlesource.com/1014568
Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551588}

This CL removes the last static initializer on Mac.

The AtomicOps_Internalx86CPUFeatures structure used to be initialized at start
time.  I've changed it to be initialized lazily.  Code that used to look like:
  if (AtomicOps_Internalx86CPUFeatures.has_amd_lock_mb_bug)
will now look like:
  if (Get_AtomicOps_Internalx86CPUFeatures().has_amd_lock_mb_bug)

This structure is used in low-level atomic operations like compare-and-swap, so
performance is a priority.  In the fast case where the structure is already
initialized, the new implementation shouldn't require any additional cycles on
modern CPUs.

BUG=831951
R=pkasting

CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.android:android_archive_rel_ng;master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.win:win_archive;master.tryserver.chromium.win:win_x64_archive

Change-Id: I37166109190d7a764c4234e0de343360d18cfbab
Reviewed-on: https://chromium-review.googlesource.com/1015628Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551587}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/059b1287..bde5be65

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: Iae7c5b0f4356f1f808e55c7ea16f912ca0ce88e1
Reviewed-on: https://chromium-review.googlesource.com/1016044Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551586}

TBR=dpranke

Bug: 782863
Change-Id: I58d9133edb8ef51ab5cd3c6cf9fdb8684cc007b5
Reviewed-on: https://chromium-review.googlesource.com/1016172Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551585}

TBR=dcheng@chromium.org

Test: add a gesture event listener in a background page. Observe callback's gesture when performing various gestures on-device.
Change-Id: I539b57b987be9c5fbeeed095ecd5650fd8fe9da0
Reviewed-on: https://chromium-review.googlesource.com/1014629
Commit-Queue: David Tseng <dtseng@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551584}

https://skia.googlesource.com/skia.git/+log/c186e17a6b78..a05e199cd962

$ git log c186e17a6..a05e199cd --date=short --no-merges --format='%ad %ae %s'
2018-04-17 bungeman Remove text flag filtering from SkBitmapDevice.
2018-04-17 angle-skia-autoroll Roll third_party/externals/angle2/ 86de76b69..aed1b56aa (5 commits)
2018-04-17 reed show sum of cubic errors

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

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

https://pdfium.googlesource.com/pdfium.git/+log/aed62531a9b0..51a41ea222ee

$ git log aed62531a..51a41ea22 --date=short --no-merges --format='%ad %ae %s'
2018-04-17 tsepez Use span<> in GetBits32().
2018-04-17 tsepez XFA_XPDPacket_MergeRootNode is dead code, too.
2018-04-17 tsepez Base64 stuff is all dead code in cxfa_ffdoc.cpp
2018-04-17 dsinclair CFX_XML Cleanup
2018-04-17 dsinclair Add ownership to CFX_XMLNode children
2018-04-17 tsepez Avoid some string -> ptr -> string duplicate allocations in FF Environment

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: Iafe3ca2a954f1acd5788f1bcd910315154380bff
Reviewed-on: https://chromium-review.googlesource.com/1016168
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@{#551582}

Issue 831074 was resolved with a C++ fix, but there was a JS fix patch
prior to that that also fixed the problem. It was abandoned [1] but it
contained useful new comments + Closure annotations. Let's use them.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/1013823/18

Bug: 833834
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ic33a6f90ba99eedebc631dae09cb8bc45040fac9
Reviewed-on: https://chromium-review.googlesource.com/1014822Reviewed-by: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551581}

Change-Id: If39a65f4adea6aa57f8bc784e4e8e8e97d2d53f8
Reviewed-on: https://chromium-review.googlesource.com/1013785
Commit-Queue: Joey Scarr <jsca@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551580}

R=nednguyen@google.com, rmistry@chromium.org

Change-Id: Ia39c9f5217cc702c5db4689c45db22d8b1770071
Reviewed-on: https://chromium-review.googlesource.com/1015523Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551579}

Bug: 832192
Change-Id: Id3c33aebbd262c6b78f464cde1d201024309cf0e
Reviewed-on: https://chromium-review.googlesource.com/1015143Reviewed-by: Tatsuhisa Yamaguchi <yamaguchi@chromium.org>
Commit-Queue: Noel Gordon <noel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551578}

These are being added to the existing set of TypedArrays as part of
the BigInt proposal: https://tc39.github.io/proposal-bigint/
V8 implements and ships them already.

Bug: v8:6791, chromium:833489
Change-Id: I77b8620b5818efe94ecf47ecd17fbdb9124cd426
Reviewed-on: https://chromium-review.googlesource.com/1014670
Commit-Queue: Jakob Kummerow <jkummerow@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551577}

getMatchedCSSRules has been disabled by default since M63. It should be
ok to delete the corresponding code now. We also remove some unused
expectation files that we forgot to delete when we disabled the API.

This patch should land in M68.

Bug: 437569
Change-Id: I2789fb4546380e30849de6d579cd3329cdea8d3f
Reviewed-on: https://chromium-review.googlesource.com/1009505Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551576}

This CL makes DocumetnWebSocketChannel print line numbers to the console on
WebSocket connection failures in more cases.

WebSocket on Workers don't provide the line numbers on failures by default, so
WorkerWebSocketChannel::Fail() provides them in some way instead. With the
off-main-thread WebSocket is enabled, WebSocket on Workers goes through
DocumentWebSocketChannel, not WorkerWebSocketChannel, so this supplement doesn't
work and fails some layout tests. To fix it, this CL copies the logic from
WorkerWebSocketChannel::Fail() to DocumentWebSocketChannel::Fail().

This fix also improves console messages for WebSocket on Document. See changes
in *-expected.txt.

Bug: 825740
Change-Id: I0e2aee99700fe9af8a897a07202ca86f4faec811
Reviewed-on: https://chromium-review.googlesource.com/1013777Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551575}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/6e6b9f035719..6a93eff9ef52

$ git log 6e6b9f035..6a93eff9e --date=short --no-merges --format='%ad %ae %s'
2018-04-17 xixuan Add logging for errors in GetPackageDependencies.

Created with:
  roll-dep src/third_party/chromite
BUG=chromium:None


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: Id54435024d1977b30da42335c06f11e31ac43107
Reviewed-on: https://chromium-review.googlesource.com/1016136
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#551574}

Previously, storage::SandboxQuotaObserver used a custom timer
implementation (TimedTaskHelper). Crash involving this custom timer
implementation have been reported (e.g. http://crash/e2c6ff1ef4863460).
Therefore, we are moving all uses of TimedTaskHelper to the well
maintained base::Timer.

Note: The TaskRunner passed to the TimedTaskHelper in
storage::SandboxQuotaObserver was always the one on which the
storage::SandboxQuotaObserver was used (as proved by the
DCHECK(update_notify_runner_->RunsTasksInCurrentSequence()) at the top
of the method from which the timer is started), so there is no need to
an explicit call to base::Timer::SetTaskRunner in this CL.

Bug: 760326
Change-Id: I3e6c8955338437e99b7f6437ed2faf17b00038f8
Reviewed-on: https://chromium-review.googlesource.com/1012588
Commit-Queue: François Doray <fdoray@chromium.org>
Reviewed-by: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#551573}