GitLab

https://android.googlesource.com/platform/external/perfetto.git/+log/8c5bd85a9ac2..db63601344ca

git log 8c5bd85a9ac2..db63601344ca --date=short --first-parent --format='%ad %ae %s'
2020-02-24 ilkos@google.com Merge "Revert "Add regex matching for the focus""
2020-02-24 skyostil@google.com Merge "TrackEvent: Add API for querying whether a tracing category is enabled"
2020-02-24 ilkos@google.com Merge "Add regex matching for the focus"

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-chromium-autoroll
Please CC perfetto-bugs@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/+/master/autoroll/README.md

Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: I0c9d1043d0995979a3995e3ee62f8381dcb147bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067233Reviewed-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@{#743947}

Build error in GCC:
../../services/network/public/cpp/content_security_policy/csp_source_list.h:19:6: error: ‘string’ in namespace ‘std’ does not name a type

Bug: 819294
Change-Id: I9c8665050cae038530a79323b65932a124adf2a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067074
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Reviewed-by: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743946}

We're refactoring startup tracing in Chrome, see design doc[1]. With
the new startup tracing architecture, each process needs to allocate a
shared memory buffer when enabling startup tracing.

In the browser process on linux (when the zygote is enabled), this can
only happen after InitializeZygoteSandboxForBrowserProcess() is run,
because this function forks & may emit trace events in the forked
process - which could cause deadlocks or writing to the same SMB from
two processes at the same time and corrupting trace data.

This patch moves startup tracing initialization until after this point
when the zygote is enabled.

[1] https://docs.google.com/document/d/1FygJQbD29vMkfVfT7m0Lb1u1zZZU1VgXAPi_R0uBoTw/edit?usp=sharing

Bug: 1006753
Change-Id: I21eebfd9196731f810a24e41787c42b66568f3ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067075
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Sami Kyöstilä <skyostil@chromium.org>
Auto-Submit: Eric Seckler <eseckler@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743945}

Makes the implementation of the background helper in the
WindowsSpellChecker class cleaner by using PostTaskAndReplyWithResult.

Currently, a reference to the main thread task runner is passed to the
background helper at construction, and the background helper uses it in
several methods to post callback tasks on the main thread. With this
change, the background helper is simplified and just needs to return
results normally.

Note that with this change, we lose a little bit of visibility on the
fact that the callbacks are run on the main thread. This isn't really
an issue because the callbacks don't need to be run on the main thread.
The important thing is that COM objects are interacted with on the
background thread, and the background helper already enforces that.

Change-Id: I86afa6daf6d4e038bd4bdce9a058a9dd6417eed8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067263Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org>
Commit-Queue: Guillaume Jenkins <gujen@google.com>
Cr-Commit-Position: refs/heads/master@{#743944}

Add an instrumentation test for the case when max number of redirects
is reached using an SXG fallback.

In particular the tests ensures that:
 - the test case does not crash (crbug.com/994439),
 - the test case results in error page (due to
   net::ERR_TO_MANY_REDIRECTS).

Originally this case resulted in chrome and webview crashes, see
crbug.com/994439. Also after the CL in [1] webview will not invoke
callbacks (such as onPageFinished, onReceivedError) for this case.
This issue is tracked in crbug.com/1052242 and is documented in the
test.

In more detail the test constructs an SGX with a fallback url and
ensures the max number redirects is reached, by redirecting 19 times
before loading the SXG. The SXG invokes a fallback url which results
in an extra redirect reaching the max number of redirects
(kMaxRedirects = 20). In that case the url_loader_ in [2] has already
been cleared and is a nullptr.

Note: depends on CL in [1].

[1] https://chromium-review.googlesource.com/c/chromium/src/+/2043173
[2] https://cs.chromium.org/chromium/src/content/browser/loader/navigation_url_loader_impl.cc?l=979&rcl=947d318437fdbae52043963f215c9cd409cd2db5

BUG=994439,1052242
TEST=run_webview_instrumentation_test_apk -f ClientOnPageFinishedTest#testMaxRedirect_SXG

Change-Id: Ic1e635e37741018d893f9b0807ca0f809d27bbbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057130
Commit-Queue: Tim Volodine <timvolodine@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743943}

This change:
1) Removes clumptini, victorvianna, & hhw from flag owners
2) Replaces a few usernames with email addresses when those usernames
   don't have @chromium.org accounts but *do* have @google.com accounts

Bug: 1053302
Change-Id: I0de0409ee84518ee6c10e8be7dac8d0f71664b56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2065436Reviewed-by: Ben Wells <benwells@chromium.org>
Reviewed-by: Jan Krcal <jkrcal@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743942}

This CL adds machine level policy support for Local State preferences. A
BrowserPolicyConnectorIOS object is added to ApplicationContextImpl and
initialized at startup when setting up Local State. A basic
ConfigurationPolicyListHandlerFactory is created to assist in this
process, but for now, no policy->pref mappings are registered on iOS.

BUG=1024115

Change-Id: Ib72399856c30515fc8396b758b150a85165b8239
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067276Reviewed-by: Owen Min <zmin@chromium.org>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743941}

The other two overrides in this dialog (Accept & Cancel) are going to
need considerably more thought.

Bug: 1011446
Change-Id: I91f36db3a7b8de521484d172503eeea141a850be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067200Reviewed-by: Peter Boström <pbos@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743940}

This CL removes system_webview_shell_layout_test_apk_no_field_trial
as tests expectation depend on features and often can't be met without
field trials enabled.

Bug: 1054775
Change-Id: I29c7fe836557caa43af52e6b123766dcf0f3e928
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2069855Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743939}

Before this patch, debug build hits an assert that CanMakePayment pref
is accessed only from the UI thread.

This patch posts the IS_READY_TO_PAY reply from an Android payment app
to the UI thread.

After this patch, the CanMakePayment pref is always checked from the UI
thread.

Bug: 1054869
Change-Id: I5ac85ac54aa648ac72df1602026eff5efa2a1ceb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067809Reviewed-by: Liquan (Max) Gu <maxlg@chromium.org>
Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743938}

- Remove useless includes
- Remove WebWidget::IsFlinging it is no longer used

Change-Id: I10e1d0679b067f86b0a9a57c32befb1bbc90a275
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066853Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743937}

https://skia.googlesource.com/skia.git/+log/cc5415a8ce36..9642b31a71fc

git log cc5415a8ce36..9642b31a71fc --date=short --first-parent --format='%ad %ae %s'
2020-02-24 fmalita@chromium.org [skottie] Add support for text animator blur

Created with:
  gclient setdep -r src/third_party/skia@9642b31a71fc

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 jlavrova@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/+/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: jlavrova@google.com
Change-Id: Iefc6b7bb9012089bc00789ae09414497963934ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2070090Reviewed-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@{#743936}

Bug: 1043580
Change-Id: I33fb24d7a832d68a76b7364978c004c4d3ecc26c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066929Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Anton Bikineev <bikineev@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743935}

Remove use of --qemu-require-kvm argument from waterfalls.pyl since the
argument was removed by
https://chromium-review.googlesource.com/c/chromium/src/+/1549585

Bug: 778467
Change-Id: Ie3bbf6574a440ce629e5f6d2a5584701960a36f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066855
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Auto-Submit: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743934}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/bc317330..be465ac3

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,v8-waterfall-sheriff@grotations.appspotmail.com

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

Arguments are handled individually and slightly differently in each
WebUI class. In most cases, handling should depend only on the list
of their types and could be done uniformly.

Bug: 1051919
Change-Id: Ic810894fa8d98fa2ac8e7f3af0020499b834f8f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2049981Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Vladislav Kuzkokov <vkuzkokov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743932}

Some Android P devices don't support vulkan extension
VK_ANDROID_external_memory_android_hardware_buffer. For those devices,
chrome will fallback to ExternalVkImageBacking which uses
VK_KHR_external_memory_fd extension or pixel copy for GL and Vulkan
inerop.

Bug: 1049864
Change-Id: I101a4c83a2dbfcfdbade29084a863e7563f631e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067290Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743931}

This expands the popup_opener_tab_helper, which traditionally
tracks the pop-ups and navigation of the site for the purposes
of tab-unders, to include recording a user's pop up blocker content
settings to UKM.

This is done by querying the user's content settings when the
web contents associated with the site is destroyed and recording
it to a new UKM: Popup.Page.Allowed. Where the value of true
represents the user explicitly allowing all pop-ups on a site.

Change-Id: I33c729021511a154d944bdf45ca188971292640b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062488
Commit-Queue: Justin Miron <justinmiron@google.com>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743930}

Bug: 1039697
Change-Id: Ibbef1963c95085d07393e7fdd7094b5425ba5d15
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2070329
Commit-Queue: Nico Weber <thakis@chromium.org>
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743929}

https://dawn.googlesource.com/dawn.git/+log/bc34d908f60d..33466973bc4c

git log bc34d908f60d..33466973bc4c --date=short --first-parent --format='%ad %ae %s'
2020-02-24 cwallez@chromium.org CMake: Add support for the D3D12 backend

Created with:
  gclient setdep -r src/third_party/dawn@33466973bc4c

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/dawn-chromium-autoroll
Please CC cwallez@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/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
Bug: None
Tbr: cwallez@google.com
Change-Id: I5c8ca09785f0303aeffee3b7d170c6849e93612c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2070088Reviewed-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@{#743928}

net_http_server_fuzzer fails with Run() timeouts, so increase the Run()
timeout in //net/base/fuzzer_test_support.cc from action_timeout() to
action_max_timeout().

Bug: 1055084
Change-Id: Idbcff1645d60327bd39267e6b936ffaa233c6f08
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066754
Auto-Submit: Wez <wez@chromium.org>
Reviewed-by: Maksim Orlovich <morlovich@chromium.org>
Commit-Queue: Wez <wez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743927}

Don't show a primary account re-authentication dialog for child users,
so they wouldn't get in signed-out state. Forcibly logout all accounts
to re-mint the cookies.

Bug: 1052099
Change-Id: I1d643856b3500e1ce366ef3e9282c334fbb40dbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059412Reviewed-by: Kush Sinha <sinhak@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Anastasiia Nikolaienko <anastasiian@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743926}

Now that the Skia-side CL:

https://skia-review.googlesource.com/c/skia/+/272343 (Move SkDeferredDisplayList.h into include\core)

has landed, Chrome can refer to SkDeferredDisplayList.h in its new location (include/core).

Change-Id: I1a175bddbbe91e6422450d1ffe17436907e836e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067805Reviewed-by: Peng Huang <penghuang@chromium.org>
Commit-Queue: Robert Phillips <robertphillips@google.com>
Cr-Commit-Position: refs/heads/master@{#743925}

This CL converts FrameMsg_EnforceInsecureRequestPolicy to method on
blink RemoteFrame mojom. It also updates the unit test with
intercepting RemoteFrame and removes checking the IPC message.

BUG=1047284

Change-Id: I9578c49cfcc08b3a682ec2899627dc6503965654
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2038513Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Julie Kim <jkim@igalia.com>
Cr-Commit-Position: refs/heads/master@{#743924}

The original change was reverted for crbug.com/1052790 (
webgl_conformance_tests on Android device Nexus 5 failing),
However the change is only used for Android 10, it should not affect
Nexus 5. So the CL is not related to the problem.

This is a reland of 75b5db21

Original change's description:
> SkiaOutputdeviceBufferQueue: kick off next frame earlier
>
> PageFlipComplete() is not trivial, so call FinishSwapBuffers()
> before it to kick off next frame in viz thread earlier, and compositor
> will have more time budget to render the next frame.
>
> Bug: None
> Change-Id: Ie6e0f87d75d81b405447757585ec291887ca0063
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057043
> Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
> Auto-Submit: Peng Huang <penghuang@chromium.org>
> Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#741430}

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

This reverts commit 74270ce2.

Reason for revert: Apparently causes crashes, https://crbug.com/1055188

Original change's description:
> Roll libunwind 43bb9f8722..d999d54f4b
> 
> ...and enable Wbitwise-conditional-parentheses on android.
> 
> https://chromium.googlesource.com/external/github.com/llvm/llvm-project/libunwind.git/+log/43bb9f8722..d999d54f4b
> 
>  Fix a -Wbitwise-conditional-parentheses warning in _LIBUNWIND_ARM_EHABI libunwind builds
> 11b0129 [libunwind] Treat assembly files as C on mingw
> 76f6916 [libunwind] Fix building standalone after c48974ffd7d1676
> aea9f89 [libunwind] Set LIBUNWIND_ASM_SOURCES to the ASM source language from C
> e4cbc26 Bump the trunk major version to 11
> e12b248 [libunwind] Fix evaluating DWARF operation DW_OP_pick
> c3889d9 [unwind] Don't link libpthread and libdl on Fuchsia
> 81f7e17 [libunwind][RISCV] Add 64-bit RISC-V support
> baf07ac Reland "Enable `-funwind-tables` flag when building libunwind"
> 2ef1190 Revert "Enable `-funwind-tables` flag when building libunwind"
> 2fd0a70 Enable `-funwind-tables` flag when building libunwind
> f939ab7 [libunwind] Emit dependent libraries only when detected
> 4cd4dca [libunwind] Adjust the signal_frame test for Arm
> 0b1d80f change LLVM_VERSION_SUFFIX default from svn to git
> b6a6639 Correctly update isSignalFrame when unwinding the stack via dwarf.
> e7f96ac unwind: restore the LINKER_LANGUAGE
> e24563d unwind: reflow some of the build rules (NFC)
> f2c3035 unwind: disable RTTI during the build of libunwind
> a4a7180 Revert "build: explicitly set the linker language for unwind"
> ccff66b build: explicitly set the linker language for unwind
> a914ec1 [libunwind] [Windows] Add a log message if EnumProcessModules fails
> 2a4f136 [libunwind][Android] Fix findUnwindSections for ARM EHABI Bionic
> b6bfd8b [libunwind][Android] Improve workaround for PIE zero-dlpi_addr bug
> 1073ad9 [libunwind] Fix issues introduced in r374606
> cfb6df8 [libunwind] Refactor CMake flag checks to match libc++ and libc++abi
> 57be2d2 [libunwind] Adjust libunwind_01.pass.cpp test for ARM EHABI
> 5342138 Unwind: avoid warning about unused typedef
> 78b42cc Unwind: prevent unw_get_proc_info from returning stale data
> 2aa34a8 unwind: remove a could of extraneous `else` (NFC)
> c699521 [runtimes] Don't depend on libpthread on Android
> 9d72a29 [libunwind][ARM] Fix types in _Unwind_VRS_Get.
> d003462 [libunwind][ARM] Fix loading FP registers on big-endian targets
> 558e694 Bump the trunk version to 10.0.0svn
> 8d9ed37 [libunwind] Fix Unwind-EHABI.cpp:getByte on big-endian targets
> 0baf612 [libunwind][AArch64] Fix libunwind::Registers_arm64::jumpto
> b5b4a50 [Docs] Modernize references to macOS
> 7aecb76 [CMake] Use find_package(LLVM) instead of LLVMConfig
> e2fa4a0 [runtimes] Use -Wunknown-pragmas for the pragma check
> 0e59516 [runtimes] Check if pragma comment(lib, ...) is supported first
> 7b72703 [runtimes] Support ELF dependent libraries feature
> 06a69dc [libunwind] [test] Fix inferring source paths
> 1f9c24d [runtimes] Move libunwind, libc++abi and libc++ to lib/$target/c++ and include/c++
> 7611bf2 [PPC] Fix 32-bit build of libunwind
> 8a6fc69 [PPC64][libunwind] Fix r2 not properly restored
> 7f90e76 Add a new LIBUNWIND_WEAK_PTHREAD Cmake option to force
> 22e7c0c [gn] Support for building libunwind
> 103afa4 [NFC] Fix typo in debug log
> f5d6a44 Add support for ARMv7-M architecture which uses the Thumb 2 ISA (unified syntax)
> f8c730d [NFC] Move the export attribute after extern "C".
> 59d0c60 [NFC] Correct outdated links to the Itanium C++ ABI documentation
> 01fc413 [libunwind] Fix the typo in unw_save_vfp_as_X alias
> 2b63e62 Move the alias definition of unw_getcontext to within !defined(__USING_SJLJ_EXCEPTIONS__)
> 2ec9ffc [libunwind] Export the weak alias in Mach-O
> 9bbfad5 [libunwind] Export the unw_* symbols as weak symbols
> e63f955 [libunwind] Do not share an object library to create the static/shared libraries
> 2a2b62e Revert "[runtimes] Move libunwind, libc++abi and libc++ to lib/ and include/"
> 9021011 [runtimes] Move libunwind, libc++abi and libc++ to lib/ and include/
> 4287808 [CMake][libunwind] Define add_target_flags which is missing
> 3674fe4 [CMake] Don't cache LLVM_MAIN_SRC_DIR
> 99b7c05 [CMake] Support compiler-rt builtins library in tests
> a6a888a [CMake] Support CMake variables for setting target, sysroot and toolchain
> 5f5036e Provide a placement new definition for the SEH version of UnwindCursor
> 36f6154 [libunwind] Provide placement new definition
> f50a5ed [libunwind] Remove the remote unwinding support
> 370ec3f [CMake] Use correct visibility for linked libraries in CMake
> a0f0700 Revert "[CMake] Use correct visibility for linked libraries in CMake"
> d6e1714 [CMake] Use correct visibility for linked libraries in CMake
> 809c2b5 [libunwind] Support building hermetic static library
> ac0d9e0 Drop the dependency on <algorithm>, add placement new inline
> 8835912 Adjust documentation for git migration.
> fafb21e Don't define unw_fpreg_t to uint64_t for __ARM_DWARF_EH__
> a9ccb4e Revert "[libunwind] Drop the dependency on <algorithm>, add placement new inline"
> cf8d0d6 Revert "[CMake] Use __libc_start_main rather than fopen when checking for C library"
> b31f294 [libunwind] Drop the dependency on <algorithm>, add placement new inline
> 6a3a019 [CMake] Use __libc_start_main rather than fopen when checking for C library
> 1f978e9 [libunwind] Use placement new to avoid dependency C++ library
> 06be328 [libunwind] Don't abort if encoutering invalid .eh_frame_hdr
> 059a163 Silence warnings about unused parameters
> 13d23c8 Remove an unused variable
> 688e594 Add casts to avoid warnings about implicit conversions losing precision
> 985a1d1 Fix warnings about printf format strings
> 55b1c00 Enable LLVM_ENABLE_WARNINGS when building standalone out of tree
> 0dc7999 Fix typos throughout the license files that somehow I and my reviewers
> 61860a5 Update more file headers across all of the LLVM projects in the monorepo
> 60b38b7 Install new LLVM license structure and new developer policy.
> 9180f77 [SjLj] Don't use __declspec(thread) in MinGW mode
> 14d9c7b Bump the trunk version to 9.0.0svn
> b9268be Update year in license files
> 9f2f07a [Sparc] Add Sparc V8 support
> 38d0a65 Revert "[Sparc] Add Sparc V8 support"
> d71bc56 [Sparc] Add Sparc V8 support
> ce15011 [SEH] Add initial support for AArch64
> cba83c3 [AArch64][libunwind] Unwinding support for return address signing with B Key
> 4d8e431 [AArch64][libunwind] Unwinding support for return address signing
> 
> Bug: 1016947
> Change-Id: I37d815a111ce4a5cf4a246fc4558d8c7ba5f7fad
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062638
> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
> Auto-Submit: Nico Weber <thakis@chromium.org>
> Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#743604}

TBR=thakis@chromium.org,thomasanderson@chromium.org

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

Bug: 1016947
Change-Id: I057e99ca246ea87fbcc8799f3ba157915e24a54b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2068735Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743922}

* Remove shared-clipboard-receiver (enabled by default)
* Extend shared-clipboard-ui
* Extend sharing-derive-vapid-key
* Extend click-to-call-ui

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

.. the remove the former.

Drive by CL. Both methods are identical.

BUG=None
R=haraken@chromium.org
TBR=kinuko@chromium.org

Change-Id: I664c6289d89ef9b8335d3346c295485bd9312a89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2069571Reviewed-by: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Auto-Submit: Antonio Gomes <tonikitoo@igalia.com>
Commit-Queue: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743920}

https://skia.googlesource.com/skia.git/+log/57bc977e124c..cc5415a8ce36

git log 57bc977e124c..cc5415a8ce36 --date=short --first-parent --format='%ad %ae %s'
2020-02-24 nifong@google.com Modify 3D example with light and bump shader.

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

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 jlavrova@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/+/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: jlavrova@google.com
Change-Id: I3af94fbf769bb4628c1c0d5b7ac3ec5fd43ff91a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2070085Reviewed-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@{#743919}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/e1d7a0fe6ffb..e0897515da03

git log e1d7a0fe6ffb..e0897515da03 --date=short --first-parent --format='%ad %ae %s'
2020-02-24 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS.

Created with:
  gclient setdep -r src/third_party/devtools-frontend/src@e0897515da03

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/+/master/autoroll/README.md

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

..from net::ERR_FAILED to net::ERR_BLOCKED_BY_RESPONSE. This is more
precise, as the navigation was blocked.

Bug: chromium:1051466
Change-Id: Ic3b7166a581710610f00fee197afbd0dcc2e9f14
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066748
Commit-Queue: Sigurd Schneider <sigurds@chromium.org>
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Reviewed-by: Camille Lamy <clamy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743917}

When running the multi user mode on Chrome OS, windows can visit
another user's desktop. This was implemented for up to 3 users and
didn't work correctly when more than 3 users were signed in. Since the
upper limit is 5 users, this cl adds 2 command_ids enabling it for up
to 5 users.

Bug: 940461
Change-Id: I884ce02440a44c0deba449e039da66aa8ceed334
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036055
Commit-Queue: Anina Koehler <aninak@google.com>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Alexander Hendrich <hendrich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743916}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5d5361f3bf54..6b9651c5ec90


Created with:
  gclient setdep -r src-internal@6b9651c5ec90

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@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/+/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: jbudorick@google.com
Change-Id: I180bc680443287e6f40d2c50274dea8e243a9b17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2070083Reviewed-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@{#743915}

This CL adds async/await to the remaining web tests in
http/tests/devtools/console for the upcoming source map asyncification.

The CL also adds a few live location sync points where necessary. This
generally happens right after console message rendering is triggered.
Before the console message is logged, all pending live location
updates need to be {await}ed, as these will happen asynchronous in
the future.

Note: console-uncaught-promise.js is re-baselined as the test output
contains a stack trace with a frame from the test script itself.
As the test moves around some code, we also require a new baseline
reflecting those changes.

Bug: chromium:1032016
Change-Id: I57e5708038f4978b903080e5699afcab4e3f5b05
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066856
Commit-Queue: Simon Zünd <szuend@chromium.org>
Reviewed-by: Mathias Bynens <mathias@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743914}

Used AccessPasswordInSettingsEvent::ACCESS_PASSWORD_COPIED metrics to
count number of times user clicked Copy password button in the password
settings. Added related check to unittests.

Bug: 917337
Change-Id: I4b6172acfaffc0f8b840632cfc320187e242ad7a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2064549
Commit-Queue: Viktor Semeniuk <vsemeniuk@google.com>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743913}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/a66f0bf6..bc317330

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,v8-waterfall-sheriff@grotations.appspotmail.com

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

Now that both Find In Page and Text Zoom have their own separate
commands, we can move the actual implementations into BrowserCoordinator.
This leaves BVC simpler and simplifies the cleanup logic, because now
both coordinators can be stopped in BrowserCoordinator's
-stopChildCoordinators.

Bug: 1052818
Change-Id: Ib19dc967fae1777a086a6184ab328062eeef525c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062442
Commit-Queue: Robbie Gibson <rkgibson@google.com>
Reviewed-by: Mark Cogan <marq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743911}

GCC fails to resolve IsA template as a function parameter in DeleteSelectionCommand.
To avoid this we add a static function that uses it internally, with the expected
function signature expected by EnclosingNodeOfType.

Bug: 819294
Change-Id: If9dfcfb4ca7e298d33545bfd870b6e3d05f9ce76
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2052173
Commit-Queue: José Dapena Paz <jdapena@igalia.com>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743910}

relies on Extensions methods to wait for the web app to be installed,
or to check the web app launch url.

Not yet addressed: InstallBookmarkApp calls in ExtensionPolicyTest.
https://crbug.com/1055183

Bug: 1052722
Change-Id: I5b7f81b8fe3c778ce5adbe46d28da40e7a070986
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2067784Reviewed-by: Alexey Baskakov <loyso@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Maksim Ivanov <emaxx@chromium.org>
Auto-Submit: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743909}

This CL fixes a test that is checking the wrong behavior at the moment,
and disables the test until the fix in V8 lands.

Background:
The idea of the test is to create an invalid WebAssembly module, and
then check that the module is rejected by streaming compilation. The
invalid module was created by taking an empty module and adding two '0'
bytes at the end. However, two '0' bytes represent an empty unknown
section, which was originally accected by the streaming decoder. The
test, however, misinterpreted the test result (i.e. "FAIL Invalid code:
compileStreaming assert_unreached: Should have rejected: undefined
Reached unreachable decoder" a.k.a. FAIL, streaming compilation
succeeded unexpectedly) as the error message of the streaming compiler,
and then marked it in the test expectations as the expected behavior.

The CL changed the test now to add bytes that clearly create an invalid
module, and also deleted the invalid test expectations.

R=leszeks@chromium.org

Bug: v8:10126
Change-Id: Ie49a7a890abd841a85dc9f634308762ea07e5928
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066907Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Commit-Queue: Andreas Haas <ahaas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743908}