GitLab

Other similar targets under the //fuchsia directory are referred to as
"core" rather than "common". This target is renamed for consistency.

Bug: 922635
Change-Id: I84e54aa5183f7590f0caa88b0f943e88ee9aea56
Reviewed-on: https://chromium-review.googlesource.com/c/1489519
Commit-Queue: Kevin Marshall <kmarshall@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Kevin Marshall <kmarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636100}

Adds radio buttons to chrome://offline-internals to enable sending
X-Offline-Prefetch-Testing with GeneratePageBundle requests so that
prefetching can be tested in countries for which prefetching is
restricted (or so that the "forbidden" response can be tested from
Weblite-friendly countries).

Bug: 881120
Change-Id: I66d03d6f2cb71a06b08e5cd300e789bf60acc1c4
Reviewed-on: https://chromium-review.googlesource.com/c/1481951
Auto-Submit: Ian Wells <iwells@chromium.org>
Reviewed-by: Dan H <harringtond@google.com>
Commit-Queue: Ian Wells <iwells@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636099}

Bug: 934025
Change-Id: Ibad5ef62fa80c57be05fb145b3b44c70f2585ae4
Reviewed-on: https://chromium-review.googlesource.com/c/1479887
Commit-Queue: Robert Liao <robliao@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636098}

This is wired up as follows:
. ash::WmToplevelWindowEventHandler, which handles toplevel resizes/moving calls
  to aura::Window when the resize loop starts/end. Specifically
  NotifyResizeLoop*.
. aura::Window::NotifyResizeLoop* calls to WindowObserver::OnResizeLoop*.
. NativeWidgetAura gets overrides for OnResizeLoop* that calls to Widget
  functions (OnNativeWidget*UserBoundsChange).
. For the remote client case NonClientFrameController, which is a WidgetDelegate,
  forwards the calls to ws::TopLevelWindow.
. ws::TopLevelWindow trivials forwards the call to the remote client over mojom.
. WindowTreeClient (the remote client) forwards the calls to the aura::Window.
. DesktopWindowTreeHostMus (remote client) overrides the new WindowObserver functions
  and calls to the Widget.

This means we can collect metrics for window resizing on ChromeOS.

BUG=none
TEST=covered by tests

Change-Id: Iccfe3b769aa4a5813dde5571db4d29e6ef54125a
Reviewed-on: https://chromium-review.googlesource.com/c/1485128Reviewed-by: Chris Palmer <palmer@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636097}

A PortContext can refer to a render frame based context or a
Service Worker based context that is used to identify the source
of an extension messaging message. This CL changes render frame
based context identification to use PortContext and Service
Worker extension messaging will use the Service Worker
based context in future.

This CL does not introduce any behavior change, and only
provides the ability to specify a Service Worker endpoint for
messaging related IPCs and adds TODOs to places where it
will need to change in future.

Summary of IPC changes:
* renderer->browser: Related IPCs use PortContext as parameter
instead of frame routing id. This will facilitate specifying
an extension Service Worker or an extension render frame.
These are ExtensionHostMsg_OpenChannelTo* and
ExtensionHostMsg_{Open/Close}Port messages.
* browser-> renderer: These IPCs instruct renderer to validate,
open, or close a message port or deliver a message to a port.
This CL adds a worker thread id parameter to these IPCs so that
they can get routed to a Service Worker, or, if its value is
kMainThreadId, they get routed to a render frame. This CL does
not change existing behavior and always sends kMainThreadId as
the param value.

Bug: 925918
Test: No behavior change is expected.
Change-Id: I06c969b9251b06f184db98b465f7b08b24305157
Reviewed-on: https://chromium-review.googlesource.com/c/1455650
Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org>
Auto-Submit: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636096}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/0876951b..eabd978a

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: I9240493b73510390e2a8adff4b1d18bbce4db8cf
Reviewed-on: https://chromium-review.googlesource.com/c/1491791Reviewed-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@{#636095}

https://skia.googlesource.com/skia.git/+log/cc61a2caa270..34d13313235f


git log cc61a2caa270..34d13313235f --date=short --no-merges --format='%ad %ae %s'
2019-02-27 brianosman@google.com Particles: Improvements to SkCurve
2019-02-27 reed@google.com Avoid forcing rasterpipeline due to device colorspace
2019-02-27 kjlubick@google.com update canvaskit docs to new API
2019-02-27 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader ead1a345a36c..5edafb5ac109 (1 commits)


Created with:
  gclient setdep -r src/third_party/skia@34d13313235f

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;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: I133d1c2263a03e3bce305928ad92f8615d357e01
Reviewed-on: https://chromium-review.googlesource.com/c/1492173Reviewed-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@{#636094}

https://webrtc.googlesource.com/src.git/+log/1a7a4afd139e..48e7065ac6a3


git log 1a7a4afd139e..48e7065ac6a3 --date=short --no-merges --format='%ad %ae %s'
2019-02-27 eladalon@webrtc.org Remove default IDs for RTP extensions from rtp_parameters.h


Created with:
  gclient setdep -r src/third_party/webrtc@48e7065ac6a3

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I6a1768c6bafb0ba5bcdb850a47d03e1fb9381a27
Reviewed-on: https://chromium-review.googlesource.com/c/1491764Reviewed-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@{#636093}

This is a reland of https://chromium-review.googlesource.com/c/1388164
with a fix + hardening for a callback reentrancy bug. Diff patchset 1
to patchset 3 for the changes. Patchset 3 to 5 are rebase/commit message
changes.

This pushes the IO/UI hop to inside //content, which simplifies the
callers. (Every caller is actually a UI thread object with an ad hoc IO
thread proxy.) LoginDelegate itself is now uniquely-owned and the proxy
is moved to inside ResourceDispatcherHost on the ResourceLoader path. On
the network service path, we don't need a thread hop at all, so this
simplifies things and saves a UI/IO round-trip.

Bug: 908926
Change-Id: I2a38890f95b967f8739423d520e95a264289d267
Reviewed-on: https://chromium-review.googlesource.com/c/1457001Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Carlos IL <carlosil@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636092}

These shouldn't be NOTREACHED as they may be called from
TouchSelectionMenuRunnerChromeOS::OpenMenu. They may be called from
TouchSelectionMenuRunnerChromeOS as it's possible for
TouchSelectionControllerImpl to be supplied as the
ui::TouchSelectionMenuClient to TouchSelectionMenuRunnerChromeOS::OpenMenu, and
TouchSelectionMenuRunnerChromeOS calls these functions.

BUG=924360
TEST=none

Change-Id: I86e55842775542c95d6fa92137173e04f3085f0c
Reviewed-on: https://chromium-review.googlesource.com/c/1491900
Commit-Queue: Scott Violet <sky@chromium.org>
Commit-Queue: David Jacobo <djacobo@chromium.org>
Auto-Submit: Scott Violet <sky@chromium.org>
Reviewed-by: David Jacobo <djacobo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636091}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0c952caaabe0..65b79c43c5bc


Created with:
  gclient setdep -r src-internal@65b79c43c5bc

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: I8901a657435f5ffd983ab8e81a2e991cfd81b63a
Reviewed-on: https://chromium-review.googlesource.com/c/1492171Reviewed-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@{#636090}

Fullscreen window bounds should take into account the
bounds of the docked magnifier and the chromevox panel.
Otherwise, the window would be fullscreened using the
entire screen bounds, rather than the available space
left below the docked magnifier and chromevox panel.

BUG=868623
TEST=Added new test

Change-Id: Ibaef9910a39edad95138b8a9a9909cffc1dad16d
Reviewed-on: https://chromium-review.googlesource.com/c/1490903
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636089}

The exception type changed in Android O-MR1 in:
https://android-review.googlesource.com/c/platform/frameworks/base/+/394932
It went from IllegalArgumentException to TooManyRequestsException which isn't
an exposed class, so unfortunately we have to catch the broader shared parent
class, RuntimeException.

Bug: 931484
Change-Id: Id8bc1e674d2b674b4811829cad6db5d7cf24a0f8
Reviewed-on: https://chromium-review.googlesource.com/c/1470521
Auto-Submit: Paul Jensen <pauljensen@chromium.org>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636088}

Bug: 931806
Change-Id: I89db8c24edfb9a7e1c4c6bf3ac3d0faa68d70ca1
Reviewed-on: https://chromium-review.googlesource.com/c/1472450
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Ramya Nagarajan <ramyan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636087}

This CL is adding the FROM_HERE location of the call sites to each
ScopedBlockingCall. This modification will provide the
detailed location to the trace events and allow developpers do
understand cause of janks of long tasks.

This CL is adding manually the cases not caught by the previous CL:
  https://chromium-review.googlesource.com/c/chromium/src/+/1483834


TBR=gab@chromium.org

Bug: 934302
Change-Id: Id2b959ef007fd7fec6d5b7cf8373f93e816c8195
Reviewed-on: https://chromium-review.googlesource.com/c/1491896Reviewed-by: Gabriel Charette <gab@chromium.org>
Commit-Queue: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636086}

Bug: 897998
Change-Id: I4d3071a44efcbf539447b5cceb0e6430b3616e90
Reviewed-on: https://chromium-review.googlesource.com/c/1490500
Commit-Queue: Siyu An <siyua@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636085}

Change-Id: I8080c2db41db07908e4aaa76fb4138750a9a0eb8
Reviewed-on: https://chromium-review.googlesource.com/c/1478076
Commit-Queue: François Doray <fdoray@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636084}

This will enable tests to receive callback executions from FakeWebFrame
and configure what FakeWebFrame passes to callback. Also allows for
configuring CanCallJavascriptFunction to return false.

Change-Id: I5b84d88c2df0e30ec7d81b48b0cf9a5c66a18c51
Reviewed-on: https://chromium-review.googlesource.com/c/1482136
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636083}

Following bot results are included.
15799 15805 15821 15829 15836 15847 15852 15859

3 lines were removed and 6 lines were deflaked by consecutive
results since 15769.

TBR=eae@chromium.org, mstensho@chromium.org
NOTRY=true

Bug: 591099
Change-Id: I6e6567eb120e96817e6690cd5430b4ade409e324
Reviewed-on: https://chromium-review.googlesource.com/c/1489651Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636082}

This reverts ba496ac3.

BUG=936080,933153

Change-Id: Ic173698e5285806763606b5cf38d5078947df11f
Reviewed-on: https://chromium-review.googlesource.com/c/1489637Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Mike West <mkwst@chromium.org>
Auto-Submit: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636081}

PIN keyboard should only be visible when device is in tablet mode.
Update view layout and add handling of gestures to move focus of access
code input.

Bug: 911326
Test: ParentAccessViewTest
Change-Id: I66ac5a039549312d1686875478ae6fa743082bd5
Reviewed-on: https://chromium-review.googlesource.com/c/1480824Reviewed-by: Jacob Dufault <jdufault@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636080}

With CL [1], if a compositor animation was running, any changes
to transforms, filters, or effects were ignored during the animation,
including properties other than the ones being animated. For example,
if a transform animation was running, any changes to
backface-visibility would also be ignored, even though that change
is not handled by the compositor. With this CL, only changes to the
specific properties that can be animated on the compositor (e.g.
the transform matrix) will be ignored, while other changes will
still cause a commit.

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


Bug: 933141
Change-Id: If6be65239c20dd36e721e5cf4e84db992e7369c6
Reviewed-on: https://chromium-review.googlesource.com/c/1484072
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636079}

tbr: spqchan@chromium.org
Bug: 936475
Change-Id: I61678d76dfa7586a92872edca3fcc7131a604501
Reviewed-on: https://chromium-review.googlesource.com/c/1492231Reviewed-by: Ella Ge <eirage@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636078}

TBR: dgozman@chromium.org
No-Try: true
Bug: 936479
Change-Id: I57919f0358c30575a980377534a06b4e8ecf0760
Reviewed-on: https://chromium-review.googlesource.com/c/1492174Reviewed-by: Ella Ge <eirage@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636077}

A previous CL made the background color the same in all session states:
https://chromium-review.googlesource.com/c/chromium/src/+/1374197

BUG=920968

Change-Id: I50a781c9a16bf3490174d1b636bfb5a7b600561d
Reviewed-on: https://chromium-review.googlesource.com/c/1490893Reviewed-by: Manu Cornet <manucornet@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Tim Song <tengs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636076}

Bug: 927195
Change-Id: I8a6dbe9df6471cbb12f623fc359a88c6d1405a20
Reviewed-on: https://chromium-review.googlesource.com/c/1489177Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636075}

The indicator is confusing. Also, SingleProcessMash is about to enter
Finch dev trials and it will be even more confusing if the indicator
comes and goes.

"SingleProcessMash" still appears in about:version next to the platform
version. On test images, it also appears at the lock screen next to
that version number.

Bug: 924798
Change-Id: I481006b2a9ee88071aae3a8852467a7086e590f0
Reviewed-on: https://chromium-review.googlesource.com/c/1491767Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636074}

Bug: 915568
Change-Id: I827ee479965bba614e01a4dee3d1b117e7b031c6
Reviewed-on: https://chromium-review.googlesource.com/c/1480353Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Simon Que <sque@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636073}

This CL applies an Aria attribute onto the media (video/audio) to indicate
buffering.

Change-Id: I01032bb047316f4f0408f7c106f8fea0fab8ccbe
Reviewed-on: https://chromium-review.googlesource.com/c/1444612Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: CJ DiMeglio <lethalantidote@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636072}

This CL removes an odd but obsolete feature to the Chromium linker,
which added a 16 MiB guard region when loading a given native library.

This was done a long time ago when our build system used to process
'regular' shared libraries generated by the linker, in order to compress
relocations inside it using a custom scheme. Said relocations were
later uncompressed / processed at load time through a static C++
initializer.

The main drawback of this scheme was that it modified the
correspondance between virtual addresses in the ELF files, and their
actual mapped location. This created all kind of chaos for tools like
Breakpad, and the guard region was added to mitigate the issue.

This custom compression scheme has been completely discarded, in favor
of adding the necessary machinery to the linker itself, in order to
directly generate shared libraries with the right compressed
relocations (which are of course supported by the crazy linker), without
any virtual / mapping address space discrepancies.

As such, this trick is no longer needed, simplifying our code.

This will also make it considerably easier to implementing
android_dlopen_ext() in the crazy linker.

BUG=504410,936001
R=pasko@chromium.org, agrieve@chromium.org, cjgrant@chromium.org

Change-Id: I5a38b952442160072f0e24f48289f41f0269cdc6
Reviewed-on: https://chromium-review.googlesource.com/c/1491271Reviewed-by: David Turner <digit@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: David Turner <digit@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636071}

We believe that we're still seeing issues with setting new fields in
a protobuf storing information about metrics. This CL reverts setting
those fields, and one problematic place where we set a related boolean.

OmniboxEventProto.IsKeywordSuggestion - per suggestion
OmniboxEventProto.InKeywordMode - per navigation
OmniboxEventProto.KeywordModeEntryMethod - if previous field true

Original CL: 1351452

Bug: 934316
Change-Id: I099bec55826cb663dee449673a16f4ff1890e2da
Reviewed-on: https://chromium-review.googlesource.com/c/1481732Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: Kevin Bailey <krb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636070}

Use reftest-wait to avoid the test finishing too early.

Change-Id: I2f568e1b4fe55eccec9f07012d7c7f8f6b66fd15
Reviewed-on: https://chromium-review.googlesource.com/c/1491135
Auto-Submit: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636069}

Bug: 891339
Change-Id: I76dc38e26dd359c656e16910dfb1d317e2f64528
Reviewed-on: https://chromium-review.googlesource.com/c/1470691
Commit-Queue: Richard Knoll <knollr@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636068}

https://android.googlesource.com/platform/external/perfetto.git/+log/5450dc0a9c83..617f4eb4e5b7


git log 5450dc0a9c83..617f4eb4e5b7 --date=short --no-merges --format='%ad %ae %s'
2019-02-27 primiano@google.com Merge "Make Producer.CreateTraceWriter thread-safe"
2019-02-27 hjd@google.com perfetto-ui: Unify track and track group borders
2019-02-27 hjd@google.com perfetto-ui: Remove 'Tracks' header panel


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

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: Ib53566536d684e1cde9a19a2e84717a1d7d732be
Reviewed-on: https://chromium-review.googlesource.com/c/1491763Reviewed-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@{#636067}

Change-Id: I81198806879df502bc3eb1b7522330c3c4a82805
Reviewed-on: https://chromium-review.googlesource.com/c/1491553
Commit-Queue: Jordan Demeulenaere <jdemeulenaere@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636066}

R=drubery

Bug: 934060
Change-Id: Id95aeeead0dc3c5e60bf837d1bc8222385633471
Reviewed-on: https://chromium-review.googlesource.com/c/1490905
Auto-Submit: Varun Khaneja <vakh@chromium.org>
Commit-Queue: Daniel Rubery <drubery@chromium.org>
Reviewed-by: Daniel Rubery <drubery@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636065}

Bug: 739844
Change-Id: Icf443d02de9567e9f7aacfc04141551337fe8fbb
Reviewed-on: https://chromium-review.googlesource.com/c/1488926
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636064}

These tests were in http_proxy_client_socket_pool_unittest.cc.
Since the HttpProxyClientSocketPool has since been removed, they need
a new home. This CL moves them in with most of the other socket tagging
tests, in TransportClientSocketPool's unit test file.

This is part of an effort to flatten the socket pools.
https://docs.google.com/document/d/1g0EA4iDqaDhNXA_mq-YK3SlSX-xRkoKvZetAQqdRrxM/edit

Bug: 472729
Change-Id: Ibf5a26aef732108cb5e1cfedcaf92811387091e3
Reviewed-on: https://chromium-review.googlesource.com/c/1471910
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Paul Jensen <pauljensen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636063}

Replace const SVGComputedStyle* with const SVGComputedStyle& as the
argument to the Diff*, InheritFrom and CopyNonInheritedFromCached
methods.

Change-Id: I79c14a39c09089882857fcbe61f4578c18cdd5ac
Reviewed-on: https://chromium-review.googlesource.com/c/1491655Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#636062}

- Reloads client_state file every time
- Added possibility to save state keys for clients
- LocalPolicyTestServer provides function to store configuration file

I'm gonna introduce LocalPolicyTestServerMixin in the next CL

Bug: 934224
Change-Id: I7960159b5db8c62e2515f8cedccd469e66a4192e
Reviewed-on: https://chromium-review.googlesource.com/c/1482459
Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Cr-Commit-Position: refs/heads/master@{#636061}