Publish DEPS for 111.0.5563.39
Incrementing VERSION to 111.0.5563.39
Change-Id: If0663327e6505cb36a8a936e863b7e38a3cab482
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4279361
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#700}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[M111] Prefer official paper names for duplicate sizes
In crrev.com/c/4157931, we dropped borderless sizes from the localized
paper name list so they wouldn't override standard size names. We have
subsequently found printers that report multiple non-borderless paper
entries with the same dimensions. We can't just drop all of the
non-standard names because sometimes there are no official PWG sizes
corresponding to any of the entries.
What we ideally want is to use the official PWG name that has a curated
localization if it is available for a particular size. If no official
name for a given size is available, we should pick any of the
non-borderless entries to display.
Achieve this in two steps:
1. Before generating a name for a non-standard size, look it up to see
if the dimensions correspond to an official size. Use the same
display name as the official size if one exists. This ensures that
all the entries with the same dimensions sort next to each other.
2. Track whether each entry came from the table of official sizes and
sort official sizes above non-standard ones. This means that the
official size will always be first if it exists (and therefore chosen
during de-duplication). If an official size doesn't exist, the first
non-standard size will be chosen.
This wasn't a clean cherry pick from M112 because of crrev.com/c/4104564 and
crrev.com/c/4242510. I checked that the final diff is the same and deployed to
a R111-15329.29.0 build to verify the behavior is the same.
(cherry picked from commit 9666ffd979c948ad4e72c0c0813a76aa9dc30088)
Bug: b:268586056
Test: Manual review of paper size lists on lab printers
Change-Id: I3b2604a287f94a0685e80a5860a9ef6296d032c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4242274
Reviewed-by: Lei Zhang <[email protected]>
Commit-Queue: Benjamin Gordon <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105376}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4276463
Cr-Commit-Position: refs/branch-heads/5563@{#699}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[cc-side-panel] Squashed Panorama a11y fixes
This is a squash of the following changes:
>> [ntp][cr-elements] Give Panorama shortcut buttons accessible names
>>
>> UI screenshot: screenshot/3c33cebpM7XihUw.png
>> Accessibility tree screenshot: screenshot/78egjf3SGauAQoV.png
>>
>> Problem: We don’t define labels for our `cr-radio-button`s.
>> This causes `aria-labelledby` [1] for our `cr-radio-button`s to
>> be an empty string [2].
>>
>> Caveat: We cannot use `cr-radio-button`'s `label` attribute as is
because the styling is different than what we need. The default cr-radio-button is left aligned and only >> has one label. Our buttons are right aligned and have two labels.
>>
>> Proposed Solution: Create attribute that hides `cr-radio-button`s
>> label text when added.
>>
*Other alternatives were discussed and vetted i.e. moving our custom button label into `cr-radio-button.` >> This solution was chosen because
it allows us to preserve our existing shortcuts UI and create a custom aria-label which consists of both >> labels (follow up CL).
>>
[1] https://source.chromium.org/chromium/chromium/src/+/main:ui/webui/resources/cr_elements/>> cr_radio_button/cr_radio_button.html;drc=730ff74c221e59ccdf7b116ae924d9d1b150341e;l=6
>> [2]
https://source.chromium.org/chromium/chromium/src/+/main:ui/webui/resources/cr_elements/cr_radio_button/>> cr_radio_button_mixin.ts;drc=ab67842ff06675153972984b5c7b7dcd7f6df395;l=53.
>>
>> Bug: 1416276
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264930
>> Reviewed-by: John Lee <[email protected]>
>> Commit-Queue: Paul Adedeji <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1107079}
>> (cherry picked from commit 91b2e6615ffc12ed129d61c6649929b4413596a8)
>>
>>
>> [NTP] Do not extract color if no image or failed request
>>
>> Added a check of the http_response_code to handle the case of fetch_url
>> being empty, since there were a few edge cases where it was happening.
>> If it happens, the user will keep their current theme color, but it will
>> no longer be shown in Appearance as the extracted color.
>>
>> Set the http_response_code in the unit tests, since the default appears
>> to be RESPONSE_CODE_INVALID. Added a new test for the case of the code
>> being RESPONSE_CODE_INVALID.
>>
>> Bug: 1415162
>> Change-Id: I13251edf1cd7b8b4f0f51ecbc4c8fc52c224542d
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262697
>> Reviewed-by: Tibor Goldschwendt <[email protected]>
>> Commit-Queue: Riley Tatum <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1106934}
>> (cherry picked from commit 5ec65a7475c6b9d6d91a92c82f1b1bf652030c10)
>>
>>
>> [cc-side-panel] Use aria-current
>>
>> This CL:
>> * Replaces aria-checked with aria-current for button role elements since
>> aria-checked isn't compatible with role button,
>> * Sets aria-current to 'true' or 'false' string values as required by
>> the spec, and
>> * Makes Chrome Color tiles role button to be consistent with the rest of
>> the UI.
>>
>> Bug: 1415829
>> Change-Id: Idf756a53a6af9240975c8ec989b4d9ac44e9b8fe
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262522
>> Reviewed-by: Riley Tatum <[email protected]>
>> Auto-Submit: Tibor Goldschwendt <[email protected]>
>> Commit-Queue: Riley Tatum <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1106908}
>> (cherry picked from commit 284ef60083d7c7df036da0780364aff04341f44e)
>>
>>
>> [ntp][side-panel] Move aria-label from parent div to images
>>
>> Problem: Screen readers are reading sources as well
>> Solution: Move aria-label to images directly
>>
>> Custom Theme
>> before: screenshot/BkEaKC7pvKyfSzV.png
>> after: screenshot/AATmVVRfqTV3CVZ.png
>>
>> Uploaded Theme
>> before: screenshot/BBhG4kj7U9kG4jt.png
>> after: screenshot/86CXm6gHq3bzPVq.png
>>
>> Classic Chrome
>> before: screenshot/8MhFjewV4BARaUZ.png
>> after: screenshot/BmEmT6HeLWkPhfo.png
>>
>> Change-Id: I38ba8c9593cc0704b3d885af34f97a27b294f69f
>> Bug: 1415566
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262528
>> Reviewed-by: Tibor Goldschwendt <[email protected]>
>> Commit-Queue: Paul Adedeji <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1106768}
>> (cherry picked from commit 37e41b558e3978e9e5152736bdc734075b1a951e)
>>
>>
>> [ntp][side-panel] Add aria-pressed to customize chrome button
>>
>> Change-Id: I191002e193488da157e68405b69b4b596fa342b1
>> Bug: 1415555
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257576
>> Commit-Queue: Paul Adedeji <[email protected]>
>> Reviewed-by: Tibor Goldschwendt <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1106391}
>> (cherry picked from commit df8224b2d402d1d9b6b9f0fbe4ad863249ff1ab0)
>>
>>
>> [ntp][side-panel] Define initial focus states for pages
>>
>> Video demo for solution in bug comments
>>
>> Change-Id: I8c1969850d1cf996a5ba30f9f906a21fc783f32f
>> Bug: 1415576
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4251557
>> Reviewed-by: Tibor Goldschwendt <[email protected]>
>> Commit-Queue: Paul Adedeji <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1106302}
>> (cherry picked from commit 5ed3d92d1f49cc35bbbc7b45f850d2cae2f0a1c2)
>>
>>
>> [NTP][Panorama] Fix outlines, upload icon, and chrome colors in hcm
>>
>> I borrowed how high contrast mode is currently handled in the prod
>> customize chrome dialog.
>>
Changed the chrome colors icon to be made as an svg rather than being colored divs. As an svg, Windows >> doesn't remove the color in high contrast mode.
>>
>> Note: This was tested by copying html and css into dev tools on my
>> personal windows laptop with Canary, not with a build. If there is a
>> better way to do this without dev setup on a windows computer that I
>> should try, let me know.
>>
>> Screenshots:
>> screenshot/AfJc4ochZp8csyi
>> screenshot/BvAXYZhXRG7Qx7n
>> screenshot/96Aoj3yTyETcZTN
>> screenshot/F2A3fgsMVskqbah
>> screenshot/BGJS8kACwK22jMw
>>
>> SVG change not in high contrast:
>> screenshot/AhjGHTjAMFGiwLG
>>
>> Bug: 1416254, 1415980
>> Change-Id: Ib621c6526cb4b184a994eab4c9323e30e3b69d52
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257025
>> Commit-Queue: Riley Tatum <[email protected]>
>> Reviewed-by: Paul Adedeji <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1106290}
>> (cherry picked from commit b2414d1faa960a6599585f52604f177ed36b04ee)
>>
>>
>> Make radio button checked status visible in high contrast mode
>>
>> Before:
>> screenshot/BPG5YaaFvtvyKhX
>>
>> After:
>> screenshot/BwHWpHYeNKdo2g5
>>
>> Bug: 1416281
>> Change-Id: I36164c4d97be2db58fd38706d4975155ae30f4a3
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257228
>> Reviewed-by: John Lee <[email protected]>
>> Commit-Queue: Riley Tatum <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1105957}
>> (cherry picked from commit 158d292aacf9496f7753c52de67b2e605619a3d8)
>>
>>
>> [ntp][panorama] Add alt text to theme snapshot
>>
>> Change-Id: I8927abfb19dd4a2071dfb5741f763dc752731096
>> Bug: 1415566
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250098
>> Reviewed-by: Tibor Goldschwendt <[email protected]>
>> Commit-Queue: Paul Adedeji <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1105810}
>> (cherry picked from commit 95da1d529edf5481ba14127f8a1b9410fbd6f057)
>>
>>
>> [ntp][side-panel] Add aria labels to shortcut buttons
>>
>> Change-Id: I291f99928120becef1de375a4fb20a54918b12b4
>> Bug: 1416276
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250150
>> Commit-Queue: Paul Adedeji <[email protected]>
>> Reviewed-by: Tibor Goldschwendt <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1105316}
>> (cherry picked from commit 6837812963d8bf6eb4747e466f49996197978f8a)
>>
>>
>> [NTP][Panorama] Change h1s to h2s
>>
>> This doesn't change it visually. It was a request from the a11y team.
>>
>> Screenshots:
>> screenshot/8bnuquFTBpd3YiQ
>> screenshot/59PFYP9vjPh8ZSJ
>> screenshot/9kjHi8qR6osdETe
>> screenshot/9Ww5TmwdBYp7EHX
>>
>> Bug: 1415515
>> Change-Id: Iaf49fae5db7ce80b025f69bcee57ea4b7bc236fc
>> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4247639
>> Reviewed-by: Paul Adedeji <[email protected]>
>> Commit-Queue: Riley Tatum <[email protected]>
>> Cr-Commit-Position: refs/heads/main@{#1105147}
>> (cherry picked from commit 3817fcde3ff727bd79b303f9a38858fdbc643d4b)
Fixed: 1418079
Change-Id: Ia078ddff55f9e82838e8d78894677fb0a1bf6479
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4276522
Reviewed-by: John Lee <[email protected]>
Reviewed-by: Paul Adedeji <[email protected]>
Commit-Queue: Tibor Goldschwendt <[email protected]>
Reviewed-by: Riley Tatum <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#698}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[M111] Skip reloading initial NavigationEntries
Merge to M111.
Currently, doing a reload while on the initial NavigationEntry might
result in committing an unrelated pending NavigationEntry and
mistakenly marking that entry as an initial NavigationEntry. That will
cause problems, such as the URL bar showing about:blank instead of the
URL of the NavigationEntry. To prevent that happening in this case,
skip reloading initial NavigationEntries entirely. This is a
short-term fix, while we work on a long-term fix to no longer
mistakenly mark the unrelated pending NavigationEntry as the initial
NavigationEntry.
(cherry picked from commit 31063532586a2e6c47fa7529e1dc0a97558d901c)
Bug: 1414625
Change-Id: I7ff1370efa558512b38bfe63370a66ce373c1db1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262220
Reviewed-by: Rakina Zata Amni <[email protected]>
Reviewed-by: Sirisha Kavuluru <[email protected]>
Commit-Queue: Shu Yang <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1107211}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4276381
Reviewed-by: Robert Kroeger <[email protected]>
Auto-Submit: Shu Yang <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#697}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll v8 11.1 from 9b6a1a4c32fd to 3e5cb8693c29 (2 revisions)
https://chromium.googlesource.com/v8/v8.git/+log/9b6a1a4c32fd..3e5cb8693c29
2023-02-21 v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Version 11.1.277.9
2023-02-21 [email protected] Merged: [ic] store slow stubs for objects with access checks in DefineNamedIC
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/v8-chromium-release-0
Please CC [email protected],[email protected],[email protected] on the revert to ensure that a human
is aware of the problem.
To file a bug in v8 11.1: https://bugs.chromium.org/p/v8/issues/entry
To file a bug in Chromium m111: https://bugs.chromium.org/p/chromium/issues/entry
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/main/autoroll/README.md
Bug: chromium:1415249
Tbr: [email protected]
Change-Id: Ib9d55ac7d639049037c02fd3f59948d6c40de354
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4276783
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#696}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Multiplanar: Fallback to media YUV/RGB conversion for legacy mailboxes
For multiplanar support, we had added YUV to RGB conversion and
RGB to YUV conversion [1] as part of passthrough command decoder.
This conversion only supports shared images and not legacy mailboxes.
This change checks for legacy mailbox and falls back to previous path
for YUV/RGB conversion instead.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/4192067
(cherry picked from commit e6498df7434d7150c58fb2db3b313a85ed94eb3f)
Bug: 1416342
Change-Id: I8def8ea80e7479de06c976601c6d77de8a1646f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250368
Commit-Queue: Saifuddin Hitawala <[email protected]>
Reviewed-by: Dale Curtis <[email protected]>
Reviewed-by: Vasiliy Telezhnikov <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105844}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4275001
Commit-Queue: Prudhvikumar Bommana <[email protected]>
Owners-Override: Prudhvikumar Bommana <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#695}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676975494-ec34e0d3ec3dc1eea4bf42b20e8ea66b9ebed55a.profdata to chrome-win64-5563-1677001674-38657673b38da3f54c61347ecd7555d16759747f.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I89cbc57ed67b6e8de93d444df391ada632459f61
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4276501
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#694}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676975494-d2279a2dc4d3c755294aecd3f3962eb853958b5c.profdata to chrome-mac-5563-1677001674-45b1e7897a44a4a23335ae47beea3054ba882cb8.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I8cafbfd77d4230aec325fb18ef5dc4f7d7a66458
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4276561
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#693}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Ensure safe access to children during ui::Layer::OnDeviceScaleFactorChanged()
(cherry picked from commit d16c4344b0c9881b5b00a5234b6b5b0619039b6f)
Bug: 1413539
Change-Id: Ia63a3177bb53019afbff0fa2c1b8b2da57c7246f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265793
Auto-Submit: Xianzhu Wang <[email protected]>
Commit-Queue: Scott Violet <[email protected]>
Reviewed-by: Scott Violet <[email protected]>
Reviewed-by: Robert Flack <[email protected]>
Commit-Queue: Robert Flack <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1107099}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4275561
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#692}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.38
Change-Id: I5482807ef34768f2297f457796983128f54b17a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4277221
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#691}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Prevent potential integer overflow in PersistentMemoryAllocator
BUG=1415328
(cherry picked from commit 19de280a0c28065acf2a7e001af5c981698a461c)
Change-Id: I66dcae6a1aacc1310ddd715033b3704c932b9800
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250177
Reviewed-by: Alexei Svitkine <[email protected]>
Commit-Queue: Will Harris <[email protected]>
Commit-Queue: Alexei Svitkine <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105177}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4275621
Commit-Queue: Joe Mason <[email protected]>
Auto-Submit: Joe Mason <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#690}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Do not register browser_watcher activity report with crashpad
BUG=1415328
(cherry picked from commit f93c88303ccbb64014a575b8ae093aa166832922)
Change-Id: I109f6dac083a69a26841ee5e975e02093ca4cbf6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257669
Reviewed-by: Robert Sesek <[email protected]>
Commit-Queue: Will Harris <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1106253}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4275641
Commit-Queue: Joe Mason <[email protected]>
Commit-Queue: Robert Sesek <[email protected]>
Auto-Submit: Joe Mason <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#689}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[DefaultOffline]: New fonts and remove border radius.
Since this is an offline page, we can't use any fonts
that need to be downloaded (and the way it was specified
didn't work anyway). So, as requested by UX, we switch
to the system default sans serif font, and increase the
text just a bit to make the error message more obvious.
Also, using a border radius doesn't work for all icons,
for example the gCalendar one (which is circular and the
corners would get cut off). So, we'll stick to rectangular
ones.
(cherry picked from commit 1d78df8cb5c6ccd68419194f6e04151dcb6e2c59)
Bug: 1410786, 1280518
Change-Id: I279b61404cf639876ae3842aedb0a32bf8bb4eb0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4198147
Commit-Queue: Finnur Thorarinsson <[email protected]>
Reviewed-by: Chase Phillips <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1098921}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274941
Reviewed-by: Prudhvikumar Bommana <[email protected]>
Commit-Queue: Daniel Murphy <[email protected]>
Reviewed-by: Daniel Murphy <[email protected]>
Auto-Submit: Finnur Thorarinsson <[email protected]>
Owners-Override: Prudhvikumar Bommana <[email protected]>
Commit-Queue: Prudhvikumar Bommana <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#688}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[PCCT] Prevent fling gesture from resizing the fixed-height tab
Flinging up hard can animate the tab to the top height status
i.e. full height. This must be disallowed for fixed-height tab.
(cherry picked from commit 0ec147e7893802314b1d36ea34a14e0c1c62a29f)
Bug: 1416949
Change-Id: I2bdafcf02ef352a391cd4bad341002b617f0cf87
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262168
Reviewed-by: Kevin Grosu <[email protected]>
Code-Coverage: Findit <[email protected]>
Commit-Queue: Jinsuk Kim <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1106463}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273254
Cr-Commit-Position: refs/branch-heads/5563@{#687}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Prevent potential integer overflow in PersistentMemoryAllocator
https://crrev.com/c/4250177 added an extra check for potential
integer overflow in GetAllocSize but forgot to add the same
check in GetBlock.
This meant that it was possible to get a pointer to a block
but calling GetAllocSize on the same block would return zero.
This change makes the two functions consistent with each other
so calling GetBlock on invalid data will return nullptr.
BUG=1417317,1415328
(cherry picked from commit 81be8e8f2e13a9f1fe6d3150205a3c13af1db6e9)
Change-Id: I8eb3d91bae4528fc97517d202baf337536a4c81f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264177
Reviewed-by: Alexei Svitkine <[email protected]>
Commit-Queue: Alexei Svitkine <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1107105}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274620
Commit-Queue: Joe Mason <[email protected]>
Auto-Submit: Joe Mason <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#686}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Reported GDI usage on ERROR_NO_MORE_USER_HANDLES
Chrome sometimes fails to open its main window and this has recently
started happening with a previously not seen error code - 1158 which is
ERROR_NO_MORE_USER_HANDLES. This change handles that case and calls
CollectGDIUsageAndDie() to get more information about what type of
handles are being exhausted.
(cherry picked from commit 8d90d1956e55d883cf5cfa6b59c7f788e58b1871)
Bug: 1414766
Change-Id: I2edc0bba05f618718301ec8a1387b01d9612c448
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257386
Reviewed-by: Avi Drissman <[email protected]>
Auto-Submit: Bruce Dawson <[email protected]>
Commit-Queue: Avi Drissman <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1106274}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273267
Owners-Override: Prudhvikumar Bommana <[email protected]>
Reviewed-by: Prudhvikumar Bommana <[email protected]>
Commit-Queue: Prudhvikumar Bommana <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#685}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[search_engines] Exclude Policy and Play API engines from Sync merging
There's a security bug in which the call to ResetTemplateURLGUID can
cause a policy-created engine to be deleted. This means that after
the call, either the current `conflicting_turl` pointer, or future
iterations in the loop may point to an already-freed TemplateURL,
causing the use-after free bug.
This CL addresses that by forbidding Policy-created and Play API
engines from being merged into Synced engines.
Although Play API engines aren't directly affected, they seem to also
not be something that should be merged to Synced engines.
(cherry picked from commit 315632458eb795ef9d9dce3fd1062f9e6f2c2077)
Bug: 1414224
Change-Id: Ide43d71e9844e04a7ffe2e7ad2a522b6ca1535a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250623
Reviewed-by: Matthew Denton <[email protected]>
Reviewed-by: Mikel Astiz <[email protected]>
Commit-Queue: Tommy Li <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1106249}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274985
Commit-Queue: Krishna Govind <[email protected]>
Reviewed-by: Tommy Li <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#684}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Avoid showing the device chooser dialog in extension popups
An extension popup window does not have a valid extensions toolbar
container and cannot show dialogs that are anchored to the extension
icon. Check that GetExtensionsToolbarContainer returns non-null before
creating the chooser dialog.
(cherry picked from commit a82d0f4deac0f331d8b033516bf226b76835d805)
Bug: 1415183
Change-Id: Ife2e38c879c474bcfd6bf17be14ff07cab092ac3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261791
Commit-Queue: Matt Reynolds <[email protected]>
Reviewed-by: Elias Klim <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1106881}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4275243
Reviewed-by: Krishna Govind <[email protected]>
Owners-Override: Krishna Govind <[email protected]>
Commit-Queue: Prudhvikumar Bommana <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#683}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Atom AFDO profile from 111-5563.14-1676293165-benchmark-111.0.5563.36-r1 to 111-5563.31-1676890340-benchmark-111.0.5563.37-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: Ife35fd36d09f79793e7cade2ab3633112ffd4455
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273756
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#682}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
ios: Validate exception code buffer size before read.
Cherry picked from Crashpad 0adab59836b1085bd9796ebade029092b7ec5207.
Bug: 1415371
Change-Id: I4ce1760a73567e9cca46aa1cedd897c873490fdb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272967
Reviewed-by: Harry Souders <[email protected]>
Commit-Queue: Harry Souders <[email protected]>
Owners-Override: Harry Souders <[email protected]>
Commit-Queue: Justin Cohen <[email protected]>
Auto-Submit: Justin Cohen <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#681}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Skip finalizing permission requests in pending queue
Bug: 1415366
(cherry picked from commit dd597022c93047e88f6ddb812eb04ed392222b33)
Change-Id: I2bd464a202354d9941bed8498bd44b5c5ebea6de
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4271191
Commit-Queue: Thomas Nguyen <[email protected]>
Reviewed-by: Andy Paicu <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1107426}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274632
Owners-Override: Daniel Yip <[email protected]>
Reviewed-by: Daniel Yip <[email protected]>
Commit-Queue: Krishna Govind <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#680}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Fix crash in ChromePasswordManagerClient::ShowPasswordGenerationPopup.
Part of stack from crash report:
base::ImmediateCrash()
logging::CheckFailure()
base::WeakPtr<PasswordGenerationPopupControllerImpl>::operator->()
...
`popup_controller_` was invalidated, presumably through the following
calls:
Show() ->
PasswordGenerationPopupView::Create() failed to create view ->
HideImpl ->
delete this;
(cherry picked from commit 9b5402a88afb6038b605f3d2dbc5be47b688433c)
Bug: 1414043
Change-Id: I7f4933fe45d59f32f41e116936586773b3161050
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255411
Commit-Queue: Dmitry Vykochko <[email protected]>
Reviewed-by: Vasilii Sukhanov <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1106151}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273177
Commit-Queue: Prudhvikumar Bommana <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Owners-Override: Prudhvikumar Bommana <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#679}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[v8][wasm] Ignore incoming bytes after streaming abortion
This is a follow-up to https://crrev.com/c/4249278: If the streaming
decoder has been reset (because of a network abort or abortion by the
user) we should not try to call further methods on it (see new bug:
https://crbug.com/1416820).
R=​[email protected]
Bug: 1399790, 1400066, 1416820
(cherry picked from commit 9c11cc377f0e97bae872a91eade6bac586454615)
Change-Id: I7a562fe548d2bb8eeb29fef4449a077963bb4d49
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272858
Reviewed-by: Kentaro Hara <[email protected]>
Commit-Queue: Clemens Backes <[email protected]>
Auto-Submit: Clemens Backes <[email protected]>
Commit-Queue: Kentaro Hara <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#678}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Fix crash on Android non-DCHECK builds
This CL handles the case we are creating permission subscriptions in
BFCache, and does not allow dereferencing unset
|status_at_bf_cache_entry_|.
It is acceptable to fire extra events in this case.
Bug: 1415837
(cherry picked from commit f9ccec8dadc7d384ad033413e16499053d7ea3c5)
Change-Id: I13a9f83efda6300df4848aebd00e3e0ddcd581fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260046
Reviewed-by: Elias Klim <[email protected]>
Commit-Queue: Thomas Nguyen <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1107445}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4271787
Cr-Commit-Position: refs/branch-heads/5563@{#677}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676949027-79d75e992b5e6b336d59036a485fc5fd3b212f24.profdata to chrome-win32-5563-1676975494-28dc1262bbaeeb7539025d4e955a52f31a4a9198.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I5517a37eaec71a83604fff5d3bd1fe9f4d9b255c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273749
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#676}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[v8][wasm] Avoid repeated streaming abortion
We see crashes that could be triggered e.g. by concurrent abortion of
Wasm streaming by the client and via the network, or concurrent abortion
and finishing the download.
We do not have a reproducer yet, but not calling {Abort} or {Finish}
multiple times might fix the issue and is a good convention anyway.
To make the order of events easier to follow, this also converts a scope
object to a function call to convert the exception to a streaming abort
message.
R=​[email protected]
Bug: 1399790, 1400066, 1406746
(cherry picked from commit c8536dbeba7e17e7ae3c8e2329186567e80b0493)
Change-Id: Ia34c5cc4368fc9c46b5eaf0c336e220c882a89f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274821
Reviewed-by: Kentaro Hara <[email protected]>
Commit-Queue: Kentaro Hara <[email protected]>
Auto-Submit: Clemens Backes <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#675}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-21 UTC
Change-Id: I412ead7eaf6c92e925735ae0cb924237ea198a67
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272318
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#674}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676949027-cc292ff131e9577d53180ead9577e855fb991d0b.profdata to chrome-win64-5563-1676975494-ec34e0d3ec3dc1eea4bf42b20e8ea66b9ebed55a.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: Idfddfd4022e866f58d481ea31dff58f1c45913b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272316
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#673}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-21 UTC
Change-Id: Ia5e6183f01d2ef956871ceba507e741cb6e442ed
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274118
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#672}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676949027-cbd2ca6f78cc1592982ab9d36c6075c25254dca4.profdata to chrome-linux-5563-1676975494-91f2f2fecfc8afcd118798da9eaa0053963fae4f.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: Ic60bb27ff1ffb9596a5ed6701db852697b971703
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274768
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#671}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676949027-b58e1ec76f436cd0d11ef2016669b47e048ea0b9.profdata to chrome-mac-5563-1676975494-d2279a2dc4d3c755294aecd3f3962eb853958b5c.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I68cf04c992b1051e8c3b6cc5bb119e7cab68905b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273992
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#670}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Updating XTBs based on .GRDs from branch 5563
Change-Id: I7347d7cb5bc70945188d6b1052785e02aecb9d6b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273838
Commit-Queue: Rubber Stamper <[email protected]>
Auto-Submit: Ben Mason <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#669}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Amd64 AFDO from 111.0.5563.36_rc-r1-merged to 111.0.5563.37_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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I04e93d0eceb470e568cf42f02356933b242615d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273413
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#668}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676927866-484a4f10d84d8ee05ad0deb38c396b69e20b3b6b.profdata to chrome-mac-5563-1676949027-b58e1ec76f436cd0d11ef2016669b47e048ea0b9.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I07061313be491bb8960c7fda6f604b083a971946
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4274108
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#667}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676927866-29a85400bc72870938020fe87723ac0ef86315a4.profdata to chrome-win32-5563-1676949027-79d75e992b5e6b336d59036a485fc5fd3b212f24.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: Idb13d6cbd566caf0738b885c45afa1cdf5a9b694
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273592
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#666}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676927866-657b59ba040e2c7d44e3cb3ef9a19c75b8981fd7.profdata to chrome-win64-5563-1676949027-cc292ff131e9577d53180ead9577e855fb991d0b.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I5d55e4e822587a674cebef145f06e9adc8ef6c4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273591
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#665}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676927866-e714826dd23e7252827fda216cc45b65fcda7018.profdata to chrome-linux-5563-1676949027-cbd2ca6f78cc1592982ab9d36c6075c25254dca4.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: Ic992993174f73ea5ad910443034891a0a8a13731
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273052
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#664}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Add use count on event handler modification/updates detected by SWGS.
To understand the effect of https://github.com/whatwg/dom/pull/1161,
let me add use counters to count updates of handlers prohibited by this
proposal.
(cherry picked from commit c49519ff6d3b9374e9c52dfdb657a38a69b99751)
Bug: 1347319
Change-Id: Ic6a19a512222dabca8e52416fdab9629ce9a70ad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259225
Commit-Queue: Yoshisato Yanagisawa <[email protected]>
Reviewed-by: Kouhei Ueno <[email protected]>
Reviewed-by: Minoru Chikamune <[email protected]>
Reviewed-by: Shunya Shishido <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1106099}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273346
Auto-Submit: Yoshisato Yanagisawa <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#663}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676914202-07329aed06d6137919596de95cf67e8bb82db1b8.profdata to chrome-win32-5563-1676927866-29a85400bc72870938020fe87723ac0ef86315a4.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: Ibdebe1ba737ca910b488596fa69039d74e872f6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273488
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#662}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676914202-f5f6c120f4446189fd15e687740599e20186a505.profdata to chrome-win64-5563-1676927866-657b59ba040e2c7d44e3cb3ef9a19c75b8981fd7.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I20d687c9da39d58b04e7e090c98f4ce8a10009c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273409
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#661}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676914202-dffe7a5b0fb6487f97fd302ed5d972642c978196.profdata to chrome-mac-5563-1676927866-484a4f10d84d8ee05ad0deb38c396b69e20b3b6b.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I3b4ba0c46a9c0aa5bc50d0f8f7b9af0d50ceb1c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272584
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#660}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676914202-597c504fb8f80b432b8b4e17d06f22684df676cf.profdata to chrome-linux-5563-1676927866-e714826dd23e7252827fda216cc45b65fcda7018.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I6fc9861d807dfdc6d11cbeb977b5bf1babaa1977
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273229
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#659}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.37
Change-Id: Id703244b19d8f8e89bd22d77fca8598f20c70bc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273787
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#658}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676891749-f40153e563911d0375b0ff27f1a625f22ed4041b.profdata to chrome-win32-5563-1676914202-07329aed06d6137919596de95cf67e8bb82db1b8.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I61411a42c0df41524bebfe881809864cd2ddb270
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272927
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#657}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676891749-e3c89beacf9e0a71cc194c30d4b3b48bc885f632.profdata to chrome-win64-5563-1676914202-f5f6c120f4446189fd15e687740599e20186a505.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I33347d4c14885e62edcaaca75b8cfc862f641845
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272728
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#656}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676841040-47805e8f3788b73f38c31c7c3e93515e447eb8b0.profdata to chrome-linux-5563-1676914202-597c504fb8f80b432b8b4e17d06f22684df676cf.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: Ic27023000be60dfd284e5bac55bb3ea8e4f53832
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272990
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#655}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676891749-3b3dadb6a1e276c066a9f8d518f0308572cd8b72.profdata to chrome-mac-5563-1676914202-dffe7a5b0fb6487f97fd302ed5d972642c978196.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I5e2327f4f997f5714067bdb87548489c4459b104
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4273225
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#654}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[Cherry-pick][Overflow menu] Fixed blue dot badge rendering wrong color
A bug was found where the blue dot in the overflow menu would sometimes
appear black (or white in dark mode) when the settings destination is
badged with the dot which should have been blue. The bug was only
present when `use-sf-symbols` flag was disabled, and this fix makes it
work for both scenarios (enabled or disabled). This bug also affects
the already-released feature of badging the reading list destination.
This fix accomplishes the same thing as before: a blue circle.
(cherry picked from commit dad42964514c12cc9c77b658ddb62d14e4c1ab21)
Bug: 1412766
Change-Id: I07b0fb12e3291513f5283e649b92434352dcb4af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262027
Reviewed-by: Gauthier Ambard <[email protected]>
Commit-Queue: Nicolas MacBeth <[email protected]>
Reviewed-by: Louis Romero <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1106784}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272165
Cr-Commit-Position: refs/branch-heads/5563@{#653}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Bigcore AFDO profile from 111-5563.8-1676287958-benchmark-111.0.5563.35-r1 to 111-5563.8-1676287958-benchmark-111.0.5563.36-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: Ica798b638a4fcfc04ae09d35790ff95c9f3e80d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272865
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#652}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Atom AFDO profile from 111-5563.14-1676293165-benchmark-111.0.5563.34-r1 to 111-5563.14-1676293165-benchmark-111.0.5563.36-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: Ifb91cf339d6d2b0137742cc1c84cd2f1d67402cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272725
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#651}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Arm AFDO profile from 111-5550.0-1676292529-benchmark-111.0.5563.35-r1 to 111-5550.0-1676292529-benchmark-111.0.5563.36-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I1a2da85a34f9b1588cb88a9a2cff1d90f6913fdb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4272545
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#650}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676861084-cf06c277b55dfbc3a1b831e26352d5328195e336.profdata to chrome-mac-5563-1676891749-3b3dadb6a1e276c066a9f8d518f0308572cd8b72.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I8d860a6d23dde5977f8f294c4736682bd74f41f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4271357
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#649}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-20 UTC
Change-Id: Ib618f6a090841047eebb4d99fe3f2e136a7d7b34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4270774
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#648}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676861084-12d17890c4f9192652e1ce9fe76deb317be3fa85.profdata to chrome-win32-5563-1676891749-f40153e563911d0375b0ff27f1a625f22ed4041b.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I44eb23520a6a4819c0ea97df2cf9d9a81c364469
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4271356
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#647}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676861084-46edf7e25bd89c6c95ce760de469558973c6e4a5.profdata to chrome-win64-5563-1676891749-e3c89beacf9e0a71cc194c30d4b3b48bc885f632.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I65bf56b39b59af2f307b084d0485c32601635086
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4271358
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#646}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Include the without_jni jar in the cronet_package output
Downstream consumers need that jar, so it needs to be exported as part
of cronet_package.
(cherry picked from commit 099bc0ee064a03c851a2ca93905f65921e258a26)
Bug: b:266917718, 1401015
Change-Id: Ie832951343da01b388de2b89c34d297d3daa7e49
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269598
Auto-Submit: Mohannad Farrag <[email protected]>
Reviewed-by: Stefano Duo <[email protected]>
Commit-Queue: Mohannad Farrag <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#645}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Also bundle repackage_native_impl output
As things stand, both repackage_native and repackage_test_jars
bundle org/chromium/base/natives/GEN_JNI.class. This causes issues
downstream, where the one bundled in repackage_native is currently
winning (for not well defined reasons). Winning in this context means
that Java -> C++ JNI calls will be resolved looked up inside
GEN_JNI.class. This is a problem because repackage_native's GEN_JNI
doesn't contain JNI defined by tests, so tests fails with
java.lang.NoSuchMethodError: No static method
org_chromium_net_NativeTestServer_startNativeTestServer
This CL circumvent the issue by also bundling the output of
repackage_native_impl. Its output is in fact exactly the same of
repackage_native, modulo the stripping of GEN_JNI.class. This way
the one bundled in repackage_test_jars will always win.
Rename repackage_native_impl to repackage_native_without_jni
to better reflect its contents.
(cherry picked from commit 33dcf69fcc63050f70fe88db3ff90b2644ddd5a8)
Bug: b:266917718, 1401015
Change-Id: I31117dcc86a60c88fec5525ef0fca0ab532e1db7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269597
Auto-Submit: Mohannad Farrag <[email protected]>
Reviewed-by: Stefano Duo <[email protected]>
Commit-Queue: Stefano Duo <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#644}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Updating XTBs based on .GRDs from branch 5563
Change-Id: Ie237f29b250194696a86e862b7e20e6d0d5db11d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269434
Commit-Queue: Rubber Stamper <[email protected]>
Auto-Submit: Ben Mason <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#643}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Generate JNI registration for cronet_tests_java.jar
Otherwise the resulting jar doesn't work as it is missing the GEN_JNI class.
(cherry picked from commit 64c4d8615b0088a195492da2f62f830111ad755f)
Bug: b:266917718, 1401015
Change-Id: Id30f6c5d4891cbf3c35381c5b07e1c9e028ca0cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269596
Auto-Submit: Mohannad Farrag <[email protected]>
Commit-Queue: Stefano Duo <[email protected]>
Reviewed-by: Stefano Duo <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#642}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676801392-7c591c2db8e4bd40eb21a1431d070a396b1a93d8.profdata to chrome-win32-5563-1676861084-12d17890c4f9192652e1ce9fe76deb317be3fa85.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I07f5549e27db5f0c00d24ec85ab797f0a7597e04
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4270536
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#641}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[Merge 111] Privacy Sandbox: Enable custom lifecycle for bottom sheet
To prevent the Privacy Sandbox notice being dismissed by the start
screen, hasCustomLifecycle is overridden to true for the
BottomSheetContent.
The bottom sheet notice will begin to be superseded in M111, and be
completely deprecated in M115, by a full screen notice which does not have the same concern. Thus, no further tracking bug is required.
(cherry picked from commit 30dcfaa121575723d827836c2377d47e5697aea3)
Bug: 1415300
Change-Id: I81dd2adb4a5897745a594c74e574aff14aca6226
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4248177
Reviewed-by: Theresa Sullivan <[email protected]>
Commit-Queue: Theodore Olsauskas-Warren <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105314}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268690
Reviewed-by: Olesia Marukhno <[email protected]>
Auto-Submit: Theodore Olsauskas-Warren <[email protected]>
Commit-Queue: Olesia Marukhno <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#640}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Amd64 AFDO from 111.0.5563.35_rc-r1-merged to 111.0.5563.36_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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I4d48c72717327aece7678de21b29f6fee9e6e5b4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269701
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#639}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676841040-e0740675e05b61af6230e1d09265cea70f494604.profdata to chrome-win64-5563-1676861084-46edf7e25bd89c6c95ce760de469558973c6e4a5.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I5033d30509888d2e05dd24d0017c86389d2680d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269060
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#638}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676841040-0732454cba983b18771f5782c0899037027a788e.profdata to chrome-mac-5563-1676861084-cf06c277b55dfbc3a1b831e26352d5328195e336.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I3da7734e723ab6dfdd56c2b19c5614d60add9952
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4270458
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#637}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676828485-2f2ecb0081543dc47eb090aa325fad87d676932d.profdata to chrome-win64-5563-1676841040-e0740675e05b61af6230e1d09265cea70f494604.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I03ed33abe4d7773b3d795fe7a50d23ad6978018c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269655
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#636}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676801392-33f79fb850c44d599ac96166814ec021ef4de857.profdata to chrome-linux-5563-1676841040-47805e8f3788b73f38c31c7c3e93515e447eb8b0.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I2b2a810db00d413605521ab138a349adf44cffa5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269657
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#635}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676828485-719f7b37a092ccf5e6da9131aa1339062be2e77c.profdata to chrome-mac-5563-1676841040-0732454cba983b18771f5782c0899037027a788e.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: If95e9d376925fd85ad181e7fd614c9b0e5374ae9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269654
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#634}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.36
Change-Id: I6716a4a1c1468414f01d3d03e33e6ff66e3a468e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4270070
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#633}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676801392-6e132b4ab1e88056d444d19d634a84b76087ff74.profdata to chrome-win64-5563-1676828485-2f2ecb0081543dc47eb090aa325fad87d676932d.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: Ie3eece6e5ae38cf6cf90e9054f8f84de0a0de8ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268978
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#632}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676801392-71d489cec98628aca9dc12a6afdfbc7e7c9aa493.profdata to chrome-mac-5563-1676828485-719f7b37a092ccf5e6da9131aa1339062be2e77c.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: Ia6db2b61fefa2185cb5e6cb1b387886ab8ef628d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269331
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#631}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Revert "Integrate ConnectAndConfigureSocket to QuicStreamFactory::Job."
This reverts commit 1a1f3b359d546e4af58e3b2cb24899d1c87c1138.
Reason for revert: b/267653996
Original change's description:
> Integrate ConnectAndConfigureSocket to QuicStreamFactory::Job.
>
> This change makes QUIC session creation within a QuicStreamFactory::Job always asynchronous. It also
> modifies the HTTP stream factory job to use WaitForQuicSessionCreation() so that the main job remains
> blocked until a QUIC session is created.
>
> There are now a few unit tests removed in quic_stream_factory_test and
> http_stream_factory_job_controller_unittest. These tests are no longer
> relevant as they tested iterations of QUIC session creation + connection
> returning sync.
>
> There are also three unit tests added (ResultAfterQuicSessionCreationCallback*) to test the WaitForQuicSessionCreation() and OnQuicSessionCreationComplete() calls.
>
> Bug: 1295460
> Change-Id: I3394375b30cfed7d954bd14bdb45e97aa3c17909
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4008686
> Reviewed-by: Renjie Tang <[email protected]>
> Reviewed-by: Ryan Hamilton <[email protected]>
> Commit-Queue: Liza Burakova <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1092132}
(cherry picked from commit e73158976ab118f71c67c2d76ed5956a110f633d)
Bug: 1295460, 1414417, 1409382, b/267653996
Change-Id: I0515c91a8ccf2b7980e46ec82e0a54f33b7fdc16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4232197
Reviewed-by: Liza Burakova <[email protected]>
Reviewed-by: Ryan Hamilton <[email protected]>
Commit-Queue: Stefano Duo <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104083}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259730
Cr-Commit-Position: refs/branch-heads/5563@{#630}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Bigcore AFDO profile from 111-5563.8-1676287958-benchmark-111.0.5563.34-r1 to 111-5563.8-1676287958-benchmark-111.0.5563.35-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I2e697a5242872ce9d054243fd92041aa6ed86d79
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269053
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#629}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Arm AFDO profile from 111-5550.0-1676292529-benchmark-111.0.5563.34-r1 to 111-5550.0-1676292529-benchmark-111.0.5563.35-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: Idf0493c40d19c4e503f909dd40cd5ff8d44124da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4269054
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#628}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-19 UTC
Change-Id: I02f85481f2112dd9f61144a700654c7c135eb709
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267795
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#627}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676755522-0ab19dd705fdd805be32c9a8a27812bfc9438da7.profdata to chrome-win32-5563-1676801392-7c591c2db8e4bd40eb21a1431d070a396b1a93d8.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I889adebde33c26f6a88ec92d69ed1621b498d8c7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268851
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#626}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676775664-c8bb9ebca43db6978be608642de4f61199cfe27e.profdata to chrome-win64-5563-1676801392-6e132b4ab1e88056d444d19d634a84b76087ff74.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I755905d490d809ee475e67339c625fe22a8ac29a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267580
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#625}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676775664-70a2e6b525083c8a898b356d7270503af26fb8a6.profdata to chrome-linux-5563-1676801392-33f79fb850c44d599ac96166814ec021ef4de857.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: Ied6ec4839465796b5f6a8f92147ed5f5dff15c56
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268871
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#624}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676775664-fc7d849f39cd1b3a64de8e0fc1953a4ff86c0a2c.profdata to chrome-mac-5563-1676801392-71d489cec98628aca9dc12a6afdfbc7e7c9aa493.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I48bb928cae0c7d9fd4157f23b4c26ac0deb75bdf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267581
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#623}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Amd64 AFDO from 111.0.5563.34_rc-r1-merged to 111.0.5563.35_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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: If1ce20733313a204d5c60755c10e6ef3b5574a2b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268119
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#622}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676755522-2273633e996645611667c36be3dd8b5c42b31886.profdata to chrome-win64-5563-1676775664-c8bb9ebca43db6978be608642de4f61199cfe27e.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I27ee932638b0c12961c716c70d9eee81d60bb2ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268531
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#621}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676755522-ab594c6d332051bbc7891209f5b9b63b5b415648.profdata to chrome-linux-5563-1676775664-70a2e6b525083c8a898b356d7270503af26fb8a6.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I83a9960a68b2caeaf78b64f860623df4c081b7c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268452
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#620}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676755522-59ba15347152a765d85a81149c8b46dfc0baaea8.profdata to chrome-mac-5563-1676775664-fc7d849f39cd1b3a64de8e0fc1953a4ff86c0a2c.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: Ic38692e18c626170172128cbe626d3b445cdfaea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268610
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#619}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676742447-4e3db00554b0117233bd16dabad909f7f36d161d.profdata to chrome-win32-5563-1676755522-0ab19dd705fdd805be32c9a8a27812bfc9438da7.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: If6b0e747d90304de0354193ee1eaced3a3386e3c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267815
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#618}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676742447-4637aabbff14d344966f0194afff51bcf8e6eb51.profdata to chrome-win64-5563-1676755522-2273633e996645611667c36be3dd8b5c42b31886.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: Id8fae0c4625a25eac239f11e51286eb3ef555e5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267814
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#617}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676742447-aab9a63d4780d556ffcb9c6a15a1799de5ab0c4b.profdata to chrome-linux-5563-1676755522-ab594c6d332051bbc7891209f5b9b63b5b415648.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I41f5401a10ff3e50c5ba71633ddd7765dbdd5adf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267792
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#616}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676742447-875e34809e69e267d98cd3f91a8b4819413f7c67.profdata to chrome-mac-5563-1676755522-59ba15347152a765d85a81149c8b46dfc0baaea8.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I778b056c373516ffa5f3e8b40579b245717832d0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268110
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#615}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.35
Change-Id: If496522d0d3273c7a13dfa1a98d9541191f2e723
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4268191
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#614}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676718133-3f19cc07093de59f5934e683103b368f42c088ae.profdata to chrome-win32-5563-1676742447-4e3db00554b0117233bd16dabad909f7f36d161d.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I23edb6eb2a8c528f0e09e2d474cc91f1f42b737d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267496
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#613}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676718133-cbed613ac67ca0c2e271423bf86dadcb0453eed5.profdata to chrome-win64-5563-1676742447-4637aabbff14d344966f0194afff51bcf8e6eb51.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: Ifb10b2835024387440781d9630c2857f95ebd82b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267495
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#612}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676718133-8512488a0c620142319e84239561aa239a05358f.profdata to chrome-linux-5563-1676742447-aab9a63d4780d556ffcb9c6a15a1799de5ab0c4b.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: Ia2337c6ec88292644d243a68e28af6d220e66ce7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267574
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#611}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676718133-c37b0a20d6f516dcac6b7c7915d337d44b753045.profdata to chrome-mac-5563-1676742447-875e34809e69e267d98cd3f91a8b4819413f7c67.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I2e7b07d106877fba82b7b55ce04c7b7833d435a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267571
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#610}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Bigcore AFDO profile from 111-5563.8-1676287958-benchmark-111.0.5563.33-r1 to 111-5563.8-1676287958-benchmark-111.0.5563.34-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I35d659829e8d9e8c8ba13e66d837498c343bc59c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267570
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#609}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-18 UTC
Change-Id: I65c4ad4c29cf8d0a8fe687c4d95f181649ef7869
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265715
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#608}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Atom AFDO profile from 111-5563.14-1676293165-benchmark-111.0.5563.33-r1 to 111-5563.14-1676293165-benchmark-111.0.5563.34-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: Ib1973a1e1ab27d89ed65f39f285525830b52ac96
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267530
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#607}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Arm AFDO profile from 111-5550.0-1676292529-benchmark-111.0.5563.33-r1 to 111-5550.0-1676292529-benchmark-111.0.5563.34-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I55bda7c1a7b3278c22ce1265e99cd1f5b5537f01
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267451
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#606}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676694542-cb4a260c0a687f823007a525b73ab4c8313848bf.profdata to chrome-linux-5563-1676718133-8512488a0c620142319e84239561aa239a05358f.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I973a69a8c93ac7b0a9bdca94036762a65f27fa7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267276
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#605}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676694542-2482edef6256144faecde5a5b9db0d7415b1ee78.profdata to chrome-win64-5563-1676718133-cbed613ac67ca0c2e271423bf86dadcb0453eed5.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I4e7fd4416b32199c28a874793894c0ee9d91b0b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267274
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#604}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676694542-22878bd2602458dcbd7a5bb795410fc718b80ed0.profdata to chrome-win32-5563-1676718133-3f19cc07093de59f5934e683103b368f42c088ae.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I0ffc82733c0b1c4ba3dba645e128844ce4801c0e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267151
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#603}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676694542-f0caf009b68e603f1afa0911123d11d6c9d7da22.profdata to chrome-mac-5563-1676718133-c37b0a20d6f516dcac6b7c7915d337d44b753045.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: Ie96f455aea6adc75bab38b26aafac28c80bfb39b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4267273
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#602}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[M111] Reland "Reinforce FRE using FWMP.dev_disable_boot"
This is a reland of commit 0a09ab86bd0e95fd8c263a48aec4c1f1b0b87b9b
Previous test issues are fixed by https://crrev.com/c/4253889
Original change's description:
> Reinforce FRE using FWMP.dev_disable_boot
>
> Use FWMP.dev_disable_boot as an additional signal to do FRE checks.
> See go/fre-on-dev_disable_boot for details.
>
> - Adjusted unit tests for FWMP reading
> - Manual tests with and without FWMP.dev_disable_boot set
>
> Bug: b/268267865
> Change-Id: Icbb69f4c915bc6973675fa15309822adeeafcaed
> Tests:
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4241802
> Reviewed-by: Pavol Marko <[email protected]>
> Reviewed-by: Martin Bidlingmaier <[email protected]>
> Commit-Queue: Roland Bock <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1105032}
(cherry picked from commit 68ad8b478c7c21111ced27a8fbd84b3d777a8183)
Bug: b/268267865
Change-Id: I5d7b38dfbbc25e7b893a9799b9cae748180a7581
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255465
Reviewed-by: Martin Bidlingmaier <[email protected]>
Reviewed-by: Pavol Marko <[email protected]>
Commit-Queue: Roland Bock <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105746}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259965
Cr-Commit-Position: refs/branch-heads/5563@{#601}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Amd64 AFDO from 111.0.5563.33_rc-r1-merged to 111.0.5563.34_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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I5d5485eb1c65347a7814b92c2dbaba8a70ee7dea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265925
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#600}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[M111] Skip auto enrollment check screen in tests
Auto enrollment check screen is shown in OOBE depending on how fast auto
enrollmen controller finishes. To avoid flaky tests, disable auto
enrollment check screen in wizard controller by default.
Also make the auto enrollment check screen mock a nice mock, because
if not expected, showing or not showing the screen is fine.
Tests that expect the screen to be shown are still flaky.
(cherry picked from commit dd24f16eb0f002d7fe9e5c693ceef1cc1e06ce1b)
Test: browser_tests *WizardController*
Bug: 1416261,b/268267865
Change-Id: I2087b964835c321e0f0a1b78252dc0643a7e258e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4253889
Commit-Queue: Miriam Polzer <[email protected]>
Reviewed-by: Renato Silva <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105610}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260306
Commit-Queue: Roland Bock <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#599}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676672694-d99eb9084274ee0e471fbbe5c6aeee32f35e7501.profdata to chrome-win32-5563-1676694542-22878bd2602458dcbd7a5bb795410fc718b80ed0.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I5a92466b55d1e037ee5ea501e91c8cc0c9bde0a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4266774
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#598}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676672694-0686573b17b26e80c4c564f65ac428048075c610.profdata to chrome-win64-5563-1676694542-2482edef6256144faecde5a5b9db0d7415b1ee78.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I45a3933a1dbbd4ed2f2dedb429044c5f3f4e0e71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265745
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#597}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676672694-ba92f0cce651dc0243b3e0e8ec5673ea204d482b.profdata to chrome-mac-5563-1676694542-f0caf009b68e603f1afa0911123d11d6c9d7da22.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: Ia9af3c77aa81119e8376e985fe658c5278476ff1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4266833
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#596}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676650263-4a5cf6b71be21b3d77785f696f50b6d537b6970d.profdata to chrome-linux-5563-1676694542-cb4a260c0a687f823007a525b73ab4c8313848bf.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: Ic905b7dc6d6b6397e9480e78eb3dc4ee4e0e679e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264496
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#595}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[merge-m111][CrOS] Update eche_app to Y9Vb3-WAI0IRjTRTVDtPP86MNNpZItvfey3JuYZXXeYC
Cherry-pick of change to fix timeout.
CIPD package: https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/eche_app/app/+/Y9Vb3-WAI0IRjTRTVDtPP86MNNpZItvfey3JuYZXXeYC
Release Notes: http://go/eche_app-x20/relnotes/Branch/eche_app_20230123_RC03.html
Bug: b:268246425
Change-Id: I105f48965ade693a87b82b70b44b3ef825a8f727
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4266530
Reviewed-by: Michael Hansen <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#594}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676650263-7edbe609d52b30f71a82041a2f45bba36eae69f3.profdata to chrome-win32-5563-1676672694-d99eb9084274ee0e471fbbe5c6aeee32f35e7501.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I53d4e78904329ce115509e9c91e6971b4f4f0c8d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4266133
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#593}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676650263-002b89f1f4f82b779e65e587ef37bee2c75a6180.profdata to chrome-win64-5563-1676672694-0686573b17b26e80c4c564f65ac428048075c610.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: Ib0eb15504ba60fc76ac9bec3b27ddf815452c979
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264681
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#592}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676650263-66f780a26f772674b567cef0c9967aa6679358e4.profdata to chrome-mac-5563-1676672694-ba92f0cce651dc0243b3e0e8ec5673ea204d482b.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I9bb180fcb078c17df44a5f4d06d29775c55327db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265919
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#591}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[skylab_tests] Update skylab tests cros img version
This cl only affect Lacros on-device config builders like
lacros-amd64-generic-chrome-skylab. This cl will certainly NOT affect
linux-lacros builders(linux-lacros-tester-rel, linux-lacros-rel, etc)
or any other platforms.
This CL will update cros image version for skylab tests. CROS_BOARD_LKGM
is updated according to chromeos/CHROMEOS_LKGM; CROS_BOARD_DEV,
CROS_BOARD_BETA and CROS_BOARD_STABLE are updated according to Omaha.
If this CL caused regressions, please revert and pause the autoroller at
https://luci-scheduler.appspot.com/jobs/chrome/lacros-skylab-tests-cros-img-roller
Also please file a bug to OS>LaCrOS>Partner, and CC [email protected],
[email protected].
[email protected]
Requires-Testing: True
Change-Id: I254598abcfd35cb04ae16ab5d1c2c81bc6e4d54f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4266510
Auto-Submit: skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com <skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#590}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.34
Change-Id: I283b230b7e4d31b1bddd4afe77af3cf991a609ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4266431
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#589}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Direct third_party/icu to the chromium/m111 branch
The ICU chromium/m111 branch currently contains the following change
relative to the formerly fixed revision:
e64e8afd9a40 Break at '@', restoring pre-ICU 72 behavior (Chrome
111.0.5563)
Bug: 1410331
Change-Id: I38535b0b2a68a3a20039d3cfc0b97c394fe15322
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262576
Reviewed-by: Krishna Govind <[email protected]>
Owners-Override: Krishna Govind <[email protected]>
Commit-Queue: Krishna Govind <[email protected]>
Reviewed-by: Frank Tang <[email protected]>
Commit-Queue: Mark Mentovai <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#588}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676632589-467c8f34e00a5c401dd42772e68b7a8040ec23d0.profdata to chrome-win64-5563-1676650263-002b89f1f4f82b779e65e587ef37bee2c75a6180.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: Ie06a0a8b4657c0b6f05d6b32c7a82bb5d5171f50
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264818
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#587}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676632589-de2c28e8c0b671d62a602c2d4860a51c90f64831.profdata to chrome-win32-5563-1676650263-7edbe609d52b30f71a82041a2f45bba36eae69f3.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: Ie07532d4bf2357f2738723485be145ca95c8486b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264694
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#586}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Update RLZ brand codes map for M111+
R=​[email protected]
(cherry picked from commit ac59fd6cd36d28987e85be7ec991bafb7577e734)
Bug: 1416292
Change-Id: I39c968e09c7137bc9d5560335f9881fa0537eb29
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255273
Commit-Queue: Stephen Lin <[email protected]>
Reviewed-by: Peter Kasting <[email protected]>
Commit-Queue: Peter Kasting <[email protected]>
Auto-Submit: Stephen Lin <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105729}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260517
Cr-Commit-Position: refs/branch-heads/5563@{#585}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[sync] Fix metric Sync.TrustedVaultJavascriptAddRecoveryMethodSucceeded
The previous implementation always returned failures. This is because,
in Java, Void is not instantiable and the success case always accepted
null. This made the success case indistinguishable from the failures
case, once forwarded to the Consumer.
Instead, the success case needs to be distinguished from the failure
case when dealing with the Promise, and propagate a boolean to the
Consumer.
(cherry picked from commit 7d53449b7478740abfc8a248c42e07b7ee58268a)
Bug: 1403195, 1411694
Change-Id: I81aaf4685b493a6c65997713192f335e5fa7c9dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250858
Reviewed-by: Boris Sazonov <[email protected]>
Commit-Queue: Mikel Astiz <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105657}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265550
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#584}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676632589-c339ad7493cdf06470baac720ee8a873e6bee740.profdata to chrome-linux-5563-1676650263-4a5cf6b71be21b3d77785f696f50b6d537b6970d.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: Ief0284fddcd3520a3d571151681a075d038f73eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264919
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#583}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Fix crash in gpu::SkiaGLImageRepresentation::Create
(cherry picked from commit 44c987cddee2a136302c5a991eee7a43cc6922c8)
Bug: 1415073
Change-Id: Ia3f95bafa4258c7bfd3b1cf4bc691399b2c83114
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4245742
Reviewed-by: Vasiliy Telezhnikov <[email protected]>
Commit-Queue: Peng Huang <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104621}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262038
Commit-Queue: Vasiliy Telezhnikov <[email protected]>
Auto-Submit: Peng Huang <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#582}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676632589-9f6d5a422a0b7e5e0fdbbb8507c6ddc9ed69b405.profdata to chrome-mac-5563-1676650263-66f780a26f772674b567cef0c9967aa6679358e4.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I9757ba229ad10b5525e47e8066420518ff0503cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263975
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#581}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Bigcore AFDO profile from 111-5563.8-1676287958-benchmark-111.0.5563.31-r1 to 111-5563.8-1676287958-benchmark-111.0.5563.33-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I98d3bd9e6da1df8834b4d07572ef1c774e33fd0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264678
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#580}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Atom AFDO profile from 111-5563.14-1676293165-benchmark-111.0.5563.31-r1 to 111-5563.14-1676293165-benchmark-111.0.5563.33-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I9c66859cfc63d3a957c621e1044bdf408e38e0b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264824
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#579}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[CrOS WiFi] Fix crash from GetAvailableManagedWifiNetwork()
Fix crash occurring when GetAvailableManagedWifiNetwork() is called when
there is no Wi-Fi device. This crash is due to not checking if the
device exists before attempting to access a property on it.
(cherry picked from commit 3791e205ef99fdea70b28db5cbaa246d7dcccb1b)
Bug: b:269169473
Test: DUT and *NetworkStateHandlerTest*
Change-Id: I0d7029a066f37890883f8a5f14594d00658a47f2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250139
Reviewed-by: Azeem Arshad <[email protected]>
Commit-Queue: Gordon Seto <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105208}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265011
Auto-Submit: Gordon Seto <[email protected]>
Reviewed-by: Kyle Horimoto <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#578}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[Crash fix] Add null check on tab before triggering desktop site
per-site settings IPHs
(cherry picked from commit fa57ee4bcaba3828a1b08dc26a3a9fa0daa6b099)
Bug: 1416519
Change-Id: Id672c45ac83ead2ec9d5002b76a0a7946c7e3d02
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255713
Reviewed-by: Sirisha Kavuluru <[email protected]>
Commit-Queue: Aishwarya Rajesh <[email protected]>
Code-Coverage: Findit <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105934}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4265130
Reviewed-by: Krishna Govind <[email protected]>
Owners-Override: Krishna Govind <[email protected]>
Commit-Queue: Krishna Govind <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#577}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Arm AFDO profile from 111-5550.0-1676292529-benchmark-111.0.5563.31-r1 to 111-5550.0-1676292529-benchmark-111.0.5563.33-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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I3b76012f4b97f5b5becb440f0fffe1dd0b465916
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264758
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#576}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Fix status bar color on start surface return
(cherry picked from commit 936579e12d7fd34d1cff8fd1f82f7be3629894c9)
Bug: 1410745
Change-Id: Ia55e8b5cc7b6e896ffb35778a6c90e1af1a96cac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4252537
Reviewed-by: Theresa Sullivan <[email protected]>
Code-Coverage: Findit <[email protected]>
Commit-Queue: Sinan Sahin <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105439}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263114
Auto-Submit: Sinan Sahin <[email protected]>
Commit-Queue: Matthew Jones <[email protected]>
Reviewed-by: Matthew Jones <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#575}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-17 UTC
Change-Id: I5745f6ffaeb0b2ecc3d58e47a936b57401aadfad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264470
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#574}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676591665-670e743dea6ce876c9408abe7cbe24868052bba6.profdata to chrome-linux-5563-1676632589-c339ad7493cdf06470baac720ee8a873e6bee740.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I52cba879f43749e0f5bbf475fa193d6fbaf58ea3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263266
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#573}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676591665-614ef01d573ea874de1540c79b9b887f08248d89.profdata to chrome-win32-5563-1676632589-de2c28e8c0b671d62a602c2d4860a51c90f64831.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I82150eac8a9c102fccfedd001bad53509d2b6daa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263497
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#572}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-17 UTC
Change-Id: I097434b9f09e03103e1486c503ccc9bbe60c1fd6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4264430
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#571}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676591665-5814e38cad4607c13ae7b0d82c18a5073c7eeeef.profdata to chrome-mac-5563-1676632589-9f6d5a422a0b7e5e0fdbbb8507c6ddc9ed69b405.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I3b1424e38d3fe6e315cf3017182bd4fe15f435a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263263
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#570}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676611902-59b2748d5c24a3a148ab3612beedfadfd0ae7065.profdata to chrome-win64-5563-1676632589-467c8f34e00a5c401dd42772e68b7a8040ec23d0.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I951396a57d45c08f6bed507ff074cf1da4a86918
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263551
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#569}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Updating XTBs based on .GRDs from branch 5563
Change-Id: I5aa101f81eb97f7b87c761316435f9340b235c82
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261532
Commit-Queue: Rubber Stamper <[email protected]>
Auto-Submit: Ben Mason <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#568}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676569721-c71cf62b9ffec71ebd8d856c1b60e7f784af1f15.profdata to chrome-win64-5563-1676611902-59b2748d5c24a3a148ab3612beedfadfd0ae7065.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I57cfdde116eca1b664bf4177c040a29329c9a9f7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263296
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#567}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Amd64 AFDO from 111.0.5563.31_rc-r1-merged to 111.0.5563.33_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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I6b33bbfff6008bd9feae77871f5122818fb919ab
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263859
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#566}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Fix request chip is not persistent while embedded iframe navigation
This CL fixes a bug when the currently active permission request chip will become invisible if an embedded iframe performed navigation.
An invisible chip leads to ignored permission requests.
(cherry picked from commit 3c074b2bd062d8382bf7126fbcc876c3eeca648e)
Bug: 1413648
Change-Id: Iada5a6a681dc2a4ca60eec49fa6dba0f98e1fa80
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4251159
Commit-Queue: Illia Klimov <[email protected]>
Reviewed-by: Balazs Engedy <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105623}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262391
Commit-Queue: Elias Klim <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#565}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[bfcache] NotRestoredReasons return null for non-history/successful bfcache navigation
This CL makes NotRestoredReasons to return null for non-history/ successful bfcache navigation. They used to return undefined and it was impossible to tell from the case where the API is disabled.
Bug:1413663
(cherry picked from commit ee4cb6666189ed5a698f50dbf338d91194eb9944)
Change-Id: Id4e53954909bda3ae2d6a4cb6ae8178b0bd83ea7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4224862
Auto-Submit: Yuzu Saijo <[email protected]>
Commit-Queue: Kentaro Hara <[email protected]>
Reviewed-by: Kentaro Hara <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1102155}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263449
Commit-Queue: Yuzu Saijo <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#564}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
exo: UILockController: Deregister WindowState observer earlier.
ExitNotifier and WindowState are both owned window properties, so
are destroyed when their Window is.
The order of window property destruction isn't guaranteed, so
sometimes the WindowState is destroyed prior to the ExitNotifier,
which causes the ExitNotifier to call RemoveObserver() on the
destroyed WindowState. Fix this by removing the observer prior
to owned window properties being destroyed.
BUG=1402533
TEST=Smoke test Borealis window opening and closing. Note I was unable to reproduce the original crash, so this fix is somewhat speculative.
(cherry picked from commit dbc2f3dd657fa45935d7a2e318f9dce80d5ee6d8)
Change-Id: I3dfc9197270860db0a5ad8b7de03a2570a08c0b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4248463
Commit-Queue: Mitsuru Oshima <[email protected]>
Auto-Submit: Chloe Pelling <[email protected]>
Reviewed-by: Mitsuru Oshima <[email protected]>
Commit-Queue: Chloe Pelling <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105389}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263687
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#563}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676547318-7fb2a2eccbbaaa6defddee223f916c24e7e6dca0.profdata to chrome-win32-5563-1676591665-614ef01d573ea874de1540c79b9b887f08248d89.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I1de5fd798681d23aabdd500029731bbc5bb38662
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260161
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#562}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676569721-78626f27e1247bf566e429757fb35e0c4bdc5655.profdata to chrome-linux-5563-1676591665-670e743dea6ce876c9408abe7cbe24868052bba6.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I52b21316bc4116f19e5c1927cee14e9e8fe1e156
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4263096
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#561}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676547318-f5b13ad3812c6831cc4ee35b18b32e4b43dc018e.profdata to chrome-mac-5563-1676591665-5814e38cad4607c13ae7b0d82c18a5073c7eeeef.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: Iae757ffe7340347a337226a14de4e4902b06c0ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262753
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#560}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[skylab_tests] Update skylab tests cros img version
This cl only affect Lacros on-device config builders like
lacros-amd64-generic-chrome-skylab. This cl will certainly NOT affect
linux-lacros builders(linux-lacros-tester-rel, linux-lacros-rel, etc)
or any other platforms.
This CL will update cros image version for skylab tests. CROS_BOARD_LKGM
is updated according to chromeos/CHROMEOS_LKGM; CROS_BOARD_DEV,
CROS_BOARD_BETA and CROS_BOARD_STABLE are updated according to Omaha.
If this CL caused regressions, please revert and pause the autoroller at
https://luci-scheduler.appspot.com/jobs/chrome/lacros-skylab-tests-cros-img-roller
Also please file a bug to OS>LaCrOS>Partner, and CC [email protected],
[email protected].
[email protected]
Requires-Testing: True
Change-Id: I433eb805abf8e02c5cd7dc138007211342c916cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261137
Auto-Submit: skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com <skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#559}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Remove RenderFrameHostObserver
Introducing a new observer interface along with WebContentObserver
should have a design doc and discussion, with a clear statement of the
problems that could be resolved. It would be more reasonable to remove
the RenderFrameHostObserver at this time being.
Bug: 1409410
(cherry picked from commit 1c30015f47dc693054c391c6fd4de0f52272bd46)
Change-Id: I50f8907363c1b37e60d724eb40fe94bb27163ac2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4187600
Commit-Queue: Thomas Nguyen <[email protected]>
Reviewed-by: Alexander Timin <[email protected]>
Reviewed-by: Charlie Reis <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1100329}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4251399
Commit-Queue: Alexander Timin <[email protected]>
Auto-Submit: Thomas Nguyen <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#558}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.33
Change-Id: I8872b4bf5100631881672387d2f529f47c55b78c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262796
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#557}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[M111][ios/password grouping] Fix crash when deleting blocklist
Behavior changes are only for kPasswordsGrouping enabled. The crash
only affects tablets. Details in the linked bug.
(cherry picked from commit ce2d6ee1c747195fdf4344230cf8919d9a1ee8ab)
Fixed: 1416403
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4251878
Reviewed-by: Tommy Martino <[email protected]>
Auto-Submit: Victor Vianna <[email protected]>
Commit-Queue: Victor Vianna <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105979}
Change-Id: I3a666e4eef1fb161b35f7ed3b568dcf62ee1d1f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4258327
Commit-Queue: Tommy Martino <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#556}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[M111][ios] Fix code referring to various array copies rather than one
See details in the linked bug. Also use the occasion to replace
std::find_if() with base::ranges::find_if() and improve readability
of the comparator predicate.
(cherry picked from commit 0a8a0f1d15fd99b9c8b734c9d56fddb87058aaf6)
Fixed: 1416259
Change-Id: Ifdde0db97d381d2652a9d84e4cb31dadf3c8b87a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4251758
Reviewed-by: Tommy Martino <[email protected]>
Auto-Submit: Victor Vianna <[email protected]>
Commit-Queue: Victor Vianna <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105701}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4258845
Commit-Queue: Tommy Martino <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#555}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
SystemTrustStore: if trusted in system and CRS, prefer CRS trust record
If it's trusted as an anchor in both, it doesn't much matter. If it's
trusted as a leaf in the system store, then preferring the CRS trust
means it can still be used as an anchor. Presumably there is no
situation in which a certificate in the CRS would ever actually be
usable as a leaf cert, so ignoring the system leaf trust record doesn't
matter.
Distrust records still have precedence regardless of which store they
come from, so this change doesn't affect the ability of distrusting CRS
roots.
(cherry picked from commit 5d0d3ddf759472ddfca94fecdc2203b99202518b)
Bug: 1415524
Change-Id: I8def4b51ce10f847c45388c35e0af7f4b6faf283
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4247499
Auto-Submit: Matt Mueller <[email protected]>
Reviewed-by: Bob Beck <[email protected]>
Commit-Queue: Bob Beck <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105105}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261233
Commit-Queue: Rubber Stamper <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#554}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Disable two flaky tests on all platforms
The flakiness appears to be widespread, so I'm just disabling these
tests on all platforms, and merging the bugs into one main bug.
Merge: Flaky on M111 as well
(cherry picked from commit 2ecc7fd9965fbb9e559a32a3398d4db0139cc0cc)
Bug: 1222653
Change-Id: I7aa60116c5304c3d9b8917b0a3f889e64bf4a239
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4199582
Commit-Queue: Xiaocheng Hu <[email protected]>
Reviewed-by: Xiaocheng Hu <[email protected]>
Commit-Queue: Mason Freed <[email protected]>
Auto-Submit: Mason Freed <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1098112}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261914
Owners-Override: Robert Liao <[email protected]>
Auto-Submit: Robert Liao <[email protected]>
Reviewed-by: Mason Freed <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#553}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[iOS] Stop feed top section coordinator and make fieldtrial compact
Stops the feed top section coordinator before setting it to nil when
updating the NTP for the feed, which is called when the primary
account changes.
Updates the field trial config to use the compact promo since that's the
launched version.
(cherry picked from commit cad9c702c74d9fb909be28ad4584dc54f05816d4)
Bug: 1416235
Change-Id: Ie550610f6f4334ee17d0230332c9f759c8290008
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250541
Commit-Queue: Adam Arcaro <[email protected]>
Reviewed-by: Sergio Collazos <[email protected]>
Commit-Queue: Sergio Collazos <[email protected]>
Auto-Submit: Adam Arcaro <[email protected]>
Reviewed-by: Chris Lu <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105317}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261131
Cr-Commit-Position: refs/branch-heads/5563@{#552}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[WebPayments] Unify early exits in AndroidPaymentAppFactory
(M111 merge)
This CL corrects an issue where AppFinder::OnGetAppDescriptions had a
different early-exit check than AppFinder::IsReadyToPay. This could
cause OnGetAppDescriptions to reach AppFinder::OnDoneCreatingPaymentApps
and delete the current instance whilst it was still in use.
A test is added that exercises the failing path before the fix.
(cherry picked from commit f06f8ce3044f265d15ebda7578a76625d45df8f0)
Bug: 1414738
Change-Id: I31dd8a62a83acf60412df1d055aeba311f2df430
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4245784
Reviewed-by: Nick Burris <[email protected]>
Commit-Queue: Stephen McGruer <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104754}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262695
Auto-Submit: Stephen McGruer <[email protected]>
Commit-Queue: Nick Burris <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#551}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[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 [email protected].
[email protected]
Change-Id: I0ae0724b062b82a7460da95a638ed54279707ae1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262987
Commit-Queue: Rubber Stamper <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Auto-Submit: lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com <lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#550}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[ios] Add workaround for background refresh experiment only
Background refresh exposed issues with background cold starts.
We created a workaround so that we can test the background refresh code
in a 1% experiment. This workaround is behind the background refresh
flag and will not be launched.
This workaround prevents background cold starts from putting the app
into a bad state. It returns the app into a good state, then exits
the app.
The known issue that this CL addresses is that the metrics service
needs to be set back to the background state. This also sets the
correct state for the clean exit beacon, among other things.
(cherry picked from commit 7537132bd5dbe38a3266a1cca5233674b8a5f109)
bug: 1396459
Change-Id: I63edd1af1a8964f5d8f735dfe3b9074108113303
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4117317
Commit-Queue: edchin <[email protected]>
Reviewed-by: Mark Cogan <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1101024}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261343
Reviewed-by: Sergio Collazos <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#549}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Discard pre-computed OOF layout results inside repeated content.
The result generally cannot be re-used in actual layout in such
situations. We were already discarding it if we were participating in
block fragmentation, but not when inside repeated content (which
participates in block fragmentation in its own twisted way, but at the
same time establishes a monolithic root). The particular problem in this
case was that we ended up with a culled inline inside repeated content
(a fixed positioned element, when printing). NGInlineLayoutStateStack::
OnOpenTag() tries to guard against that, but couldn't, because the
constraint space doesn't have the IsInsideRepeatableContent flag set
when performing pre-layout in ComputeOutOfFlowBlockDimensions(). That's
only set in NGOutOfFlowLayoutPart::GenerateFragment().
(cherry picked from commit 2bbc3a935c6c1ddeeeeaea1b2b0f23c29fab65c2)
Bug: 1402156
Change-Id: Ie68ee7567a1fd0c68b2e49d4520c30f9e814609e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4248189
Reviewed-by: Ian Kilpatrick <[email protected]>
Commit-Queue: Morten Stenshorne <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105038}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261452
Owners-Override: Prudhvikumar Bommana <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Ian Kilpatrick <[email protected]>
Commit-Queue: Prudhvikumar Bommana <[email protected]>
Reviewed-by: Prudhvikumar Bommana <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#548}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.32
Change-Id: I69420e417ab256b460ec5e4841b1ad6ae46dd448
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261973
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#547}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676547318-5dc32ae07cb61ef2826097dfc54c631f987befcb.profdata to chrome-win64-5563-1676569721-c71cf62b9ffec71ebd8d856c1b60e7f784af1f15.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I3372dc4eeacd6ca7a56df1fb8e6133c1810b3aba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261910
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#546}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676519369-71531ae0fde6d2119e5fd8ec6dda0fe4c9679685.profdata to chrome-linux-5563-1676569721-78626f27e1247bf566e429757fb35e0c4bdc5655.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I12efb207ad3db6a7b5e6a3844e017a6eba9fb4ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261340
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#545}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[Merge M111][Tab Strip Redesign] Fix close button y-position
Folio Screenshot: https://screenshot.googleplex.com/94GFd4H59RLKU2V
Detached Screenshot: https://screenshot.googleplex.com/7hLzfT96N7W5pet
(cherry picked from commit 4564a1d9963d3a9d70b93eeda485b766f8d55c64)
Bug: 1385967
Change-Id: If86a315bb7c64c1d5b7cf967bbec60c157781dce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4242159
Reviewed-by: Sirisha Kavuluru <[email protected]>
Commit-Queue: Zhe Li <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104644}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4261333
Cr-Commit-Position: refs/branch-heads/5563@{#544}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Revert "An update on toasts"
This reverts commit 81b1aab79b5136ff7f1d2b3ae1adae784dab4dee.
Reason for revert: reverting to reland once the following edge cases are
considered: lock screen, side shelf, overlap with sliders and other UI.
Kept the removal of some code that was not meant to be landed on
`ToastManagerImpl::OnRootWindowWillShutdown()`.
More context here: https://groups.google.com/a/google.com/g/cros-status-area/c/VWUhdVLOIyg/m/sgZ_f2BNBAAJ
Original change's description:
> An update on toasts
>
> Anchor toasts on the right side, using the same offset as
> notification popups, and other shelf bubbles.
>
> Update the window for toasts to ensure they layer on top of
> notifications.
>
> After changing the window, it appears that the toast's window is null
> during shutdown (if I explicitly stop tablet mode before shutdown, the window is not null). Remove the code which prevents deletion of toast overlays when root windows are shutting down. After talking to the code author it was revealed that this code was not meant to be landed.
>
> Screenshot: https://screenshot.googleplex.com/8jjTMHpyb3Vppye.png
>
> Bug: b:254869752, b:256685837
> Change-Id: I01a4cbec5553ad3ec62cfcd98c6e1675d925f952
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3997092
> Commit-Queue: Alex Newcomer <[email protected]>
> Reviewed-by: Ahmed Fakhry <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1081859}
(cherry picked from commit 3e3a3fff9cddeb71fe3e609f9bfa432639aed705)
Bug: b:254869752, b:256685837
Change-Id: Ib58a5293bb43afabc90f1cc43c8c89aca82e4549
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4248478
Reviewed-by: Alex Newcomer <[email protected]>
Reviewed-by: Ahmed Fakhry <[email protected]>
Commit-Queue: Kevin Radtke <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105299}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4251957
Cr-Commit-Position: refs/branch-heads/5563@{#543}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Android Evict when Not Active
RenderViewHostImpl::CollectSurfaceIdsForEviction can return no surfaces
when the RenderViewHostImpl is not activated.
For features::kEvictSubtree we were using this as the sole source of
surfaces to evict. We had a check to confirm that the current surface
was in the list. However we weren't doing anything when the list was
empty.
For most tab changes this was fine. However eviction could occur during
same-tab navigation to different origins. This leads to the non-active
RVHI and the feature not evicting anything.
This change updated DelegatedFrameHostAndroid::EvictDelegatedFrame to
evict the current surface in these conditions. Matching behaviour when
the feature is off.
The UMA has been updated to MemoryAndroid.EvictedTreeSize2 and will
track total eviction size for both feature on/off. And will include
pre-navigation surfaces.
(cherry picked from commit a6054061d3929edf6711b4ad959e38a884234f81)
Bug: 1393349
Change-Id: I346ee339d595e4317adaaa0bd9ab63a3b3cc72cd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4247557
Reviewed-by: Benoit Lize <[email protected]>
Commit-Queue: Jonathan Ross <[email protected]>
Reviewed-by: Bo Liu <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105141}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4258150
Auto-Submit: Jonathan Ross <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#542}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Bigcore AFDO profile from 111-5563.8-1676287958-benchmark-111.0.5563.28-r1 to 111-5563.8-1676287958-benchmark-111.0.5563.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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: Id1491d9b38772af254548b334177e702c4c98775
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4262270
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#541}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[Metadata][Settings Page][Clank] Show card product name on the "Edit
card" Page
Show the card product name (like American Express Gold Card) if
available on the server card editor page.
Mock: https://www.figma.com/file/N6F3DN9prdEzQiylOtVBCW/X-PA-share?node-id=2%3A7011&t=Y4exUsGFyCD3vWBm-0
Implementation: https://screenshot.googleplex.com/9CfG9rM7v27Bcr8
Note: If the card product name is too long, truncate the product name.
Always show the last 4 digits.
(cherry picked from commit e58b74044f3bc8f72b96e614bc091dfe2f865bd8)
Bug: 1410418, 1413894
Change-Id: Iece5ea2acff640d9e296e0882b5b6f01d23908e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4225295
Reviewed-by: Michael Thiessen <[email protected]>
Reviewed-by: Friedrich Horschig <[email protected]>
Commit-Queue: Vishwas Uppoor <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1103857}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257389
Cr-Commit-Position: refs/branch-heads/5563@{#540}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Arm AFDO profile from 111-5550.0-1676292529-benchmark-111.0.5563.28-r1 to 111-5550.0-1676292529-benchmark-111.0.5563.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-arm-chromium-beta
Please CC [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I77de165c7b618aee2f95de3ce78010dd176ae19a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260750
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#539}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Atom AFDO profile from 111-5563.14-1676293165-benchmark-111.0.5563.28-r1 to 111-5563.14-1676293165-benchmark-111.0.5563.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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I594254cf241e435aae3abcbecd8ae6d20d879195
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260752
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#538}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676519369-1e4d1f660aaf57007aabab89abd01a215bef5a0a.profdata to chrome-win64-5563-1676547318-5dc32ae07cb61ef2826097dfc54c631f987befcb.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I2634997651916a9ff179a34199b827f0debc0fba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260466
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#537}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[Metadata][Settings Page][Clank] Card art image for virtual cards is of
incorrect dimension on "Payment methods" page
Card art image for Capital One virtual cards is of incorrect dimension.
This is because this resource is available in a single size, and the
"Payment methods" page displays the icon as is.
Scale the icon to the desired size before setting it on the page.
Before: https://screenshot.googleplex.com/B99eSTdVWsoFuQe
After: https://screenshot.googleplex.com/8ekUznhGVN5o7tC
(cherry picked from commit 1b5cb43a5a92cd21a8ec07773815dbd2a178885b)
Bug: 1410418, 1413893
Change-Id: I458958e4720c6b2c87bb93758920ef51acb4bb95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4229213
Reviewed-by: Siddharth Shah <[email protected]>
Commit-Queue: Vishwas Uppoor <[email protected]>
Reviewed-by: Friedrich Horschig <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1103983}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257731
Cr-Commit-Position: refs/branch-heads/5563@{#536}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676475911-28cedf4b8be424bbff3752cf2493e87602445e7b.profdata to chrome-win32-5563-1676547318-7fb2a2eccbbaaa6defddee223f916c24e7e6dca0.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I910063a4acd8af198b0b02d6c398c72a0a1c21ec
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260505
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#535}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[Merge to M111][ChromeVox] Fix 'ChromeVox spoken feedback is ready'
Fix 'ChromeVox spoken feedback is ready' on startup of ChromeVox.
Before, a race condition existed where the text might not be spoken,
based on when a listener was registered. Now, speak intro text when ready.
(cherry picked from commit 7948942fab08f6e94bd6babe0fc494d3ea071db5)
Fixed: b/268105940
Bug: b/267764065
Change-Id: Ibd227dda44796eca0864285d708edc9d302b0cec
AX-Relnotes: N/A.
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4226180
Auto-Submit: Josiah Krutz <[email protected]>
Reviewed-by: Anastasia Helfinstein <[email protected]>
Reviewed-by: Katie Dektar <[email protected]>
Commit-Queue: Josiah Krutz <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104192}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257658
Commit-Queue: Katie Dektar <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#534}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-16 UTC
Change-Id: I3e14568856ee9a6a6844486cb9f4d524924d006f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260565
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#533}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Updating XTBs based on .GRDs from branch 5563
Change-Id: I6aeb63fd7a126277c252d6e1b910d0b45a8ef5b9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259586
Bot-Commit: Rubber Stamper <[email protected]>
Auto-Submit: Ben Mason <[email protected]>
Commit-Queue: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#532}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676519369-46543d60b6c3eca30cc85874070383383647b478.profdata to chrome-mac-5563-1676547318-f5b13ad3812c6831cc4ee35b18b32e4b43dc018e.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: Id180df3a366d5d095f07ea591d60f9424c7b26dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260386
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#531}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Sync HttpBridge: Ensure destruction happens on the right thread
Before this CL: HttpBridge implemented its own custom
DestroyURLLoaderOnIOThread() method, to destroy some network resources
on the network thread. However, during browser shutdown, it's not
necessarily guaranteed that the task with that method actually still
runs. If it doesn't, the network resources will end up getting
destroyed in HttpBridge's dtor, on the wrong threa.
After this CL: HttpBridge uses DeleteSoon/ReleaseSoon to destroy the
network resources. These either run on the correct thread, or not at
all (leaking the objects in question, which doesn't really matter
during browser shutdown).
One interesting difference: The URLLoader's callbacks now hold a
reference to the HttpBridge. This is necessary to ensure that if one
of the callbacks gets run after Abort(), but before the URLLoader
actually got destroyed, the HttpBridge still exists. (Before, this was
handled implicitly via the DestroyURLLoaderOnIOThread() task.)
(cherry picked from commit ba719df005f029dbcfe1e450276f958e4b05e1bf)
Bug: 1413968
Change-Id: Idfbb4da5042fe7f9f680ae96e644f5c87df36c85
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4245918
Reviewed-by: Maksim Moskvitin <[email protected]>
Commit-Queue: Marc Treib <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104959}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4260066
Commit-Queue: Maksim Moskvitin <[email protected]>
Auto-Submit: Marc Treib <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#530}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Cleanups in Sync's HttpBridge
Mostly related to unit tests.
* Simpler way of injecting a test SharedURLLoaderFactory
* Removed an unnecessary test-only global variable (which the test never
properly reset) - injecting into the ctor instead
* Updated some outdated comments
(cherry picked from commit a6bb9797a233c08ba46d026fdb73292adaa90e1e)
Bug: 1413968
Change-Id: Ica76e7703c7cf23078d8895dcd8f8156880eb452
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4239542
Reviewed-by: Maksim Moskvitin <[email protected]>
Commit-Queue: Marc Treib <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104445}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259746
Commit-Queue: Maksim Moskvitin <[email protected]>
Auto-Submit: Marc Treib <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#529}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Recreate prompt view on browser change
(cherry picked from commit 8a597b09ee68b6710ff162a70bf835be3dbc6097)
Bug: 1369374
Change-Id: I4991e01bac7abcbda194096684f43962f7221ec3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4247017
Commit-Queue: Florian Jacky <[email protected]>
Reviewed-by: Illia Klimov <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1105027}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259805
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Illia Klimov <[email protected]>
Auto-Submit: Florian Jacky <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#528}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Amd64 AFDO from 111.0.5563.28_rc-r1-merged to 111.0.5563.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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I108fe55784da9796a188b23412bd5b3aca220fbc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259687
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#527}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676497312-c008724ae0d438206a3bf3bbba57b2da19a8a349.profdata to chrome-win64-5563-1676519369-1e4d1f660aaf57007aabab89abd01a215bef5a0a.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I929c2c4e3f43485224ebdd9c18717961b4d221d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257404
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#526}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676497312-8b0542c2ee5a91bc3637b3fbe5ab896d09f98b7c.profdata to chrome-linux-5563-1676519369-71531ae0fde6d2119e5fd8ec6dda0fe4c9679685.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: Id374a20933796901250ccca1ae1225feb9b84d6f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4258279
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#525}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676497312-c10448c5d02c6329dff63a5f1f2d70c99e992fba.profdata to chrome-mac-5563-1676519369-46543d60b6c3eca30cc85874070383383647b478.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I279a1b6185b80035769a6d1125573b43c45f4a51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4258014
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#524}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Fix chrome://vm page to work with polymer
(cherry picked from commit fae7ea6397b769a75989f6f2a2dc1f0b041530fe)
Bug: b/240930700
Change-Id: Ife4ec0d2f5e3943d874cc66f01b46952817b3bbb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4227372
Commit-Queue: Timothy Loh <[email protected]>
Auto-Submit: Joel Hockey <[email protected]>
Code-Coverage: Findit <[email protected]>
Reviewed-by: Timothy Loh <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1102022}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4258646
Auto-Submit: Jason Lin <[email protected]>
Commit-Queue: Jason Lin <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#523}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676475911-eb352be8bd428200c0918b70e13b1a82fc35383d.profdata to chrome-win64-5563-1676497312-c008724ae0d438206a3bf3bbba57b2da19a8a349.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: Ib1b26d39c854811a154ab0c4902d4f3567c92464
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257704
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#522}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676475911-44b941ac293d7ad67336a26db054d14928feb7f1.profdata to chrome-linux-5563-1676497312-8b0542c2ee5a91bc3637b3fbe5ab896d09f98b7c.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I232781e6e10131fd9c1552f9e16c8fe461be49bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257609
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#521}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676475911-8f5b5dc5512f7c9e472912500dc8b95bcf3ba5b1.profdata to chrome-mac-5563-1676497312-c10448c5d02c6329dff63a5f1f2d70c99e992fba.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I7d4b661d94b7e8e822ce52ebb992df3d64e568ee
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257559
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#520}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[skylab_tests] Update skylab tests cros img version
This cl only affect Lacros on-device config builders like
lacros-amd64-generic-chrome-skylab. This cl will certainly NOT affect
linux-lacros builders(linux-lacros-tester-rel, linux-lacros-rel, etc)
or any other platforms.
This CL will update cros image version for skylab tests. CROS_BOARD_LKGM
is updated according to chromeos/CHROMEOS_LKGM; CROS_BOARD_DEV,
CROS_BOARD_BETA and CROS_BOARD_STABLE are updated according to Omaha.
If this CL caused regressions, please revert and pause the autoroller at
https://luci-scheduler.appspot.com/jobs/chrome/lacros-skylab-tests-cros-img-roller
Also please file a bug to OS>LaCrOS>Partner, and CC [email protected],
[email protected].
[email protected]
Requires-Testing: True
Change-Id: Iefe1f7210b21d9633fc15ad9ed5a413f62694ec7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259045
Auto-Submit: skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com <skylab-test-cros-roller@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: Rubber Stamper <[email protected]>
Commit-Queue: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#519}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.31
Change-Id: If3d8584f14d05d98b910d8e66d30f360b9c85d24
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4259025
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#518}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Reland "[Side Panel] Fix crash if browser closes before side panel entry loads"
This is a reland of commit 947b2d1a68b04b1111e1ece88501de52bafa694d
Original change's description:
> [Side Panel] Fix crash if browser closes before side panel entry loads
>
> Fix a crash that happens if the browser closes with the side panel open
> but the active entry has not been set, which can happen when the entry
> to be shown is currently loading. This triggers the
> OnTabStripModelChanged event where GetContentView() returns true but
> current_entry_ is null. The crash was caused by attempting to inspect
> a property of current_entry_ when null.
>
> The fix is very simple: check current_entry_ to be non-null before
> attempting to use it in IsExtensionEntry(current_entry_).
>
> A follow up task could involve trying to abort the load when the browser
> closes, documented in crbug.com/1410685
>
> Bug: 1408947
> Change-Id: Ic8a1ae8e25b89ffa6ed2370cd9c1cea32e9aeb4f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4185060
> Commit-Queue: Kelvin Jiang <[email protected]>
> Reviewed-by: Caroline Rising <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1097775}
(cherry picked from commit bf3a0ec4a381380d1a5dbe72f659ed7742c26aee)
Bug: 1408947
Change-Id: Ic555e98c57469acb88496d6e30df9bca5e1a966c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4199557
Reviewed-by: Peter Boström <[email protected]>
Auto-Submit: Kelvin Jiang <[email protected]>
Commit-Queue: Peter Boström <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1098121}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4250153
Commit-Queue: Prudhvikumar Bommana <[email protected]>
Reviewed-by: Caroline Rising <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#517}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676435573-e987039d3c995768e57d09bb12e1e08fee7a0b80.profdata to chrome-win32-5563-1676475911-28cedf4b8be424bbff3752cf2493e87602445e7b.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: Ie4ef277cc36e67a882b8eecb29bf5fe751e12020
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4256707
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#516}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.30
Change-Id: I9fff027c3f2430df750ba59d84e3e7e6c14b86a0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4257745
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#515}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676454568-5f745600c7afef0b99760842279a85ed953ea463.profdata to chrome-win64-5563-1676475911-eb352be8bd428200c0918b70e13b1a82fc35383d.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I298704efdbbc701b6710cba24064b8054f9a8c8f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255120
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#514}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Android: Explicitly set JAVA_HOME for kotlinc
The `kotlinc` command expects JAVA_HOME to be set (or at least `java` to
be available), but some bots have neither. Thus explicitly set JAVA_HOME
when running the `koltinc` command.
(cherry picked from commit 11399297190221983410650c5e2bf4a0008d849a)
Bug: 1410527, 1416461
Change-Id: Icf0e07edc247829dd7ca999938625e9fea6ddc49
Fixed: 1410527
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4199759
Auto-Submit: Peter Wen <[email protected]>
Reviewed-by: Andrew Grieve <[email protected]>
Commit-Queue: Peter Wen <[email protected]>
Commit-Queue: Andrew Grieve <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1097995}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4256367
Reviewed-by: Harry Souders <[email protected]>
Commit-Queue: Harry Souders <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#513}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Bigcore AFDO profile from 111-5563.8-1676287958-benchmark-111.0.5563.26-r1 to 111-5563.8-1676287958-benchmark-111.0.5563.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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I46d7c7a936568bae3b2d2d787e3cc98622a567d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4256890
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#512}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676454568-3c4a2a929f2beedc51b7a91c58be09cfd48c77aa.profdata to chrome-linux-5563-1676475911-44b941ac293d7ad67336a26db054d14928feb7f1.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I2d676e9f312ae1a8597abe99e7afaf30787861d8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4256727
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#511}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[cc] Add a feature to look harder for solid colored tiles
CC tries to identify tiles that are solid colored, to avoid allocating
any memory to those. However, it is not very persistent, and gives up if
the tiles has more than 1 operation in its paint op list. This causes
problems on macOS, where the browser compositor UI has tiles that are
never visible and solid colored, covering the whole browser window. But
these (at least locally) have a paint op list with 3 entries.
This costs us ~24MiB of memory per Chrome window on a 14 inch macbook
pro. For more details, see
https://docs.google.com/document/d/1XwXaNmCUb7VBfEn9C8tBuXnaVol0FLBRickLeJui1_s/edit#
(google internal).
This CL adds a feature to try lists up to 5 elements.
(cherry picked from commit 0efb0a0ddbfecc8ad1cdbb71a7e208494d78526d)
Bug: 1355820
Change-Id: I270cdb23d2c01200845e6f85d7150a2dcbdf5793
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4210420
Commit-Queue: Benoit Lize <[email protected]>
Reviewed-by: Jonathan Ross <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1100916}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255767
Owners-Override: Benoit Lize <[email protected]>
Reviewed-by: Thiabaud Engelbrecht <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#510}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[merge m111] Document that a Browser may be deleted when it still has tabs.
Change the CHECK to a DCHECK to avoid generating many crash reports.
(cherry picked from commit 6b7a496cab3c9bca9059ea22b317136ee6643d2a)
Bug: 1407055
Change-Id: Ifa703c4abb15dda5a950d1570e2efa1cfb800ce6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4245618
Auto-Submit: Francois Pierre Doray <[email protected]>
Commit-Queue: Francois Pierre Doray <[email protected]>
Reviewed-by: Scott Violet <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104619}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255727
Reviewed-by: Prudhvikumar Bommana <[email protected]>
Owners-Override: Prudhvikumar Bommana <[email protected]>
Commit-Queue: Prudhvikumar Bommana <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#509}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Atom AFDO profile from 111-5563.14-1676293165-benchmark-111.0.5563.26-r1 to 111-5563.14-1676293165-benchmark-111.0.5563.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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I4067a6335a6de867bf873bae175719d676cbe36b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255019
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#508}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676454568-dbf0289773450f9e77e41913f153f0ab791ba79f.profdata to chrome-mac-5563-1676475911-8f5b5dc5512f7c9e472912500dc8b95bcf3ba5b1.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: Ib0d7a28854e7c3d03fc087ca180a7302b58aabe2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255455
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#507}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Revert "Do not activate the browser window when handling -[NSApplicationDelegate application:openURLs:] on Mac."
This reverts commit 64d6d7f36e7b443733404bb40b549d8c0a666e6f and commit fc00be1e6c64a56041f23089551d62416b102a12.
Reason for revert: This approach could cause regression issues where browser windows should be activated for certain user interactions but are actually not. The -[NSWindow makeKeyAndOrderFront:] call should generally not be skipped when opening new browser windows.
Original change's description for commit 64d6d7f36e7b443733404bb40b549d8c0a666e6f:
> Do not activate the browser window when handling -[NSApplicationDelegate application:openURLs:] on Mac.
>
> AppKit applications should not activate themselves when handing
> -[NSApplicationDelegate application:openURLs:]. Specifically, when other
> application invoking Chromium based browser using -[NSWorkspace
> openURL:configuration:completionHandler:], the `configuration.activates`
> parameter controls whether to cause the system to bring the target app
> to the foreground.
>
> Preventing to activating the browser window when handling such events,
> makes Chromium compliant with such settings.
>
> Bug: 1385436, 854609
> Change-Id: Ie4e20156607a76ccac424d310806e6b135b0500e
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4031786
> Reviewed-by: Tommy Martino <[email protected]>
> Reviewed-by: Avi Drissman <[email protected]>
> Commit-Queue: Leonard Grey <[email protected]>
> Reviewed-by: Leonard Grey <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1080945}
Original change's description for commit fc00be1e6c64a56041f23089551d62416b102a12:
> Fix minimized browser window not being activated when handling application:openURLs: on Mac.
>
> Change Ie4e20156607a76ccac424d310806e6b135b0500e introduced a behavior
> that prefers not activating the browser window when handing
> -[NSApplicationDelegate application:openURLs:] and leaves the task to
> the LaunchServices. The minimized browser windows should be an
> exception since the OS won't activate such windows. This CL fixes this
> regression issue and adds related tests.
>
> Bug: 1401678
> Change-Id: I1610d9c6e86c672eacfcd05ed2755cbcb8ece6d0
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4111828
> Reviewed-by: Avi Drissman <[email protected]>
> Commit-Queue: Avi Drissman <[email protected]>
> Reviewed-by: Tommy Martino <[email protected]>
> Cr-Commit-Position: refs/heads/main@{#1085480}
(cherry picked from commit b37d8f7d0f4661d125f439ee9f1538e25235ff19)
Bug: 1414624, 1413966
Change-Id: Ibbe1c1d302704489411185dedb7c4684ebe85b95
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4242560
Reviewed-by: Tommy Martino <[email protected]>
Reviewed-by: Avi Drissman <[email protected]>
Commit-Queue: Avi Drissman <[email protected]>
Reviewed-by: Leonard Grey <[email protected]>
Cr-Original-Commit-Position: refs/heads/main@{#1104647}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4256146
Auto-Submit: Avi Drissman <[email protected]>
Commit-Queue: Leonard Grey <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#506}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll ChromeOS Arm AFDO profile from 111-5550.0-1676292529-benchmark-111.0.5563.26-r1 to 111-5550.0-1676292529-benchmark-111.0.5563.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-arm-chromium-beta
Please CC [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I86a941dfd94f94aa1ea4c41800ab064c777217f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255016
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#505}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
[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 [email protected].
[email protected]
Change-Id: I44338a1290bb36d754c79047c571a98fce964951
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4256147
Auto-Submit: lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com <lacros-tracking-roller@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Rubber Stamper <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#504}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Incrementing VERSION to 111.0.5563.29
Change-Id: I2e9936788a99dc4eecb6861c6e562536046584fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4256526
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5563@{#503}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Updating XTBs based on .GRDs from branch 5563
Change-Id: I51ee92326381cfb8338832f32e3a85fa644047a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4254905
Commit-Queue: Rubber Stamper <[email protected]>
Bot-Commit: Rubber Stamper <[email protected]>
Auto-Submit: Ben Mason <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#502}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-15 UTC
Change-Id: Ie65539acd9449b01dedb1fcc68d00b47db4725c5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255045
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#501}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676435573-6ca9095a860912512073a2e380dfef2038fafd39.profdata to chrome-win64-5563-1676454568-5f745600c7afef0b99760842279a85ed953ea463.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: If323d5c6d4fea6adb005382bd02042ccb4f39298
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4254606
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#500}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Automatic update from google3
Automatic update for 2023-02-15 UTC
Change-Id: I3f4c99337a0932ea9d8aaef07c3bdf23ac32dc43
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4254925
Commit-Queue: PKI Metadata Updates Bot <[email protected]>
Bot-Commit: PKI Metadata Updates Bot <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#499}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Linux PGO Profile
Roll Chrome Linux PGO profile from chrome-linux-5563-1676416059-f5c3f9953034cde182d7ee27b30456d4072ef211.profdata to chrome-linux-5563-1676454568-3c4a2a929f2beedc51b7a91c58be09cfd48c77aa.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:linux-chrome
Tbr: [email protected]
Change-Id: I1b61fa6d8f54b15bc2d6c6d64f7fc80fa958df42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4255106
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#498}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676435573-6ecb6f7197a1f6edcda9d37c5e1d0c3b8761655b.profdata to chrome-mac-5563-1676454568-dbf0289773450f9e77e41913f153f0ab791ba79f.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I6c3d7afa4203ca88c7a0d3fa6e30ac146a91470e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4254587
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#497}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Amd64 AFDO from 111.0.5563.26_rc-r1-merged to 111.0.5563.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 [email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Tbr: [email protected]
Change-Id: I94e835a97790d84a16fd0cb192e2377dbdaffefd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4254425
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#496}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win32 PGO Profile
Roll Chrome Win32 PGO profile from chrome-win32-5563-1676396217-8ae7e6cb850ed015fafdd3a0f282eb838bfc6bcf.profdata to chrome-win32-5563-1676435573-e987039d3c995768e57d09bb12e1e08fee7a0b80.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win-chrome
Tbr: [email protected]
Change-Id: I8e85fad8e50410cfdb258e026ab63619872c0e40
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4251427
Bot-Commit: Chrome Release Autoroll <[email protected]>
Commit-Queue: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#495}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Win64 PGO Profile
Roll Chrome Win64 PGO profile from chrome-win64-5563-1676416059-264c1505ba73341770efc8df42532de5f6fe8952.profdata to chrome-win64-5563-1676435573-6ca9095a860912512073a2e380dfef2038fafd39.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:win64-chrome
Tbr: [email protected]
Change-Id: I1b8c975b2fc1d42fd0880b444159e7e7568351c4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4252866
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#494}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
Roll Chrome Mac PGO Profile
Roll Chrome Mac PGO profile from chrome-mac-5563-1676416059-821ddb704405913460485dcc2f8d211c6a0fda72.profdata to chrome-mac-5563-1676435573-6ecb6f7197a1f6edcda9d37c5e1d0c3b8761655b.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 [email protected],[email protected] 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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md
Cq-Include-Trybots: luci.chrome-m111.try:mac-chrome
Tbr: [email protected]
Change-Id: I02b186e11c61055a4cdefc5598374f1af48924be
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4252422
Commit-Queue: Chrome Release Autoroll <[email protected]>
Bot-Commit: Chrome Release Autoroll <[email protected]>
Cr-Commit-Position: refs/branch-heads/5563@{#493}
Cr-Branched-From: 3ac59a6729cdb287a7ee629a0004c907ec1b06dc-refs/heads/main@{#1097615}
