GitLab

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/dad75d09..6acd03c9

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=luci.chromium.try:linux-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: I7411c73a9357b69d3661e71c560a794726c6dbc7
Reviewed-on: https://chromium-review.googlesource.com/c/1354234Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#611889}

Create styleguide_python and add myself.

Bug: None
Change-Id: Idb174184d4b4f5214423a0d1f5bea88dacb34505
Reviewed-on: https://chromium-review.googlesource.com/c/1354325Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611888}

https://android.googlesource.com/platform/external/perfetto.git/+log/fd13c06f14de..c959e1230546


git log fd13c06f14de..c959e1230546 --date=short --no-merges --format='%ad %ae %s'
2018-11-28 hjd@google.com Merge "perfetto-ui: Update events in record page"


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

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

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=perfetto-bugs@google.com

Change-Id: If00050bbb8048d81aedf4b7d1fc20489eb88f48d
Reviewed-on: https://chromium-review.googlesource.com/c/1354241Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#611887}

Bug: 909808
Change-Id: I6c93692b6700dd54331df4c22323f5a581ddd264
Reviewed-on: https://chromium-review.googlesource.com/c/1353951
Commit-Queue: Pavel Feldman <pfeldman@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611886}

Change MigrationBeforeHandshake2 to track explicitly labeled retried
connection. ConnectionOnNonDefaultNetwork will track those connection
that started on the default network but network change is encountered
during connection setup.

Additionally, add two more histograms
- MigrationBeforeHandshakeFailedReason will track the net error code
returned when an error is encountered by the new connection on the
alternate network;
- NetworkChangeDuringMigrationBeforeHandshake will track how often the
default network is changed during migration before handshake.

Bug: 790547
Change-Id: I3ebd0e6a05a1a56d45326917f341095594333564
Reviewed-on: https://chromium-review.googlesource.com/c/1352749Reviewed-by: Ryan Hamilton <rch@chromium.org>
Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Commit-Queue: Zhongyi Shi <zhongyi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611885}

This CL changes GeneratedBackgroundPageJob to not suspend file url requests when
the system suspends. There is no reason to suspend requests which don't require
network activity.

This helps solve bugs where extension event listeners are not registered as
the request for extension background pages are aborted on system suspend.

BUG=898494

Change-Id: I12c267322e28aee573c14160a91868b1cbec0a1b
Reviewed-on: https://chromium-review.googlesource.com/c/1352443
Commit-Queue: Karan Bhatia <karandeepb@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611884}

This enables GPU process VulkanSurfaces to present to Scenic views. Each
surface sends a message to the browser over mojo asking to export a node
to attach the surface resources to. Once this export occurs, the surface
contents will be visible in the global scene.

Bug: 861853
Test: run_content_shell \
  --enable-features=VizDisplayCompositor,UseSkiaRenderer,UseSkiaDeferredDisplayList,UiGpuRasterization,OzoneDrmMojo
  --enable-oop-rasterization --enable-vulkan --enable-gpu-rasterization \
  --enable-raster-to-sk-image --use-raster-context-provider \
  --force-gpu-rasterization --use-gl=swiftshader --no-sandbox \
  --disable-gpu-sandbox

Change-Id: Ib39c7f2a6bcb833fbd2cd3e0718229efb69ca940

Reviewed-on: https://chromium-review.googlesource.com/c/1343277Reviewed-by: Ken Rockot <rockot@google.com>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Robert Kroeger <rjkroege@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611883}

Bug: 907621
Change-Id: I543e58a273ab502f3526a7ac03d049c51cb4e50c
Reviewed-on: https://chromium-review.googlesource.com/c/1347448Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Kayce Basques <kayce@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611882}

Add state to support pausing a web audio device such that it can be
restarted when the frame is returned to be visible.

BUG=907125

Change-Id: I01aef9c19c81e35e68ee1e299e16cd6c9946ebde
Reviewed-on: https://chromium-review.googlesource.com/c/1344265Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611881}

MessageLoop will go away, eventually.

BUG=891670

Change-Id: I862c7162f8ce785e3533bb5869050b9047ffd317
Reviewed-on: https://chromium-review.googlesource.com/c/1352753
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611880}

This reverts commit 17b07c4c.

Reason for revert: Breaking chromeos_unittests, see https://crbug.com/909883

Original change's description:
> [CrOS MultiDevice] Fix crash in BleConnectionManagerImpl.
> 
> When a SecureChannel disconnects due to authentication failures,
> BleConnectionManagerImpl invokes the relevant failure callback, which
> then causes ConnectionAttemptBase to cancel the connection attempt.
> 
> When the attempt is cancelled, the SecureChannel object is deleted via
> BleConnectionManagerImpl::ProcessPotentialLingeringChannel(), but
> BleConnectionManagerImpl::HandleSecureChannelDisconnection() assumed
> that the object was still valid and tried to to remove itself as an
> observer, causing a segfault.
> 
> The fix is to check whether the object has been deleted before
> attempting to call RemoveObserver().
> 
> Bug: 905904
> Change-Id: Ic593ef4047ff481e218c89028324eb0863131cdc
> Reviewed-on: https://chromium-review.googlesource.com/c/1352855
> Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#611781}

TBR=khorimoto@chromium.org,hansberry@chromium.org

Change-Id: I575b604a98318f778cd1f7d93c31e14806da2e3f
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 905904
Reviewed-on: https://chromium-review.googlesource.com/c/1354327Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#611879}

Adds a ProtoDatabaseProvider(Factory) to provide ProtoDatabases with
the user directory, with ProtoDatabaseProvider as a
BrowserContextKeyedService.

Since ProtoDatabase is just an interface, and the underlying
implementation of it can vary from client to client, a
ProtoDatabaseWrapper that contains a pointer to a ProtoDatabase is
created, also built off ProtoDatabase.

Modifies the Feature Engagement Tracker to use the new provider for
its two databases.

Bug: 870813
Change-Id: I26376a14e8280605b7e3431862e5fe3ad6b9c8db
Reviewed-on: https://chromium-review.googlesource.com/c/1318053Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Commit-Queue: Troy Hildebrandt <thildebr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611878}

This is the second CL for web share target V2.

The goal of this CL is to implement the new web share target launcher according to the new web share target spec.
https://pr-preview.s3.amazonaws.com/ewilligers/web-share-target/pull/53.html#launching-the-web-share-target

There're three main parts of this CL that are put together:
1) Parse the fields received from the android manifest on the server-side
2) Perform the files-matching, which involves matching the share files with
   with share target files entries that accept the same mime type.
3) Launch the web share target. Specifically, this involves the additional step of
   generating the POST request. There're two possible encoding types for the POST request:
   Multipart/form-data encoding and application/x-www-form-urlencoded, both of which
   are implemented inside a new file named webapk_post_share_target_navigator.cc.
   It performs all the encoding/escaping needed for the two encoding methods.

One additional function is added to mime_util.cc in order to support the multipart/form-data POST request.

Change-Id: I719af0dc33fe64561963ae9aecc9d01192f1c17a
Reviewed-on: https://chromium-review.googlesource.com/c/1271776
Commit-Queue: Ethan Xu <xuethan@google.com>
Reviewed-by: Bence Béky <bnc@chromium.org>
Reviewed-by: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611877}

The underlying problem is how Chrome determines what action
mode should be shown on long press.  If you long press on
whitespace, then just the paste popup is shown.  If you long
press on text, then cut/copy/paste is shown.

On these test devices, it simply happened to touch on whitespace
where other devices would touch on the text based on the offsets
calculated.

This changes the bulk of the tests to not have whitespace at
all to avoid this.  For testLongPressInputWhileComposingText, it
just makes the first portion of the text very long to avoid the
mismatch (not fool proof, but better).

BUG=907573

Change-Id: I87fabd8d6fcc8a532976e2abe028e60664e3c7f5
Reviewed-on: https://chromium-review.googlesource.com/c/1353953Reviewed-by: Changwan Ryu <changwan@chromium.org>
Commit-Queue: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611876}

Disabling this prevents drawing the UI in the corner of an external
display at the internal display's size when closing the lid.

This makes the transition in this use case smoother, and also avoids
displaying uninitialized framebuffer contents on some gpus.

BUG=898524

Change-Id: Id23ef472ad7d7504c74644bd11186a4380e36f13
Reviewed-on: https://chromium-review.googlesource.com/c/1352709Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Commit-Queue: Drew Davenport <ddavenport@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611875}

After I changed the bypass policy for localhost, this test stopped routing through proxy.

Bug: 901896
Change-Id: I5f604865b60837143e7b2bc00c3dcbc9971c70c3
Reviewed-on: https://chromium-review.googlesource.com/c/1351145Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611874}

Change-Id: I65f32e69901e78bf56d028c5e09fcca3c964850c
Reviewed-on: https://chromium-review.googlesource.com/c/1352812Reviewed-by: Kyle Milka <kmilka@chromium.org>
Reviewed-by: Kristi Park <kristipark@chromium.org>
Reviewed-by: Gayane Petrosyan <gayane@chromium.org>
Commit-Queue: Ramya Nagarajan <ramyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611873}

This is the first patch that adds tests that start Service Manager and run
without full browser starts.

Bug: 904549
Change-Id: I713aa68ba5ce7af11075a73a4ff52303b3c013ec
Reviewed-on: https://chromium-review.googlesource.com/c/1332259
Commit-Queue: Xi Han <hanxi@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611872}

This is adding the interface changes, the code checking for corectedness,
does type conversion and checks for the edge cases mentioned in spec.

This is also adding WPT.

Bug: 907909
Change-Id: Ieebe5b25202a403e50a09576ac283690c0f0ba55
Reviewed-on: https://chromium-review.googlesource.com/c/1348972
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Chrome Cunningham <chcunningham@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611871}

Update the SurfaceControl ABI based on NDK changes and hook up
transaction acks from the framework for GLSurface swap acks.

Change-Id: I7919bbe97cc621c1912657ed4c1894ede8308fab
Bug: 889328
Reviewed-on: https://chromium-review.googlesource.com/c/1347792Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611870}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/dbc542d5f0f3..cbdf45b8cca9


Created with:
  gclient setdep -r src-internal@cbdf45b8cca9

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-chromium-autoroll

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

Change-Id: I460dbdd5c3a6ad7a866c63144ba5702325b51ef1
Reviewed-on: https://chromium-review.googlesource.com/c/1354299Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#611869}

Bug: 894513
Change-Id: Ic1d07c820cfce2aa4eae54a54e748fd0450ca7ab
Reviewed-on: https://chromium-review.googlesource.com/c/1347797Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: Carlos IL <carlosil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611868}

Change-Id: I69146b9a9a0bc750f37ef87083c146a62044018e
Reviewed-on: https://chromium-review.googlesource.com/c/1349949Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611867}

Bug: 396473
Change-Id: I372f2493d01ce4a2c3271bce9800451cff0cc63c
Reviewed-on: https://chromium-review.googlesource.com/c/1352614
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611866}

See skia cl https://skia-review.googlesource.com/c/skia/+/173226

Change-Id: Id097cfd805140a297dff07bbfae1037f2a18467a
Reviewed-on: https://chromium-review.googlesource.com/c/1352679Reviewed-by: Florin Malita <fmalita@chromium.org>
Commit-Queue: Mike Reed <reed@google.com>
Cr-Commit-Position: refs/heads/master@{#611865}

The code is not reachable in SPv2 mode. This check is a leftover
from an earlier iteration of the SPv2 implementation.

Change-Id: I3cbeb1f7e085bfab493130c1f2fe3aa1486a33e6
Reviewed-on: https://chromium-review.googlesource.com/c/1351807Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611864}

This does not appear to be used.

Bug: none
Test: compile

Change-Id: I4fd983a685ee9e1d493b34d542c3f40d9253643c

Reviewed-on: https://chromium-review.googlesource.com/c/1345417Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611863}

Page info no longer displays the number of bits of security, so we no longer
need the various security_bits fields contained in SSL structs.

Specifically, this patch removes security_bits from the following
structs/classes:
  * net::SSLInfo
  * content::SSLStatus,
  * security_state::VisibleSecurityState
  * security_state::SecurityInfo

Bug: 905692
Change-Id: Ia55be6573476453c8dfcabc7dcf36b9ddf27d290
Reviewed-on: https://chromium-review.googlesource.com/c/1338259
Commit-Queue: Daniel McArdle <dmcardle@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611862}

When the GPU process restarts we need to re-send the cursor bitmap since
all GPU process display state is lost.

It looks like it may have been broken all the way back to d818104f
("[Ozone-Drm] Notify cursor of channel established last"), which fixed a
different issue but also caused the message that was intended to restore
the cursor (in CommitBoundsChange) to not get delivered.

Reland fixing case where a GPU process connects and the cursor is not
placed because there are no displays to place it on. This should only
affects tests, because there's always at least one display on Chrome OS.

Bug: 908682
Test: kill $(pgrep -f type=gpu-process), cursor restored

Change-Id: I378d14e61c95822c2362d047123e5f7e40778a80
Reviewed-on: https://chromium-review.googlesource.com/c/1351143Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611861}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll

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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
TBR=cr-fuchsia+bot@chromium.org

Change-Id: Ia8469eb5c5803c4db403d682cd8f8bc84b4cf1c6
Reviewed-on: https://chromium-review.googlesource.com/c/1354300Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#611860}

This patch ensures that we don't accidentally use display locking in
mode 1, which isn't currently supported.

R=chrishtr@chromium.org

Bug: 882663
Change-Id: I2be26e2573ebe93a97bd6df4c8fcb7cd6221b28c
Reviewed-on: https://chromium-review.googlesource.com/c/1347102Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611859}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/e7e7a29184f5..4274496685fe


git log e7e7a29184f5..4274496685fe --date=short --no-merges --format='%ad %ae %s'
2018-11-28 cjmcdonald@chromium.org chromeos_config: Add grunt_march USE flag to grunt-release builder


Created with:
  gclient setdep -r src/third_party/chromite@4274496685fe

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

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: I77bf66ab3b0a8cab29348e22d27fb33a3c94cd26
Reviewed-on: https://chromium-review.googlesource.com/c/1354298Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#611858}

Add stats platform API for client and server side.

R=rch@chromium.org

Change-Id: Ic26e26b1e77916f1f76da3c7cb9b1b1cc43e3e8f
Reviewed-on: https://chromium-review.googlesource.com/c/1344193Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Dan Zhang <danzh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611857}

r562058 made the network process always run in a job object to try to avoid it outliving the browser process. This was added to make the network process quit sooner if there was a lot of pending I/O, which happened with layout tests. Windows before version 8 doesn't support nested job objects though, so we need to stop this mitigation for those old versions.

Bug: 904361
Change-Id: If75fc933052b1b7d4ef3d3e90664f777624c04d7
Reviewed-on: https://chromium-review.googlesource.com/c/1350977
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: James Forshaw <forshaw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611856}

Bug: 873719
Change-Id: I3b9a44f5fa1b9ec47acb429e9062fcd2fbbb8f27
Reviewed-on: https://chromium-review.googlesource.com/c/1347038Reviewed-by: Cait Phillips <caitkp@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Reviewed-by: agrieve <agrieve@chromium.org>
Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611855}

Bug: 901867
Change-Id: Ica4f7ef18854c726f678485ce045042b8d13fbc1
Reviewed-on: https://chromium-review.googlesource.com/c/1352334Reviewed-by: Michael Martis <martis@chromium.org>
Commit-Queue: anthonyvd <anthonyvd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611854}

https://chromium.googlesource.com/catapult.git/+log/6457c042bc7b..029a56af584c


git log 6457c042bc7b..029a56af584c --date=short --no-merges --format='%ad %ae %s'
2018-11-28 nednguyen@google.com Disable testSmokeStartingWebPageReplayGoServer


Created with:
  gclient setdep -r src/third_party/catapult@029a56af584c

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll

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

BUG=chromium:909746
TBR=sullivan@chromium.org

Change-Id: Iacd9bd664c2e2a236365c120bdc810ff8e31a873
Reviewed-on: https://chromium-review.googlesource.com/c/1354181Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#611853}

Also remove a bunch of usages of MockResourceContext that are no longer needed.

Bug: 908955
Change-Id: I3485595c83ef8e22f245c22c97775845c5e0e7fc
Reviewed-on: https://chromium-review.googlesource.com/c/1352035Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611852}

https://pdfium.googlesource.com/pdfium.git/+log/cb8a4ddc2277..b67698386664


git log cb8a4ddc2277..b67698386664 --date=short --no-merges --format='%ad %ae %s'
2018-11-28 asweintraub@google.com Fix for a bug where no valid codepoints are recognized in certain PDFs.


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

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

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:909762
TBR=dsinclair@chromium.org

Change-Id: Ib6b3b5038a133df9fcfc404253a3de0e5756b205
Reviewed-on: https://chromium-review.googlesource.com/c/1352868Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#611851}

Change-Id: I6fe3dd94a248914cd3f86339f7a152fdda3886d0
Reviewed-on: https://chromium-review.googlesource.com/c/1353033Reviewed-by: Andrew Moylan <amoylan@chromium.org>
Commit-Queue: Charles . <charleszhao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611850}