GitLab

This reverts commit 461a68da.

Reason for revert: This is no longer needed: We've decided to let each DFM load native resources (on install) in its own way, instead of relying on common infrastructure.

Reverting this also fixes crbug.com/994035

Original change's description:
> [Bundles] Add module_installer_backend.cc with native OnInstallModule handler.
>
> To prepare for handling native resource loading after DFM installation,
> this CL adds a new hook in ModuleInstallerBackend.onFinished() to call
> (via JNI) a new native handler for each newly installed module:
>   JNI_ModuleInstallerBackend_OnInstallModule()
>
> AsyncTask is used to make the JNI call asynchronous, taking place
> outside the UI thread. This allows file access (e.g., to open native
> resources) to take place in the native code, thereby preventing
> assert failure in Debug builds.
>
> After the JNI call, |mListener.onFinished()| is called on UI thread,
> just like before.
>
> Bug: 927131
> Change-Id: I36880cc7739a48534052b51d3d655d1ae0beb29a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1702905
> Commit-Queue: Samuel Huang <huangs@chromium.org>
> Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
> Reviewed-by: danakj <danakj@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#680452}

TBR=danakj@chromium.org,huangs@chromium.org,agrieve@chromium.org,tiborg@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 927131,994035
Change-Id: If9fdbffb35d226615135c9db596ad50960bc2958
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756154Reviewed-by: Samuel Huang <huangs@chromium.org>
Commit-Queue: Samuel Huang <huangs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687309}

Roll src/net/third_party/quiche/src/ 4ff606217..c152cc559 (7 commits)

https://quiche.googlesource.com/quiche.git/+log/4ff606217c21..c152cc559e6c

$ git log 4ff606217..c152cc559 --date=short --no-merges --format='%ad %ae %s'
2019-08-13 renjietang Prevent QuicStreamSequencer from taking in new data after the stream is reset.
2019-08-13 renjietang Early return in QuicSpdyClientSessionBase after connection is closed.
2019-08-13 danzh gfe-relnote: n/a(code clean up) inline quic::CreatePccSender()
2019-08-13 renjietang Allow creation of HTTP/3 static stream after MAX_STREAM frame is received.
2019-08-13 bnc Track unacknowledged references on the encoder stream in QpackBlockingManager.
2019-08-12 renjietang Improve hard-coded QuicSimpleServerStream's push promise id.
2019-08-12 renjietang Initialize session in quic_simple_server_stream_test.

Created with:
  roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src

R=bnc@chromium.org

Change-Id: I7be248b26644adfe330d2005f3c0192a50607d4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756145
Commit-Queue: Ian Swett <ianswett@chromium.org>
Reviewed-by: Bence Béky <bnc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687308}

When web page adds toJSON function to Array prototype, ChromeDriver
incorrectly calls this function while doing JSON serialization of
array objects. This is incorrect, as the W3C WebDriver spec
(https://w3c.github.io/webdriver/#dfn-internal-json-clone-algorithm)
explicitly specifies that implementation should check for collection
before looking for the toJSON function.

Bug: chromedriver:3084
Change-Id: Ib2ed0c79833a6ca557d33595687efd70ade7d8c8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1749617
Commit-Queue: John Chen <johnchen@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Reviewed-by: Rohan Pavone <rohpavone@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687307}

Since CL 1737730, AppList visibility is now correct in tablet mode.

After this change, bugs have surfaced with the shelf background.
To fix this, modify HomeLauncherGestureHandler so we no longer notify
observers that the animation has completed before clearing state.

The specific issue was that
HomeLauncherGestureHandler::IsDragInProgress returns true when
observers are notified of home launcher animation completion.

So, fix this, then check HomeLauncherGestureHandler::IsDragInProgress
to more accurately determine the proper shelf background.

Also check for widget visibility, not activation, because the widget
is not activated in tablet mode when shown.

Bug: 990995

Change-Id: I560a6db4c045dbbc802f18b43266e2c1f2f19e1a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1746915Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Sammie Quon <sammiequon@chromium.org>
Commit-Queue: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687306}

Added AutotestPrivateGetAllInstalledAppsFunction to autotestPrivate api.
Created enums for AppType and AppReadiness in autotest_private_api.idl
Added test case to confirm that all default apps are available. Updated
HistogramValue enum for extension functions with new item.

Test: locally on eve and browser_tests --gtest_filter="AutotestPrivateApiTest.AutotestPrivate"
Bug: 989231
Change-Id: Id8a83335d7ad0922480652bb871e200e470d923a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1742394Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Brendan Hansknecht <bhansknecht@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687305}

Nobody uses it anymore.
Depends on http://crrev.com/c/1754158.

BUG=989976,b:131626644

Change-Id: I04bd32cf285b46b79c22f997ef6dc972ec55e8f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754159Reviewed-by: Gabriel Marin <gmx@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687304}

Clang derives the value of __ANDROID_API__ from the triple these days.
The behaviour of the HWASAN pass is dependent on the API level in the triple,
so it's going to need to be accurate.

Bug: 916828
Change-Id: Ie8ab8942fcb22a1247bd0ef3a2c622c7992e71ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755145Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Peter Collingbourne <pcc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687303}

https://chromium.googlesource.com/angle/angle.git/+log/611663f4f61c..be74c47db7dd

git log 611663f4f61c..be74c47db7dd --date=short --no-merges --format='%ad %ae %s'
2019-08-15 jmadill@chromium.org Capture/Replay: Also capture on postSubBuffer.

Created with:
  gclient setdep -r src/third_party/angle@be74c47db7dd

The AutoRoll server is located here: https://autoroll.skia.org/r/angle-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: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=syoussefi@chromium.org

Bug: None
Change-Id: Ife267e7e54660d630e121f4a5b4684af309d5ba0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755560Reviewed-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@{#687302}

Bug: 992345
Change-Id: I7160af820454a08c1b7eb2ff13845cc0eeba759d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1751944
Commit-Queue: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Reviewed-by: Richard Knoll <knollr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687301}

Create a suggestion chip that shows up once when an update
has been applied to a chromebook.

Bug: 992490

Change-Id: I91492d5eefeccfce5037309da8c9683a76cb8158
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1731770
Commit-Queue: Cameron Womack <camw@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Jenny Zhang <jennyz@chromium.org>
Reviewed-by: Tao Wu <wutao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687300}

While handling events from DevTools, ChromeDriver should avoid making
unnecessary blocking function calls, to avoid blocking other parts of
the system. This CL replaces some calls to SendCommand with
SendCommandAndIgnoreResponse in event handlers. Only places where the
replacement is safe is made.

Bug: chromedriver:907
Change-Id: Idd73b4e6bfeaf750ae7ba341a1033ec30b720682
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755404Reviewed-by: Rohan Pavone <rohpavone@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687299}

BrowserActivityWatcher is now a TabStripModelObserver, and runs the
activity callback whenever a tab action is taken (to include parenting,
i.e. addition or replacement, as well as closing).

Note these notifications are sent by Browser, so they don't exist on
Android. BrowserActivityWatcher and TabStripModelObserver are also
unique to desktop, so this entire CL only affects desktop.

Bug: 268984
Change-Id: I668e22bf637c33266060cd27c1464118a8c6ed1c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1752912Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687298}

Bug: 992146
Change-Id: Ib7c3ae979bebc79f64a455ecd29c6e4f2b76512b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1751796Reviewed-by: Aran Gilman <gilmanmh@google.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Anna Malova <amalova@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687297}

Reduce some duplicative tests between iOS12 vs 13. In general it's good
to test both iOS versions here, but cycle time for both builders are
getting too high.

Bug: 992500
Change-Id: I6d6d30e66c8cb8320c20d934e05167e43d8d2282
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756150
Auto-Submit: Justin Cohen <justincohen@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687296}

This is the fifth commit in the series of updating all the old svg
animation tests.

The usage of testharness has replaced the older SVGAnimationTest.js
for all where it's suitable. No functionality should have changed
and the tests should cover almost the same.

In all of the animations where there is a sampling at T=0, where
it was assumed that no animations had started. Which didn't work
flawlessly when moved to the new system, it has thus been removed.

Bug: 985335
Change-Id: I34fc15e34d01f774c7992ed6c1d79d9e86cd9409
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753003
Auto-Submit: Edvard Thörnros <edvardt@opera.com>
Commit-Queue: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687295}

This changelist allows a user client to send DevTools commands through
a ChromeDriver websocket connection made between the user client and
ChromeDriver. It should be followed by a changelist that allows the client
to receive events from DevTools in real time.

The test client has been augmented to be able to create
a websocket connection with ChromeDriver.

To keep command IDs sent to DevTools unique,it was decided that
commands sent from ChromeDriver through the websocket connection between the
user and Chromedriver will have negative IDs, and commands not sent through
the websocket connection will have positive IDs. ChromeDriver will not receive
command responses from with negative IDs, as the websocket connection between
ChromeDriver and the client is supposed to eventually allow bidirectional
communication between the client and DevTools. Therefore, negative ID commands
will eventually be sent to the user client, which will be completed in another
CL.

The websocket message sent by the client to ChromeDriver is formatted through
DevToolClient's SendCommandInternal method in order to abstract away OOPIFs.

Some notes:
When ChromeDriver receives a request to establish a websocket connection, the
method OnWebSocketRequest in chromedriver_server.cc is invoked. In this method
ChromeDriver accepts the websocket connection.

When ChromeDriver receives a websocket message from the client, the method
OnWebSocketMessage in chromedriver_server.cc is invoked. The websocket message
should be a JSON dictionary with a key "urlPath" that contains the http endpoint
send_command_from_websocket, a key "id" with a negative value, and cmd and
params identical to what would be seen in a call to ExecuteSendCommand (or
similar). The method OnWebSocketMessage formats an http request with that
information.

ExecuteSendCommandFromWebSocket in window_commands.cc is called and a similar code
pathway as ExecuteSendCommand is taken. Notable differences include the passing of
a negative ID which is used in place of the positive ID usually assigned by
ChromeDriver.

In SyncWebSocketImpl, a response/event is only queued in the received_queue_ if
it is relevant to ChromeDriver. This is denoted by either being an event or
containing and positive ID. Currently, all negative ID messages are dropped, but
the subsequent CL in the relation chain forwards messages with negative IDs to
the client.

R=crouleau@chromium.org, johnchen@chromium.org

Bug: chromedriver:2815
Change-Id: I3f900567fa184a2af5f0092338e071172acc879d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1730860
Commit-Queue: Julian Kung <juliankung@google.com>
Reviewed-by: John Chen <johnchen@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687294}

The WrapOutputStream logic as written only works for Python 2.
Python 3.7 added a dedicated API for this, but older Python 3
versions require a bit of effort.  It's all a bit hairy, but
there aren't any other options here.

Bug: 983071
Test: `./grit/test_suite_all.py` passes
Change-Id: I980fe4e92af7b5c0a44f25737ac267bb90d207d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755385Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687293}

https://android.googlesource.com/platform/external/perfetto.git/+log/f714c29b97d0..74bf49a9abc9

git log f714c29b97d0..74bf49a9abc9 --date=short --no-merges --format='%ad %ae %s'
2019-08-15 khokhlov@google.com Merge "Trace processor: Export legacy ftrace and json trace events to JSON"

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

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

Bug: None
Change-Id: Iad99ba8bbd2a6a9ee1af9fc163ea693237388b5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755558Reviewed-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@{#687292}

The Python folks decided to break re.sub behavior and have it randomly
replace empty matches with non-empty strings.  For example:
  >>> re.sub(r'(.*)', r'foo', 'asd')
  'foofoo'

To avoid this crazy pants behavior, we could make the regex match the
entire string (by adding ^ and $ anchors), but this bit of code doesn't
really need a regex at all.  We're simply inserting the string "2x"
before the last "/" in the filename.  Rewrite the code to do a little
ad-hoc string splitting instead as this is a bit easier to read.

Bug: 983071
Test: `./grit/test_suite_all.py` passes
Change-Id: I7aa005d685bb1019c464af1c1f12ce2701431ddb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755391Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687291}

We rely on the unicode(node) result for testing & display of the
node state, but this doesn't work in Python 3 where str==unicode.
Rename the exsting __unicode__ to __str__ and add a backwards
compatible alias for Python 2.  Now str(node) works in both.

Bug: 983071
Test: `./grit/test_suite_all.py` passes
Change-Id: I9cb3027d3f013e53c0a6bfc23705ea7a30e88ea0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755393Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687290}

If you include both base/win/async_operation.h and base/win/vector.h
then a few aliases (like Complex, Abi) will collide.

This CL proposes using dedicated type names to prevent collision to
happen.

BUG=728870

Change-Id: Ib7757ecd0793a25de18818f1156920973e8ef8c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755748
Commit-Queue: Robert Liao <robliao@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687289}

Before the present CL, the caption buttons of a browser window would be
hidden most of the time, but not at the moment when a browser window is
created in tablet mode. Workflows such as entering and exiting overview
would then cause the browser window caption buttons to be hidden because
they were supposed to be hidden all along. As of the present CL, the
caption buttons really will be hidden in the first place.

The present CL adds a very flaky unit test. Without the present CL, the
related test TabletModeBrowserCaptionButtonVisibility is already a
little bit flaky, meaning that the present CL is not really introducing
a new problem. The present CL just adds to the priority of addressing
the preexisting test flake issue. See Issue 993974.

Test: browser_tests HomeLauncherBrowserNonClientFrameViewAshTest.CaptionButtonVisibilityForBrowserLaunchedInTabletMode
Bug: 993594, 993974
Change-Id: I63442abd452eba4ea6b35ad67273dec000ea1c70
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754239Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Avery Musbach <amusbach@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687288}

AMD GPU driver shows the whole black frame if the surface size is coded size
specified in the bitstream. This bug turns out when Android begins to inform the
adjusted size (crrev.com/c/1694962 & crrev.com/c/1722468).

This CL is a workaround for this driver bug. VaapiVDA ignores the frame size
adjusted by a client and use coded size embedded in codec bitstream.

Bug: b:139460315, b:139325471
Test: android.media.cts.EncodeDecodeTest on grunt and atlas
Change-Id: Ic9b2d69b2ceb669e1e8660edc2df3f3f0fc20b6d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755434
Commit-Queue: Hirokazu Honda <hiroh@chromium.org>
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687287}

This is a reland of 1219f372

It was initially reverted per conflict with skyostil@'s crrev.com/686824
landing simultaneously. I fixed that in the reland that landed in
crrev.com/687250 but crrev.com/686824 was reverted simultaneously making
the first patch the one needed again... So I'm relanding the first CL
as-is.

Original change's description:
> [base] Additional no-compile tests for traits_bag.h
>
> This assertion was tested in task_traits_unittest.nc already but it
> should also be tested generically alongside the generic code.
>
> Change-Id: I77ea066a2a82c63f6ad8c692a23b93f74913fe1d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753655
> Auto-Submit: Gabriel Charette <gab@chromium.org>
> Reviewed-by: François Doray <fdoray@chromium.org>
> Commit-Queue: Gabriel Charette <gab@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#686836}

Change-Id: I39da37fc659a1bdf7476f772d816e43a3ef10df4

TBR=fdoray@chromium.org

Change-Id: I39da37fc659a1bdf7476f772d816e43a3ef10df4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756151Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687286}

remove (Canvas|OffscreenCanvas).TextMetrics.MeasureText metrics. Since measuring
text is dependent on the length of the text, the measurement times are not comparable.

Bug: 982019

TBR=rkaplow@chromium.org

Change-Id: Iaddc190ba5d71a5aacdbe48ddff8427cbb616bf9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753588
Commit-Queue: Yi Xu <yiyix@chromium.org>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687285}

Recent changes have removed its usage throughout the codebase.

Bug: 268984
Change-Id: Id6b211af5e99d8774f68db7235196f869ca782b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753548Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Evan Stade <estade@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687284}

Fix symlink creation for cases when the binary does not have build-id.

When --symbols-dir is a relative path, the symlink under discussion
would look like this:

'path/to/libfoo.so/000000000000000000000000000000000' -> (pointing to)
        'path/to/libfoo.so/<HASH>'

It works for absolute paths, but not for relative ones like 'path/to'.
It will work for both absolute and relative paths if the link itself is
relative and points to -> '<HASH>'. Fortunately it is easy to do.

Done.

Bug: None
Change-Id: Ic764f0380063e2f2e15cf484afd5468dcca8f51f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745986Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Auto-Submit: Egor Pasko <pasko@chromium.org>
Commit-Queue: Egor Pasko <pasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687283}

This CL creates the MultiSourceMemoryPressureMonitor,
MemoryPressureVoteAggregator, and MemoryPressureVoter classes described
here: https://docs.google.com/document/d/1W3FPDyjIAKBcFGNYsHA3EKR1FHrJlbBaqT4_RUnxzq0/edit#.
The aggregator class collects votes from voter instances via the OnVote
method. A MemoryPressureVoteAggregator object will be owned by the
MultiSourceMemoryPressureMonitor class, which will be merged with the
MemoryPressureMonitor class after subsequent CL's which will migrate
the OS-specific MemoryPressureMonitors to own a Voter and use that
Voter to inform the Monitor of their votes.

Bug: 980965
Change-Id: Ib84aadca9a4cf74b3c1f8a42787d63a96f5dfd17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1719109
Commit-Queue: Ryan Powell <ryanpow@google.com>
Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687282}

https://skia.googlesource.com/skia.git/+log/201cdbb64614..096b09187476

git log 201cdbb64614..096b09187476 --date=short --no-merges --format='%ad %ae %s'
2019-08-15 bsalomon@google.com Make GrBlend.h private
2019-08-15 brianosman@google.com Add SkImage::reinterpretColorSpace
2019-08-15 egdaniel@google.com Remove remaining functions in GrGLCaps that use GrPixelConfig.
2019-08-15 michaelludwig@google.com Move the source image into Context

Created with:
  gclient setdep -r src/third_party/skia@096b09187476

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

Bug: chromium:795132 chromium:985500
Change-Id: If39f8a34c9c0653236b6494284635a9c7d8d90a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755553Reviewed-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@{#687281}

No-Try because the test hasn't arrived yet.

TBR=lpz

No-Try: True
Bug: 994214
Change-Id: I522b21423261f1f9d3cdccad6c3a40edc78b9185
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755973Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Robert Ma <robertma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687280}

Bug: 949729
Change-Id: I8ebb40af59aea33f27e0a38e7ac6e617af099b41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1751963
Commit-Queue: Fred Mello <fredmello@chromium.org>
Reviewed-by: Peter Wen <wnwen@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687279}

https://swiftshader.googlesource.com/SwiftShader.git/+log/75b6f212c853..ae0f75063c10

git log 75b6f212c853..ae0f75063c10 --date=short --no-merges --format='%ad %ae %s'
2019-08-15 chrisforbes@google.com Add libyarn static library to Android build

Created with:
  gclient setdep -r src/third_party/swiftshader@ae0f75063c10

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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: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=swiftshader-team+autoroll@google.com

Bug: chromium:b/139010488
Change-Id: I030e013b5fbd1123ec51b22de2e03d08d03931d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755556Reviewed-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@{#687278}

This reverts commit 0e2df95c.

Reason for revert: Needs a bot upgrade instead (crbug.com/994039)

Original change's description:
> [ios] Fix host os targeting on chromium.clang/ios bots.
> 
> Xcode 11 requires 10.14
> 
> Change-Id: Ib0e59878ee4bae8e76d73cd881dc58781becad95
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754323
> Commit-Queue: Justin Cohen <justincohen@chromium.org>
> Reviewed-by: John Budorick <jbudorick@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#686923}

TBR=justincohen@chromium.org,jbudorick@chromium.org,hypan@google.com

Change-Id: Ia12d64719ef0b1f964c4631dff2f4e738d45b4b6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1756152Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687277}

This change updates the selection and search text/background colors
in forced colors mode to HighlightText and Highlight.

Bug: 970285
Change-Id: I170fdce8be02e31c26273e4eab5390427e672065
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1735471Reviewed-by: Stephen Chenney <schenney@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Kevin Babbitt <kbabbitt@microsoft.com>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#687276}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5a3cb6082190..cb5f1034aafc


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

The AutoRoll server is located here: https://skia-autoroll.corp.goog/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.


CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

Bug: chromium:None,chromium:None
Change-Id: I3cacd75b614402e63881fe02e370f9e0d9f4b95e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755550Reviewed-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@{#687275}

Currently, Chrome sends ARCVM's *guest* PIDs to debugd to adjust oom
scores which doesn't make sense at all and may even have a serious
side effect. Important host-side processes unrelated to ARC might be
killed because of the bad oom scores adjustment.

This CL temporarily disables the feature until we come up with a
proper oom handling design for ARCVM.

BUG=b:135633925
TEST=launch ARCVM, run 'grep 'WARNING debugd' /var/log/messages'.
 verify there's no warning from debugd.

Change-Id: I541f7b0fe34fd80e82726ec30b32a63574e8d0c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1754783Reviewed-by: François Doray <fdoray@chromium.org>
Commit-Queue: Yusuke Sato <yusukes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687274}

This change adds SMSReceiverStart to UKM use counters to record usage
of the API and see how it is being used to help with improvements.

More on metrics for SMS Receiver API here [1].

[1] http://doc/1dB5UM9x8Ap2-bs6Xn0KnbC_B1KNLIUv4W05MunuXYh0#heading=h.kwlb7w9qxxpc

Bug: 976332
Change-Id: I10d6150b6fd2dc8e434a2486da18db134b3f39d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1745608Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Ayu Ishii <ayui@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687273}

This makes the wrapper's internal methods also core thread-aware rather
than assuming IO thread, following up to the public method changes from
https://chromium-review.googlesource.com/c/chromium/src/+/1753843.

After this CL, the plan is to locally change the thread to UI and see
what breaks, and start landing CLs for the individual callsites to make
them core thread-aware.

Bug: 824858
Change-Id: I9c351fa77d83cee9ef60d6fa2afee2fc35570c17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1753847
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687272}

https://chromium.googlesource.com/catapult.git/+log/73af388b695c..7053241136b9

git log 73af388b695c..7053241136b9 --date=short --no-merges --format='%ad %ae %s'
2019-08-15 khokhlov@google.com [Telemetry] Set intermediate_dir independent of output_dir

Created with:
  gclient setdep -r src/third_party/catapult@7053241136b9

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
TBR=sadrul@google.com

Bug: chromium:981349
Change-Id: I3c157bb0874b68b65d0e510679e230a1146d5cd7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755554Reviewed-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@{#687271}

Light theme: http://screen/XMbqH13O2hu
Dark theme: http://screen/AyXbKiGV8LZ

Bug: 982371
Change-Id: I7b3d9ae278b32aa3f145fd68e05109424c82f227
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1724691
Commit-Queue: Yann Dago <ydago@chromium.org>
Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#687270}