GitLab

Overlays need to ensure they propagate the correct background
information up the tree. In this case the bottom toolbar wasn't
doing this which would cause screen flashing in some cases.

Bug: 951115
Change-Id: I9c7af7844345c95ed07215802137c2bf67bcf77b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437022Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Matthew Jones <mdjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811843}

Updates the name to be consistent with the source and tests in
//chrome/common/profiler.

Change-Id: Ic181aa3a67435a2af3e3e4592d06f5492ebb1f37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437603
Commit-Queue: Mike Wittman <wittman@chromium.org>
Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811842}

`string::operator=(int)` turns into `string::operator=(char)` by casting
the RHS of the assignment, so this code turns into `env = "\x01"`; `env
= "1"` was probably what was intended.

Bug: 1130867
Change-Id: I8a1a1e268c65246c35d864314502fb4aab62e6b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2425333Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: George Burgess <gbiv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811841}

Taking supported profiles into account when choosing when to use
an accelerated video encoder.

Bug: 1119636, 1127073
Change-Id: I8dd52bf6270342f48ba7ec734c91dc4b24e1196c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437783Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811840}

Bug: 1129670, 1120093
Change-Id: I8b48d2c3ff9fda7fc347219f40deed60b9dd206d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2426481
Commit-Queue: Sophey Dong <sophey@chromium.org>
Reviewed-by: Tanya Gupta <tgupta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811839}

A previous CL at r809271 accidentally uploaded incorrect screenshots
causing some confusion to translators.

Bug: None
Change-Id: I5fb8a60a0c2511f563252f87b03a7b720805b5ca
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438519
Commit-Queue: John Lee <johntlee@chromium.org>
Auto-Submit: dpapad <dpapad@chromium.org>
Reviewed-by: John Lee <johntlee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811838}

Roll Chrome Linux PGO profile from chrome-linux-master-1601380366-03c4c1b9f0c0034a1b47d4510e955a5823e9948c.profdata to chrome-linux-master-1601402113-7fdca9625e1fa7a11789090d4f40670ef10ac97f.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-linux-chromium
Please CC sebmarchand@chromium.org,jeffyoon@google.com,liaoyuke@google.com,chrome-brapp-engprod@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chrome
Tbr: sebmarchand@chromium.org,jeffyoon@google.com,liaoyuke@google.com,chrome-brapp-engprod@google.com
Change-Id: Ia8ccc7ddb17613e74f3a12ba73c2598aaa8ef5af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438291Reviewed-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@{#811837}

I didn't mean to commit that.

Bug: 1015315
Change-Id: I5f69aa5160219e63d4334976888e39c25b2bfe34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437381
Auto-Submit: Hans Wennborg <hans@chromium.org>
Commit-Queue: Reid Kleckner <rnk@chromium.org>
Reviewed-by: Reid Kleckner <rnk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811836}

There are a couple of Polymer Behaviors currently defined in the
ui/webui/resources/html/* and ui/webui/resources/js/* folders. Since
Polymer Behaviors can only be used in Polymer elements, makes more
sense to define them in cr_elements/ along with other such behaviors.

Moreover this simplifies the testing code by being able to leverage
cr_elements_browsertest.js.

Bug: 1133385
Change-Id: I66eb64812ae4c502452971da003b7a84f5f9d3fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435820Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Commit-Queue: dpapad <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811835}

As pointed out by mek@, currently BlobDataItem::ShrinkBytes only resizes
the number of elements in the backing std::vector.  The backing capacity
of the vector remains the same.  For any blob less than 512KB this will
result in wasted memory usage.

Bug: 1133110
Change-Id: I71de9ce6cf75afbc7029d86841c8e5a754b69b52
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436868Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811834}

Roll Chrome Mac PGO profile from chrome-mac-master-1601380366-c2cef07ee462371a6daba327da84ce5730b353c6.profdata to chrome-mac-master-1601402113-90af030cdb9e3c62fe724fde5c9a9eda66c16b0e.profdata

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pgo-mac-chromium
Please CC sebmarchand@chromium.org,jeffyoon@google.com,liaoyuke@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:mac-chrome
Tbr: sebmarchand@chromium.org,jeffyoon@google.com,liaoyuke@google.com
Change-Id: Ide1f8862dd0488007fb22e5bcb70abfbbcd676da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438820Reviewed-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@{#811833}

Bug: 1096586
Change-Id: Ied4e1b49ee7e6f154395762a1054924abe6a85a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438730Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811832}

The WGL path hasn't been used in the last many years and
shouldn't be used in the future since ANGLE provides an EGL
implementation on top of D3D or GL depending on what's available.

Remove all WGL support code since it isn't needed anymore.

Bug: chromium:1133372
Change-Id: I1c23f3b17682082e43d7c6072c085a94735e4cf8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2434341
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811831}

EG1 code isn't built and run anymore. Remove the code from codebase by
making `#if defined(CHROME_EARL_GREY_2)` default and removing what's in
'#if defined(CHROME_EARL_GREY_1)'.

Command:
`find . -name '*.mm' -exec unifdef -DCHROME_EARL_GREY_2 -o {} {} \;`
`find . -name '*.mm' -exec unifdef -UCHROME_EARL_GREY_1 -o {} {} \;`

Plus manual handling for .h files, comments and unwrapping Maybe_test*.

Bug: 1102995, 922813, 1035764, 1033726, 1036221, 1036078, 1036071, 1036094, 972681
Change-Id: I06da0e04b8081c74cd32cb2412f9db9bfdb3a774
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2433584Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811830}

This function is nearly identical to media::GetImageBufferColorSpace,
but instead operates on a CMFormatDescriptionRef.

Add DCHECKs that the behavior of the two functions be the same, that is,
the kCVImageBuffer-prefixed and  kCMFormatDescription-prefixed
constants be equal.

Use base::mac::CFCast instead of reinterpret_casts.

The next patch in this sequence will move these two functions over
to media/base/mac, because it will be accessed in capture.

Bug: 959962
Change-Id: I8a4d8468abc866a13cb6181cbd49d9ee04288124
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436513
Commit-Queue: ccameron <ccameron@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811829}

This CL bumps M87 histogram expirations to M90 for both MIX-DL and
Safety Tips.

Fixed: 1125668
Fixed: 1125752
Fixed: 1125753
Fixed: 1125754
Fixed: 1125755
Fixed: 1125756
Fixed: 1125757
Fixed: 1125758
Fixed: 1125759
Fixed: 1125760
Fixed: 1125761
Fixed: 1125762
Fixed: 1125763
Fixed: 1125808
Fixed: 1125809
Change-Id: I2a0c92d663772618d71bf27b7535d6b928c3dbc6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435648
Auto-Submit: Joe DeBlasio <jdeblasio@chromium.org>
Commit-Queue: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811828}

Why: Before this patch we'd ignore any recompute event coming during
an in-progress computation. That assumes the history query callback is
the last task to run before the computation completes. However, since
we are going to add SortingLSH based computation after the history
callback, and the check (i.e. file read) is async, the original
assumption no longer holds. And there could be races.

What: This CL handles of recompute that comes during an in-progress
computation. We'll use a member variable to keep track of the last
recompute event (trigger) that we weren't able to handle. After the
current one completes, we'll ignore its result, and we'll recompute
again using that pending trigger.


Bug: 1062736
Change-Id: I3e30d26d47352480faa39494b0f6b4171f361456
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437782Reviewed-by: Josh Karlin <jkarlin@chromium.org>
Commit-Queue: Yao Xiao <yaoxia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811827}

The root layer is always a scroll container, so checking for
root-layer in addition to scroll container is unnecessary.

BUG=1087667

Change-Id: I179f9f5aaa9e65481e753067db46c98a756d8a67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432412
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811826}

This CL brings up RulesetService in WebLayer as a first step to enabling
the subresource filter component. To facilitate this bringup, this CL
refactors much of the //chrome-level creation of RulesetService into a
static RulesetService::Create() method that is shared between //weblayer
and //chrome.

Bug: 1116095
Change-Id: I285bc68fd59164826696cc700a3fbe7b934e582a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2434342
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811825}

This CL adds clarifying comments to
PendingAppManagerImplBrowserTest.AlreadyRegistered.

In addition to comments this also adds
WebAppRegistrationWaiter::AwaitNextNonFailedRegistration() to avoid
having to use /web_apps/no_service_worker.html for the sake of asserting
on a particular RegistrationResultCode. The normal install flow with
/web_apps/basic.html is flakily either kSuccess or kAlreadyInstalled as
the service worker may asynchronously register during the first install
pass.

Change-Id: I6e6aa14882424c3ccc2affa90afd2798cfaed897
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437549Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Auto-Submit: Alan Cutter <alancutter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811824}

https://screenshot.googleplex.com/BZPMXkBm3xsHJ2H

Bug: 1125150
Test: browser_tests --gtest_filter=DiagnosticsApp*
Change-Id: Ibbb36615e3ff5c67aba09fff479e52a2a6389df4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432676Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org>
Commit-Queue: Joon Ahn <joonbug@chromium.org>
Commit-Queue: Jimmy Gong <jimmyxgong@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811823}

Adds a policy so enterprise users can disable
Kaleidoscope (media recommendations).

Change-Id: I5ccd6aa99c77deb4ef91edcd8a3ea15c22f5bc5e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2429463
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811822}

Bug: 1124434
Change-Id: I3f4252c3b69809ad6966202e7788b2368dc1385d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391612Reviewed-by: Tomasz Wiszkowski <ender@google.com>
Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Brandon Wylie <wylieb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811821}

The Viewport.MetaTagType UMA is broadly useful to get an understanding
of what percentage of pages are "mobile optimized" so we extend it until
M95.

However, this CL removes the more specific Viewport.OverviewZoom
histogram as it's no longer useful.

Bug: 1089632
Change-Id: I0e4a06f043389bbc20e8d07a64263e2e9fccfba4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432770Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811820}

Windows Update installs a custom composite device driver for Samsung
Android devices. This driver appears to behave similarly to Microsoft's
composite device driver except that it does not use the same instance
ID format. This patch adds the driver to the list of recognized
composite drivers and adds fallback logic to find the interface number
in other hardware IDs.

Bug: 1127206
Change-Id: Id48ed6673bf4a195f11a81f8284cc98730e99272
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436786
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811819}

This API is suspected to leak cross-site entropy about users.
This instrumentation reports digests of the values read using this API
to UKM to determine the available entropy of the API for identifying
users across sites.

Bug: 973801
Change-Id: I56a4002ae5ad4f1b0d56633a3ac74674b9f089be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2434100Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Commit-Queue: Maksim Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811818}

Add a histogram to collect aggregate watchtime for
all media feeds so we can see the distribution of
watchtimes.

BUG=1110373

Change-Id: I472cff204e299efabe9f0b90949b14ca3d0fd912
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432590Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811817}

This CL removes the trailing slash - if there is one - from the
--android-deps-dir command line parameter to
//third_party/android_deps/fetch_all.py

BUG=1132330

Change-Id: I8800cdc8ebc38150a47a52333646e86b24dd9b2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437021Reviewed-by: Sam Maier <smaier@chromium.org>
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811816}

PaintLayer::PerspectiveOrigin didn't really require any information
from PaintLayer, so moved it to LayoutBox. Additionally adds an
additional optional parameter (the size) for when PerspectiveOrigin is
called when the LayoutBox size in incorrect.

This occurs with the new fragment overflow calculator as it
calculates the layout-overflow *before* information is copied back
to the LayoutBox.

Bug: 1066616
Change-Id: Icb54306fe9804bb13de0fbb7e22b4657db3371ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412749
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811815}

This change removes margin for error message for all cr-inputs. For the
username field it is added only if the input field is invalid.

Bug: 377410
Change-Id: Ief394cf58ea3923e8ba25ffa8152be0b9cf7bd21
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438390Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com>
Cr-Commit-Position: refs/heads/master@{#811814}

This reverts commit 55996955.

Reason for revert: Fixed the crash, which was caused by deleting
the temp folder.

Original change's description:
> Revert "Add Crash Restoration support for multi-window"
>
> This reverts commit 64875586.
>
> Reason for revert: Speculatively reverting due to https://crbug.com/1132229.
>
> Original change's description:
> > Add Crash Restoration support for multi-window
> >
> > After a crash info bar will be presented on all foreground scenes
> > if the user choose to restore all foreground windows will be restored.
> > if not all windows tabs for all windows which were opened on the last
> > run will be added to the recent closed tabs.
> >
> > Bug: 1126311, 1114179
> > Change-Id: I80623012dc132e2702004d2dbc0bbcb410a7d91c
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415929
> > Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
> > Reviewed-by: Mark Cogan <marq@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#810406}
>
> TBR=marq@chromium.org,mrefaat@chromium.org
>
> Change-Id: I4045617e7eb138e0212f8b1d1062df7ce0b45f74
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 1126311
> Bug: 1114179
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2428972
> Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#810536}

TBR=marq@chromium.org,mrefaat@chromium.org,jdoerrie@chromium.org


Bug: 1126311, 1132229
Bug: 1114179
Change-Id: I911b88c3b57b54aff678648d2da7a6b03038610f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2431454Reviewed-by: Mark Cogan <marq@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Mohammad Refaat <mrefaat@chromium.org>
Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811813}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/fa4bfe45..0d81cd72

Please follow these instructions for assigning/CC'ing issues:
https://v8.dev/docs/triage-issues

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
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Iebe261137ce024d0fe60f11cffd24abe69e96fb1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436717Reviewed-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@{#811812}

https://swiftshader.googlesource.com/SwiftShader.git/+log/1075baee443c..ac160bd364cb

2020-09-29 bclayton@google.com System/Types: Add support for vec3
2020-09-29 bclayton@google.com Pipeline: Remove hack to disable spirv-opt when debugging

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/swiftshader-chromium-autoroll
Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: None
Tbr: swiftshader-team+autoroll@google.com
Change-Id: I44a1204c02a272449058cde2fcec5433bff8d9a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438438Reviewed-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@{#811811}

We now enforce that Tab attributes cannot be acquired
on an uninitialized Tab. If we don't bail out here
we will attempt to pull the title or url off an uninitialized
Tab leading to a crash.

Bug: 1133038
Change-Id: Idd39105dc47ac208b5e9e33144996f3643fec25c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436326Reviewed-by: Peter Williamson <petewil@chromium.org>
Commit-Queue: David Maunder <davidjm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811810}

Fixed: chromium:1089720
Change-Id: I2844cc399d0a67cabf0df613ec4e2913dd01e364
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438053
Auto-Submit: Yang Guo <yangguo@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811809}

This test currently fails when run on Fuchsia's infrastructure because
fuchsia.intl.PropertyProvider is not available in images used to run
the tests on Fuchsia infrastructure and is not included by default in
Fuchsia's hermetic test environment. fuchsia.sys.Loader is included in
both.

Bug: 1131669, fuchsia:53697
Change-Id: I7f3cc3386f16a82cc3865acdbd698759f076f284
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2427000Reviewed-by: Wez <wez@chromium.org>
Commit-Queue: David Dorwin <ddorwin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811808}

Uses JS modules for the NTP module and updates
closure so it can resolve chrome://kaleidoscope.

Change-Id: I985b20a7faca215bd5194a4a21c790d5a4ff0262
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2435441Reviewed-by: calamity <calamity@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811807}

This CL makes the RTC log data available in ConnectionToClient. For
non-WebRTC client connections, nullptr is returned.

Bug: 1122798
Change-Id: Ib613f304c6ebe9ec7af4496487eca5c12c5f03d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2436282Reviewed-by: Joe Downing <joedow@google.com>
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Auto-Submit: Lambros Lambrou <lambroslambrou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811806}

These machines are using the main linux pool, which is overloaded.
See bug for more details.

No-Presubmit: true
Bug: 1133410
Change-Id: I4b29e1d343c1dcbf46d185251db931199f06b322
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2438852
Commit-Queue: Stephen Martinis <martiniss@chromium.org>
Reviewed-by: Andrii Shyshkalov <tandrii@google.com>
Reviewed-by: Quinten Yearsley <qyearsley@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811805}

A non-null BrowserPluginGuestManager is never set, so we remove the
member variable.

We also do a bit of polish on the ShellBrowserContext's constructor
since we're in the area.

Bug: 533069
Change-Id: I2bba2b59fa022c407803acb065df29b701d98d91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2432756
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811804}