GitLab

OpenPDFParamsParser currently maintains an array of requests and assumes
they will get replied in the same order. By changing the return type of
getNamedDestinationCallback() to a promise, this CL enables
getViewportFromUrlParams() to handle the data returned by the plugin
directly, without storing all the requests inside OpenPDFParamsParser.

This CL also removes the usage of onNamedDestinationReceived() from
browser tests.

Bug: 55776,535978,748852
Change-Id: If6e8285a363d2efee169457856ca465cb498805a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2391102
Commit-Queue: Hui Yingst <nigi@chromium.org>
Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809449}

- .dwp files produced by clank build will now be output to
lib.unstripped folder instead of the root out folder. This is to ensure
they are in the expected place for Breakpad symbol generation and symbol
archiving.

Bug: 1112935
Change-Id: Id5cfb8a0188e3a6fa30fb56ed98bdb4e7da2af03
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406595
Commit-Queue: Nelson Billing <nbilling@google.com>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809448}

Fixes this compilation error:
../../components/autofill/core/browser/data_model/autofill_offer_data.cc:56:8: error: ‘sort’ is not a member of ‘std’; did you mean ‘sqrt’?

Bug: 957519
Change-Id: Iaef429cfca5e55af8b819457f9b9729ab4f669f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423586
Commit-Queue: Parastoo Geranmayeh <parastoog@google.com>
Reviewed-by: Parastoo Geranmayeh <parastoog@google.com>
Cr-Commit-Position: refs/heads/master@{#809447}

Bug: None
Change-Id: I9a0817a90270266a538062aaf4e322a86fa3ed6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422146Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809446}

This CL makes the "don't show again" checkbox by default unchecked.
This is discussed with PM that the 3+1 approach may be confusing to the
user, and we don't want a IPH on the download later dialog.

Bug: 1117573
Change-Id: I23a95720d031489a4a5ccfa4ec872e9e613279a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423044
Commit-Queue: Xing Liu <xingliu@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809445}

Controls can be applied on the device as a whole, or only on a request.
Add an optional request parameter to SetExtCtrls() to cover this
use-case. We can use it in the V4L2DecodeSurface once the config store
is retired.

BUG=chromium:1009921
TEST=video.DecodeAccel.h264 passes on Kukui.

Change-Id: I2fefdedd2b9ad3a2b02d3a8ecfe74bbd19b6db58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2421994
Commit-Queue: Fritz Koenig <frkoenig@chromium.org>
Reviewed-by: Fritz Koenig <frkoenig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809444}

Stumbled upon a big bunch of these, so took the opportunity to quickly
fix them. Looks like they are all gone, at least according to this
command:

    $ git grep 'struct *v4l2_.*= *{.*};'

BUG=b:153935975
TEST=video.DecodeAccel.h264 passes on Kukui.

Change-Id: I2c4709ff0a15c01c446a8599c7de5e498017294b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2421993Reviewed-by: Fritz Koenig <frkoenig@chromium.org>
Commit-Queue: Fritz Koenig <frkoenig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809443}

R=khorimoto@chromium.org

Bug: 1045266
Test: OSSettingsInternetKnownNetworksPage*
Change-Id: I8b689fc1fa915f2dc2a2994515422d9d0e0db68a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419583
Commit-Queue: James Hawkins <jhawkins@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809442}

ActivationAction controls both focus and blur behaviors of a bubble:
a) DO_NOT_ACTIVATE: no focus, persistent bubble.
b) ACTIVATE: get focus on creation, dismiss bubble on blur.
The blur behavior was not well documented.

Feature bug 1121399 introduces snoozable IPH bubble that needs to
c) get focus on creation, persist on blur.

To add support for c) and keep support for a) and b), this CL breaks
ActivationAction into two bools to control focus and blur behaviors of a
bubble separately.


Bug: 1121399
Change-Id: I2a38d740d901905bc13855d421000bff4bf2ca3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423305
Commit-Queue: Keren Zhu <kerenzhu@chromium.org>
Reviewed-by: Collin Baker <collinbaker@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809441}

Bug: 1115597
Change-Id: Ibd17d29f636ac6b4b480d8e20658e51a3a31d650
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2409606Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809440}

Remove the "TEMP" comment for WebLocalFrame::UsageCountChromeLoadTimes()
from 4 years ago.

Bug: 621512
Change-Id: If823b6685d73e3065e931a12e231380e6cd0833d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2404523Reviewed-by: Nate Chapin <japhet@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809439}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/899ea244a8db..2fb4be6e85e6

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

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

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

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: chromium:1128988
Tbr: huangdarwin@google.com,lgrey@google.com
Change-Id: I9c05869132f0c86936ac52259b46f2d2aeb69900
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424723Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#809438}

Add the LanConnectivity routine to the ServiceConnection.

BUG=chromium:956783
TEST=1) chromeos_unittests --gtest_filter=CrosHealthdServiceConnectionTest.*
2) Applied LanConnectivity changes and successfully ran the
LanConnectivity routine on a DUT (verified using cros-health-tool diag
--action=run_routine --routine=lan_connectivity).

Change-Id: Ia0c9fd15d07c121d04fa08466694575cc3048d0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2321005
Commit-Queue: Kartik Hegde <khegde@chromium.org>
Reviewed-by: Paul Moy <pmoy@chromium.org>
Reviewed-by: Oleh Lamzin <lamzin@google.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809437}

Bug: 1069183
Change-Id: I6bbcb5857c798faabd164e7b08523d05ec7aecdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414916
Commit-Queue: Dan H <harringtond@chromium.org>
Reviewed-by: Esmael Elmoslimany <aee@chromium.org>
Reviewed-by: Carlos Knippschild <carlosk@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809436}

In destination dialog display red error status text whenever a local
CrOS printer has an error printer status.

Hide the search-hint <span> when empty to make more room for the error
status text.

Screenshot: http://screen/rsAqy3dWhECQNyS

Bug: 1123754
Change-Id: Ifbbee309b8dee17ad88c4a51923c0f445cf225c8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405711Reviewed-by: Rebekah Potter <rbpotter@chromium.org>
Commit-Queue: Gavin Williams <gavinwill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809435}

https://android.googlesource.com/platform/external/perfetto.git/+log/ada5d5129f48..82c70d97576c

2020-09-22 fmayer@google.com Merge "Have separate sampler per heap."

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

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

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

Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel
Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: I40e4aaf295b21fb28ff7be47ff71746a99d72825
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424567Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#809434}

An non-focasable widget will not set its anchor view's kAnchoredDialogKey,
but currently a bubble dialog will reset kAnchoredDialogKey when it
detaches from its anchor view. This will break the focus traversal path
if kAnchoredDialogKey was pointing to a different widget.

This CL fixes this issue by resetting kAnchoredDialogKey only if it
is pointing to the current bubble. This issue blocks bug 1121399
where a focusable IPH bubble will contest kAnchoredDialogKey of a tab
while a non-focusable tab hover card might anchor to it. The hover card
will later accidentally detaches the IPH bubble from the tab when it
dismisses.

Bug: 1121399
Change-Id: Ia7f82ee166eae100cd18ffa816ddf50cf02acba6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422709Reviewed-by: Wei Li <weili@chromium.org>
Commit-Queue: Keren Zhu <kerenzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809433}

Change ModuleRecord::ModuleRequests to return directly
Vector<ModuleRequest>. This avoids the overhead of two temporary
Vectors for source position and specifiers.

Remove ModuleRecord::ModuleRequestPositions as it is no longer needed.

Bug: 945094
Change-Id: Ie6400e7511f2a5879bbf95223f4eeb021b4ae0c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414288
Commit-Queue: Camillo Bruni <cbruni@chromium.org>
Auto-Submit: Camillo Bruni <cbruni@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809432}

This CL add system toast for reverse scrolling gesture changes.

 - If the user perform wrong gestures twice, a system toast will show up
 to indicate the right gestures.

 - If the toast shows at the fist time, it will disappear until the user
 perform the right gesture. Otherwise, it will shows for 2500ms.

Bug: 1107183

Change-Id: I1fd3fb9f0c898ca15cae2de87df6e89c7b62aecc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417242
Commit-Queue: Xiaodan Zhu <zxdan@chromium.org>
Reviewed-by: Jun Mukai <mukai@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809431}

Old behavior: Use max content contribution for flex base size, which is
roughly: use computed width if it exists, otherwise use intrinsic size
after applying the aspect ratio and min/main/max height. In either
case, apply min/max width.

New behavior is similar to the 'max-content' size: use the intrinsic
width after applying the aspect ratio and min/main/max height. Ignore
computed min/main/max width.

Also, we weren't returning available size as the max-content size of an
SVG item that only has an aspect ratio and no intrinsic sizes, which is
what Firefox does and what the spec dictates.

Both of these are fixed with a new aspect-ratio sizing method that
currently lives in flex but will be moved to NGReplacedLayoutAlgorithm
when it exists.

Change-Id: I4afb382a7604a4fcd0626f0702edf72f21cd0bcc
Bug: 987000
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399082Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809430}

Fix a crash related to change
https://chromium-review.googlesource.com/c/chromium/src/+/2418998

Seems there is reentrancy during destruction for pepper plugin
instance. Do not access any containers if we've been marked for
deletion. This follows the same convention for handling messages.

BUG=1130991

Change-Id: I2004265dc5592761c24c957be6231c3a1ad86d2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423271Reviewed-by: Bill Budge <bbudge@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809429}

This is a followup to this patch:
https://chromium-review.googlesource.com/c/chromium/src/+/2412834

...to make the same changes to LocalFileStreamReader that were requested
for the FilesystemProxyFileStreamReader in that review.

Bug: 1119547
Change-Id: Ibaccd858c807969eb185012add8ab01fed4aad33
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422271
Auto-Submit: enne <enne@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Commit-Queue: enne <enne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809428}

The callers can just do layer->device_scale_factor() themselves.

R=sky@chromium.org

Bug: 1130050
Change-Id: Iccfd2ae47b4988e3f83868f10f99b61b4be3e0a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419507
Auto-Submit: danakj <danakj@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809427}

As is, the utility processes launched by the Cloud Print service process
are generic utility processes. This worked fine for Cloud Print on
Windows until https://crrev.com/748400 limited the sandbox types to do
gdi32.dll patching for. To resume gdi32.dll patching, update the utility
processes to be of type |kPdfConversion|, which better reflects what
they do.

Bug: 1128450
Change-Id: Ib2f3bfb688891d628ba798965f3e137ec4490c28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423543Reviewed-by: Will Harris <wfh@chromium.org>
Commit-Queue: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809426}

R=johntlee@chromium.org

Fixed: 1130854
Change-Id: I546c0650bb940ce8a92d4cf2a3ea54a309ba1346
Bug: 1130854
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423056Reviewed-by: John Lee <johntlee@chromium.org>
Commit-Queue: Rebekah Potter <rbpotter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809425}

The client is using the supported pixel format reported
by the capture device to start capturing, NV12 is
supported by some capture devices on Chrome OS and virtual
capture devices. So we should allow the client to request
NV12 as the capture pixel format.

      device

Bug: b/166284508
Test: Manually on Cast device that use NV12 virtual capture
Change-Id: I8fd713ec46c52f49928bed5fedc51bdcc342c855
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416757Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Commit-Queue: Peter Qiu <zqiu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809424}

Increase the animation layer on each side by a ratio of the root window
width. When swiping, users can see this padding if they swipe towards a
direction with no more desks (i.e. swipe right at desk 0). Clamps the
translation such that the entire animation layer is always visible.

Tested that the edge padding does not affect non continuous gestures.
Though not seen, the edge padding is there for simplification. Can be
easily modified if desired in the future.

Test: manual
Bug: 1111445
Change-Id: I3b204d8ef1e1648b421310e1aa714346a94959aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417491
Commit-Queue: Sammie Quon <sammiequon@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809423}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/ff52c73e..eb373a50

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

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel
CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel

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

Change-Id: I2a9ca78044b2e5367b61e547aa09a1977c2ab881
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424065Reviewed-by: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#809422}

Use the WidgetBase implementations instead of going via the
WebWidgetClient.

BUG=1097816

Change-Id: Ib08b5748806fe3862ac291d354043326d3172282
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419129Reviewed-by: danakj <danakj@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809421}

In the past, Conflict(409) are used when
1) There are multiple device records for one device id.
2) Database concurrent update exception.

Few months ago, the enterprise server began to return the
Too Many Request(429) for the second situation above to allow the client
side to setup different retry strategies.

Policy Fetch and CBCM reporting will retry on 429 but not 409.
Chrome OS demo mode will show the error message and retry.
Chrome OS enrollment will record a different UMA value.

Bug: 1108817
Skip-Translation-Screenshots-Check: True
Change-Id: I3b302ab03e16a41a30103f809c1b51813647dd7c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2419119
Commit-Queue: Owen Min <zmin@chromium.org>
Reviewed-by: Aga Wronska <agawronska@chromium.org>
Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809420}

Previously when navigating through a link from a page that was translated would case the new page to be translated automatically without any UI being shown. Now the normal translate UI will be shown, so that the user knows that the page is being translated.

Bug: 1057731
Change-Id: I777955d2b755c212565ed374641eb819e636bd41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422816Reviewed-by: Megan Jablonski <megjablon@chromium.org>
Commit-Queue: Max Curran <curranmax@chromium.org>
Auto-Submit: Max Curran <curranmax@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809419}

This CL enables the profile switch interception, and adds performance
histograms.
It supports switching to an existing profile, whether it is already
loaded or not.

It also adds an histogram to measure the performance of the session
startup (which in mainly the time to inject the account on the web).

Screenshot: https://screenshot.googleplex.com/95FNoDH6QqSkCcV

Note: strings are not finalized and will be updated in a follow-up CL.

Bug: 1076880
Change-Id: Ia3ce4a816dc328d032d7660fac199a7a36338429
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2416349Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Monica Basta <msalama@chromium.org>
Commit-Queue: David Roger <droger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809418}

Updates the expires_after attribute for 91 histograms that show
frequent access in the past 90 days.  These are the 90% most
frequently used histograms over that time that do not already
have a date later than or within 60 days of 2020-12-21.

TBR=chromium-metrics-reviews@google.com

Change-Id: I3eb8a8b903a4d423a43ffd0216aefe5eaf86a50f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424484Reviewed-by: Chrome Metrics Logs <chrome-metrics-team+robot@google.com>
Commit-Queue: Chrome Metrics Logs <chrome-metrics-team+robot@google.com>
Cr-Commit-Position: refs/heads/master@{#809417}

Bug: 1099917
Change-Id: I33b7700dc218308af87373722afe7c7639f5cb8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417074
Commit-Queue: Roman Arora <romanarora@chromium.org>
Reviewed-by: Thomas Lukaszewicz <tluk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809416}

Chromium iOS recipes seem to be based on generic recipes like for
example [1] nowadays.

This is a follow-up of https://chromium-review.googlesource.com/c/chromium/tools/build/+/2418820.

[1] - https://source.chromium.org/chromium/chromium/tools/build/+/master:recipes/recipes/chromium_trybot.py

Bug: webrtc:11604
Change-Id: I3abc8b53f79ff5ca27fc9f2b965f611e396eeaf7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2420609Reviewed-by: Dirk Pranke <dpranke@google.com>
Commit-Queue: Mirko Bonadei <mbonadei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809415}

Bug: 1123889
Test: manual. see bug for repro step.
Change-Id: I3f99b00ccb6478a1bdc1dc871827a48e8560911f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422866Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809414}

https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/9f82884d032c..f46b7d67f8f2

2020-09-22 cpinnamaneni@microsoft.com Network sort requests on type

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/devtools-frontend-chromium
Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human
is aware of the problem.

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

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

Bug: chromium:1130839
Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com
Change-Id: Ic0695c0ce4cf998d3d58d8b12492c6f0af92099d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2424564Reviewed-by: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#809413}

Updates the expires_after attribute for 2 histograms that have
been used to generate alerts in the past 90 days and do not already have
a date later than or within 60 days of 2020-12-21.

TBR=chromium-metrics-reviews@google.com

Change-Id: Iacab9b2d240b398566ad36946caac6473e9b9cbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423171Reviewed-by: Chrome Metrics Logs <chrome-metrics-team+robot@google.com>
Commit-Queue: Chrome Metrics Logs <chrome-metrics-team+robot@google.com>
Cr-Commit-Position: refs/heads/master@{#809412}

Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202009220800_RC00.html

https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/u9IxXetAD5rBCs-E3qW49qhhcWCVkh51yLFjLWQfwOIC

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

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

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

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: b/138961540,b/165872577,b/168547738
Tbr: media-app@grotations.appspotmail.com
Change-Id: I72b1d5a7241225e24308c8663c6332eebb3d5c66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2423979Reviewed-by: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#809411}

According the query
https://console.cloud.google.com/bigquery?sq=575346572923:aac7a4bc484d424f93a1f65b7000c6cb,
unit_tests has the second highest failure count.

Also move the chrome_public_test_apk to MM-x86-rel-non-cq

Bug: 997376, 1127110
Change-Id: I1ca4a1250233fe0cf1d0615f3580ccc10ba01ed4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2422710
Auto-Submit: Haiyang Pan <hypan@google.com>
Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
Commit-Queue: Yuke Liao <liaoyuke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#809410}