GitLab

This CL migrates floating-not-effect-on-grid-items.html
from fast/css-grid-layout to
external/wpt/css/css-grid/grid-model with WPT styles,
adding links to the relevant specs, and test description.

Additionally, this test is renamed to grid-float-002.html
to be aligned with existing tests.

Bug: 1063749
Change-Id: I1fe5a1a554ee2e2a15f526c8d1f18b8ba013ce6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153446
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Manuel Rego <rego@igalia.com>
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/master@{#760297}

No behavior change.

Bug: 1056290
Change-Id: Ic7c1de0e00f86d3941f65f8856eb1baf66667dfb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154725
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760296}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=kariah@chromium.org

Change-Id: I411dfb3cd95f9533e920f35391f3cd4d229438ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155357Reviewed-by: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#760295}

This CL migrates grid-container-scroll-accounts-for-sizing.html
from fast/css-grid-layout to
external/wpt/css/css-grid/grid-model with WPT styles,
adding links to the relevant specs, and test description.

Additionally, this test is renamed to
grid-container-scrollbars-sizing-001.html to be aligned with
existing tests.

Bug: 1063749
Change-Id: I370f3a02a7d5aac8bcfad2544447e1fe046b7a13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153453
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#760294}

This CL migrates grid-container-scroll-accounts-for-auto-margin.html
from fast/css-grid-layout to
external/wpt/css/css-grid/alignment with WPT styles,
adding links to the relevant specs, and test description.

Additionally, this test is renamed to
grid-container-auto-margin-scrollbars-001.html to be aligned
with existing tests.

Bug: 1063749
Change-Id: Ib44cdce4fc7c20121efd8cbf0af76cc325a90f1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153449
Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com>
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Manuel Rego <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#760293}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/f25b9eba..3c8fb8b1

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: Ibce6d6c732689a092146c72ed09718174ca1c9cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153276Reviewed-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@{#760292}

Fix build break when `enable_feed_in_chrome = false`.

Change-Id: I7a3dbb52b47a6cf9ef7081b022ae15db61c26e6d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154628Reviewed-by: Dan H <harringtond@chromium.org>
Commit-Queue: Richard He <linyhe@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#760291}

Absolutely positioned flex items were getting placed wrong when the
containing block was legacy. This patch stores the relevant edges in
legacy and makes NG pick them up on the other side.

The above only works for abspos items controlled by NG. Legacy abspos
flex items with a legacy containing block, e.g.
position-absolute-009.html in this CL, still don't work.

Bug: 845235, 1066859
Change-Id: I3d6beb0bfe80292181b81d2e42bf79bf73ddc834
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146133Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760290}

We no longer use process-per-site for WebUI (see crbug.com/982266), so
fix a couple of comments that implied that we do.

Bug: 1015882, 982266
Change-Id: I639c5b0b159c5e88f15263fdab01dc2dec95b33b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151681Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760289}

https://pdfium.googlesource.com/pdfium.git/+log/4c0fac2e6b05..416bf2e2bf82

git log 4c0fac2e6b05..416bf2e2bf82 --date=short --first-parent --format='%ad %ae %s'
2020-04-18 tsepez@chromium.org Move char/wchar_t vectors to data partition.
2020-04-18 thestig@chromium.org Add third_party/base/immediate_crash.h.
2020-04-17 thestig@chromium.org Use spans in CPDF_TextRenderer.
2020-04-17 thestig@chromium.org Use Chromium-style names in GetCharPosList().

Created with:
  gclient setdep -r src/third_party/pdfium@416bf2e2bf82

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/pdfium-autoroll
Please CC pdfium-deps-rolls@chromium.org 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: pdfium-deps-rolls@chromium.org
Change-Id: I7c0bd27e31bcf94aa2ea77ed93fab0221234852a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155290Reviewed-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@{#760288}

Do not check in about_page_browser_proxy as this is still used by OS
settings, so needs to be autogenerated.

Bug: 1069258
Change-Id: I34fe291d6c1cb71be0a1a94545576829a841e52b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154233Reviewed-by: dpapad <dpapad@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760287}

This change reverts an unintentional ' ' space added to a string in chrome/app/generated_resources.grd

Bug: 1065116
Change-Id: I21e9103fdb8176d07ebbe231bd1a4c795e4fea00
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155018
Commit-Queue: Eric Lawrence [MSFT] <ericlaw@microsoft.com>
Reviewed-by: Eric Lawrence [MSFT] <ericlaw@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#760286}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0f1cadb29473..5ff098232588


Created with:
  gclient setdep -r src-internal@5ff098232588

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 sahel@google.com,pdr@google.com,mamir@google.com,meredithl@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: chromium:1046880,chromium:1069208
Tbr: sahel@google.com,pdr@google.com,mamir@google.com,meredithl@google.com
Change-Id: I39fd8b46eb74040cdde530c6c6a11b6f53c3d0b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155198Reviewed-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@{#760285}

Bug: 1065986
Change-Id: I4d3339006bbea2aaf1a6c9566e34a6faa506b04c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2148247
Commit-Queue: Sam Bowen <sgbowen@google.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Becca Hughes <beccahughes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760284}

Was hitting confusing error messages caused by the code not waiting for
the threads to finish when an exception is thrown by one of them.

Also:
 * Converts from multiprocessing.pool.ThreadPool -> multiprocessing.dummy.Pool
   * Since ThreadPool is an undocumented API.
 * Makes jetify paths a bit nicer (helps grok errors)

Bug: None
Change-Id: I17c676adc2dcb1f42a2698d48dc7b4bf9ab0f3f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155016Reviewed-by: benjamin joyce <bjoyce@chromium.org>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760283}

Using wpt-import in Chromium 388759a2.
With Chromium commits locally applied on WPT:
d0ad7cf8 "UpgradeInsecureRequest: Add WPTs for static-import in dedicated/shared workers"
86131ac4 "Add a test for ReplaceTrack that verifies video track content."
6c8523d2 "[scroll-timeline] Implement element-based scroll offset"
4de68d38 "fixup! [css-grid] Migrate flex-sizing-columns-min-max-width.html to WPT"
f511fde8 "[css-grid] Migrate grid-gutters-and-flex-content.html to WPT"
a236d77b "[css-grid] Migrate grid-gutters-and-tracks.html to WPT"
b0ae2767 "Clean up lazy load tests"


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

Directory owners for changes in this CL:
bjonesbe@adobe.com:
  external/wpt/css/css-shapes
cbiesinger@chromium.org:
  external/wpt/css/css-flexbox
drott@chromium.org, kojii@chromium.org:
  external/wpt/css/css-fonts
kojii@chromium.org:
  external/wpt/css/CSS2/text
kojii@chromium.org, mstensho@chromium.org:
  external/wpt/css/CSS2
mstensho@chromium.org:
  external/wpt/css/css-multicol
rego@igalia.com:
  external/wpt/css/css-contain

NOAUTOREVERT=true
TBR=robertma

No-Export: true
Change-Id: I3d2cf63c5cd393350b32def2529f9a7b75684e27
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153275Reviewed-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@{#760282}

The results of the disk-usage test reports inflated numbers for Chrome
since we don't strip symbols. By doing so here, we can get results
that more resemble what gets shipped on devices.

Bug: 1071107
Change-Id: I55104f1c02a21d076df971e49edbc306e3cdd3d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155050Reviewed-by: Erik Chen <erikchen@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760281}

Bug: 1070409
Change-Id: I140340c6954da9c1bfcd8d004c4978e4e8abe1eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154627
Commit-Queue: Nigel Tao <nigeltao@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760280}

Building renderer.lib clean directly fails.

Repro steps:
1. rmdir /s/q out\default
2. gn gen out\default
3. autoninja.bat -C out\default obj/chrome/renderer/renderer.lib

For details on the process to find these see the comments in crrev.com/c/2153933

Change-Id: Ia4b708b7e9a8bf50294f68437fcb9a38eaf4b595
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153935
Commit-Queue: Brian Manthos <brianman@microsoft.com>
Reviewed-by: Donn Denman <donnd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760279}

Bug: 1065508
Change-Id: Ieb3d033e514a3815743129ce881dfd5c3c08a121
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2149907Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760278}

Bug: 1070409
Change-Id: Icfcf9133efc925696ab5d6f68ceba359ee79363c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154434
Commit-Queue: Nigel Tao <nigeltao@chromium.org>
Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760277}

Bug: 1036023
Change-Id: I4a4ba4b8f9e41dd0f32a487cdf8f10ff0e828926
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155278
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Reviewed-by: Kyle Milka <kmilka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760276}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/d1705a0f..f25b9eba

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: Ie23f47902533355fa9ee545030bd267f170d161f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153735Reviewed-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@{#760275}

Bug: None
Change-Id: I403ae122bf417f3474f15157f23a67a96c3919a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155280
Auto-Submit: dpapad <dpapad@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: dpapad <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760274}

The bot
https://ci.chromium.org/p/chrome/builders/ci/chromeos-betty-pi-arc-cfi-thin-lto-chrome
runs on 104 GB mem machines, but only has a single linker running
at any time.

This bumps it up to 2 (and unpins the value of max_jobs_per_link) to
see what effect it has on build times.

Change-Id: Ifbd14cc05e2bfa60156969a6a8da8ed05f6afa93
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2149388
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Bob Haarman <inglorion@chromium.org>
Reviewed-by: Bob Haarman <inglorion@chromium.org>
Reviewed-by: George Burgess <gbiv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760273}

This is needed for the use of std::find.

Change-Id: I2dc43b3887c467986c5346be5a9e27a987e1e5b3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152333Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#760272}

Bug: 1068008
Test: fast/workers/sandbox-origin-setup-crash.html
Change-Id: I7f87ce0c2a9119f3e78455e15463c5a4e1be9039
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140951
Commit-Queue: Nate Chapin <japhet@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760271}

https://chromium.googlesource.com/angle/angle.git/+log/13e4cdb26a25..2d5da0298b9b

git log 13e4cdb26a25..2d5da0298b9b --date=short --first-parent --format='%ad %ae %s'
2020-04-17 jmadill@chromium.org Minor angle_end2end_tests cleanups.
2020-04-17 lehoangq@gmail.com Separate GLES1's state enum switch code from GLES2+
2020-04-17 cclao@google.com Vulkan: store ImageLayout in PackedAttachmentOpsDesc
2020-04-17 geofflang@google.com Remove more bad files before rolling into AOSP.

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

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 timvp@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_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: None
Tbr: timvp@google.com
Change-Id: I5af8473c3572faa10054cc514f97c382e7a3e3f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154904Reviewed-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@{#760270}

Previously if the signals from dlcservice for installation completion is
posted prior to the installation dbus method callback being posted, the
DCHECK would assert and this change removes the DCHECK.

BUG=b:153527570
TEST=unit_test --gtest_filter=Dlcservice*

Change-Id: I619d2f1b29cf262b76d4c1389a92970b99d47431
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144399
Commit-Queue: Jae Hoon Kim <kimjae@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Auto-Submit: Jae Hoon Kim <kimjae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760269}

https://android.googlesource.com/platform/external/perfetto.git/+log/a5ce9072b623..34b3e095fffc

git log a5ce9072b623..34b3e095fffc --date=short --first-parent --format='%ad %ae %s'
2020-04-17 oysteine@google.com Merge "Pass process_priority from the StreamingProfile packets through to the JSON output"

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

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: I5140fb3f0a9d85ef5f757a091116b42be918c8ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155193Reviewed-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@{#760268}

https://swiftshader.googlesource.com/SwiftShader.git/+log/377573cc1038..068611f07d28

git log 377573cc1038..068611f07d28 --date=short --first-parent --format='%ad %ae %s'
2020-04-17 capn@google.com Fix JIT on separate thread

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

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/+/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: I9f2d11415267e99b1f7148e0baba7b2baa2f47ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155286Reviewed-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@{#760267}

Bug: 1016278
Change-Id: Icd80e3b287f090ffb4ac67437e7e1ebae392c98b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154228Reviewed-by: Peter Kvitek <kvitekp@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760266}

M81 is still deleting backup files, so keeping this metric active
until the end of 2020. Will review then and determine if the
quantity deleted is low enough to remove this feature (and UMA).

Bug: 975751
Change-Id: I43926c27e4ce4dd4d6a06d6a5fa612c1db3bd303
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152887
Commit-Queue: Chris Mumford <cmumford@google.com>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Reviewed-by: Brian White <bcwhite@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760265}

* Remove an extra code block ending.
* Remove a reference to a part of the page that no longer exists.

Change-Id: I59d4979d97070f5396ba4b818ccaba208c584b99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155249Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Sam Bowen <sgbowen@google.com>
Cr-Commit-Position: refs/heads/master@{#760264}

Bug: 1069258
Change-Id: I80674d8534d9773ac9329fde6d931425f3e2b5e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2154822
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@{#760263}

CPU stack sampling profiler jank analysis is hinting at these methods
is this a bias or is there really jank in here? Add trace events to
balance stack sampling with slow reports.

Added trace events to both MessagePumpForUI::ProcessNextWindowsMessage
and MessagePumpForUI::WaitForWork's lookups. The stack sampling
analysis seems to be hinting more at ProcessNextWindowsMessage for
now, but a lot of this gets inlined in Release builds so it's hard to
tell for sure.

This CL also highlights a discrepancy between the checks in
ProcessNextWindowsMessage and WaitForWork. WaitForWork uses
MSG msg = {0} whereas ProcessNextWindowsMessage uses an uninitialized
MSG object. It doesn't seem necessary for this structure to be
initialized, will make it consistent in a follow-up CL.

R=fdoray@chromium.org

Bug: 899897
Change-Id: Ibd8a43e0346e6eb7e09432582a76235ed350ae6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153321
Commit-Queue: Gabriel Charette <gab@chromium.org>
Auto-Submit: Gabriel Charette <gab@chromium.org>
Reviewed-by: oysteine <oysteine@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760262}

This change adds the WebApp.Launcher.UpdateResult metric, which will
report failures updating Progressive Web App (PWA) launcher
executables.

On Windows, each PWA has a separate launcher executable in its web-app
data directory (located at
<User Data dir>/<profile>/Web Applications/_crx_<app ID>/).

When Chrome is launched by an out-of-date PWA launcher, it updates all
PWA launchers for the current profile. Because these updates involve
file operations and take place in the user-data directory, they may
fail due to permissions errors, etc.

This metric will allow us to monitor how often PWA-launcher update is
failing, and handle common failure causes if necessary.

Bug: 1067241
Change-Id: Ie2ea99ea2f1c284a2388e3eb52b664c6ba5af8ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2146084Reviewed-by: Steven Holte <holte@chromium.org>
Commit-Queue: Jesse McKenna <jessemckenna@google.com>
Cr-Commit-Position: refs/heads/master@{#760261}

Also removing obsolete TODO (already addressed), as well as
the unused "showOsSettings" loadTimeData boolean.

Bug: 967888
Change-Id: I36a99fae23e5369b01c9610b837866fce5a7934f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2155182Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: dpapad <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760260}

Bug: 1064424,1018613
Change-Id: I203d857986e6c27c2171ecb4148e3ea928a1b758
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2153454
Commit-Queue: Jia Meng <jiameng@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760259}

This CL wires the API with ash::FpsCounter to report smoothness.

Bug: 1062124
Change-Id: I5df059da64a507ee4349f0717df81633d063a7d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147864
Commit-Queue: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#760258}