GitLab

Profile API is being updated (issue 1033903) and the usage of
GetOffTheRecordProfile and HasOffTheRecordProfile without argument is
getting deprecated. Use cases of this call that ONLY refer to incognito
or guest mode can use [Get/Has]PrimaryOTRProfile() instead.

c/b/media tests are updated to use the new API.

This CL does not change any behavior.

Bug: 1060940
Change-Id: I567319bf00a335c12b3a5c4c3171efe60d1b2577
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2210583
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Auto-Submit: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772306}

Change Log:
https://chromium.googlesource.com/external/github.com/abseil/abseil-cpp/+log/768eb2ca28..33caf1097e
Full diff:
https://chromium.googlesource.com/external/github.com/abseil/abseil-cpp/+/768eb2ca28..33caf1097e

Bug: None
Change-Id: I96ffb18e05362b3d56a7d0e17ae1e98a678cb97a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218307Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
Commit-Queue: Danil Chapovalov <danilchap@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772305}

Roll Chrome Win64 PGO profile from chrome-win64-master-1590580498-39ab72543da7a96a4f695b1a54bce8558b65f184.profdata to chrome-win64-master-1590594916-ea624ec669480df16e05aa1202066a2c230a60a5.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-win64-chromium
Please CC 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: chrome/try:win64-chrome
Tbr: jeffyoon@google.com,liaoyuke@google.com
Change-Id: Ib48632b6632d06c4f9c7d4d614db3560bdc60aa3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218728Reviewed-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@{#772304}

Roll Chrome Win32 PGO profile from chrome-win32-master-1590580498-31d289ff4006e295949604b3b99c516a32499368.profdata to chrome-win32-master-1590594916-1a49bd7be838713a54921f61c31eff74f9ded2d9.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-win32-chromium
Please CC 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: chrome/try:win-chrome
Tbr: jeffyoon@google.com,liaoyuke@google.com
Change-Id: Ied0fd2c45e93e726c6a1ca2a8b1c7e11c61d579f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218730Reviewed-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@{#772303}

Specifically:
 - cr_drawer_tests.js
 - cr_expand_button_focus_tests.js
 - cr_expand_button_tests.js

Bug: 1000989
Change-Id: I5b7bb247e645d795dd45387d4b9d80a2e02e6c12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215459
Commit-Queue: dpapad <dpapad@chromium.org>
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@{#772302}

Use --project to pass in a generated project.xml file for each lint
target instead of passing each argument through the command line. This
allows the lint checks to function more correctly and thoroughly than
before.

Currently lint does not fully support srcjars (fix is in ToT but not yet
in our lint version), so we extract generated sources and generated
resources in a consistent temporary location under their lint target's
gen dir, removing them if lint succeeds and leaving them in place if
lint fails in order to make it easier to debug lint failures.

Clean up and remove various options that are no longer used or needed.
e.g. display lint errors directly rather than parsing an xml file from
lint's results.

Simplify suppressions file comments and remove unnecessary ones. Ignore
common failures for translations since we have a dedicated translation
team.

Remove an unused dimens and fix a few issues. Suppress additional issues
found by this lint improvement.

Bug: 1082743
Change-Id: I67147e582bd904308fe6a5fc5a11baebd60db41b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212550
Commit-Queue: Peter Wen <wnwen@chromium.org>
Reviewed-by: Theresa  <twellington@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Auto-Submit: Peter Wen <wnwen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772301}

https://chromium.googlesource.com/chromium/src/third_party/libunwindstack.git/+log/dfd3f3d84cfc..046920fc491a

$ git log dfd3f3d84..046920fc4 --date=short --no-merges --format='%ad %ae %s'
2020-05-26 wittman [Sampling profiler] Fix AsmRegs build logic for cross-compilation
2020-05-19 wittman [Sampling profiler] Include AsmGetRegs asm functions on x86/x64

Created with:
  roll-dep src/third_party/libunwindstack
R=etiennep@chromium.org

Bug: 1004855
Change-Id: I8cae2e24f9a6de1e9d4945c352a01dec8d722874
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216327
Auto-Submit: Mike Wittman <wittman@chromium.org>
Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org>
Reviewed-by: Etienne Pierre-Doray <etiennep@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772300}

https://skia.googlesource.com/skia.git/+log/55822f17bd5c..c95dd320931c

2020-05-27 csmartdalton@google.com vk: Call addResource() on indirect draw buffers
2020-05-27 reed@google.com prealloc space for a simple fRunsInVisualOrder
2020-05-27 kjlubick@google.com [canvaskit] Fix width/height API
2020-05-27 michaelludwig@google.com Reland "Simplify GrRTC::clean APIs"

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC westont@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-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
Bug: None
Tbr: westont@google.com
Change-Id: I49fe0497b0ebcd389ecf24a16f5582b04c63d5db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218437Reviewed-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@{#772299}

Using wpt-import in Chromium 7e5ebc13.

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

NOAUTOREVERT=true
TBR=smcgruer

No-Export: true
Change-Id: Ie29a8cca61ceac3f4178279d49cdfb85771539d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218387Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#772298}

This reverts commit 100226ae.

Reason for revert: Broke the feature on Android. Also, the feature has been disabled on webview in crrev.com/c/2156991

Bug: 1086686

Original change's description:
> [mojo] Enable default InstalledAppProvider binder for Android
> 
> Since only Chrome binds InstalledAppProvider, but a default no-op
> behaviour is expected for other embedders (tests, WebView, WebLayer),
> this change removed the 'non-Android' condition for the default
> InstalledAppProvider binder to avoid renderer termination for the
> 'no binder found' case.
> 
> Bug: 1064644, 1064827
> Test: No crash when opening reddit.com in webview shell on an emulator
> Change-Id: Ia9e6d98f0abff94929bf10dcd778166c90907f40
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124872
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#755083}

TBR=dcheng@chromium.org,oksamyt@chromium.org

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

Bug: 1064644, 1064827
Change-Id: Ie2ccdb3724abe7b28dcc461dedebb286c667f595
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218028Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772297}

The reporting API it calls into will soon take NetworkIsolationKeys, and
we want to be able to DCHECK all requests have non-empty NIKs fairly
soon, so it makes sense to start wiring this up now.

The ExpectCTReporter is not currently passed non-empty
NetworkIsolationKeys by net/. That will be taken care of in followup
CLs.

Bug: 969893
Change-Id: I69c4c1615ac3001ad596fd0c97283a087a90a674
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212462
Commit-Queue: Matt Menke <mmenke@chromium.org>
Reviewed-by: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772296}

The only remaining code there was a call to RunLoop::RunUntilIdle() that had
been present since this file was added to the tree.

Whatever it was waiting for seems to have been fixed since then though, as
removing the call still allows all tests to pass, and we get no subsequent
crashes.

Change-Id: Ie1141f7870d89ed4f1ea89015e4ce2b4b67acc36
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216223
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772295}

Since Math.random() in python generates a random number in range [0,1),
we need to use rand(256) to generate number [0, 255]. Update all calls
in canvas perftest to call rand(256).

Bug:1087019

Change-Id: I75ded3269cf652d7d352e32eefbfeddb999583b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216736
Commit-Queue: Yi Xu <yiyix@chromium.org>
Reviewed-by: Juanmi Huertas <juanmihd@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772294}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/8ae7f6e09a0b..0b9eddaa2663

2020-05-27 saklein@chromium.org Build API: execute with --debug by default
2020-05-27 dianders@chromium.org remote_access: Fix crash with 'cros flash' if port not specified
2020-05-27 mmortensen@google.com GetBuildMetadata: Port get_models & run_cros_config_host from cbuildbot.
2020-05-26 dhanyaganesh@chromium.org config: Refactor some configs
2020-05-26 saklein@chromium.org cros flash-ap: Fix ssh flash with non-22 port.
2020-05-26 mikenichols@chromium.org chromeos-config: Remove eve-lacros custom configuration
2020-05-26 bpastene@chromium.org cros_chrome_sdk: Create build dirs when using --no-shell.
2020-05-26 chrome-bot@chromium.org Update config settings by config-updater.
2020-05-26 navil@google.com chromeos_config: Disable release-basic builder.
2020-05-26 navil@google.com chromeos_config: fix fail fast builder gs_path
2020-05-26 morg@google.com Remove (atlas|kukui) boards from vmpi PFQ
2020-05-26 judyhsiao@google.com usergroup_baseline: Add sound_card_init to audio and cras group
2020-05-26 niwa@google.com Remove unused targets (x86 and arm) from ANDROID_VMRVC_BUILD_TARGETS
2020-05-26 chrome-bot@chromium.org Update config settings by config-updater.
2020-05-26 stimim@google.com workspace_stages: remove duplicated android packages
2020-05-25 chrome-bot@chromium.org Update config settings by config-updater.
2020-05-23 vapier@chromium.org cros lint: allow "#!/usr/bin/env python" shebangs
2020-05-23 kerker@google.com image_test: add /usr/lib/node_modules/ to the whitelist
2020-05-22 levinale@chromium.org Add zwisler to the OWNERS.kernel file
2020-05-22 achuith@chromium.org vm: Increase connect timeout for non-KVM.
2020-05-22 manojgupta@google.com chromeos_config: asan: Disable rootfs verification
2020-05-22 bpastene@chromium.org auto_updater: Fix args to RemoteDevice.run() when cmd is a string.
2020-05-22 dianders@chromium.org remote_access: Don't force the port to 22 if unspecified
2020-05-22 malaykeshav@chromium.org Revert "deploy_chrome: Warn before deploying to device with mismatched board"
2020-05-22 levinale@chromium.org Add a per-file permission for kernel Owners file
2020-05-22 vapier@chromium.org OWNERS.chrome: set COMPONENT
2020-05-22 chrome-bot@chromium.org Update config settings by config-updater.
2020-05-22 navil@google.com chromeos_config: Add child builds for fail fast builder.
2020-05-22 navil@google.com chromeos_config: Create template for the fail fast release builder.
2020-05-22 richardfung@google.com Remove android-container-qt targets
2020-05-21 vapier@chromium.org OWNERS: update build settings
2020-05-21 dhaddock@chromium.org paygen_build_lib_unittest: Fix au_e2e control file.
2020-05-21 levinale@chromium.org Chromite: add owners file for the kernel

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/chromite-chromium-autoroll
Please CC chrome-os-gardeners@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

Bug: 1086560
Cq-Include-Trybots: luci.chrome.try:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel
Tbr: chrome-os-gardeners@google.com
Change-Id: I14a8966aac606a9bb5098c16d350fc8ad36ecf7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218431Reviewed-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@{#772293}

For data gathering re SxS, apparently it's possible for Spotlight to
return a search query result for which there is no path. Defend
against this.

Bug: 1086555, 1061486
Change-Id: I972c6cda16d5c0801673addefd064cdfbc810904
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218549
Auto-Submit: Avi Drissman <avi@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772292}

Bug: None
Change-Id: Ifcca583ad1f475d78e600584904efdcd4bdac739
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218449
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Robert Liao <robliao@chromium.org>
Reviewed-by: Robert Liao <robliao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772291}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/d81fad6de554..212c527f90e9

2020-05-27 jacktfranklin@chromium.org Upgrade to TypeScript 3.9.3
2020-05-27 tvanderlippe@chromium.org Typecheck browser_sdk/LogManager.js with TypeScript
2020-05-27 jacktfranklin@chromium.org Sort expected files in search results e2e test

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.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

Bug: chromium:1011811
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: Iacf63754c8a96505e71c76ae2638396693c562b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218433Reviewed-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@{#772290}

Bug: chromium:1011811, chromium:1079233
Change-Id: I9abc4d504fb61809b9dc93d0370c613da3a20fa9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218051
Auto-Submit: Jan Scheffler <janscheffler@chromium.org>
Reviewed-by: Tim van der Lippe <tvanderlippe@chromium.org>
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772289}

Bug: 1072823
Change-Id: I15a96f9568aa98a55e96413652b1e7c5a8a23a39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2105613
Auto-Submit: Yann Dago <ydago@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Commit-Queue: Yann Dago <ydago@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772288}

Task APIs v3 will all have an explicit destination. In the past
"default traits" meant ThreadPool. These CLs are thus a no-op
except for the few callers that clearly wanted to post a QuitClosure()
on the current thread (posting a QuitClosure() to a parallel task will
merely bounce it back to the current thread anyways). Those few callers
were migrated to ThreadTaskRunnerHandle::Get().

These changes are thus required to phase out task APIs v2 (post_task.h)
Design doc: https://docs.google.com/document/d/1tssusPykvx3g0gvbvU4HxGyn3MjJlIylnsH13-Tv6s4/edit

This specific change is a subset of
https://chromium-review.googlesource.com/c/chromium/src/+/2216733

This CL was uploaded by git cl split.

R=petewil@chromium.org

Bug: 1026641
Change-Id: Id676174f093ce32d2cc691ca2deb8415f0b95c0a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217203
Auto-Submit: Gabriel Charette <gab@chromium.org>
Commit-Queue: Peter Williamson <petewil@chromium.org>
Reviewed-by: Peter Williamson <petewil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772287}

monochrome_apk_checker.py gets called from bots and sometimes extra
arguments are passed in that are not relevant for this script. This cl
just changes the parser behaviour to ignore unknown arguments.

Bug: 1084351
Change-Id: I9b574bd6ae8f16e3c097baa7b50811557a2e773b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209115Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Mohamed Heikal <mheikal@chromium.org>
Auto-Submit: Mohamed Heikal <mheikal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772286}

The crash in crbug/1086749 is likely due to the page method calls being
handled after destruction of |autocomplete_controller_|. mojo::Receiver
guarantees that page method calls will NEVER run beyond the lifetime of
the receiver object. Moving the Receiver (as well as the Remote) member
variable toward the end of the list of member variables should fix this
crash as the receiver object gets destroyed first.

Bug: 1086749
Change-Id: I42d1229416e5909c4f3b9bd187a4db2da88b7d2a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217211
Commit-Queue: Moe Ahmadi <mahmadi@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772285}

Roll Chrome Mac PGO profile from chrome-mac-master-1590580498-ea3616ac9902235828b373566b290618f1842868.profdata to chrome-mac-master-1590594916-60e361b5828c3c2c59992f70098f83fe3dce39a9.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 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: chrome/try:mac-chrome
Tbr: jeffyoon@google.com,liaoyuke@google.com
Change-Id: Ide13c8a6156086f94e0f1d5d2b69e9ae89db08a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218647Reviewed-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@{#772284}

The decltype(<func>) passed as template parameter to
CBBFunctionToVector does not return a function pointer
and GCC complains like this:

../../device/fido/virtual_fido_device.cc:104:68: error:
 'int(struct cbb_st*, const struct evp_pkey_st*)' is not a valid type
 for a template non-type parameter
  104 |                         EVP_marshal_private_key>(pkey_.get());
      |                                                           ^

Fix this by passing decltype(&<func>).

Bug: 819294
Change-Id: I8114c3d75c9865779d58c0b6a6c48e6affd3175b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217414Reviewed-by: Adam Langley <agl@chromium.org>
Commit-Queue: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772283}

This is a reland of de6734f7

Original change's description:
> vma_wrapper: create VmaAllocator for vulkan 1.1.0
> 
> For vulkan 1.1.0, VmaAllocator will use dedicated memory
> allocation for some big vulkan memory request, and free
> it when the allocation is released. Without this change,
> the VmaAllocator will allocate memory from self managed
> memory blocks for all vulkan memory request. And the
> memory may not be released when the allocation is
> released. VmaAllocator may keep the memory for later
> usage. It could be the reason for the memory regression
> in fuchsia.
> 
> Bug: fuchsia:52463
> Change-Id: I7b905435d31b927b2344724f8a2e1738e0544410
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215414
> Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
> Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
> Auto-Submit: Peng Huang <penghuang@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#771927}

Bug: fuchsia:52463
Change-Id: I4da1f291a574f72ad16811ffafffb3be36392af6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218247
Commit-Queue: Peng Huang <penghuang@chromium.org>
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772282}

Task APIs v3 will all have an explicit destination. In the past
"default traits" meant ThreadPool. These CLs are thus a no-op
except for the few callers that clearly wanted to post a QuitClosure()
on the current thread (posting a QuitClosure() to a parallel task will
merely bounce it back to the current thread anyways). Those few callers
were migrated to ThreadTaskRunnerHandle::Get().

These changes are thus required to phase out task APIs v2 (post_task.h)
Design doc: https://docs.google.com/document/d/1tssusPykvx3g0gvbvU4HxGyn3MjJlIylnsH13-Tv6s4/edit

This specific change is a subset of
https://chromium-review.googlesource.com/c/chromium/src/+/2216733

This CL was uploaded by git cl split.

R=mek@chromium.org

Bug: 1026641
Change-Id: I3c723c41dc313d8eaa664260c7569a7bde398076
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216737
Auto-Submit: Gabriel Charette <gab@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772281}

https://chromium.googlesource.com/angle/angle.git/+log/4a81e3dba0fd..ca092f016532

2020-05-27 gbiv@chromium.org translator: explicitly specify underlying types for enums

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC ynovikov@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_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86
Bug: chromium:1084580
Tbr: ynovikov@google.com
Change-Id: I1d19ff3d8252d3f77950217be58b85a870cc4ba9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218432Reviewed-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@{#772280}

Task APIs v3 will all have an explicit destination. In the past
"default traits" meant ThreadPool. These CLs are thus a no-op
except for the few callers that clearly wanted to post a QuitClosure()
on the current thread (posting a QuitClosure() to a parallel task will
merely bounce it back to the current thread anyways). Those few callers
were migrated to ThreadTaskRunnerHandle::Get().

These changes are thus required to phase out task APIs v2 (post_task.h)
Design doc: https://docs.google.com/document/d/1tssusPykvx3g0gvbvU4HxGyn3MjJlIylnsH13-Tv6s4/edit

This specific change is a subset of
https://chromium-review.googlesource.com/c/chromium/src/+/2216733

This CL was uploaded by git cl split.

R=pkasting@chromium.org

Bug: 1026641
Change-Id: Id38d941acd0e77333cdcef9c34a3eb509650755c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215917
Auto-Submit: Gabriel Charette <gab@chromium.org>
Commit-Queue: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772279}

There is no need to pass a std::unique_ptr to PlatformSensorProviderLinux
and also hold the raw pointer in PlatformSensorAndProviderLinuxTest.
Instead, just pass the std::unique_ptr and access it directly, as the test
class is already a friend of PlatformSensorProviderLinux.

R=reillyg

Change-Id: I41624ccedb9dfd886f047d0ad9550c877966af3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218047
Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772278}

[base] Make PostTask destination explicit in /content/public/test/browser_task_environment_unittest.cc

Task APIs v3 will all have an explicit destination. In the past
"default traits" meant ThreadPool. These CLs are thus a no-op
except for the few callers that clearly wanted to post a QuitClosure()
on the current thread (posting a QuitClosure() to a parallel task will
merely bounce it back to the current thread anyways). Those few callers
were migrated to ThreadTaskRunnerHandle::Get().

These changes are thus required to phase out task APIs v2 (post_task.h)
Design doc: https://docs.google.com/document/d/1tssusPykvx3g0gvbvU4HxGyn3MjJlIylnsH13-Tv6s4/edit

This specific change is a subset of
https://chromium-review.googlesource.com/c/chromium/src/+/2216733

This CL was uploaded by git cl split.

R=sky@chromium.org

Bug: 1026641
Change-Id: I87ec188abf4b2e6a359d69409a74bbf90674197c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215918
Auto-Submit: Gabriel Charette <gab@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772277}

When an OverlayPresentationContext's capabilities are updated,
OverlayPresenter will hide the currently-presented overlay UI if the
new capabilities are insufficient to present it.  However, the previous
implementation mistakenly checked against GetActiveRequest() rather
than |presented_request_| to handle this logic.  GetActiveRequest()
returns the front request of the active WebState's queue, which is
often, but not always the presented request when |presenting_| is true.
|presented_request_| is more accurate, as there are two points in time
where it differs from GetActiveRequest():
- When presented overlay UI is being dismissed due to request
  cancellation.  At this point, the request will have already been
  removed from the active WebState's queue.
- When presented overlay UI is being dismissed due to a change in the
  active WebState.  The request still belongs to the previously-
  active WebState, so will not be returned by GetActiveRequest().

Bug: 1065564
Change-Id: I4c7eec8ba28311f520cff482d316bb4ac8e24a23
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212520Reviewed-by: Chris Lu <thegreenfrog@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Auto-Submit: Kurt Horimoto <kkhorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772276}

Its only call site was the function right above it. Merge them together for
simplicity.

While here, use base::MakeRefCounted<> rather than creating a
scoped_refptr<> and passing it to base::Callback::Run().

Change-Id: Id1ccce0493dfdcaccb3689d07b661e0267e2ba46
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218068
Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772275}

This method was never implemented and is not called anywhere. It is better
to readd it if we ever really have a use for it.

Change-Id: I1c9b379e3dbe867e91f06f0170dce3abe04b8c98
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218087
Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772274}

Task APIs v3 will all have an explicit destination. In the past
"default traits" meant ThreadPool. These CLs are thus a no-op
except for the few callers that clearly wanted to post a QuitClosure()
on the current thread (posting a QuitClosure() to a parallel task will
merely bounce it back to the current thread anyways). Those few callers
were migrated to ThreadTaskRunnerHandle::Get().

These changes are thus required to phase out task APIs v2 (post_task.h)
Design doc: https://docs.google.com/document/d/1tssusPykvx3g0gvbvU4HxGyn3MjJlIylnsH13-Tv6s4/edit

This specific change is a subset of
https://chromium-review.googlesource.com/c/chromium/src/+/2216733

This CL was uploaded by git cl split.

R=sky@chromium.org

Bug: 1026641
Change-Id: I54a1ce913a2b19504b20494a930810d1a50f9139
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215919
Auto-Submit: Gabriel Charette <gab@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772273}

Task APIs v3 will all have an explicit destination. In the past
"default traits" meant ThreadPool. These CLs are thus a no-op
except for the few callers that clearly wanted to post a QuitClosure()
on the current thread (posting a QuitClosure() to a parallel task will
merely bounce it back to the current thread anyways). Those few callers
were migrated to ThreadTaskRunnerHandle::Get().

These changes are thus required to phase out task APIs v2 (post_task.h)
Design doc: https://docs.google.com/document/d/1tssusPykvx3g0gvbvU4HxGyn3MjJlIylnsH13-Tv6s4/edit

This specific change is a subset of
https://chromium-review.googlesource.com/c/chromium/src/+/2216733

This CL was uploaded by git cl split.

R=hansberry@chromium.org

Bug: 1026641
Change-Id: If8c3e0326a77e5ffca7f6e885cbda1bd37c0b3d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216735
Auto-Submit: Gabriel Charette <gab@chromium.org>
Commit-Queue: Ryan Hansberry <hansberry@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772272}

... by making sure the iframe under test is in-process (there's no point
for testing for OOPIF, since JS context isolation is provided naturally
there).

Bug: 608015
Change-Id: I81382e9e0c8943c67c0226582c90f57a3964dd68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2216640Reviewed-by: Yang Guo <yangguo@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772271}

Bug: 1083485
Test: fast/frames/document-addressSpace-in-initial-document-after-navigation.html
Change-Id: I08229cb5143e3a348d0897d4ad186978a858b7b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215443Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772270}

This CL introduces following methods for dictionary members whose type
is nullabe.  These methods are migration adapters, and will be removed
after IDL compiler migraiton.

- fooNonNull(): Returns a non-null type value for a member |foo|.
  It crashes if foo() is missing or has a null value.
- hasFooNonNull(): Returns true iff |foo| has a non-null value.

In practice, however, they are aliases of foo() and hasFoo() in the
running IDL compiler.  We are changing behaviors of foo() and hasFoo()
precisely in the new compiler, and expect these new methods work as
migration adapters.


Bug: 839389
Change-Id: If19479779ea3d19b498e23a5001aabd38366a2ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2215648
Commit-Queue: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772269}

Bug: 1020213
Change-Id: Ib637c351af63496ba9b7bb538b0df0639fd18f96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2212630
Commit-Queue: Jerome Gingras <jgingras@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772268}

IWYU. This fixes the libstdc++ build after commit 41989bd8 ("Remove/replace
unnecessary logging.h includes in .cc files (cc)").

Bug: 957519
Change-Id: I1e782e8310ca548947b2d541af6a2159d928d1f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2218090Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: vmpstr <vmpstr@chromium.org>
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/master@{#772267}