NetworkPortalSigninController: Partially revert popup window changes

This reverts the popup window changes for captive portal signin for
supervised users. See bug for details.

BUG=b:335900877
TEST=Manual testing

(cherry picked from commit 2896d2a0a69319ecbb68c12ecd25638640b0d923)

Change-Id: I3bfe6bcb11533e90ca9f5c23e71de4660f9e3418
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517868
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1297179}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5521937
Auto-Submit: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Aga Wronska <agawronska@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#790}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ui/ash/network/network_portal_signin_controller.cc[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1715080407-921c0f98715714cf63480ddd5ffe955df9525bf9-ae4a29683c7e056f90e337adc718a0beabd56127.profdata to chrome-mac-6422-1715102072-7490a3df9710f00640da390f7617a411e4da2fbf-13cfbf145656b369f9c23bff70ab2fb07e1e2fdb.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I05c1c93e224b76cb0fc38fd1c7d5bf45bd0387ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5523166
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#789}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1715080407-98bfeb57250f6be306b28b0c0dd379450877d7ea-ae4a29683c7e056f90e337adc718a0beabd56127.profdata to chrome-linux-6422-1715102072-9bdbfa29f2bb1ff28f0f031b98501a1193b8d03b-13cfbf145656b369f9c23bff70ab2fb07e1e2fdb.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I21a3840c2c309455a4594a90d3afc43ae346879d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5523039
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#788}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

[M125][compose] Handles keyboard navigation with the new submenu.

Key handling added:

1. Horizontal arrows are used to open/close the subpopup.
2. Shift+TAB on an open subpopup closes it and focuses on the parent
   content area.
3. On a subpopup, vertical arrows are used to select different child
   suggestions available.

Demo: https://screencast.googleplex.com/cast/NDc4NzI0ODEzNzUwMjcyMHw5N2M1YjA2YS04Mg
Bug: b/333929225
Change-Id: Ie6c4cbc980ad7c57cf0e8f9bd2447df5751ea922
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513776
Cr-Original-Commit-Position: refs/heads/main@{#1296747}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519285
Commit-Queue: Trevor Perrier <perrier@chromium.org>
Reviewed-by: Bruno Braga <brunobraga@google.com>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#787}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ui/views/autofill/popup/popup_view_views.cc[diff]
• chrome/browser/ui/views/autofill/popup/popup_view_views.h[diff]
• chrome/browser/ui/views/autofill/popup/popup_view_views_unittest.cc[diff]

[Merge to 125] Fix a calendar crash

Root cause: The event list view can open before the up next view is
created. This causes the crash when the event list view is
closed because it cannot find the up-next-view to calculate the
correct height. This issue especially happens with multi-calendar views
due to the increased loading time. This makes it more likely to open
the event list view before the up next view is ready.

Fix: Build the up-next-view if it's not created yet to ensure the
 up-next-view exists before attempting to get its height when
 closing the event list view.

Bug: b/336722659
Change-Id: I43769b21b0533478624e98f7742f15b4164acda2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5523171
Reviewed-by: Alex Newcomer <newcomer@chromium.org>
Commit-Queue: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#786}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/system/time/calendar_view.cc[diff]
• ash/system/time/calendar_view.h[diff]
• ash/system/time/calendar_view_unittest.cc[diff]

[M125]Compose: disable proactive nudge with a random probability.

Bug: 338670197, b/338463183
Change-Id: I88d65bf99a808818b166c3bb1b9e9d674f86670f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512928
Auto-Submit: Justin DeWitt <dewittj@chromium.org>
Commit-Queue: Trevor Perrier <perrier@chromium.org>
Reviewed-by: Trevor Perrier <perrier@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295882}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516726
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Reviewed-by: Christoph Schwering <schwering@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#785}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/compose/chrome_compose_client_unittest.cc[diff]
• chrome/browser/compose/compose_enabling.cc[diff]
• chrome/browser/compose/compose_enabling.h[diff]
• chrome/browser/compose/compose_enabling_unittest.cc[diff]
• components/compose/core/browser/config.cc[diff]
• components/compose/core/browser/config.h[diff]

[M125][Compose] Add new global toggle pref for the proactive nudge

Bug: 338670197, b/335014680
Change-Id: Ibc348516d766094c4ae773152cb87d543fa86dfb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5491036
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Commit-Queue: Anthony Cui <cuianthony@chromium.org>
Reviewed-by: Trevor Perrier <perrier@chromium.org>
Reviewed-by: Dominic Battre <battre@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294403}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516725
Reviewed-by: Christoph Schwering <schwering@google.com>
Commit-Queue: Trevor Perrier <perrier@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#784}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/compose/chrome_compose_client.cc[diff]
• chrome/browser/compose/chrome_compose_client.h[diff]
• chrome/browser/compose/chrome_compose_client_unittest.cc[diff]
• chrome/browser/compose/compose_enabling.cc[diff]
• chrome/browser/compose/compose_enabling.h[diff]
• chrome/browser/compose/compose_enabling_unittest.cc[diff]
• chrome/browser/prefs/browser_prefs.cc[diff]
• chrome/common/pref_names.h[diff]
• components/compose/core/browser/compose_client.h[diff]
• components/compose/core/browser/compose_manager_impl.cc[diff]
• components/compose/core/browser/compose_manager_impl_unittest.cc[diff]

[M125][Compose] Send text selection to proactive nudge

Previously it was assumed that using the autofill popup to start
Compose was only done through the saved state popup.

That assumption is no longer true and there was a bug where selected
text was not used to initiate a Compose session when using the
proactive nudge.

This CL fixes this assumption so selected text works with the
proactive nudge. It also refactors for readability the logic around
the selected text when starting Compose.

While refactoring a bug where kStartedWithSelection was always being
recorded for FRE sessions was accidentally fixed and the unittest
updated.

(cherry picked from commit ea7f08f0358cffb434814241b176d36033b76ccb)

Bug: 338670197, b:335302962
Change-Id: I853c44e954463703897b6d83791b0b5e146194d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5484587
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Auto-Submit: Trevor Perrier <perrier@chromium.org>
Commit-Queue: Trevor Perrier <perrier@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1292747}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516115
Reviewed-by: Christoph Schwering <schwering@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#783}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/compose/chrome_compose_client.cc[diff]
• chrome/browser/compose/chrome_compose_client_unittest.cc[diff]
• chrome/browser/compose/compose_session.cc[diff]
• chrome/browser/compose/compose_session.h[diff]

[M125][compose] Add submenu actions skeleton and forward calls from AED

What this Cl does:

1. Adds the new handler methods for the compose submenu inside the
   compose delegate.
2. Updates the Autofill delegate to forward calls to the methods above
   when a suggestion is accepted.
3. Adds tests to the autofill external delegate only.

Next steps:

1. Implement the handler methods inside the compose submenu. Perhaps
   they could take care of it themselves since this is now agnostic from
   Autofill UI.
2. Think whether we want specific metrics for these suggestions being
   accepted.

Bug: 338670197, b/333929225
Change-Id: I3e10db9497236fabfce2ec2570489802c2d31dd9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5471736
Reviewed-by: Jan Keitel <jkeitel@google.com>
Commit-Queue: Bruno Braga <brunobraga@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1291813}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516348
Commit-Queue: Trevor Perrier <perrier@chromium.org>
Reviewed-by: Christoph Schwering <schwering@google.com>
Reviewed-by: Bruno Braga <brunobraga@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#782}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/autofill/core/browser/autofill_compose_delegate.h[diff]
• components/autofill/core/browser/autofill_external_delegate.cc[diff]
• components/autofill/core/browser/autofill_external_delegate_unittest.cc[diff]
• components/autofill/core/browser/mock_autofill_compose_delegate.h[diff]
• components/compose/core/browser/compose_manager_impl.cc[diff]
• components/compose/core/browser/compose_manager_impl.h[diff]

[M125][compose] Make expandable menu icon depend on suggestion type

Another option could be to make the expandable icon a property of the
suggestion struct. However since for now this is tied to a popup item
id (and I believe it will always be), it is cleaner to make the
decision based on it.

Design: https://screenshot.googleplex.com/BUyAFBrNgKWHMYY
Demo: https://screenshot.googleplex.com/6xstBwFU5s9CVY2

Note: It seems like the design has a bold icon style,
I will ask the compose team whether this is indeed the case.
If so, we can update it accordingly, such update would not affect
what is done in this CL and would likely entail optionally applying
a icon style also depending on the popup item id.

Bug: 338670197, b/333929225
Change-Id: I27751885267afffaaf59ba64bf9f850a8276166b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5471624
Reviewed-by: Jan Keitel <jkeitel@google.com>
Commit-Queue: Bruno Braga <brunobraga@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1291805}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516499
Reviewed-by: Bruno Braga <brunobraga@google.com>
Commit-Queue: Trevor Perrier <perrier@chromium.org>
Reviewed-by: Christoph Schwering <schwering@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#781}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ui/views/autofill/popup/popup_cell_utils.cc[diff]
• chrome/browser/ui/views/autofill/popup/popup_cell_utils.h[diff]
• chrome/browser/ui/views/autofill/popup/popup_cell_utils_unittest.cc[Added - diff]
• chrome/browser/ui/views/autofill/popup/popup_row_view.cc[diff]
• chrome/test/BUILD.gn[diff]

[M125][compose] Create child suggestions for the new nudge design

What this CL does?

1. Introduce the 3 new child suggestions to the compose popup.
2. Introduce the strings.

Next steps:

1. Implement each new suggestion acceptance behaviour.
2. Make it possible to update the expandable suggestion icon.

Demo: https://screencast.googleplex.com/cast/NDYwMjE2MTU5Njk4OTQ0MHw4NzU1NDgxOC02Nw

Bug: 338670197, b/333929225
Change-Id: I053b2a0801853866504efc1a0b7e6eb79e9913d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5471563
Commit-Queue: Bruno Braga <brunobraga@google.com>
Reviewed-by: Jan Keitel <jkeitel@google.com>
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516284
Reviewed-by: Christoph Schwering <schwering@google.com>
Reviewed-by: Bruno Braga <brunobraga@google.com>
Commit-Queue: Trevor Perrier <perrier@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#780}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ui/views/autofill/popup/popup_view_utils.cc[diff]
• components/autofill/core/browser/autofill_external_delegate.cc[diff]
• components/autofill/core/browser/browser_autofill_manager.cc[diff]
• components/autofill/core/browser/filling_product.cc[diff]
• components/autofill/core/browser/ui/popup_item_ids.cc[diff]
• components/autofill/core/browser/ui/popup_item_ids.h[diff]
• components/compose/core/browser/compose_manager_impl.cc[diff]
• components/compose/core/browser/compose_manager_impl_unittest.cc[diff]
• components/compose_strings.grdp[diff]
• components/compose_strings_grdp/IDS_COMPOSE_DISABLE_HELP_ME_WRITE_CHILD_SUGGESTION_TEXT.png.sha1[Added - diff]
• components/compose_strings_grdp/IDS_COMPOSE_GO_TO_SETTINGS_CHILD_SUGGESTION_TEXT.png.sha1[Added - diff]
• components/compose_strings_grdp/IDS_COMPOSE_NEVER_SHOW_ON_THIS_SITE_AGAIN_CHILD_SUGGESTION_TEXT.png.sha1[Added - diff]

[M125][compose] Move suggestion generation to compose delegate.

In order to make Autofill behave more as a platform and load
product specific logic to their delegates, this CL moved compose
suggestion generation away from the manager.

(cherry picked from commit a90822b1df9b9b330728a3599308fa2a44b88840)

Bug: 338670197, b/333929225
Change-Id: Icac575fceb3bd1ae4e73404bab0a504728f86c5f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5466294
Commit-Queue: Bruno Braga <brunobraga@google.com>
Reviewed-by: Peter Boström <pbos@chromium.org>
Reviewed-by: Jan Keitel <jkeitel@google.com>
Reviewed-by: Cait Phillips <caitkp@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1291735}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509213
Reviewed-by: Christoph Schwering <schwering@google.com>
Reviewed-by: Bruno Braga <brunobraga@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#779}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/autofill/core/browser/autofill_compose_delegate.h[diff]
• components/autofill/core/browser/browser_autofill_manager.cc[diff]
• components/autofill/core/browser/browser_autofill_manager_unittest.cc[diff]
• components/autofill/core/browser/mock_autofill_compose_delegate.h[diff]
• components/autofill/core/browser/ui/suggestion.h[diff]
• components/compose/core/browser/BUILD.gn[diff]
• components/compose/core/browser/DEPS[diff]
• components/compose/core/browser/compose_manager_impl.cc[diff]
• components/compose/core/browser/compose_manager_impl.h[diff]
• components/compose/core/browser/compose_manager_impl_unittest.cc[diff]

[merge to 125] splitview: Fix window re-snapped to opposite side

This fixes the incorrect snapped window bounds, which was happening
due to us not ending split view correctly.

Test: added, verified it fails w/o fix
Bug: b/338228780
Change-Id: I20b45dd1e60868396ef8940b9c787be758bbe266
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519971
Commit-Queue: Sophie Wen <sophiewen@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#778}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/wm/splitview/split_view_controller.cc[diff]
• ash/wm/splitview/split_view_multi_display_unittest.cc[diff]

[merge to 125] overview: Fix faster splitview item focus crash

This fixes the dangling ptr crash after the faster split view is
destroyed.

(cherry picked from commit a7331d628f3899102010b8958aca339d1efae5b4)

Test: added, verified it fails w/o fix in CL:5519580
Bug: b/336289329
Change-Id: I879d992802fbced5f26e99dbe2d10992814ad7c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519302
Commit-Queue: Sophie Wen <sophiewen@chromium.org>
Reviewed-by: Sammie Quon <sammiequon@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1297207}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5520009
Cr-Commit-Position: refs/branch-heads/6422@{#777}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/wm/overview/overview_grid.cc[diff]
• ash/wm/snap_group/snap_group_unittest.cc[diff]

Fix size calculations in V8StringToUTF8

While I'm here, remove the unnecessary use of base::WriteInto, which is
a remnant of C++03 copy-on-write strings. Also ask V8 not to write a
NUL terminator because std::(u16)string already owns that byte.

(cherry picked from commit f414dc31032a453f4a6c88977d7894fcb3cba44e)

Bug: 338574384
Change-Id: I5c6eaa99093925db799736f321eab92d35f5acbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515743
Reviewed-by: mmenke <mmenke@chromium.org>
Commit-Queue: David Benjamin <davidben@chromium.org>
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1297196}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5523035
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: mmenke <mmenke@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#776}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• services/proxy_resolver/proxy_resolver_v8.cc[diff]
• services/proxy_resolver/test/data/proxy_resolver_v8_unittest/pac_library_unittest.js[diff]

[M125] [Compose] Default-disable the dogfood footer for on device.

Is not desirable in external usage of this feature.

(cherry picked from commit 0943e1d0753943b65ee57a772b96d045e9b4d28d)

Fixed: 336877207
Change-Id: I366e66c2e8bef31156406844322b909db6712c7e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5485762
Auto-Submit: Justin DeWitt <dewittj@chromium.org>
Reviewed-by: Anthony Cui <cuianthony@chromium.org>
Commit-Queue: Anthony Cui <cuianthony@chromium.org>
Commit-Queue: Justin DeWitt <dewittj@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1292542}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5522335
Cr-Commit-Position: refs/branch-heads/6422@{#775}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/test/data/webui/compose/compose_app_test.ts[diff]
• components/compose/core/browser/compose_features.cc[diff]

[M125] gpu: Fix incorrect Mac backpressure fence wait

In CALayerTreeCoordinator, presented_frames_.front() is the previously
committed (to CoreAnimation) frame, except for the very first frame when
it's the just presented (but not yet committed) frame.

ApplyBackpressure() skips waiting if presented_frames_.front() has been
committed which is almost always the case, except for the very first
frame. The intent of the code is to wait on the previously committed
frame's fence. Therefore the condition to skip needs to be negated.

Skipping backpressure fence wait has two effects:

1) It renders the backpressure fence logic non-functional.

2) It leaks memory since GLContext holds on to the fences indefinitely
   until the caller waits on them.

(cherry picked from commit 21140c0f6162bd8e01800314be8fe460cfab9495)

Fixed: 338254619
Change-Id: I9f1a88256a05bc51b80b10f654cd2f1edc52d3ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516188
Reviewed-by: ccameron chromium <ccameron@chromium.org>
Commit-Queue: ccameron chromium <ccameron@chromium.org>
Auto-Submit: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296939}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5522339
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#774}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ui/accelerated_widget_mac/ca_layer_tree_coordinator.mm[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1715051931-12b547ac72453558f106636bfef7748bfc2f4175-03f989a17183a3e28bfaa697b8561a29f2fdbf25.profdata to chrome-win32-6422-1715080407-8e520284c9bccf2500d36d821aadd7280c0b7ced-ae4a29683c7e056f90e337adc718a0beabd56127.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Iaab846b5f2314e57d50e9bc074b0d703b48418b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5521473
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#773}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Wrap uses of OriginInPageContext in a feature

Adds performance_manager::features::kResourceAttributionIncludeOrigins.
If disabled, Resource Attribution won't record measurements to
OriginInPageContexts, preventing the measurement results from using
extra memory until we figure out the correct lifetime of these contexts.

R=fdoray

(cherry picked from commit 8567b0092b453b4658f45d38d402814098624d8e)

Bug: 333248839
Change-Id: Ib88148493cebc6bfe11e90c4693cd05ab509d01f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5462019
Auto-Submit: Joe Mason <joenotcharles@google.com>
Reviewed-by: Francois Pierre Doray <fdoray@chromium.org>
Commit-Queue: Francois Pierre Doray <fdoray@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1288747}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5522174
Commit-Queue: Joe Mason <joenotcharles@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#772}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/performance_manager/features.cc[diff]
• components/performance_manager/public/features.h[diff]
• components/performance_manager/resource_attribution/cpu_measurement_monitor.cc[diff]
• components/performance_manager/resource_attribution/cpu_measurement_monitor_unittest.cc[diff]
• components/performance_manager/resource_attribution/memory_measurement_provider.cc[diff]
• components/performance_manager/resource_attribution/query_scheduler_unittest.cc[diff]

Incrementing VERSION to 125.0.6422.34

Change-Id: I8f57f0c85f974fc81f9b97100a2dac7273b76b62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5523253
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#771}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/VERSION[diff]

Incrementing VERSION to 125.0.6422.33

Change-Id: Ia57ce679de6ee861c6c0acbf706801ba4a128d60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5523233
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#770}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/VERSION[diff]

[M125] "Delay readability check until page load is done"

Delay readability check until page load is done

1) Removing the server readability check from isReadable so the MTB and
app menu won't trigger the readability.

2) added readability check call 3 seconds after
didFirstVisuallyNonEmptyPaint

3) removed other readability checks that happen early on tab selection

(cherry picked from commit 6b16d0f683ee8d78e9c7b6c794351d7f86b05538)

Bug: 335272896
Change-Id: Ie16afc76cde2dafe554c8a0f1e3373d30c3f7564
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519114
Reviewed-by: Basia Zimirska <basiaz@google.com>
Commit-Queue: Basia Zimirska <basiaz@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1297192}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519125
Reviewed-by: Krishna Govind <govind@chromium.org>
Owners-Override: Krishna Govind <govind@chromium.org>
Auto-Submit: Andrea Gomez <andreaxg@google.com>
Commit-Queue: Krishna Govind <govind@chromium.org>
Commit-Queue: Andrea Gomez <andreaxg@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#769}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/readaloud/android/java/src/org/chromium/chrome/browser/readaloud/ReadAloudController.java[diff]
• chrome/browser/readaloud/android/java/src/org/chromium/chrome/browser/readaloud/ReadAloudControllerUnitTest.java[diff]
• chrome/browser/readaloud/android/java/src/org/chromium/chrome/browser/readaloud/ReadAloudToolbarButtonController.java[diff]

[M125] gpu: Skip signaling shared event for Ganesh only IOSurface access

Shared events are only used in IOSurface backings for access across
Metal devices so skip signaling shared events on GL EndAccess unless
WebGPU or Graphite access might be needed.

For GL access across multiple GPUs which would be on different Metal
deivces, waitUntilScheduled synchronization is enough so we don't need
the shared events for that either.

(cherry picked from commit 105f286a5b10336f6a7cba54b0ba1b5748fcf3d4)

Bug: 337998762
Change-Id: I95d77d0dd33f95cba7614f5967fd7892d6df34a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5503316
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org>
Auto-Submit: Sunny Sachanandani <sunnyps@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296141}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517263
Cr-Commit-Position: refs/branch-heads/6422@{#768}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• gpu/command_buffer/service/shared_image/iosurface_image_backing.h[diff]
• gpu/command_buffer/service/shared_image/iosurface_image_backing.mm[diff]

[125] Remove a NOTREACHED that can happen

People on iPad can have manually enabled tab-groups-in-grid but not
modern-tab-strip.
This CL adds a DumpWithoutCrashing instead of a NOTREACHED, to still get
the signal about those iPads, but not have them crash.

(cherry picked from commit 486211f7a9740690c12edbe293f7eb68d77b17ca)

Bug: 333377248
Change-Id: I1a2680105fb49019828a1b022696ede00b2a1677
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514751
Auto-Submit: Louis Romero <lpromero@google.com>
Reviewed-by: Ewann Pellé <ewannpv@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Éric Noyau <noyau@chromium.org>
Commit-Queue: Louis Romero <lpromero@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1296780}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518412
Owners-Override: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#767}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/tabs/tab_strip_controller.mm[diff]

[CP-125] Fix high contrast colors for Pseudo-elements.

This CL addresses an issue where Pseudo elements fail to have forced
colors applied in Windows High Contrast mode. The issue was caused when
the resolution of some internal forced colors properties was moved from
used value time to computed value time (particularly style adjustment,
see CL:5181788). This move was necessary as system colors are now
retrieved from color providers that are accessible from the Document.

In the previous approach, The Color Provider was retrieved from the
Element's Document. However, when adjusting styles for Pseudo elements,
nullptr is passed for the Element parameter. This results in a fallback
to the default colors.

To fix this, the method of Document retrieval is altered. Instead of
accessing the Document from the Element, we now retrieve it from the
StyleResolverState. This change ensures that we do not have to rely on
the Element itself to access the Document or ColorProvider. As a
result, we have valid color providers for all elements, including Pseudo
elements. Ultimately, leading to the correct retrieval of system
colors.

(cherry picked from commit 450602e26f948d845425cef9d1406a9f126b818a)

Bug: 337900469
Change-Id: I7e02cf932eb2bf8c875b279cf2dda20c54df06f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514692
Reviewed-by: Alison Maher <almaher@microsoft.com>
Commit-Queue: Sam Davis Omekara <samomekarajr@microsoft.com>
Cr-Original-Commit-Position: refs/heads/main@{#1296443}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517267
Cr-Commit-Position: refs/branch-heads/6422@{#766}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/chrome_content_browser_client_browsertest.cc[diff]
• chrome/test/data/system-colors.html[Added - diff]
• third_party/blink/renderer/core/css/resolver/style_adjuster.cc[diff]
• third_party/blink/renderer/core/css/resolver/style_adjuster.h[diff]

Fix the color in dark mode of the VCN enrollment explanatory message.

Set the primary color on the explanatory message of the virtual card
enrollment screen on iOS to fix the color in dark mode.

Dark mode screenshot:
https://screenshot.googleplex.com/A9yNQrkPfd6bytr.png

Light mode screenshot:
https://screenshot.googleplex.com/54ZNxYnWLHufeYQ.png

Bug: 339026503
Change-Id: I70cbe50ece58a453e41244e783256f4cb39b6826
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515733
Reviewed-by: Tommy Martino <tmartino@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Owners-Override: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#765}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/autofill/bottom_sheet/virtual_card_enrollment_bottom_sheet_view_controller.mm[diff]

[M125]Don't stop playback onUrlUpdated

This CL brings back the state to how it was before M124. Putting maybeHandleTabReload and maybeStopPlayback in onUrlUpdated causes premature playback termination.

(cherry picked from commit 19f4c6c7cd5bdf0f174c9ce023c633ff3aec921d)

Bug: b/338392803
Change-Id: Id38c2be97c8844985aab070b0fc070b9c239b626
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517248
Reviewed-by: Andrea Gomez <andreaxg@google.com>
Auto-Submit: Basia Zimirska <basiaz@google.com>
Commit-Queue: Basia Zimirska <basiaz@google.com>
Reviewed-by: Basia Zimirska <basiaz@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1297057}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519279
Owners-Override: Krishna Govind <govind@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#764}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/readaloud/android/java/src/org/chromium/chrome/browser/readaloud/ReadAloudController.java[diff]
• chrome/browser/readaloud/android/java/src/org/chromium/chrome/browser/readaloud/ReadAloudControllerUnitTest.java[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1715051931-2bf4f2922e03b22cc6997d672ea9c20a5881f581-03f989a17183a3e28bfaa697b8561a29f2fdbf25.profdata to chrome-win64-6422-1715080407-c2efb54bce3d831b1bff922711c4b5481e2aa150-ae4a29683c7e056f90e337adc718a0beabd56127.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I4c8c2c6f22b9a07c2945fa06cf68641da200ad88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5521477
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#763}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

[m125] Harden Tab Search against empty BrowserList

Several pre-existing JS errors in Tab Search are having higher error
rates because of the preloading experiments. This patches contain two
mitigations:

* Don't preload Tab Search for browsers other than TYPE_NORMAL, since
  that's the only browser type that may have top chrome WebUIs.
  This will address the biggest sources of errors that we are seeing
  during ChromeOS login. The login pages creates a TYPE_APP browser but
  does not have any other browsers that host regular tabs.
* Don't update the Tab Search page if there is no browser window. This
  seems to happen during shutdown.

(cherry picked from commit 8e36899cd5b1284bae415924c92f6f5f4f146305)

Bug: 336753301, 337307746
Change-Id: Icd7ee80a827f967d0dce5e505f4f73b1ef217042
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5506635
Reviewed-by: Allen Bauer <kylixrd@chromium.org>
Commit-Queue: Keren Zhu <kerenzhu@chromium.org>
Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296136}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518356
Cr-Commit-Position: refs/branch-heads/6422@{#762}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/resources/tab_search/infinite_list.ts[diff]
• chrome/browser/resources/tab_search/tab_organization_page.ts[diff]
• chrome/browser/resources/tab_search/tab_search_page.ts[diff]
• chrome/browser/ui/views/frame/browser_view.cc[diff]
• chrome/browser/ui/webui/top_chrome/webui_contents_preload_manager.cc[diff]
• chrome/browser/ui/webui/top_chrome/webui_contents_preload_manager.h[diff]

[M125][UNOp2][Android] Refresh metrics service state in restore flow

No metric was visible for the backup/restore experiment 1 week after
it's enabled on dev/canary, and the study was not visible on the Finch
dashboard.

Following our tests, the flag's value is retrieved correctly according
to the configured distribution (50%), so our current hypothesis is that
the experiment metrics couldn't be uploaded since UMA upload was never
enabled in the restore flow, which is guarded by feature flags.

This CL updates the metrics service state in the restore flow, after
the Android preferences are restored. This would enable the metrics
upload if it's allowed by the just restored metrics-related preferences
PRIVACY_METRICS_REPORTING_PERMITTED_BY_USER and
PRIVACY_METRICS_REPORTING_PERMITTED_BY_POLICY. A flag is also added
to guard this change.

(cherry picked from commit 5799994d349cdaf935833d4eca33a772f4a5c1d2)

Bug: 338972271
Change-Id: I7890a6b130c0cbfb8c2db5a755dea561fb216bbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513688
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Commit-Queue: Menghan Yang <myuu@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1296820}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515177
Reviewed-by: Nohemi Fernandez <fernandex@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#761}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/java/src/org/chromium/chrome/browser/ChromeBackupAgentImpl.java[diff]
• chrome/android/junit/src/org/chromium/chrome/browser/ChromeBackupAgentTest.java[diff]
• components/signin/public/base/signin_feature_map.cc[diff]
• components/signin/public/base/signin_switches.cc[diff]
• components/signin/public/base/signin_switches.h[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1715051931-fc5a3fdedea379fee78a08e6c7ce07542bd39c70-03f989a17183a3e28bfaa697b8561a29f2fdbf25.profdata to chrome-mac-6422-1715080407-921c0f98715714cf63480ddd5ffe955df9525bf9-ae4a29683c7e056f90e337adc718a0beabd56127.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I9b76547e3fa1cefaf494e9be6c795d56b67ccf74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5521476
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#760}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1715038476-4f7b6f71f23ba23f402b57294718f828a5fcaedf-9c3c4c782b31989fd27e958279614427b8d5cb1e.profdata to chrome-linux-6422-1715080407-98bfeb57250f6be306b28b0c0dd379450877d7ea-ae4a29683c7e056f90e337adc718a0beabd56127.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ib9d40d37bb08e2970e39f87c6cfb682b98726c65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5521834
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#759}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Force-enable tasks view for `ENABLE_MERGE_REQUEST` build flag

PS10 - dry run with the flag manually turned on
PS11 - dry run with the flag turned off

(cherry picked from commit b97f12bdaf6d2fca80add6ae26051dcce94601e3)

Bug: b/337887051
Change-Id: I9db28a2b07f4743f394b4657a9553a404b24b93c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5498459
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: Artsiom Mitrokhin <amitrokhin@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295427}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510726
Cr-Commit-Position: refs/branch-heads/6422@{#758}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/constants/BUILD.gn[diff]
• ash/constants/DEPS[diff]
• ash/constants/ash_features.cc[diff]
• ash/constants/ash_switches.cc[diff]
• ash/constants/ash_switches.h[diff]
• ash/glanceables/classroom/glanceables_classroom_student_view_unittest.cc[diff]
• ash/system/time/calendar_view_pixeltest.cc[diff]
• ash/system/time/calendar_view_unittest.cc[diff]
• ash/system/unified/date_tray_unittest.cc[diff]
• chrome/browser/ui/ash/glanceables/glanceables_browsertest.cc[diff]
• chrome/browser/ui/ash/glanceables/glanceables_keyed_service_factory_unittest.cc[diff]

Automated Commit: LKGM 15853.24.0 for chromeos.

Uploaded by https://ci.chromium.org/b/8748640922256992913

Change-Id: Id73ab511f54f419b3aac3a43c901bae452dd06c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5520104
Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#757}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/CHROMEOS_LKGM[diff]

Roll ChromeOS Bigcore AFDO profile from 125-6422.10-1714384890-benchmark-125.0.6422.30-r1 to 125-6422.19-1714988325-benchmark-125.0.6422.31-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-bigcore-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I0447ac15f698fe74800042f8af882d5ce0aaa1cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5520994
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#756}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/bigcore.afdo.newest.txt[diff]

Roll commits from side projects in M125

Roll src/clank in M125 from 2cc0ad973a78 to 5de620fdfd73
Commits rolled:
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/2cc0ad973a78..5de620fdfd73

Generated by: http://go/bbid/8748598625858197313

Change-Id: I2fe8d47b238ca887474934f26a73c4ced7957877
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512180
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#755}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• DEPS[diff]
• clank[diff]

Roll ChromeOS Atom AFDO profile from 125-6422.10-1714388999-benchmark-125.0.6422.30-r1 to 125-6422.19-1714990376-benchmark-125.0.6422.31-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: Idfa75e4ec3a8f2ca5cb819534a5f75614f24cff7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519793
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#754}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/atom.afdo.newest.txt[diff]

Roll Amd64 AFDO from 125.0.6422.30_rc-r1-merged to 125.0.6422.31_rc-r1-merged

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file go/crostc-bug.

Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.

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

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: Ic8db37b59bec8cc818d0d8711b03c86faf587145
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517376
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#753}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/profiles/newest.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1715038476-4bea6297e85a71f309b2ae553167c89dd4884b93-9c3c4c782b31989fd27e958279614427b8d5cb1e.profdata to chrome-win64-6422-1715051931-2bf4f2922e03b22cc6997d672ea9c20a5881f581-03f989a17183a3e28bfaa697b8561a29f2fdbf25.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ib1cfff877728bb473ba9504239be9f5c49c0ad2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5520004
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#752}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1715038476-8574bc58ec6c246af2c6212c90817db0308d7f55-9c3c4c782b31989fd27e958279614427b8d5cb1e.profdata to chrome-win32-6422-1715051931-12b547ac72453558f106636bfef7748bfc2f4175-03f989a17183a3e28bfaa697b8561a29f2fdbf25.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I07de2cd1967ee3ef150c9f66e1468536ffa1fa3f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5520179
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#751}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1715038476-4cf956e02cc1ab599c5e005b6ee532463175f4f2-9c3c4c782b31989fd27e958279614427b8d5cb1e.profdata to chrome-mac-6422-1715051931-fc5a3fdedea379fee78a08e6c7ce07542bd39c70-03f989a17183a3e28bfaa697b8561a29f2fdbf25.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I711f1a5619319908e19f03c4c06ac03b817294dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5520137
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#750}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1715018346-b24c7f9bacef052c057c9ae6f0608191df6be660-c392282f1d545d3a4a2e0cfab7ffd0cde1b8fad9.profdata to chrome-win64-6422-1715038476-4bea6297e85a71f309b2ae553167c89dd4884b93-9c3c4c782b31989fd27e958279614427b8d5cb1e.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ice1f4417ad23cfe83b4934ee59b379f6b8f7f231
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519645
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#749}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1715018346-5df91686f0eb2a7a1ed1fce85d29965e087c31fb-c392282f1d545d3a4a2e0cfab7ffd0cde1b8fad9.profdata to chrome-win32-6422-1715038476-8574bc58ec6c246af2c6212c90817db0308d7f55-9c3c4c782b31989fd27e958279614427b8d5cb1e.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I9cc7224cf46411027f54f63e92cd474628750771
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519760
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#748}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714965549-67f55072099cc4fcfd5620614bbcffa72f00dbee-293694deb402782d5bdb6adb4c617c9f47eb0a74.profdata to chrome-mac-6422-1715038476-4cf956e02cc1ab599c5e005b6ee532463175f4f2-9c3c4c782b31989fd27e958279614427b8d5cb1e.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I87035a9cb37348577040e6ddbb9baf37925a4ba5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519894
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#747}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1715018346-cf07f452369228d92a8c50ea650530823139efe3-c392282f1d545d3a4a2e0cfab7ffd0cde1b8fad9.profdata to chrome-linux-6422-1715038476-4f7b6f71f23ba23f402b57294718f828a5fcaedf-9c3c4c782b31989fd27e958279614427b8d5cb1e.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I695bee3bfd4e32e07207991499473f6b0fa04bae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519482
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#746}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

[lacros skew tests] Refresh skew tests for M126 M126

This CL updates the ash version ['126.0.6463.0', '126.0.6440.0'] for Lacros version skew testing.
This cl only affect linux-lacros config builders like
linux-lacros-tester-rel, linux-lacros-rel.
This cl will certainly NOT affect Lacros on-device builders
(lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab,
etc) or any other platforms.

If this CL caused regressions, please revert and stop the autoroller
at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller
Also please file a bug to OS>LaCrOS>Partner, and CC kuanhuang@chromium.org.

R=rubber-stamper@appspot.gserviceaccount.com

Bug: None
Change-Id: Ie743f511b16e087fe9adb714b23a43107fda3658
Requires-Testing: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515302
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#745}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• infra/config/generated/testing/variants.pyl[diff]
• infra/config/targets/lacros-version-skew-variants.json[diff]
• testing/buildbot/chromium.chromiumos.json[diff]
• testing/buildbot/chromium.coverage.json[diff]
• testing/buildbot/chromium.fyi.json[diff]
• testing/buildbot/chromium.memory.json[diff]
• testing/buildbot/variants.pyl[diff]

Roll commits from side projects in M125

Roll src/clank in M125 from 95394ba2d31e to 2cc0ad973a78
Commits rolled:
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/95394ba2d31e..2cc0ad973a78

Generated by: http://go/bbid/8748638265832617601

Change-Id: I6d1eb21ee6f710a1514c77d92d135c014bb54b60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513173
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#744}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• DEPS[diff]
• clank[diff]

Incrementing VERSION to 125.0.6422.32

Change-Id: I360f5fcb906b53f824824a168e84b62aabe66e95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516078
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#743}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/VERSION[diff]

C.P: Revert "Enable UsedColorSchemeRootScrollbars feature"

Cherry picking into chromium v125 branch.


This reverts commit f086db0f5117a6c32a6b4afa80a043226e51cfad.

Reason for revert: https://issues.chromium.org/issues/337904215

Original change's description:
> Enable UsedColorSchemeRootScrollbars feature
>
> I2S: https://groups.google.com/a/chromium.org/g/blink-dev/c/UdOQkoMJYnY
> Chromestatus: https://chromestatus.com/feature/5089486318075904
>
> Bug: 40259909
> Change-Id: I6da2fe5e30237748d29df6171e7a6a80e659c0b1
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5406829
> Reviewed-by: Robert Flack <flackr@chromium.org>
> Commit-Queue: Yaroslav Shalivskyy <yshalivskyy@microsoft.com>
> Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
> Cr-Commit-Position: refs/heads/main@{#1282111}

(cherry picked from commit 1b4efb9594c143677b7a3392327e754b68b1607d)

Bug: 40259909, 337904215
Change-Id: I74e34a443c8478e99151ac8ec5e261c5481101ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5501644
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Yaroslav Shalivskyy <yshalivskyy@microsoft.com>
Cr-Original-Commit-Position: refs/heads/main@{#1294913}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510750
Reviewed-by: Olga Gerchikov <gerchiko@microsoft.com>
Commit-Queue: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#742}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• third_party/blink/renderer/platform/runtime_enabled_features.json5[diff]

[M125][Compose] Update colours and modifier options order to match spec

(cherry picked from commit 070d6e584384e010196b486c9791b06fc05102ce)

Bug: 338280329, b/335854621
Change-Id: I4011bcc9e99054189487bfac0cae694ef61bc582
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5507894
Auto-Submit: Anthony Cui <cuianthony@chromium.org>
Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Reviewed-by: Trevor Perrier <perrier@chromium.org>
Commit-Queue: Anthony Cui <cuianthony@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295199}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518682
Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#741}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/resources/compose/app.html[diff]
• chrome/browser/resources/compose/app.ts[diff]
• chrome/browser/ui/color/chrome_color_id.h[diff]
• chrome/browser/ui/color/material_chrome_color_mixer.cc[diff]

[M125] Don't use destination SiteInstance on extension redirects to data/about URLs

In the linked bug, we saw crashes where the calculated origin for
a navigation doesn't match the SiteInstance chosen for it. After
investigation, we found it might be caused by a history navigation
that got redirected to a data: URL. In the current code, we would
try to reuse the SiteInstance saved in the FrameNavigationEntry (not
related to the data URL) but use a newly calculated opaque origin for
the data URL, causing the mismatch and crash.

This CL fixes the crash by making sure we won't use the destination
SiteInstance from the FrameNavigationEntry in those cases. Note that
this actually leads to a slightly different crashing case for the
about:blank redirect case: since we won't reuse the saved
SiteInstace, the about:blank redirect will reuse  the previous page's SiteInstance (see SiteInstanceImpl::IsSameSite()). If that
SiteInstance doesn't match the final origin, we'll crash. This case
is not fixed by this CL, but since the crash will only trigger for a
smaller subset than before, it's slightly in a better state

(cherry picked from commit d2cbc59a0a47f3a320661488615a2d932545a1ec)

Bug: 1454273, 1440543
Change-Id: Ibcaf9de5608600199db17c347f7a50039a853fb4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5238193
Auto-Submit: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1292003}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517262
Commit-Queue: Charlie Reis <creis@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#740}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/chrome_navigation_browsertest.cc[diff]
• content/browser/renderer_host/render_frame_host_manager.cc[diff]
• content/browser/renderer_host/render_frame_host_manager.h[diff]
• content/browser/site_instance_impl.cc[diff]

M125: Adjust PdfService sandbox type to prevent crashes

Change the sandbox type from `kService` back to `kUtility`, which is
the sandbox type used on Chrome OS when PdfService was part of
PrintingService. Then the sandbox will allow __NR_sysinfo and let code
execution proceed when PDFium calls into FreeType.

Add a test case for this scenario using an existing test PDF that can
trigger the crash.

(cherry picked from commit 508f1f09dab21aab3e96fd66e84b35ed620e7cd2)

Bug: 334272439
Change-Id: Iaf891aece171bb47362d959cb00080e5e4ba8ff8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5503386
Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294784}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517239
Cr-Commit-Position: refs/branch-heads/6422@{#739}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ash/extensions/file_manager/file_manager_private_apitest.cc[diff]
• chrome/services/pdf/public/mojom/pdf_service.mojom[diff]
• chrome/test/data/extensions/api_test/image_loader_private/get_pdf_thumbnail/test.js[diff]

Fix how we determine page language

The previous way was causing crashes with new tabs.

(cherry picked from commit 705bdc36eb67749f081c4240b25fbffb69aaff11)

Bug: 335760697, 40275871
Change-Id: I9eff086ce2cac753f6216c6c363a77b80ee1301a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5468740
Commit-Queue: Kristi Saney <kristislee@google.com>
Auto-Submit: Kristi Saney <kristislee@google.com>
Reviewed-by: Lauren Winston <lwinston@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1290184}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519120
Cr-Commit-Position: refs/branch-heads/6422@{#738}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ui/webui/side_panel/read_anything/read_anything_untrusted_page_handler.cc[diff]
• chrome/browser/ui/webui/side_panel/read_anything/read_anything_untrusted_page_handler.h[diff]

Prevent the pinned actions container from returning a too small size during animation.

This changes the custom flex rule logic that prevents the divider from
showing when the last pinned button is hidden to only happen if we are
not in the middle of an animation. This is a temporary fix for a bug
where icons overlap if only one side panel is pinned and follow up work
will be to remove the custom flex rule and write a custom target layout
class. This can cause a double divider to be seen occasionally if the
window is too small to fit the last pinned side panel but too big to
naturally overflow the divider.

(cherry picked from commit 83da742459d0f04d400d57c0370a671ebcbbd56f)

Bug: 337932320
Change-Id: Ie150c807661bbbc99a5835f06f5ba3b783c09f63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513365
Reviewed-by: Taylor Bergquist <tbergquist@chromium.org>
Commit-Queue: Caroline Rising <corising@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296224}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516225
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Caroline Rising <corising@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#737}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ui/views/toolbar/pinned_toolbar_actions_container.cc[diff]

[M125] Set RTCEncodedVideoFrame timestamp to capture_begin_time if available

This CL also modifies the test to start using getUserMedia as the
timeouts occur when we use getNoiseStream, which creates first frame
with timestamp 0 which leads to frame drops. We also add another test
that inserts a new VideoFrame with new timestamp.

We also modify the TestExpectations of the corresponding test to
FAIL/PASS/Timeout as this change should convert the test results
timeouts to fail/pass.

Doc: go/capture-timestamp-flake

(cherry picked from commit 6dd559335a5990c3c149256fbdce3ff0a600f6f0)

Bug: 333739617, 338388034
Change-Id: I043009f05e21894a3bf8751c856bd2b6b646fbad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509354
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Palak Agarwal <agpalak@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296025}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518414
Reviewed-by: Markus Handell <handellm@google.com>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#736}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• third_party/blink/renderer/platform/peerconnection/webrtc_video_track_source.cc[diff]
• third_party/blink/web_tests/TestExpectations[diff]
• third_party/blink/web_tests/fast/peerconnection/RTCEncodedVideoFrameMetadata-timestamp.html[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714992741-dcf5220c329f2230a03d2f8faf7dfd9d03800f77-7715f73c18a154637489bc1192fbe6e1193a1487.profdata to chrome-win64-6422-1715018346-b24c7f9bacef052c057c9ae6f0608191df6be660-c392282f1d545d3a4a2e0cfab7ffd0cde1b8fad9.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I66db95d29663ff957fd31b885ab3a51ead7822af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518025
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#735}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

[Compose] add trimmed inner text for on device model

(cherry picked from commit 261a0eaca03ba687387cdccdfc08ff34774026a5)

Bug: 338083406
Change-Id: I343d5a9e989f362200fea032d02b3f7aff1498e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5507078
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Reviewed-by: Trevor Perrier <perrier@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296202}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517246
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#734}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/compose/compose_session.cc[diff]
• chrome/browser/compose/compose_session.h[diff]
• components/compose/core/browser/BUILD.gn[diff]
• components/compose/core/browser/compose_prompt_trimming_unittest.cc[Added - diff]
• components/compose/core/browser/compose_utils.cc[diff]
• components/compose/core/browser/compose_utils.h[diff]
• components/compose/core/browser/config.cc[diff]
• components/compose/core/browser/config.h[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714992741-0e6cf342293c1fdd378d1de192b0b96126b96da4-7715f73c18a154637489bc1192fbe6e1193a1487.profdata to chrome-win32-6422-1715018346-5df91686f0eb2a7a1ed1fce85d29965e087c31fb-c392282f1d545d3a4a2e0cfab7ffd0cde1b8fad9.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I7883e055a0e57582a9f15af02c588f08ff6a5995
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518619
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#733}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

M125: Roll R8 from jiR3Cmr6zLjEDaMOA... to mhSwabeiU2ueQeYkj...

Bug: 336841815

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/r8-chromium
Please CC clank-build@google.com,clank-library-failures@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

(cherry picked from commit c66ea39473a090395730efc96b7f1223b999b011)

Tbr: clank-library-failures@google.com
Change-Id: I402a02d38d72b56309ba5c220cdb17c12bb07826
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5476088
Bot-Commit: 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-Original-Commit-Position: refs/heads/main@{#1291206}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519112
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Jian Li <jianli@chromium.org>
Auto-Submit: Jian Li <jianli@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#732}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• DEPS[diff]

[M125] Revise the cohort reset relation with cookie deletion

(Merge to release branch M125 for stable channel. Feature is behind a finch flag)

This revision will only perform cohort reset when deletions that delete most URLs except for a small exception list are made.

(cherry picked from commit 7a29165c73816ca51e91349f16fea330f75f6c44)

Bug: b:338062050
Change-Id: I701d00dae57dd363fee94cddf40fc23982498e7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5502154
Auto-Submit: Jonathan Njeunje <njeunje@chromium.org>
Commit-Queue: Jonathan Njeunje <njeunje@chromium.org>
Reviewed-by: Anton Maliev <amaliev@chromium.org>
Reviewed-by: Ayu Ishii <ayui@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295126}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510063
Cr-Commit-Position: refs/branch-heads/6422@{#731}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/browsing_data/chrome_browsing_data_remover_delegate.cc[diff]
• chrome/browser/browsing_data/chrome_browsing_data_remover_delegate_unittest.cc[diff]
• components/tpcd/metadata/manager.cc[diff]
• components/tpcd/metadata/manager.h[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714992741-798475d23882d594d16f8ce4c9f9c95deb1b960e-7715f73c18a154637489bc1192fbe6e1193a1487.profdata to chrome-linux-6422-1715018346-cf07f452369228d92a8c50ea650530823139efe3-c392282f1d545d3a4a2e0cfab7ffd0cde1b8fad9.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ia8884acbaf2f5926b1e6f556d0e3a59ea11cac33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518384
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#730}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

[M125][Compose] Update modifier menu options colours

This updates the text colour used to have more contrast between enabled and disabled options. This also updates the background colour of the dropdown to match the Chrome mode/theme, which keeps options text legible even if the user's OS and Chrome appearance modes are out of sync.

light mode example:
https://screenshot.googleplex.com/7Kj6ayMzWFqWprt
dark mode example:
https://screenshot.googleplex.com/4HCfMyV2VEKwMSf

(cherry picked from commit 3e457afa179f826e294486da3bcf37ea7ad1080d)

Bug: 338463374, b/337895290, b/337888856
Change-Id: Ia8b371f0d9875065bef55ba4f99ed2e86271096d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512803
Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Commit-Queue: Anthony Cui <cuianthony@chromium.org>
Reviewed-by: Trevor Perrier <perrier@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296123}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517258
Auto-Submit: Anthony Cui <cuianthony@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Thomas Lukaszewicz <tluk@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#729}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/resources/compose/app.html[diff]
• chrome/browser/ui/color/chrome_color_id.h[diff]
• chrome/browser/ui/color/material_chrome_color_mixer.cc[diff]

Update MQLS protos for cl/629505388.

(cherry picked from commit f2aa02af5efa2d4d52d5980c63c1f9033e92799a)

Bug: b/338097476
Change-Id: I1d355cb88d3ffc92cd54af26cb528ba3f31baf46
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5502993
Reviewed-by: Sreeja Kamishetty <sreejakshetty@chromium.org>
Commit-Queue: Sreeja Kamishetty <sreejakshetty@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294636}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519189
Reviewed-by: Max Curran <curranmax@chromium.org>
Commit-Queue: Jeffrey Cohen <jeffreycohen@chromium.org>
Auto-Submit: Jeffrey Cohen <jeffreycohen@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#728}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/optimization_guide/proto/features/compose.proto[diff]

Add libsegmentation merge request

Add rules to add |merge_request| define.

(cherry picked from commit 451bb7afb1678587fa2d218be67ddba7861e575b)

Change-Id: Id424552c661fda91efeafa43ec63eb23ccd32cf8
Bug: 336007541
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5481472
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Reviewed-by: David Black <dmblack@google.com>
Commit-Queue: Gwendal Grignou <gwendal@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293292}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516374
Cr-Commit-Position: refs/branch-heads/6422@{#727}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/components/libsegmentation/BUILD.gn[Added - diff]
• chromeos/components/libsegmentation/DIR_METADATA[Added - diff]
• chromeos/components/libsegmentation/OWNERS[Added - diff]
• chromeos/components/libsegmentation/README[Added - diff]
• chromeos/components/libsegmentation/buildflags.gni[Added - diff]

[m125] Fix MediaStreamVideoCapturerSource no-return-after-failure

In MediaStreamVideoCapturerSource, if SendWheel() or SetZoomLevel()
encountered a missing device ID, they invoke the callback,
but they failed to return immediately. Instead, they passed that
moved-from callback onwards to the MediaStreamDispatcherHost.

This CL fixes this issue.

(cherry picked from commit 780e58ee6c33b9d54ba3222c00a9b96f36ef600c)

Bug: 337847746
Change-Id: I29ddbf95d3fde50357a5190049db1175bffcadcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5497319
Auto-Submit: Elad Alon <eladalon@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Elad Alon <eladalon@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293993}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5501236
Reviewed-by: Tove Petersson <tovep@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#726}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• third_party/blink/renderer/modules/mediastream/media_stream_video_capturer_source.cc[diff]
• third_party/blink/renderer/modules/mediastream/media_stream_video_capturer_source.h[diff]
• third_party/blink/renderer/modules/mediastream/media_stream_video_capturer_source_test.cc[diff]

Add FeatureParam to change button order on one-time permission dialog.

(cherry picked from commit 90a48f53da9399d022376231d33d380d7885cf8d)

Bug: 338342764
Change-Id: I6b7f32b98747a32e5503a10c40a4c4898866da4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509516
Commit-Queue: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Thomas Nguyen <tungnh@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295716}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518175
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Commit-Queue: Florian Jacky <fjacky@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#725}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ui/views/permissions/permission_prompt_bubble_base_view.cc[diff]
• components/permissions/android/java/src/org/chromium/components/permissions/PermissionDialogDelegate.java[diff]
• components/permissions/android/java/src/org/chromium/components/permissions/PermissionDialogModelFactory.java[diff]
• components/permissions/android/permission_prompt/permission_dialog_delegate.cc[diff]
• components/permissions/features.cc[diff]
• components/permissions/features.h[diff]

Roll commits from side projects in M125

Roll src/clank in M125 from 0f650cfddbb7 to 95394ba2d31e
Commits rolled:
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/0f650cfddbb7..95394ba2d31e

Generated by: http://go/bbid/8748666572072743057

Change-Id: Ic7bc699770a30a579f7b05960a181a5a454c96ba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513875
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#724}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• DEPS[diff]
• clank[diff]

[Merge to M-125]gd: Create a GameDashboardContext if the game window is parented.

When creating a GameDashboardContext for a game window, the window may
not be parented. The GameDashboardController will wait for the game
window to be parented before creating a GameDashboardContext instance.

This CL no longer depends on the window visibility to change before
creating a GameDashboardContext.

(cherry picked from commit e4e47882a5d970f72567beb7a6229f196681a809)

Bug: b:333538368
Test: Ran ash unit tests.
Test: Manual
Change-Id: Ia81952d4c97db471db87cd9cc77e414d32a18242
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5507079
Commit-Queue: Prameet Shah <phshah@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295817}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5519110
Auto-Submit: Prameet Shah <phshah@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#723}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/game_dashboard/game_dashboard_controller.cc[diff]
• ash/game_dashboard/game_dashboard_controller.h[diff]

[ios] Set ShortcutsMediator's NTPDelegate

(cherry picked from commit 6a11de8719d15b8c7eb792dcf3cafc122b599b9d)

Bug: 338435952
Change-Id: Icf845b66e11350cbe3b56256f50a7068ebf118a7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512582
Auto-Submit: Chris Lu <thegreenfrog@chromium.org>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Scott Yoder <scottyoder@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1295708}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518674
Cr-Commit-Position: refs/branch-heads/6422@{#722}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/content_suggestions/content_suggestions_coordinator.mm[diff]

Fix crash in start_host when running on a fresh machine

This crash is occurring because of a recent refactoring to share
code between OAuth, Corp, and Cloud provisoning workflows.  It
looks like this problem can only occur if a host has never been
set up and our testing likely occurred on a dirty machine (i.e.
start_host was run with an existing CRD host).

The fix is trivial and highly targeted to this specific codepath.

(cherry picked from commit ec01e2072c6fd69d55a4d99bf187c3796a3911a6)

Bug: b:338602176
Change-Id: I286b2c87699e589be1b1fd3908b01397e45eac4b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515192
Reviewed-by: Lambros Lambrou <lambroslambrou@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296182}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517407
Commit-Queue: Lambros Lambrou <lambroslambrou@chromium.org>
Auto-Submit: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#721}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• remoting/host/setup/oauth_host_starter.cc[diff]

Automatic update from google3

Automatic update for 2024-05-06 UTC

Change-Id: Ic9e9e1d56d0d9236e6c51342373b1af2477bb7fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518002
Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#720}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• net/http/transport_security_state_static.pins[diff]
• net/http/transport_security_state_static_pins.json[diff]

[ios] Remove double Magic Stack Segmentation rank fetch

ContentSuggestionsMediator's consumer is used to configure MVTs, but
-fetchLatestMagicStackRanking only needs to be called in
-configureConsumer if IsIOSMagicStackCollectionViewEnabled is NO since
-setMagicStackConsumer: already does so.

(cherry picked from commit 703b98f5fc7d121d0fea54ae04e709bbebabafb5)

Bug: 338456998
Change-Id: I002fb1f2c2c4b6aa74b21ae8dd3c3ed3b0ca8393
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512626
Auto-Submit: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Scott Yoder <scottyoder@google.com>
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1296299}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518000
Commit-Queue: Scott Yoder <scottyoder@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#719}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/content_suggestions/content_suggestions_mediator.mm[diff]

Roll commits from side projects in M125

Roll src/third_party/angle in M125 from 1107aa31e36a to f4447386db89
Commits rolled:
https://chromium.googlesource.com/angle/angle.git/+log/1107aa31e36a..f4447386db89

Generated by: http://go/bbid/8748670351080408289

Change-Id: Id3ae41623b42f5a72ed88b3dc082ae5060e8e8ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514065
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#718}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• DEPS[diff]
• third_party/angle[diff]

Automated Commit: LKGM 15853.23.0 for chromeos.

Uploaded by https://ci.chromium.org/b/8748731738975858561

Change-Id: I86f99391d0b453a3bee2004c83a098e4894453fc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517887
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#717}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/CHROMEOS_LKGM[diff]

Fix incorrect animation on the Geolocaion activity indicator

(cherry picked from commit 9b7b5a32d847f45aaee97a0bf3a741c7e6afd2f7)

Bug: 338004464
Change-Id: I8404af5b4c013de34264df0144bb8e76fd548106
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5499302
Reviewed-by: Ravjit Uppal <ravjit@chromium.org>
Commit-Queue: Elias Klim <elklm@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294315}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514924
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#716}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/ui/content_settings/content_setting_image_model.cc[diff]

[iOS] Stop updating consumer during download while in background

When Chrome is in background, UI update may lead to watchdog kill.
Suspend UI update when Chrome is in background.

(cherry picked from commit f6de0b26fb0abda4ce268a017f040dd8bcde740e)

Bug: 338192475
Change-Id: I5597cf8509a56c95a27b965962e1f0298805707c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5505635
Commit-Queue: Olivier Robin <olivierrobin@chromium.org>
Auto-Submit: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295086}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513460
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#715}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/download/download_manager_coordinator.mm[diff]
• ios/chrome/browser/ui/download/download_manager_mediator.h[diff]
• ios/chrome/browser/ui/download/download_manager_mediator.mm[diff]
• ios/chrome/browser/ui/download/download_manager_mediator_unittest.mm[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714965549-0700f11cb4654c6eeed74bb05847f39a271da671-293694deb402782d5bdb6adb4c617c9f47eb0a74.profdata to chrome-win64-6422-1714992741-dcf5220c329f2230a03d2f8faf7dfd9d03800f77-7715f73c18a154637489bc1192fbe6e1193a1487.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I473dd66d4043cf90c8d0f290944c41eb5957c954
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518596
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#714}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714965549-ab41cdda3eaec37835f555d4ae1d52f0058a185b-293694deb402782d5bdb6adb4c617c9f47eb0a74.profdata to chrome-win32-6422-1714992741-0e6cf342293c1fdd378d1de192b0b96126b96da4-7715f73c18a154637489bc1192fbe6e1193a1487.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I79a71fdbd1fe6f97dbbfd8ace1ab513f5f07c83e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516791
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#713}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714965549-d574be732b69de87594b8fafc4c9a675f710bfc1-293694deb402782d5bdb6adb4c617c9f47eb0a74.profdata to chrome-linux-6422-1714992741-798475d23882d594d16f8ce4c9f9c95deb1b960e-7715f73c18a154637489bc1192fbe6e1193a1487.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ia933e209eb7e3c9e8e125fbb0834b9550c066752
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516794
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#712}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Updating XTBs based on .GRDs from branch 6422

Change-Id: Id8c919b7354e99ac776789a7b04bb15643230750
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517551
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Ben Mason <benmason@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#711}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/strings/ash_strings_ca.xtb[diff]
• chrome/android/features/keyboard_accessory/internal/java/strings/translations/android_keyboard_accessory_strings_hy.xtb[diff]
• chrome/app/resources/generated_resources_hy.xtb[diff]
• chrome/app/resources/generated_resources_it.xtb[diff]
• chrome/browser/touch_to_fill/password_manager/android/internal/java/strings/translations/android_touch_to_fill_strings_hy.xtb[diff]
• chrome/browser/ui/android/strings/translations/android_chrome_strings_hy.xtb[diff]
• components/policy/resources/policy_templates_it.xtb[diff]
• ios/chrome/app/strings/resources/ios_google_chrome_strings_es-419.xtb[diff]

[125 merge] Make WatermarkView invisible to accessibility events

Tests are non-trivial to add to meaningfully fix this bug
so they will be added in a later CL. The feature flag is
still disabled by default so that should be an issues.

(cherry picked from commit fd5f50b0027966147ae09c30fceccde3f08ba5ce)

Bug: 336776180, 338247031
Change-Id: I04dcb089aefbb62bfd7f3f25be1336d1d0cf730b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5488258
Reviewed-by: Nasser Al-shawwa <alshawwa@chromium.org>
Auto-Submit: Dominique Fauteux-Chapleau <domfc@chromium.org>
Commit-Queue: Dominique Fauteux-Chapleau <domfc@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294509}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515726
Commit-Queue: Nasser Al-shawwa <alshawwa@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#710}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/enterprise/watermark/watermark_view.cc[diff]
• chrome/browser/enterprise/watermark/watermark_view.h[diff]

[125] Remove ScopedBatchOperation when removing excess NTPs

This lock was added recently in
https://chromium-review.googlesource.com/c/chromium/src/+/5440494 as I
moticed it was missing.
But this triggers a bug where snapshots can get incorrectly attributed
to tabs.
Until this is fixed (tracked by crbug.com/338346284), remove the lock.

(cherry picked from commit 21947ead802f537bec5bbd157d01ae512b842086)

Fixed: 337234759
Change-Id: Ia23c4295638fc5b45e4fc1b462ebc0d9084a95d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508495
Auto-Submit: Louis Romero <lpromero@google.com>
Reviewed-by: Éric Noyau <noyau@chromium.org>
Commit-Queue: Éric Noyau <noyau@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295971}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515699
Cr-Commit-Position: refs/branch-heads/6422@{#709}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/start_surface/start_surface_scene_agent.mm[diff]

Roll ChromeOS Bigcore AFDO profile from 125-6422.10-1714384890-benchmark-125.0.6422.29-r1 to 125-6422.10-1714384890-benchmark-125.0.6422.30-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-bigcore-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I007b83e50b13d7eeea742f7d679eb97af83dc0bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518143
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#708}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/bigcore.afdo.newest.txt[diff]

Roll ChromeOS Atom AFDO profile from 125-6422.10-1714388999-benchmark-125.0.6422.29-r1 to 125-6422.10-1714388999-benchmark-125.0.6422.30-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I3b85ba2e2e5b33c22793e78506393106b4b69067
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517725
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#707}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/atom.afdo.newest.txt[diff]

Roll ChromeOS Arm AFDO profile from 125-6367.66-1714391204-benchmark-125.0.6422.29-r1 to 125-6367.66-1714391204-benchmark-125.0.6422.30-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-arm-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: Ib2953f9bd648fb4df055f9ed6b0fc50f727e7e32
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518110
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#706}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/arm.afdo.newest.txt[diff]

[iOS][TabStrip] Use data source to identify selected cell in layout

This CL adds a `selectedItem: TabSwitcherItem?` field to TabStripLayout,
which can be used to identify the selected item in the data source when
trying to determine the selected IndexPath of the collection view. This
method yields better results i.e. avoids unnecessary/glitchy looking
layout invalidations when the number of cells changes in the collection
view e.g. while collapsing/expanding groups or closing tabs.

Demo:
https://drive.google.com/file/d/10ep_DsrVheLBkxqWIvQw5mrvPupd0p9c/view

(cherry picked from commit 329d25bbf9e3b846fb498be8572005f3997ec18c)

Change-Id: I51add7d945b055afa2c555a35f500fc529af37d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5458561
Reviewed-by: Ewann Pellé <ewannpv@chromium.org>
Commit-Queue: Quentin Pubert <qpubert@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1290793}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513739
Reviewed-by: Ameur Hosni <ameurhosni@google.com>
Commit-Queue: Ewann Pellé <ewannpv@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#705}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/tab_switcher/tab_strip/ui/tab_strip_layout.swift[diff]
• ios/chrome/browser/ui/tab_switcher/tab_strip/ui/tab_strip_view_controller.swift[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714943893-ced47c75ac066d22360b2cedf6e1d959001be5c1-3095b219bfe406c9dbdc61bdb48984a94150c698.profdata to chrome-win64-6422-1714965549-0700f11cb4654c6eeed74bb05847f39a271da671-293694deb402782d5bdb6adb4c617c9f47eb0a74.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I4567a139f8814aa97050c667d52c39ba34a047fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517543
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#704}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714943893-702a5232a52998e3fa7da66f18e6ad198dbc88f4-3095b219bfe406c9dbdc61bdb48984a94150c698.profdata to chrome-win32-6422-1714965549-ab41cdda3eaec37835f555d4ae1d52f0058a185b-293694deb402782d5bdb6adb4c617c9f47eb0a74.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic83ba4e01c126cc62801a5422775a217f30817c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518031
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#703}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

[M125] Don't remove accounts in OnRefreshTokensLoaded if SeedAccountsRevamp is on

In some crash reports from https://crbug.com/332900316 it looks like
before crashes some accounts were removed from AccountTrackerService
by OnRefreshTokensLoaded. This code path shouldn't be invoked if
SeedAccountsRevamp is enabled, as SigninManager is supposed to be
the only driver for account seeding in that case.

(cherry picked from commit c4d872737c7509bea3eab8d96709f853a8c04978)

Bug: 337269902
Change-Id: I4a9f82d99bfd046e1c6fd12bef960e864cb6b8e3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5490669
Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Boris Sazonov <bsazonov@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293649}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517290
Commit-Queue: Menghan Yang <myuu@google.com>
Auto-Submit: Boris Sazonov <bsazonov@chromium.org>
Reviewed-by: Menghan Yang <myuu@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#702}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/signin/internal/identity_manager/primary_account_manager.cc[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714943893-bf6d7d8307658ff8305473423a0b287d10fdd10c-3095b219bfe406c9dbdc61bdb48984a94150c698.profdata to chrome-mac-6422-1714965549-67f55072099cc4fcfd5620614bbcffa72f00dbee-293694deb402782d5bdb6adb4c617c9f47eb0a74.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ibc29907441403b5a19306e7b24fd6e181a2275cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5518030
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#701}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Amd64 AFDO from 125.0.6422.29_rc-r1-merged to 125.0.6422.30_rc-r1-merged

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file go/crostc-bug.

Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.

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

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: If109dc826911f058e7469926770ac782c7bd2636
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517796
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#700}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/profiles/newest.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714943893-22492f6470d33a6054adec582edf93cc23a95bc4-3095b219bfe406c9dbdc61bdb48984a94150c698.profdata to chrome-linux-6422-1714965549-d574be732b69de87594b8fafc4c9a675f710bfc1-293694deb402782d5bdb6adb4c617c9f47eb0a74.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ifccd8e95a5c74d38396b4150cbcf51b3d09f9d0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517099
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#699}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714928602-da03a74de0ac8b38054c7b0f8f07928cbd488949-d0d4ef6f7dd0506d126ccf4a5b26cc103a665126.profdata to chrome-win64-6422-1714943893-ced47c75ac066d22360b2cedf6e1d959001be5c1-3095b219bfe406c9dbdc61bdb48984a94150c698.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I7098bbfb18f2ac5bf4f563a987c86f672129d5a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517434
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#698}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714928602-a797f68f00b8deb166f3c86ec79ab670b132f9f5-d0d4ef6f7dd0506d126ccf4a5b26cc103a665126.profdata to chrome-win32-6422-1714943893-702a5232a52998e3fa7da66f18e6ad198dbc88f4-3095b219bfe406c9dbdc61bdb48984a94150c698.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I9b734570b570bb99b7d3ee8d9a51a9fd82f3134d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517535
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#697}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714928602-946f824bcc76bd54836bce2ebe72b5085091fd69-d0d4ef6f7dd0506d126ccf4a5b26cc103a665126.profdata to chrome-mac-6422-1714943893-bf6d7d8307658ff8305473423a0b287d10fdd10c-3095b219bfe406c9dbdc61bdb48984a94150c698.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I087fd1ff0f065dc6188fb34515a134194a5c7c39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517614
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#696}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714928602-ba161b8e1fee4658cc46907af782dc273674bc3d-d0d4ef6f7dd0506d126ccf4a5b26cc103a665126.profdata to chrome-linux-6422-1714943893-22492f6470d33a6054adec582edf93cc23a95bc4-3095b219bfe406c9dbdc61bdb48984a94150c698.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I3e0f65c24fbcf6b3dfae27c3f7b756dcb24502ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517791
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#695}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

[lacros skew tests] Refresh skew tests for M126

This CL updates the ash version ['126.0.6461.0'] for Lacros version skew testing.
This cl only affect linux-lacros config builders like
linux-lacros-tester-rel, linux-lacros-rel.
This cl will certainly NOT affect Lacros on-device builders
(lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab,
etc) or any other platforms.

If this CL caused regressions, please revert and stop the autoroller
at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller
Also please file a bug to OS>LaCrOS>Partner, and CC kuanhuang@chromium.org.

R=rubber-stamper@appspot.gserviceaccount.com

Bug: None
Change-Id: I2174dd97254c1226966f05a96f7bb637feb2e260
Requires-Testing: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517809
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#694}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• infra/config/generated/testing/variants.pyl[diff]
• infra/config/targets/lacros-version-skew-variants.json[diff]
• testing/buildbot/chromium.chromiumos.json[diff]
• testing/buildbot/chromium.coverage.json[diff]
• testing/buildbot/chromium.fyi.json[diff]
• testing/buildbot/chromium.memory.json[diff]
• testing/buildbot/variants.pyl[diff]

Incrementing VERSION to 125.0.6422.31

Change-Id: If15df61d2828c2f4139690c30692ba1c69ea3a51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517362
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#693}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/VERSION[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714910025-6b8d0516f524f84621f021f94906f71619c13fa1-3de01ea470eb4bf1dc9ea0c824b4babe8c3ead22.profdata to chrome-win64-6422-1714928602-da03a74de0ac8b38054c7b0f8f07928cbd488949-d0d4ef6f7dd0506d126ccf4a5b26cc103a665126.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I73854e999d78d071a61c2e036eeedbe56374e91b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516712
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#692}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714910025-50db8fdf5f6856c8c8fb2d87ac668eab6125fd70-3de01ea470eb4bf1dc9ea0c824b4babe8c3ead22.profdata to chrome-win32-6422-1714928602-a797f68f00b8deb166f3c86ec79ab670b132f9f5-d0d4ef6f7dd0506d126ccf4a5b26cc103a665126.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I18190235ec1e2a1f9edf75498a4161c7a3fce7e8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517413
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#691}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714835364-a84b853a9b6e7317ea5208701452bd82852a5330-3840b05c9b181e50df09e562a6db94b93059c834.profdata to chrome-mac-6422-1714928602-946f824bcc76bd54836bce2ebe72b5085091fd69-d0d4ef6f7dd0506d126ccf4a5b26cc103a665126.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I17e2b2fdc03033820c72771525b9efd6c3181d03
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517414
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#690}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714910025-a50d0e36dfa2ded3682560e4b9a836d9ddbab12e-3de01ea470eb4bf1dc9ea0c824b4babe8c3ead22.profdata to chrome-linux-6422-1714928602-ba161b8e1fee4658cc46907af782dc273674bc3d-d0d4ef6f7dd0506d126ccf4a5b26cc103a665126.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I52b5635de7a985b25a3aaafb9d4bd4505a775a9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517222
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#689}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Automatic update from google3

Automatic update for 2024-05-05 UTC

Change-Id: I988b42561b4d6fcbce9bfadbc03a5e06cbddde4a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517430
Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#688}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• net/http/transport_security_state_static.pins[diff]
• net/http/transport_security_state_static_pins.json[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714878528-81bdf2901ae86b1970e48a751013348cf6b21c62-99cfaadc08f756db28b5da92d9e60c881bc33e23.profdata to chrome-win64-6422-1714910025-6b8d0516f524f84621f021f94906f71619c13fa1-3de01ea470eb4bf1dc9ea0c824b4babe8c3ead22.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I8dff70f2ef655346243c16153d63be16cbe7da11
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516985
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#687}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714878528-b75dee1c70aed2d09fb13f0e69edbcabe5bae473-99cfaadc08f756db28b5da92d9e60c881bc33e23.profdata to chrome-win32-6422-1714910025-50db8fdf5f6856c8c8fb2d87ac668eab6125fd70-3de01ea470eb4bf1dc9ea0c824b4babe8c3ead22.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I823224adf311c1c4f3bc631c9a5918edd0009599
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517391
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#686}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Updating XTBs based on .GRDs from branch 6422

Change-Id: I78e753095c98aa87c61d58583b9e3bd3f6c8a420
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515608
Auto-Submit: Ben Mason <benmason@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#685}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/strings/components_strings_zh-TW.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_zh-TW.xtb[diff]

Automated Commit: LKGM 15853.22.0 for chromeos.

Uploaded by https://ci.chromium.org/b/8748822159413474785

Change-Id: Ie04b49f5092b613cd1d6f3849f0cffef76be282b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516674
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#684}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/CHROMEOS_LKGM[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714878528-13b5c3d6b8c68f6f289f0d137ceb49b2a4e89f37-99cfaadc08f756db28b5da92d9e60c881bc33e23.profdata to chrome-linux-6422-1714910025-a50d0e36dfa2ded3682560e4b9a836d9ddbab12e-3de01ea470eb4bf1dc9ea0c824b4babe8c3ead22.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I64414ed9a27dae49f8d49a3745ce5779c7732f09
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516672
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#683}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Roll ChromeOS Bigcore AFDO profile from 125-6422.10-1714384890-benchmark-125.0.6422.28-r1 to 125-6422.10-1714384890-benchmark-125.0.6422.29-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-bigcore-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: Ife53f388c79433b091cd87ab7c44998f37453609
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517125
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#682}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/bigcore.afdo.newest.txt[diff]

Roll ChromeOS Arm AFDO profile from 125-6367.66-1714391204-benchmark-125.0.6422.27-r1 to 125-6367.66-1714391204-benchmark-125.0.6422.29-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-arm-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I9ff1daaa913d528e43f0f2b7172a82958cd9ac8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516983
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#681}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/arm.afdo.newest.txt[diff]

Roll ChromeOS Arm Experimental AFDO profile from 125-6422.10-1714388999-benchmark-125.0.6422.26-r1 to 125-6422.10-1714388999-benchmark-125.0.6422.29-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-arm-exp-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I1be625c7de85462bec76846d9f08ef82aa8e8d13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517124
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#680}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/arm-exp.afdo.newest.txt[diff]

Roll ChromeOS Atom AFDO profile from 125-6422.10-1714388999-benchmark-125.0.6422.28-r1 to 125-6422.10-1714388999-benchmark-125.0.6422.29-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I28ca8f73d17abe76819a46c5f19d0804a0ad0ea3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516371
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#679}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/atom.afdo.newest.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714858825-a67fd784d72a1057e75a318e9feca9601360a4c6-b31b3e9035d665aecc574c50a761c7a9a486cd54.profdata to chrome-win64-6422-1714878528-81bdf2901ae86b1970e48a751013348cf6b21c62-99cfaadc08f756db28b5da92d9e60c881bc33e23.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I9557c80a1e2aa56f7383a614896d470ac189892e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516980
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#678}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714858825-731bdd0d7055c45b46e02b4c3ecf5da8ddf33bd7-b31b3e9035d665aecc574c50a761c7a9a486cd54.profdata to chrome-win32-6422-1714878528-b75dee1c70aed2d09fb13f0e69edbcabe5bae473-99cfaadc08f756db28b5da92d9e60c881bc33e23.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I8fdd02467831bdbd704bb4219df926783ed6e2b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517330
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#677}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714858825-751359da6c6585038d6f308d4f0eb5557ceb99e3-b31b3e9035d665aecc574c50a761c7a9a486cd54.profdata to chrome-linux-6422-1714878528-13b5c3d6b8c68f6f289f0d137ceb49b2a4e89f37-99cfaadc08f756db28b5da92d9e60c881bc33e23.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ie5ce1ca0fac7c1fde3150e20af7f1283954b6b2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514705
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#676}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Roll Amd64 AFDO from 125.0.6422.28_rc-r1-merged to 125.0.6422.29_rc-r1-merged

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file go/crostc-bug.

Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.

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

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: Ic18cc221b4c2c99209d912ed0bf7a02d37122a65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516704
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#675}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/profiles/newest.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714835364-009ce3da5f5ee8eb208d32e56050f2c8b6d9e9da-3840b05c9b181e50df09e562a6db94b93059c834.profdata to chrome-win32-6422-1714858825-731bdd0d7055c45b46e02b4c3ecf5da8ddf33bd7-b31b3e9035d665aecc574c50a761c7a9a486cd54.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Id8daa69756fc1d2caebf227969edb29102a79aa8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516783
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#674}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714835364-1efafbd10300c8806994bb89c47ab58b1a407533-3840b05c9b181e50df09e562a6db94b93059c834.profdata to chrome-win64-6422-1714858825-a67fd784d72a1057e75a318e9feca9601360a4c6-b31b3e9035d665aecc574c50a761c7a9a486cd54.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I95b6c9ea3b5f34c47b5bac61c62e535ca1106bf4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516914
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#673}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714835364-301e90010c244524f1772c2cfa00f946740478f6-3840b05c9b181e50df09e562a6db94b93059c834.profdata to chrome-linux-6422-1714858825-751359da6c6585038d6f308d4f0eb5557ceb99e3-b31b3e9035d665aecc574c50a761c7a9a486cd54.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I25b466d1fa535d3aa67897d91330fbd92cac9c8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516915
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#672}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

[lacros skew tests] Refresh skew tests for M126

This CL updates the ash version ['126.0.6459.0'] for Lacros version skew testing.
This cl only affect linux-lacros config builders like
linux-lacros-tester-rel, linux-lacros-rel.
This cl will certainly NOT affect Lacros on-device builders
(lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab,
etc) or any other platforms.

If this CL caused regressions, please revert and stop the autoroller
at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller
Also please file a bug to OS>LaCrOS>Partner, and CC kuanhuang@chromium.org.

R=rubber-stamper@appspot.gserviceaccount.com

Bug: None
Change-Id: I58762e21e891354d0314020ddec9532c80ea6fba
Requires-Testing: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515659
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#671}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• infra/config/generated/testing/variants.pyl[diff]
• infra/config/targets/lacros-version-skew-variants.json[diff]
• testing/buildbot/chromium.chromiumos.json[diff]
• testing/buildbot/chromium.coverage.json[diff]
• testing/buildbot/chromium.fyi.json[diff]
• testing/buildbot/chromium.memory.json[diff]
• testing/buildbot/variants.pyl[diff]

Incrementing VERSION to 125.0.6422.30

Change-Id: Iaeabbc269c4bb0daca737edd6f3173577fd90365
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514063
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#670}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/VERSION[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714823272-38fd909ce75fea7de11e7375eaea39569f4a44c2-2898b88525f0fc4427f3c69d2bc7eec598e27a8b.profdata to chrome-mac-6422-1714835364-a84b853a9b6e7317ea5208701452bd82852a5330-3840b05c9b181e50df09e562a6db94b93059c834.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I2561374f5a577a27b6e7623f78a705ac10305170
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516910
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#669}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714823272-1013fbfeadb1cc6c924bde1dd3a70bbd0a3f12e7-2898b88525f0fc4427f3c69d2bc7eec598e27a8b.profdata to chrome-win64-6422-1714835364-1efafbd10300c8806994bb89c47ab58b1a407533-3840b05c9b181e50df09e562a6db94b93059c834.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I7800aac81558e18e38a67da268a6dee97cab9202
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514571
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#668}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714823272-f28c9ce8277a96942965138766b245c3415f4fc8-2898b88525f0fc4427f3c69d2bc7eec598e27a8b.profdata to chrome-win32-6422-1714835364-009ce3da5f5ee8eb208d32e56050f2c8b6d9e9da-3840b05c9b181e50df09e562a6db94b93059c834.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic8fa96a66190af036cda2d2cafc7afc72420d673
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5517133
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#667}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714823272-7a7d9d3d3375c0ea6eed99d5bce3f61824fe47fe-2898b88525f0fc4427f3c69d2bc7eec598e27a8b.profdata to chrome-linux-6422-1714835364-301e90010c244524f1772c2cfa00f946740478f6-3840b05c9b181e50df09e562a6db94b93059c834.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I8ebac87db070730f8bd73ae53c9f1abcabcd528d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516756
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#666}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714792396-61e08b8784b5cb38af144228dd5f8d594e675664-4338dbfc05573d0e13fa6441697be19da24c70f3.profdata to chrome-win32-6422-1714823272-f28c9ce8277a96942965138766b245c3415f4fc8-2898b88525f0fc4427f3c69d2bc7eec598e27a8b.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I862c7cb886075ad34d30f76ac169e53a8362645a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516904
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#665}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714792396-1a03c69c0142832b1d15081d7ddd2038f662e02b-4338dbfc05573d0e13fa6441697be19da24c70f3.profdata to chrome-win64-6422-1714823272-1013fbfeadb1cc6c924bde1dd3a70bbd0a3f12e7-2898b88525f0fc4427f3c69d2bc7eec598e27a8b.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ia52dbe1a6b7ebf7bf4a40ccc629e25a7a0119673
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516903
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#664}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714758650-a5dfd519786216d2a2df4a1f71e4e479808539a9-c3c0b88f050b6953860c166b3d734fe866231a99.profdata to chrome-mac-6422-1714823272-38fd909ce75fea7de11e7375eaea39569f4a44c2-2898b88525f0fc4427f3c69d2bc7eec598e27a8b.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I6559cc33cbfcbbbdb072ba50f96222dd9de49455
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516889
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#663}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714792396-54edb9c4b9b52ea2ae7b67dd4a7abacd0b431bc2-4338dbfc05573d0e13fa6441697be19da24c70f3.profdata to chrome-linux-6422-1714823272-7a7d9d3d3375c0ea6eed99d5bce3f61824fe47fe-2898b88525f0fc4427f3c69d2bc7eec598e27a8b.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I41856de7824c4ca1349521ff7b67678a0c06b8ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516891
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#662}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Updating XTBs based on .GRDs from branch 6422

Change-Id: I2cdd1e18f7473c909fc6c1fcced9feff1f62c2f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512574
Auto-Submit: Ben Mason <benmason@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#661}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/app/resources/generated_resources_en-GB.xtb[diff]
• chrome/app/resources/generated_resources_pt-BR.xtb[diff]
• chrome/browser/ui/android/strings/translations/android_chrome_strings_eu.xtb[diff]
• chromeos/strings/chromeos_strings_de.xtb[diff]
• chromeos/strings/chromeos_strings_eu.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_de.xtb[diff]
• ui/chromeos/translations/ui_chromeos_strings_de.xtb[diff]

Automated Commit: LKGM 15853.21.0 for chromeos.

Uploaded by https://ci.chromium.org/b/8748912613471135057

Change-Id: I74c85c2d0ddcf6ba1093d913e407b98d03155efc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513166
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#660}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/CHROMEOS_LKGM[diff]

Roll ChromeOS Bigcore AFDO profile from 125-6422.10-1714384890-benchmark-125.0.6422.27-r1 to 125-6422.10-1714384890-benchmark-125.0.6422.28-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-bigcore-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I65164e84bfe1f5d59162c239683df3c2a24af767
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516732
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#659}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/bigcore.afdo.newest.txt[diff]

Roll ChromeOS Atom AFDO profile from 125-6422.10-1714388999-benchmark-125.0.6422.27-r1 to 125-6422.10-1714388999-benchmark-125.0.6422.28-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I2a22e5e89fd2a30c16c4646f234ef8b93391e179
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516881
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#658}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/atom.afdo.newest.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714778169-c0d2846d8726cb62cc7116742b80b4eb8d7cf881-e8004ab4f86666de340344baca38325d4cc32cb7.profdata to chrome-win32-6422-1714792396-61e08b8784b5cb38af144228dd5f8d594e675664-4338dbfc05573d0e13fa6441697be19da24c70f3.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I9e80b59a16c7bc5f2ad06c4c03728a9480373979
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516727
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#657}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714778169-24abb32370f27e3a8d856b094401bcea104c4daf-e8004ab4f86666de340344baca38325d4cc32cb7.profdata to chrome-win64-6422-1714792396-1a03c69c0142832b1d15081d7ddd2038f662e02b-4338dbfc05573d0e13fa6441697be19da24c70f3.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I4602b05be765b4e3a28b4e5d073262ae1dc3f6b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516668
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#656}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714778169-2a56bcaf39548fb2f474f5e85f990d7faef5a447-e8004ab4f86666de340344baca38325d4cc32cb7.profdata to chrome-linux-6422-1714792396-54edb9c4b9b52ea2ae7b67dd4a7abacd0b431bc2-4338dbfc05573d0e13fa6441697be19da24c70f3.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I1b148ea584ff09a93d28ce6e284251b96dd42e75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516747
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#655}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Roll Amd64 AFDO from 125.0.6422.27_rc-r1-merged to 125.0.6422.28_rc-r1-merged

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file go/crostc-bug.

Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.

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

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I59b622bb9e09546534d843d755952739d0b37e15
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516311
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#654}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/profiles/newest.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714758650-b6727e01c41719f708f43531f22912aa941d0d18-c3c0b88f050b6953860c166b3d734fe866231a99.profdata to chrome-win32-6422-1714778169-c0d2846d8726cb62cc7116742b80b4eb8d7cf881-e8004ab4f86666de340344baca38325d4cc32cb7.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I74eda076382befcad7f0cffb7622083776356461
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516528
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#653}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714758650-19318f774bcfc97f8130c4575d7c12a151951126-c3c0b88f050b6953860c166b3d734fe866231a99.profdata to chrome-win64-6422-1714778169-24abb32370f27e3a8d856b094401bcea104c4daf-e8004ab4f86666de340344baca38325d4cc32cb7.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I114aed877764d7d66f623bd0ce832cc11af2a17c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516564
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#652}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714758650-1acbce1578f83cf9a57de32d64711eae574e00d4-c3c0b88f050b6953860c166b3d734fe866231a99.profdata to chrome-linux-6422-1714778169-2a56bcaf39548fb2f474f5e85f990d7faef5a447-e8004ab4f86666de340344baca38325d4cc32cb7.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Icc7df6fa1d38d9799f023e7b49e6a3126c631ecd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5516450
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#651}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

[lacros skew tests] Refresh skew tests for M126

This CL updates the ash version ['126.0.6457.0'] for Lacros version skew testing.
This cl only affect linux-lacros config builders like
linux-lacros-tester-rel, linux-lacros-rel.
This cl will certainly NOT affect Lacros on-device builders
(lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab,
etc) or any other platforms.

If this CL caused regressions, please revert and stop the autoroller
at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller
Also please file a bug to OS>LaCrOS>Partner, and CC kuanhuang@chromium.org.

R=rubber-stamper@appspot.gserviceaccount.com

Bug: None
Change-Id: I21aa38f3e354492af0cbbac50a7c17ed7d06496b
Requires-Testing: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512331
Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#650}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• infra/config/generated/testing/variants.pyl[diff]
• infra/config/targets/lacros-version-skew-variants.json[diff]
• testing/buildbot/chromium.chromiumos.json[diff]
• testing/buildbot/chromium.coverage.json[diff]
• testing/buildbot/chromium.fyi.json[diff]
• testing/buildbot/chromium.memory.json[diff]
• testing/buildbot/variants.pyl[diff]

Incrementing VERSION to 125.0.6422.29

Change-Id: I2f1af68c47091a7088d6a5a16c981239ef53ca88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512031
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#649}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/VERSION[diff]

[M125] Collect off-store extension metrics organized by developer mode

This CL adds the recording of the number of off-store extensions
installed when the extension developer mode is enabled. These
metrics add to a previous CL where the number was recorded only
when extension developer mode is disabled.
Adding these new histograms will be used to determine the
fraction of off-store extensions that are present with developer
mode enabled vs disabled.

The CL also expands the histograms to include all manifest locations.

OBSOLETE_HISTOGRAM[Extensions.NonWebstoreLocationWithDeveloperModeOff.Disabled]=Replaced by Extensions.NonWebstoreLocationWithDeveloperModeOff.Disabled2
OBSOLETE_HISTOGRAM[Extensions.NonWebstoreLocationWithDeveloperModeOff.Enabled]=Replaced by Extensions.NonWebstoreLocationWithDeveloperModeOff.Enabled2

(cherry picked from commit 19d66855cbfaf81b5280354e3404cf0f775ccf7e)

Bug: 323947671
Change-Id: Ieff368ecbc8310247e3d256586926803c1a01cf6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5444964
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Reviewed-by: Anunoy Ghosh <anunoy@chromium.org>
Reviewed-by: Justin Lulejian <jlulejian@chromium.org>
Commit-Queue: Richard Chen <richche@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1291415}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5506677
Reviewed-by: David Bertoni <dbertoni@chromium.org>
Auto-Submit: Richard Chen <richche@google.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#648}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/extensions/installed_loader.cc[diff]
• chrome/browser/extensions/unpacked_installer.cc[diff]
• chrome/browser/extensions/unpacked_installer.h[diff]
• chrome/browser/extensions/unpacked_installer_unittest.cc[diff]
• tools/metrics/histograms/metadata/extensions/histograms.xml[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714733804-a279bf11c09fcb731012face89db02d718bf9822-68dd0c6c393e7919ed1b6afb721064ac02336a7d.profdata to chrome-win32-6422-1714758650-b6727e01c41719f708f43531f22912aa941d0d18-c3c0b88f050b6953860c166b3d734fe866231a99.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Iaa7d721e693cfb7cc3058c9e6d7fa261a0ac769c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515964
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#647}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714733804-2cd40d313323a239c07646f3b656e44216065423-68dd0c6c393e7919ed1b6afb721064ac02336a7d.profdata to chrome-win64-6422-1714758650-19318f774bcfc97f8130c4575d7c12a151951126-c3c0b88f050b6953860c166b3d734fe866231a99.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I0cb0c9b1a407cf23ea54873c76041a22f5efe46a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515850
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#646}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714733804-ceb1d87d948cd3b83ec8f1adfea214578e38a9ec-68dd0c6c393e7919ed1b6afb721064ac02336a7d.profdata to chrome-mac-6422-1714758650-a5dfd519786216d2a2df4a1f71e4e479808539a9-c3c0b88f050b6953860c166b3d734fe866231a99.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ifefd57dbdcb8f34813d03d62109b5cae33e05c56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515851
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#645}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714733804-64c2b4af8de6f7d2d886a07843ccb77d653e70c1-68dd0c6c393e7919ed1b6afb721064ac02336a7d.profdata to chrome-linux-6422-1714758650-1acbce1578f83cf9a57de32d64711eae574e00d4-c3c0b88f050b6953860c166b3d734fe866231a99.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I3122c961acad343394665e77e404e60e6657619b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515854
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#644}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

traffic-counters: Remove Promise<boolean> return in showDataUsage_()

BUG=b:338430251
TEST=manually verified the following on linux-chrome:
1. Before fix: Data Usage section is visible without "TrafficCountersEnabled" flag for WiFi: https://screenshot.googleplex.com/6uncDiNfRrur8UZ

2. After fix: Data Usage section is not visible for WiFi when
   "TrafficCountersEnabled" is turned off: https://screenshot.googleplex.com/AESNHsW8M5awRx7

3. After fix: Data Usage section is not visible for WiFi when
   "TrafficCountersEnabeld" is turned on: https://screenshot.googleplex.com/6FvT88MrNafv523

4. After fix: Data Usage section is visible for Cellular when
   "TrafficCountersEnabled" is turned on: https://screenshot.googleplex.com/7aD7FAuW2h5VvLd

5. After fix: Data usage section is not visible for Cellular when "TrafficCountersEnabled" is turned off: https://screenshot.googleplex.com/9dJLXVLxMq3weuV

(cherry picked from commit 260eef722b8f75809b220de35bccfe90f1d8b6db)

Change-Id: I4fb88725e85e787fc9f6a963d5f1f827a2466d62
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512624
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Kartik Hegde <khegde@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295723}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515320
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#643}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/resources/ash/settings/internet_page/internet_detail_subpage.ts[diff]

Fix swiping down on otp input after authentication selection.

When dismissing the otp input sheet via swipe after an authentication
selection was presented

* Before, a DCHECK was triggered in the
  CardUnmaskAuthenticationSelectionMediator due to
  presentationController's delegate still being set to the
  CardUnmaskAuthenticationSelectionViewController.
* Now, the CardUnmaskAuthenticationCoordinator is the
  presentationController's delegate, and requests the flow to be stopped
  via a BrowserCoordinator command instead. The Mediator's destructor
  will respond (similar to the desktop and Android
  implementations).

Alternatives:

* Every view under card unmask sets and unsets itself as the
  presentationController. Each ViewController would need to delegate
  this to the respective Coordinator.
* The CardUnmaskAuthenticationCoordinator listens for
  UINavigationControllerDelegate events to set the currently shown
  ViewController as the presentationController delegate if the
  ViewController implements UIAdaptivePresentationControllerDelegate.

(cherry picked from commit da40cdf585ca07378a9648cf7445cb28f2c68797)

Bug: 335879467
Change-Id: Id47eb660ffc7fd00bb0b29f5ae53777687a8652d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5497625
Commit-Queue: Slobodan Pejic <slobodan@chromium.org>
Reviewed-by: Siyu An <siyua@chromium.org>
Reviewed-by: Tommy Martino <tmartino@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294873}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5503797
Auto-Submit: Slobodan Pejic <slobodan@chromium.org>
Commit-Queue: Tommy Martino <tmartino@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#642}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/autofill/authentication/card_unmask_authentication_coordinator.mm[diff]
• ios/chrome/browser/ui/autofill/authentication/card_unmask_authentication_egtest.mm[diff]
• ios/chrome/browser/ui/autofill/authentication/card_unmask_authentication_selection_coordinator.mm[diff]
• ios/chrome/browser/ui/autofill/authentication/card_unmask_authentication_selection_mediator.mm[diff]
• ios/chrome/browser/ui/autofill/authentication/card_unmask_authentication_selection_view_controller.h[diff]
• ios/chrome/browser/ui/autofill/authentication/card_unmask_authentication_selection_view_controller.mm[diff]
• ios/chrome/browser/ui/autofill/autofill_app_interface.h[diff]
• ios/chrome/browser/ui/autofill/autofill_app_interface.mm[diff]

Roll commits from side projects in M125

Roll src/clank in M125 from 99b818feb883 to 0f650cfddbb7
Commits rolled:
https://chrome-internal.googlesource.com/clank/internal/apps.git/+log/99b818feb883..0f650cfddbb7

Generated by: http://go/bbid/8748934594211748945

Change-Id: Ifb3dad72afcf093e0c6d733dafcedfd0dc9f60bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515602
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#641}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• DEPS[diff]
• clank[diff]

Android: Make system image .apk files use only base split when fuse_apk=false

Chanes system_image_apks.py in two ways:
1. If the output is an ".apk", use only the base.apk split (this is what
   we want for webview)
2. If the output is an ".apks", then stop renaming files to not look
   like an ".apks", since doing so messes up our signing infra.

(cherry picked from commit 0957803291249644b6eed377fd9204973e05d07d)

Bug: 337005700
Change-Id: If6498cf4bd59e984ec77edfd7cd15b8a65e40835
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5490701
Auto-Submit: Andrew Grieve <agrieve@chromium.org>
Commit-Queue: Richard (Torne) Coles <torne@chromium.org>
Reviewed-by: Richard (Torne) Coles <torne@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1292661}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513646
Reviewed-by: Erhu Akpobaro <eakpobaro@google.com>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#640}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• build/android/gyp/system_image_apks.py[diff]

[Merge to M125] Shared Storage: Fix the origin used for prefs check in createWorklet

(cherry picked from commit 632fc01d593d00f5a61eef0543e24ef3e7558464)

Bug: 338071838
Change-Id: I359ef0a1457d1a7f5d3592ab3f2605f57feb030f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5502255
Reviewed-by: Yao Xiao <yaoxia@chromium.org>
Commit-Queue: Cammie Smith Barnes <cammie@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294634}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512882
Cr-Commit-Position: refs/branch-heads/6422@{#639}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/storage/shared_storage_browsertest.cc[diff]
• chrome/test/data/shared_storage/module_with_custom_header.js[Added - diff]
• chrome/test/data/shared_storage/module_with_custom_header.js.mock-http-headers[Added - diff]
• content/browser/shared_storage/shared_storage_document_service_impl.cc[diff]
• content/browser/shared_storage/shared_storage_document_service_impl.h[diff]
• content/public/test/shared_storage_test_utils.cc[diff]
• content/public/test/shared_storage_test_utils.h[diff]

Automatic update from google3

Automatic update for 2024-05-03 UTC

Change-Id: I23ae61e5eb66ab374668681608c23241800f2533
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515133
Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#638}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• net/http/transport_security_state_static.pins[diff]
• net/http/transport_security_state_static_pins.json[diff]

[omnibox] Use ASCII character set for reporting Gemini prompt in header

Encodes the prompt string using the US-ASCII characters allowed within
a URI as defined by the encodeURIComponent() JS method.

(cherry picked from commit 23ee24c62d0288458cce19c3b0e9dda3081c924b)

Bug: 326586342
Change-Id: Ibc6835404f0c128e0656a086a5f76a6e0b47b338
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512043
Reviewed-by: Rachel Blum <groby@chromium.org>
Commit-Queue: Moe Ahmadi <mahmadi@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295822}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513825
Reviewed-by: Angela Yoeurng <yoangela@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#637}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/omnibox/browser/autocomplete_controller.cc[diff]
• components/omnibox/browser/autocomplete_controller_unittest.cc[diff]

[M125] tab search: replace empty URLs with about:blank

Previous CL https://crrev.com/c/5417973 replaces empty URL with
about:blank in tab_search_page.ts, this CL applies the same fix to other
places that construct an URL object.

(cherry picked from commit c3aabaaad96801b3fc864c97991d7b6ae1c82930)

Bug: 336838292
Change-Id: Id9257559d8481a0946c1017e0240979f75630be3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5495771
Commit-Queue: Keren Zhu <kerenzhu@chromium.org>
Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293510}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5505955
Reviewed-by: Yuheng Huang <yuhengh@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#636}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/resources/tab_search/tab_data.ts[diff]
• chrome/browser/resources/tab_search/tab_organization_group.ts[diff]
• chrome/browser/resources/tab_search/tab_search_item.ts[diff]
• chrome/browser/resources/tab_search/tab_search_page.ts[diff]

[M125] Remove CHECK() from ProfileTokenQuality::AddObservation()

Temporary fix for the linked bug.

(cherry picked from commit fba9107dc7c69d0cfec7a84ffab28b9b46766dbd)

Bug: b/338269051
Change-Id: I5a227820f0bd5a551969057105eb5c2f682ae8bd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510625
Reviewed-by: Dominic Battre <battre@chromium.org>
Commit-Queue: Dominic Battre <battre@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295648}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515281
Reviewed-by: Norge Vizcay <vizcay@google.com>
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Owners-Override: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#635}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/autofill/core/browser/profile_token_quality.cc[diff]

[omnibox] Add logging for unknown AutocompleteMatchType.

Converts the NOTREACHED to DUMP_WILL_BE_NOTREACHED_NORETURN so we can
get some logging on what the erroneous type values are without crashing
in official builds.

(cherry picked from commit d96e2e77f698608e8b38bb5c65d092a445260a87)

Bug: 335406606
Change-Id: Ib04f85efbdc3907abf5f97445b8b71b4101fce3d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5488882
Reviewed-by: manuk hovanesian <manukh@chromium.org>
Commit-Queue: Justin Donnelly <jdonnelly@chromium.org>
Auto-Submit: Justin Donnelly <jdonnelly@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294612}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512964
Cr-Commit-Position: refs/branch-heads/6422@{#634}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/omnibox/browser/autocomplete_match.cc[diff]

[waffle]Update search engine descriptions

Update the descriptions provided by the search engines.

(cherry picked from commit 9460d37a04fcbe1188762d6f26c72c10b42f2011)

Skip-Translation-Screenshots-Check: True
Fixed: b:338071545, b:338344436
Change-Id: I8eee4fc53952af5528e5e76fd1f0f99da4457098
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508598
Commit-Queue: Jack Yammine <jyammine@google.com>
Reviewed-by: Nicolas Dossou-Gbété <dgn@chromium.org>
Auto-Submit: Jack Yammine <jyammine@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1295646}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513543
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#633}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/search_engine_descriptions_strings.grd[diff]
• components/strings/search_engine_descriptions_strings_af.xtb[diff]
• components/strings/search_engine_descriptions_strings_am.xtb[diff]
• components/strings/search_engine_descriptions_strings_ar.xtb[diff]
• components/strings/search_engine_descriptions_strings_as.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_az.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_bg.xtb[diff]
• components/strings/search_engine_descriptions_strings_bn.xtb[diff]
• components/strings/search_engine_descriptions_strings_bs.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_ca.xtb[diff]
• components/strings/search_engine_descriptions_strings_cs.xtb[diff]
• components/strings/search_engine_descriptions_strings_da.xtb[diff]
• components/strings/search_engine_descriptions_strings_de.xtb[diff]
• components/strings/search_engine_descriptions_strings_el.xtb[diff]
• components/strings/search_engine_descriptions_strings_es.xtb[diff]
• components/strings/search_engine_descriptions_strings_et.xtb[diff]
• components/strings/search_engine_descriptions_strings_eu.xtb[diff]
• components/strings/search_engine_descriptions_strings_fa.xtb[diff]
• components/strings/search_engine_descriptions_strings_fi.xtb[diff]
• components/strings/search_engine_descriptions_strings_fil.xtb[Added - diff]
• components/strings/search_engine_descriptions_strings_fr.xtb[diff]
• components/strings/search_engine_descriptions_strings_gl.xtb[diff]
• components/strings/search_engine_descriptions_strings_gu.xtb[diff]
• components/strings/search_engine_descriptions_strings_he.xtb[diff]
• components/strings/search_engine_descriptions_strings_hr.xtb[diff]
• components/strings/search_engine_descriptions_strings_hu.xtb[diff]
• components/strings/search_engine_descriptions_strings_hy.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_id.xtb[Added - diff]
• components/strings/search_engine_descriptions_strings_is.xtb[diff]
• components/strings/search_engine_descriptions_strings_it.xtb[diff]
• components/strings/search_engine_descriptions_strings_ja.xtb[diff]
• components/strings/search_engine_descriptions_strings_ka.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_kk.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_kn.xtb[Added - diff]
• components/strings/search_engine_descriptions_strings_ko.xtb[diff]
• components/strings/search_engine_descriptions_strings_lt.xtb[diff]
• components/strings/search_engine_descriptions_strings_lv.xtb[diff]
• components/strings/search_engine_descriptions_strings_mk.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_mn.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_mr.xtb[diff]
• components/strings/search_engine_descriptions_strings_ms.xtb[Added - diff]
• components/strings/search_engine_descriptions_strings_my.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_nb.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_nl.xtb[diff]
• components/strings/search_engine_descriptions_strings_no.xtb[diff]
• components/strings/search_engine_descriptions_strings_pl.xtb[diff]
• components/strings/search_engine_descriptions_strings_pt-PT.xtb[diff]
• components/strings/search_engine_descriptions_strings_ro.xtb[diff]
• components/strings/search_engine_descriptions_strings_ru.xtb[diff]
• components/strings/search_engine_descriptions_strings_si.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_sk.xtb[diff]
• components/strings/search_engine_descriptions_strings_sl.xtb[diff]
• components/strings/search_engine_descriptions_strings_sq.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_sr.xtb[diff]
• components/strings/search_engine_descriptions_strings_sv.xtb[diff]
• components/strings/search_engine_descriptions_strings_te.xtb[diff]
• components/strings/search_engine_descriptions_strings_th.xtb[diff]
• components/strings/search_engine_descriptions_strings_tr.xtb[diff]
• components/strings/search_engine_descriptions_strings_uk.xtb[diff]
• components/strings/search_engine_descriptions_strings_ur.xtb[Added - diff]
• components/strings/search_engine_descriptions_strings_uz.xtb[Deleted - diff]
• components/strings/search_engine_descriptions_strings_vi.xtb[diff]
• components/strings/search_engine_descriptions_strings_zh-CN.xtb[diff]
• components/strings/search_engine_descriptions_strings_zh-HK.xtb[diff]
• components/strings/search_engine_descriptions_strings_zh-TW.xtb[diff]
• components/strings/search_engine_descriptions_strings_zu.xtb[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714707121-fe8619a1f4829c8f8ba6ab2d71795414f2b579ba-8cf1008f7fb1de25c49403888c06648ef865037d.profdata to chrome-win32-6422-1714733804-a279bf11c09fcb731012face89db02d718bf9822-68dd0c6c393e7919ed1b6afb721064ac02336a7d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I4d0a8c7aac281f56072a977379bafcf37b74e636
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514742
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#632}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714707121-6677b07f58b033eecada640c818d390ac5e0c9cc-8cf1008f7fb1de25c49403888c06648ef865037d.profdata to chrome-win64-6422-1714733804-2cd40d313323a239c07646f3b656e44216065423-68dd0c6c393e7919ed1b6afb721064ac02336a7d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I32cc6c4cee6064ec62b45249a605b9167c5cd5ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515273
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#631}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714707121-10c2c8fd32d662a1e916c60ddbf1da2eb9b2e7fb-8cf1008f7fb1de25c49403888c06648ef865037d.profdata to chrome-mac-6422-1714733804-ceb1d87d948cd3b83ec8f1adfea214578e38a9ec-68dd0c6c393e7919ed1b6afb721064ac02336a7d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic3f5d20839bdf0b7651af2981544f57765caff10
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514743
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#630}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714707121-dcc01ea340c90e43a6c17f60eb08bc150fb4dfb8-8cf1008f7fb1de25c49403888c06648ef865037d.profdata to chrome-linux-6422-1714733804-64c2b4af8de6f7d2d886a07843ccb77d653e70c1-68dd0c6c393e7919ed1b6afb721064ac02336a7d.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I0daaba92cee6140c6306e06a2bb942989ae31848
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515449
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#629}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Updating XTBs based on .GRDs from branch 6422

Change-Id: I095cc21c64fd44ffea24200c3ea249c2fdd4ad87
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514834
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Ben Mason <benmason@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#628}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/strings/ash_strings_zh-CN.xtb[diff]
• chrome/app/resources/generated_resources_ar.xtb[diff]
• chrome/app/resources/generated_resources_ne.xtb[diff]
• chrome/app/resources/generated_resources_ru.xtb[diff]
• chrome/app/resources/generated_resources_zh-CN.xtb[diff]
• chrome/browser/ui/android/strings/translations/android_chrome_strings_ar.xtb[diff]
• chrome/browser/ui/android/strings/translations/android_chrome_strings_zh-CN.xtb[diff]
• chromeos/strings/chromeos_strings_zh-CN.xtb[diff]
• components/browser_ui/strings/android/translations/browser_ui_strings_ne.xtb[diff]
• components/browser_ui/strings/android/translations/browser_ui_strings_ru.xtb[diff]
• components/strings/components_strings_af.xtb[diff]
• components/strings/components_strings_am.xtb[diff]
• components/strings/components_strings_ar.xtb[diff]
• components/strings/components_strings_as.xtb[diff]
• components/strings/components_strings_az.xtb[diff]
• components/strings/components_strings_be.xtb[diff]
• components/strings/components_strings_bg.xtb[diff]
• components/strings/components_strings_bn.xtb[diff]
• components/strings/components_strings_bs.xtb[diff]
• components/strings/components_strings_ca.xtb[diff]
• components/strings/components_strings_cs.xtb[diff]
• components/strings/components_strings_cy.xtb[diff]
• components/strings/components_strings_da.xtb[diff]
• components/strings/components_strings_de.xtb[diff]
• components/strings/components_strings_el.xtb[diff]
• components/strings/components_strings_en-GB.xtb[diff]
• components/strings/components_strings_es-419.xtb[diff]
• components/strings/components_strings_es.xtb[diff]
• components/strings/components_strings_et.xtb[diff]
• components/strings/components_strings_eu.xtb[diff]
• components/strings/components_strings_fa.xtb[diff]
• components/strings/components_strings_fi.xtb[diff]
• components/strings/components_strings_fil.xtb[diff]
• components/strings/components_strings_fr-CA.xtb[diff]
• components/strings/components_strings_fr.xtb[diff]
• components/strings/components_strings_gl.xtb[diff]
• components/strings/components_strings_gu.xtb[diff]
• components/strings/components_strings_hi.xtb[diff]
• components/strings/components_strings_hr.xtb[diff]
• components/strings/components_strings_hu.xtb[diff]
• components/strings/components_strings_hy.xtb[diff]
• components/strings/components_strings_id.xtb[diff]
• components/strings/components_strings_is.xtb[diff]
• components/strings/components_strings_it.xtb[diff]
• components/strings/components_strings_iw.xtb[diff]
• components/strings/components_strings_ja.xtb[diff]
• components/strings/components_strings_ka.xtb[diff]
• components/strings/components_strings_kk.xtb[diff]
• components/strings/components_strings_km.xtb[diff]
• components/strings/components_strings_kn.xtb[diff]
• components/strings/components_strings_ko.xtb[diff]
• components/strings/components_strings_ky.xtb[diff]
• components/strings/components_strings_lo.xtb[diff]
• components/strings/components_strings_lt.xtb[diff]
• components/strings/components_strings_lv.xtb[diff]
• components/strings/components_strings_mk.xtb[diff]
• components/strings/components_strings_ml.xtb[diff]
• components/strings/components_strings_mn.xtb[diff]
• components/strings/components_strings_mr.xtb[diff]
• components/strings/components_strings_ms.xtb[diff]
• components/strings/components_strings_my.xtb[diff]
• components/strings/components_strings_ne.xtb[diff]
• components/strings/components_strings_nl.xtb[diff]
• components/strings/components_strings_no.xtb[diff]
• components/strings/components_strings_or.xtb[diff]
• components/strings/components_strings_pa.xtb[diff]
• components/strings/components_strings_pl.xtb[diff]
• components/strings/components_strings_pt-BR.xtb[diff]
• components/strings/components_strings_pt-PT.xtb[diff]
• components/strings/components_strings_ro.xtb[diff]
• components/strings/components_strings_ru.xtb[diff]
• components/strings/components_strings_si.xtb[diff]
• components/strings/components_strings_sk.xtb[diff]
• components/strings/components_strings_sl.xtb[diff]
• components/strings/components_strings_sq.xtb[diff]
• components/strings/components_strings_sr-Latn.xtb[diff]
• components/strings/components_strings_sr.xtb[diff]
• components/strings/components_strings_sv.xtb[diff]
• components/strings/components_strings_sw.xtb[diff]
• components/strings/components_strings_ta.xtb[diff]
• components/strings/components_strings_te.xtb[diff]
• components/strings/components_strings_th.xtb[diff]
• components/strings/components_strings_tr.xtb[diff]
• components/strings/components_strings_uk.xtb[diff]
• components/strings/components_strings_ur.xtb[diff]
• components/strings/components_strings_uz.xtb[diff]
• components/strings/components_strings_vi.xtb[diff]
• components/strings/components_strings_zh-CN.xtb[diff]
• components/strings/components_strings_zh-HK.xtb[diff]
• components/strings/components_strings_zh-TW.xtb[diff]
• components/strings/components_strings_zu.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_ar.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_fr.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_ru.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_zh-CN.xtb[diff]
• ios/chrome/share_extension/strings/resources/ios_share_extension_strings_ar.xtb[diff]

Automated Commit: LKGM 15853.20.0 for chromeos.

Uploaded by https://ci.chromium.org/b/8749003448316132705

Change-Id: Id8d9d5444c7d4d327cdbc9420888824bafe27474
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515270
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#627}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/CHROMEOS_LKGM[diff]

compute pressure: Rename supportedSources to knownSources

Based on specification change [1], supportedSources attribute
is renamed to knownSources.

[1]: https://github.com/w3c/compute-pressure/pull/268

(cherry picked from commit fc3b9442a95626c2ef9cb734efbbc7c6beaa717b)

Bug: 337837870
Change-Id: Ic80d0c806531ed99f8bc2c368f89e55427b0202c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5491092
Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Mike Taylor <miketaylr@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294408}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508494
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Arnaud Mandy <arnaud.mandy@intel.com>
Reviewed-by: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/branch-heads/6422@{#626}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• third_party/blink/renderer/modules/compute_pressure/pressure_observer.cc[diff]
• third_party/blink/renderer/modules/compute_pressure/pressure_observer.h[diff]
• third_party/blink/renderer/modules/compute_pressure/pressure_observer.idl[diff]
• third_party/blink/renderer/modules/compute_pressure/pressure_observer_manager.cc[diff]
• third_party/blink/web_tests/external/wpt/compute-pressure/compute_pressure_known_sources.https.any.js[Renamed from third_party/blink/web_tests/external/wpt/compute-pressure/compute_pressure_supported_sources.https.any.js - diff]
• third_party/blink/web_tests/external/wpt/interfaces/compute-pressure.idl[diff]
• third_party/blink/web_tests/virtual/stable/webexposed/global-interface-listing-dedicated-worker-expected.txt[diff]
• third_party/blink/web_tests/virtual/stable/webexposed/global-interface-listing-expected.txt[diff]
• third_party/blink/web_tests/virtual/stable/webexposed/global-interface-listing-shared-worker-expected.txt[diff]
• third_party/blink/web_tests/webexposed/global-interface-listing-dedicated-worker-expected.txt[diff]
• third_party/blink/web_tests/webexposed/global-interface-listing-expected.txt[diff]
• third_party/blink/web_tests/webexposed/global-interface-listing-shared-worker-expected.txt[diff]

Roll ChromeOS Bigcore AFDO profile from 125-6422.10-1714384890-benchmark-125.0.6422.26-r1 to 125-6422.10-1714384890-benchmark-125.0.6422.27-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-bigcore-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: Id50642d8a9d87874d72036dc48e0486bb73045c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515444
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#625}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/bigcore.afdo.newest.txt[diff]

Roll ChromeOS Arm AFDO profile from 125-6367.66-1714391204-benchmark-125.0.6422.26-r1 to 125-6367.66-1714391204-benchmark-125.0.6422.27-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-arm-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I8858d8b251654014f644fb2d31ca409ea34aa3d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514380
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#624}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/arm.afdo.newest.txt[diff]

Roll ChromeOS Atom AFDO profile from 125-6422.10-1714388999-benchmark-125.0.6422.26-r1 to 125-6422.10-1714388999-benchmark-125.0.6422.27-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: Ib24602d571f0ea0f273fed7131f6e6d1f5059d39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5515267
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#623}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/atom.afdo.newest.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714688273-19e763564cdecfb071d7f5a787b83d2e7d52a3b5-271062caae7f5e016c96fd17cfee1f065fc79625.profdata to chrome-win32-6422-1714707121-fe8619a1f4829c8f8ba6ab2d71795414f2b579ba-8cf1008f7fb1de25c49403888c06648ef865037d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I099e0722677e2145700ea628c8b1026203e77c7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514371
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#622}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714688273-80696d51234137e0215adf7c19a04229e097f847-271062caae7f5e016c96fd17cfee1f065fc79625.profdata to chrome-win64-6422-1714707121-6677b07f58b033eecada640c818d390ac5e0c9cc-8cf1008f7fb1de25c49403888c06648ef865037d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I4da10c8474fc97547e9dee899c0cbad65e6cf7f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514775
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#621}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714671275-526967c98f8c2662c272b570395bfccdac684199-2f9e1beefe10e98ee4d1e7c0bdcf8f3c57ccc24d.profdata to chrome-mac-6422-1714707121-10c2c8fd32d662a1e916c60ddbf1da2eb9b2e7fb-8cf1008f7fb1de25c49403888c06648ef865037d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I3f7f319b1ee03e0611b999a49f93f078502eef2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514728
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#620}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714688273-745328be4eccc312e3001a5499be31fc9afa8557-271062caae7f5e016c96fd17cfee1f065fc79625.profdata to chrome-linux-6422-1714707121-dcc01ea340c90e43a6c17f60eb08bc150fb4dfb8-8cf1008f7fb1de25c49403888c06648ef865037d.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic4012b6e07284c4de69ee46b1dbfd8858f178e0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514618
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#619}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Roll Amd64 AFDO from 125.0.6422.26_rc-r1-merged to 125.0.6422.27_rc-r1-merged

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file go/crostc-bug.

Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.

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

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I5001111b762f155268cf9ac41add37e755dc16eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5514774
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#618}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/profiles/newest.txt[diff]

[Merge M125] Add feature to ensure existing renderer is alive when used in RPH

When using an existing renderer, the OS process may have been killed by
the system (especially on Android). This feature makes sure the process
is started back up ASAP to decrease latency when using the renderer
process.

(cherry picked from commit cfcaadc23156c5f3df844cf417926fe83f711a74)

Bug: 332706093
Change-Id: I9c92b83ff8656e0d3803d9a97c37454df886d52d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5495030
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293864}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510298
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Auto-Submit: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#617}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• android_webview/java/src/org/chromium/android_webview/common/ProductionSupportedFlagList.java[diff]
• content/browser/renderer_host/render_process_host_impl.cc[diff]
• testing/variations/fieldtrial_testing_config.json[diff]

[Merge M125] Remove another unnecessary PostTask from input stream reader

(cherry picked from commit e665c3038b0dffb7710d9f77bfd08c3714c6172f)

Bug: 332706093
Change-Id: I5c9f38a8faa7effee93fb031e33d0f14ef5297b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5499201
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Richard (Torne) Coles <torne@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Auto-Submit: Clark DuVall <cduvall@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294674}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510982
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#616}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/embedder_support/android/util/android_stream_reader_url_loader.cc[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714671275-8a82804bb6160e80779eec5f4cd99b51efc1d4b1-2f9e1beefe10e98ee4d1e7c0bdcf8f3c57ccc24d.profdata to chrome-win64-6422-1714688273-80696d51234137e0215adf7c19a04229e097f847-271062caae7f5e016c96fd17cfee1f065fc79625.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic66835caab33e8309c96a23cdb2e4bbee0303302
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513942
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#615}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714671275-2bf602adbb3fda8f266dc4d22c42213ebcbd2eb6-2f9e1beefe10e98ee4d1e7c0bdcf8f3c57ccc24d.profdata to chrome-win32-6422-1714688273-19e763564cdecfb071d7f5a787b83d2e7d52a3b5-271062caae7f5e016c96fd17cfee1f065fc79625.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I9421abd453ac4f1dc42e02667805049237c5f00a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513601
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#614}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714671275-2695b5d33676b2c70ca893d056a6218dc5709385-2f9e1beefe10e98ee4d1e7c0bdcf8f3c57ccc24d.profdata to chrome-linux-6422-1714688273-745328be4eccc312e3001a5499be31fc9afa8557-271062caae7f5e016c96fd17cfee1f065fc79625.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I17bcae9ac0971fabe6a55f3c56e7115ec9a50c14
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513499
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#613}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

[lacros skew tests] Refresh skew tests for M126

This CL updates the ash version ['126.0.6455.0'] for Lacros version skew testing.
This cl only affect linux-lacros config builders like
linux-lacros-tester-rel, linux-lacros-rel.
This cl will certainly NOT affect Lacros on-device builders
(lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab,
etc) or any other platforms.

If this CL caused regressions, please revert and stop the autoroller
at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller
Also please file a bug to OS>LaCrOS>Partner, and CC kuanhuang@chromium.org.

R=rubber-stamper@appspot.gserviceaccount.com

Bug: None
Change-Id: Ifa624ab9f9aea2460dbd68af7283ab88d304086f
Requires-Testing: True
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513922
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#612}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• infra/config/generated/testing/variants.pyl[diff]
• infra/config/targets/lacros-version-skew-variants.json[diff]
• testing/buildbot/chromium.chromiumos.json[diff]
• testing/buildbot/chromium.coverage.json[diff]
• testing/buildbot/chromium.fyi.json[diff]
• testing/buildbot/chromium.memory.json[diff]
• testing/buildbot/variants.pyl[diff]

Incrementing VERSION to 125.0.6422.28

Change-Id: If77ff10e1ee765df788fb2aa4934bb919b21253e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513862
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#611}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/VERSION[diff]

[lacros] Update lacros QA qualified version

This CL will update lacros version in //chrome/LACROS_QA_QUALIFIED_VERSION. This
file will be used in Upreving the RootFS-Lacros in the CROS image.

If this CL caused regressions, please revert and pause the autoroller at
https://luci-scheduler.appspot.com/jobs/chrome/lacros-qa-qualified-tracking-roller
Also please file a bug to OS>LaCrOS>Partner, and CC kuanhuang@chromium.org.

R=rubber-stamper@appspot.gserviceaccount.com

Change-Id: If7253bb8ef08ea2a7f54cd45a4fc01a8f0283f16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5513124
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com <lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#610}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/LACROS_QA_QUALIFIED_VERSION[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714647247-18c9b860d6e7172bf53f5f1e100f2d243ff53eae-c5feab9720689ae620a1e04ec250f197b409c5ad.profdata to chrome-win64-6422-1714671275-8a82804bb6160e80779eec5f4cd99b51efc1d4b1-2f9e1beefe10e98ee4d1e7c0bdcf8f3c57ccc24d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ice3df6cdd88e99f4d48402d7f124d23d9e294c7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510795
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#609}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714647247-fe873ebf35b7c2fcb8c16483ec048ab273fb9571-c5feab9720689ae620a1e04ec250f197b409c5ad.profdata to chrome-win32-6422-1714671275-2bf602adbb3fda8f266dc4d22c42213ebcbd2eb6-2f9e1beefe10e98ee4d1e7c0bdcf8f3c57ccc24d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I8b429b83d81e96a1c04aaccfcfd87b1968812878
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509810
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#608}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714647247-e30eb7d13a32056b69fa3ebf23e22969b207b1de-c5feab9720689ae620a1e04ec250f197b409c5ad.profdata to chrome-linux-6422-1714671275-2695b5d33676b2c70ca893d056a6218dc5709385-2f9e1beefe10e98ee4d1e7c0bdcf8f3c57ccc24d.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ia55660dbfcf318d767b0ca460519d2f397984e55
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5512417
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#607}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714647247-6f96565a2b1d40c91de709ea9ba48d6d5c2eb3ba-c5feab9720689ae620a1e04ec250f197b409c5ad.profdata to chrome-mac-6422-1714671275-526967c98f8c2662c272b570395bfccdac684199-2f9e1beefe10e98ee4d1e7c0bdcf8f3c57ccc24d.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I60bcd9d6c28a941aaf476e751ba370e61f7093cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5511577
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#606}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Updated manual fallback IPH string to make it more clear (UX decision)

(cherry picked from commit e8ce89ebb49e7b3105ad409f12b96dbbe40124b6)

Bug: 336771061
Change-Id: I5b8dfd9547a2a9ca1f3bd1a13d593ce2da4e8a0f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5479771
Reviewed-by: Jan Keitel <jkeitel@google.com>
Commit-Queue: Theo Cristea <theocristea@google.com>
Reviewed-by: Bruno Braga <brunobraga@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1291859}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510403
Cr-Commit-Position: refs/branch-heads/6422@{#605}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/autofill_strings.grdp[diff]
• components/autofill_strings_grdp/IDS_AUTOFILL_IPH_MANUAL_FALLBACK.png.sha1[diff]

m125: [pdf-a11y]: relax AXObjectCacheImpl::MarkPluginDescendantDirty

The sole Pdf a11y trigger path is
PdfAccessibilityTree::MaybeHandleAccessibilityChange
PdfAccessibilityTree::UpdateDependentObjects
...
PdfViewWebPlugin::LoadAccessibility

This always guarantees
AXObjectCacheImpl
has a valid plugin tree source/serializer.

However, since PdfAccessibilityTree posts async tasks while building the tree, we must account for the fact that
AXObjectCacheImpl's
state may have changed.

For example, if a11y is turned off e.g.
PdfAccessibilityTree::AccessibilityModeChanged
may clear the tree from the cache.

As a result, it is acceptable to remove this CHECK.

R=aleventhal@chromium.org

(cherry picked from commit ef77a2d141758db43ceb4d87723e9451cb1519e0)

Bug: 334988068
Change-Id: I11e4c51413b9f7f6526b6955b999d1a0b95bc2a6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5469946
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1290763}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510925
Commit-Queue: David Tseng <dtseng@chromium.org>
Auto-Submit: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#604}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• third_party/blink/renderer/modules/accessibility/ax_object_cache_impl.cc[diff]

[iOS] Fix iOS 15 issue with Overflow Menu Customization toggles

It's unclear why this is necessary on iOS 15, but it does fix the issue
there.

(cherry picked from commit 044c39dddb69ae83eb7e66df3216a70d12e4820e)

Bug: 335786928
Change-Id: I975581839b692866bc17cfa95dd55790c42811dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5490192
Auto-Submit: Robbie Gibson <rkgibson@google.com>
Commit-Queue: Robbie Gibson <rkgibson@google.com>
Reviewed-by: Guillaume Jenkins <gujen@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1293093}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5511582
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#603}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ios/chrome/browser/ui/popup_menu/overflow_menu/overflow_menu_action_row.swift[diff]

Add FEDERATED_IDENTITY_API mapping to request type

A failing check due to improper mapping led to a failing CHECK on Clank.

(cherry picked from commit 846926ace326e81c80004fc78b031239537cfe48)

Bug: 335933472
Change-Id: Ieff9c23d410fd6a0b6e6fea93d83b4949f12c125
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5498595
Commit-Queue: Florian Jacky <fjacky@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Auto-Submit: Florian Jacky <fjacky@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293989}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510624
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#602}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• components/permissions/request_type.cc[diff]

Check initialization state before accessing GC-managed objects

The RADH::OnRenderError function call assumes the validity of the
associated AudioContext, which is a GC-managed object. This CL
fixes the assumption by checking the initialization state of the
RADH (which is changed before GC happens).

(cherry picked from commit 50eb6f8c2f57ebf5f0eb2480eb544f93e88673f5)

Bug: 331369797
Test: Local reproduction doesn't crash ASAN with this change
Change-Id: I2eb0ae55c6f6c1283b9fa9b31f1beca6f18a252b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5497083
Commit-Queue: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Michael Wilson <mjwilson@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293784}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510827
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#601}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• third_party/blink/renderer/modules/webaudio/audio_context.cc[diff]
• third_party/blink/renderer/modules/webaudio/realtime_audio_destination_handler.cc[diff]

[M125][Hub] Disable browser controls while visible

On LFF there is a seemingly few pixel "overlap" between the android
toolbar and the Hub's toolbar (at the bottom). For some reason in this
region click events on the Hub can "pass through" to the Toolbar. (This
is not an issue on phones). I suspect this is related to the prior
ability for the toolbar to reparent atop the Tab Switcher (although I
cannot find where this happens). As an interim solution hide the toolbar
Android view while the Hub is fully visible to prevent touch inputs from
passing through to the toolbar.

(cherry picked from commit 471d0795a39bbc4d47bef8e4f7102ce53cffc98e)

Fixed: 337616153
Change-Id: I8ddcda80145811774f7e48784960a54dc35d443b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5493335
Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Auto-Submit: Calder Kitagawa <ckitagawa@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293763}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508895
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#600}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/java/src/org/chromium/chrome/browser/hub/HubLayout.java[diff]
• chrome/android/java/src/org/chromium/chrome/browser/hub/HubLayoutUnitTest.java[diff]

Automatic update from google3

Automatic update for 2024-05-02 UTC

Change-Id: I2e21759858c960b32a9140900555e97a39ce7144
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510842
Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com>
Cr-Commit-Position: refs/branch-heads/6422@{#599}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• net/http/transport_security_state_static.pins[diff]
• net/http/transport_security_state_static_pins.json[diff]

[M125][Hub] Don't allow touch inputs to pass through HubContainerView

Prevent touch inputs through the tab switcher from reaching the toolbar
on LFF.

(cherry picked from commit d23054caac06418aa5fa469ef7c88e59ab2843fe)

Fixed: 337616153
Change-Id: I450f47cfc8c12fb9cff2120184a94aeb49e985a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5503150
Reviewed-by: Neil Coronado <nemco@google.com>
Auto-Submit: Calder Kitagawa <ckitagawa@chromium.org>
Reviewed-by: Sky Malice <skym@chromium.org>
Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1294625}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5506805
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#598}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/browser/hub/android/java/src/org/chromium/chrome/browser/hub/HubContainerView.java[diff]
• chrome/browser/hub/internal/android/java/src/org/chromium/chrome/browser/hub/HubManagerImplUnitTest.java[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714606974-2111ffe59c7d09b21cac15ac44c168046079359c-5eaffa90a0b0c7135378691126a82a4406b2e044.profdata to chrome-mac-6422-1714647247-6f96565a2b1d40c91de709ea9ba48d6d5c2eb3ba-c5feab9720689ae620a1e04ec250f197b409c5ad.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I56eea3d48f3a6565c598f7c5af3f749a6290723d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509943
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#597}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714627298-096135151e04fe1e3d4b75f8fc8882c738c160f6-2ca131066b20e105d23741a8901e23e783540cdb.profdata to chrome-win32-6422-1714647247-fe873ebf35b7c2fcb8c16483ec048ab273fb9571-c5feab9720689ae620a1e04ec250f197b409c5ad.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I7d37cf0c13c9f08672bce576c5ad1feaba348836
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509942
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#596}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714627298-c5f92010c57ae6183c2dbe3771637242bbcfc9cd-2ca131066b20e105d23741a8901e23e783540cdb.profdata to chrome-win64-6422-1714647247-18c9b860d6e7172bf53f5f1e100f2d243ff53eae-c5feab9720689ae620a1e04ec250f197b409c5ad.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I745c4c2afb2430416e513b3c71f5a76ff1968586
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509923
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#595}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Updating XTBs based on .GRDs from branch 6422

Change-Id: I2b0ea25d418abb5319c423341618906614118144
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5510003
Auto-Submit: Ben Mason <benmason@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#594}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/strings/ash_strings_fa.xtb[diff]
• ash/strings/ash_strings_pa.xtb[diff]
• chrome/android/features/tab_ui/java/strings/translations/android_chrome_tab_ui_strings_zh-CN.xtb[diff]
• chrome/app/resources/generated_resources_cs.xtb[diff]
• chrome/app/resources/generated_resources_fa.xtb[diff]
• chrome/app/resources/generated_resources_iw.xtb[diff]
• chrome/app/resources/generated_resources_or.xtb[diff]
• chrome/app/resources/generated_resources_pa.xtb[diff]
• chrome/app/resources/generated_resources_sk.xtb[diff]
• chrome/app/resources/generated_resources_zh-CN.xtb[diff]
• chrome/app/resources/generated_resources_zh-TW.xtb[diff]
• chrome/browser/ui/android/strings/translations/android_chrome_strings_fa.xtb[diff]
• chrome/browser/ui/android/strings/translations/android_chrome_strings_zh-CN.xtb[diff]
• chromeos/strings/chromeos_strings_fa.xtb[diff]
• components/browser_ui/strings/android/translations/browser_ui_strings_fa.xtb[diff]
• components/browser_ui/strings/android/translations/browser_ui_strings_zh-CN.xtb[diff]
• components/browser_ui/strings/android/translations/browser_ui_strings_zh-TW.xtb[diff]
• components/strings/components_strings_en-GB.xtb[diff]
• components/strings/components_strings_kn.xtb[diff]
• components/strings/components_strings_zh-CN.xtb[diff]
• ios/chrome/app/strings/resources/ios_google_chrome_strings_en-GB.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_ar.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_en-GB.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_zh-CN.xtb[diff]
• ios/chrome/app/strings/resources/ios_strings_zh-TW.xtb[diff]
• remoting/resources/remoting_strings_da.xtb[diff]
• ui/chromeos/translations/ui_chromeos_strings_zh-CN.xtb[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714627298-88889251b0d0d4f200f4c58b01a7b5778a9b2e57-2ca131066b20e105d23741a8901e23e783540cdb.profdata to chrome-linux-6422-1714647247-e30eb7d13a32056b69fa3ebf23e22969b207b1de-c5feab9720689ae620a1e04ec250f197b409c5ad.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I039d4ae13e98adf4195cf14f10bb5d6cf13994dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509945
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#593}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Automated Commit: LKGM 15853.19.0 for chromeos.

Uploaded by https://ci.chromium.org/b/8749093930513619793

Change-Id: Ia81fb76355dbeddb9ae66cece7e93893071bba28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5507895
Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#592}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/CHROMEOS_LKGM[diff]

Roll ChromeOS Bigcore AFDO profile from 125-6422.10-1714384890-benchmark-125.0.6422.22-r1 to 125-6422.10-1714384890-benchmark-125.0.6422.26-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-bigcore-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: If6d97dec4ce4ac1e5c19f85dba28ed267bb8c8cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509802
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#591}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/bigcore.afdo.newest.txt[diff]

Roll ChromeOS Arm AFDO profile from 125-6367.66-1714391204-benchmark-125.0.6422.20-r1 to 125-6367.66-1714391204-benchmark-125.0.6422.26-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-arm-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: Ia75f367d939c3c3ac1c89a16a46dde35ea3113f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508251
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#590}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/arm.afdo.newest.txt[diff]

Roll ChromeOS Atom AFDO profile from 125-6422.10-1714388999-benchmark-125.0.6422.22-r1 to 125-6422.10-1714388999-benchmark-125.0.6422.26-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-atom-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I420023039329e3264b29011c7fb60d35739df779
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509374
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#589}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/atom.afdo.newest.txt[diff]

Roll ChromeOS Arm Experimental AFDO profile from 125-6422.10-1714388999-benchmark-125.0.6422.20-r1 to 125-6422.10-1714388999-benchmark-125.0.6422.26-r1

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/cros-afdo-arm-exp-chromium-beta
Please CC c-compiler-chrome@google.com,mobiletc-prebuild@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I6c6a3ba5bcb340923ac197bcf953d9e4c8739485
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5506889
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#588}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chromeos/profiles/arm-exp.afdo.newest.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714606974-ba4bf53d09b745c29135ef50bbecded6477cba56-5eaffa90a0b0c7135378691126a82a4406b2e044.profdata to chrome-win32-6422-1714627298-096135151e04fe1e3d4b75f8fc8882c738c160f6-2ca131066b20e105d23741a8901e23e783540cdb.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ic1cd5170c3a7f9eceafcaf57a149a568c9c57332
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509117
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#587}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714606974-b3267acbac4c842334c59e5ef0004b5973b05ed4-5eaffa90a0b0c7135378691126a82a4406b2e044.profdata to chrome-win64-6422-1714627298-c5f92010c57ae6183c2dbe3771637242bbcfc9cd-2ca131066b20e105d23741a8901e23e783540cdb.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I36c974d281005761773fe1b4d5f9b7a0e77e369d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5506882
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#586}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714606974-1db661946c1721a4d887727ea4747bd926325aec-5eaffa90a0b0c7135378691126a82a4406b2e044.profdata to chrome-linux-6422-1714627298-88889251b0d0d4f200f4c58b01a7b5778a9b2e57-2ca131066b20e105d23741a8901e23e783540cdb.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Iedbc5a524d619c5c2e2aa7d6e122b059a6dc4afc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509118
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#585}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

Roll Amd64 AFDO from 125.0.6422.22_rc-r1-merged to 125.0.6422.26_rc-r1-merged

This CL may cause a small binary size increase, roughly proportional
to how long it's been since our last AFDO profile roll. For larger
increases (around or exceeding 100KB), please file go/crostc-bug.

Please note that, despite rolling to chrome/android, this profile is
used for both Linux and Android.

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

To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Tbr: mobiletc-prebuild@google.com
Change-Id: I09ef6ee8f2dfa5878c1e3169b20150e846371c90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5509174
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#584}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/profiles/newest.txt[diff]

[M125][Android] Seed account before request management status

When requesting the management status, an access token is required.
In consequence, the account should be seeded before the operation, otherwise, a crash may happen during the sign-in.

This CL forces the account seeding before the management status
request, when `SEED_ACCOUNTS_REVAMP` is disabled.

Theoretically, the new account seeding behaviour with
`SEED_ACCOUNTS_REVAMP` should prevent this issue. But the crash
logs indicate the contrary and further investigation is required.

(cherry picked from commit dcb496615da59c4942f719c32db372b25f428076)

Bug: 332900316
Change-Id: I3d77ad00a5bb992c4b9d471819d003003303abd0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5490280
Reviewed-by: David Roger <droger@chromium.org>
Reviewed-by: Boris Sazonov <bsazonov@chromium.org>
Commit-Queue: Menghan Yang <myuu@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1293590}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5500588
Commit-Queue: Krishna Govind <govind@chromium.org>
Auto-Submit: Menghan Yang <myuu@google.com>
Reviewed-by: Krishna Govind <govind@chromium.org>
Owners-Override: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#583}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/android/java/src/org/chromium/chrome/browser/signin/SigninManagerImpl.java[diff]
• chrome/android/junit/src/org/chromium/chrome/browser/signin/SigninManagerImplTest.java[diff]
• chrome/browser/android/DEPS[diff]
• chrome/browser/android/signin/signin_manager_android.cc[diff]
• chrome/browser/android/signin/signin_manager_android.h[diff]
• components/signin/internal/identity_manager/account_tracker_service.cc[diff]
• components/signin/internal/identity_manager/account_tracker_service.h[diff]
• components/signin/public/android/java/src/org/chromium/components/signin/identitymanager/AccountTrackerService.java[diff]

Roll Chrome Win64 PGO Profile

Roll Chrome Win64 PGO profile from chrome-win64-6422-1714585619-277e32fbccaed103d194af0a9f6551a83cbf56c9-4d370f43e125a0e1f239b23376ffbde3dcd306a9.profdata to chrome-win64-6422-1714606974-b3267acbac4c842334c59e5ef0004b5973b05ed4-5eaffa90a0b0c7135378691126a82a4406b2e044.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win64-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ifc4f36d8035f2f8da04f07936a672912977fda99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508203
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#582}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win64.pgo.txt[diff]

Roll Chrome Win32 PGO Profile

Roll Chrome Win32 PGO profile from chrome-win32-6422-1714585619-31943b3ca35cb469902c0c993beb2b1f884c7e2b-4d370f43e125a0e1f239b23376ffbde3dcd306a9.profdata to chrome-win32-6422-1714606974-ba4bf53d09b745c29135ef50bbecded6477cba56-5eaffa90a0b0c7135378691126a82a4406b2e044.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:win-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: Ie40dcc161cc156ab37f8d460345cf2138b45b7cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508202
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#581}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/win32.pgo.txt[diff]

Roll Chrome Mac PGO Profile

Roll Chrome Mac PGO profile from chrome-mac-6422-1714585619-49dba5d032b86ffb3558099e0cee7aadc8da4049-4d370f43e125a0e1f239b23376ffbde3dcd306a9.profdata to chrome-mac-6422-1714606974-2111ffe59c7d09b21cac15ac44c168046079359c-5eaffa90a0b0c7135378691126a82a4406b2e044.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-beta
Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human
is aware of the problem.

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:mac-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I6cf0c6d1d38f1e76c79d52c0c5d08941aae03914
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508199
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#580}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/mac.pgo.txt[diff]

Roll Chrome Linux PGO Profile

Roll Chrome Linux PGO profile from chrome-linux-6422-1714585619-ea77d9f7a97b1095b06a4f228f3864535c5bd177-4d370f43e125a0e1f239b23376ffbde3dcd306a9.profdata to chrome-linux-6422-1714606974-1db661946c1721a4d887727ea4747bd926325aec-5eaffa90a0b0c7135378691126a82a4406b2e044.profdata

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

To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry

To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622

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

Cq-Include-Trybots: luci.chrome-m125.try:linux-chrome
Tbr: pgo-profile-sheriffs@google.com
Change-Id: I2828b5f6538969345cc06ff631573e3eaf8c24e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508037
Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#579}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/build/linux.pgo.txt[diff]

[merge to 125] splitview: Fix tablet mode performant resize

This fixes the performant resize issue in tablet mode. The window was
using its transformed bounds in screen, when it should be using its
target bounds.

Demo: https://buganizer.corp.google.com/issues/304367964#comment13

(cherry picked from commit 048ca8a667ed5ad6112633cb05966614e8d2ca8f)

Test: added, verified it fails w/o fix in CL:5494904
Bug: b/304367964
Change-Id: Ie3897c32020115924aa6d289d873c18de9345d35
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5493778
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Sophie Wen <sophiewen@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1295217}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5507551
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#578}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/wm/splitview/split_view_controller.cc[diff]
• ash/wm/splitview/split_view_controller.h[diff]
• ash/wm/splitview/split_view_controller_unittest.cc[diff]

[merge to 125] splitview: Add crash logs in `StartResizeWithDivider()`

This will help us debug the crash.

(cherry picked from commit 7f0ca207824b86ada232ae4eec3d1a087e3c1548)

Bug: b/337283677
Change-Id: I565092e74d085321b2195f417883449d2e0e6f4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5493589
Reviewed-by: Xiaoqian Dai <xdai@chromium.org>
Commit-Queue: Sophie Wen <sophiewen@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1293939}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5498864
Cr-Commit-Position: refs/branch-heads/6422@{#577}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• ash/wm/splitview/split_view_controller.cc[diff]

Roll src/chromeos/ash/resources/internal/

Two commits are included:
bc844cc Update container app icon. by Li Lin · 11 days ago main
3a96117 Add internal strings for write and rewrite. by Darren Shen · 12 days ago

Bug: b/335884954
Change-Id: Ibe2468c90fc9bc0531e29c601d2698c0c53b335e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5503216
Commit-Queue: Li Lin <llin@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/branch-heads/6422@{#576}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• DEPS[diff]
• chromeos/ash/resources/internal[diff]

Incrementing VERSION to 125.0.6422.27

Change-Id: I63165866044c60f959c416ef0923d04c1a88d1bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5507614
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6422@{#575}
Cr-Branched-From: 9012208d0ce02e0cf0adb9b62558627c356f3278-refs/heads/main@{#1287751}

• chrome/VERSION[diff]