Chromium M132 Main Console
| Legend: | Passed | Failed | Running | Exception |
Incrementing VERSION to 132.0.6834.239
Merge-Approval-Bypass: Chrome release infra
Change-Id: I4a414a7e53493db94efd7a45544e5e34303359a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6786449
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5598}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/third_party/angle in M132 from ce13a00a2b04 to f0a78b0de48e
Commits rolled:
https://chromium.googlesource.com/angle/angle.git/+log/ce13a00a2b04..f0a78b0de48e
Generated by: http://go/bbid/8708452850195619921
Change-Id: Iac980e7a2645377d3537769426e47460e7ccca0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778667
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5597}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Avoid WorkerThread creation if the parent has been terminated
In the previous implementation, we respected `terminate()` for the child
Worker, but we did not see the current parent state. It brought CHECK
failure when the current worker thread has been terminated while it is
creating the child thread.
To avoid the situation, this CL makes the child thread started only if
the parent thread is live.
(cherry picked from commit c352cb1c99d2f6b9953046407e4bde97f438c151)
Bug: 420993774
Change-Id: I43c8108dd4dff2c76e6a6901f6845dfe2c9420c2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6600912
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1467330}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6656545
Reviewed-by: Fahad Mansoor <fahadmansoor@google.com>
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5596}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Don't allow writes to active transform feedback buffer.
(cherry picked from commit be1272f94a48e81906ba30f27864c41eb08f4e4c)
Change-Id: If7c6a2de9d4dd5253413ff9a34641b919daf058b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6667363
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1478551}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778640
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Fahad Mansoor <fahadmansoor@google.com>
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5595}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Automated Commit: LKGM 16093.111.0 for chromeos.
Uploaded by https://ci.chromium.org/b/8709061355602694065
CrOS-LKGM: 16093.111.0
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8709061355602694065
Change-Id: I5d0a675d2d1f7f3a9421d5cdbefe68b8f127dd31
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6769526
Bot-Commit: ChromeOS Release Bot (Robot) <chromeos-ci-release@chromeos-release-bot.iam.gserviceaccount.com>
Commit-Queue: ChromeOS Release Bot (Robot) <chromeos-ci-release@chromeos-release-bot.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5594}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Setting version to 132.0.6834.238
Change-Id: I570da4d8bf606ae57e60ded42002bdaad0a427dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6761813
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5593}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Automated Commit: LKGM 16093.109.0 for chromeos.
Uploaded by https://ci.chromium.org/b/8709975882220859425
CrOS-LKGM: 16093.109.0
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8709975882220859425
Change-Id: Iab6d74c398ea60c6e6eb4d9cc33bc1e39c399b0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6712725
Commit-Queue: ChromeOS Release Bot (Robot) <chromeos-ci-release@chromeos-release-bot.iam.gserviceaccount.com>
Bot-Commit: ChromeOS Release Bot (Robot) <chromeos-ci-release@chromeos-release-bot.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5592}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Incrementing VERSION to 132.0.6834.228
Merge-Approval-Bypass: Chrome release infra
Change-Id: I696c3012925775c3bec0634537d0dd36a8aa84f8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6710151
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5591}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from 618bc3081be2 to c8049c42fb33
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/618bc3081be2..c8049c42fb33
Generated by: http://go/bbid/8710464856442316865
Change-Id: I9b0934a4d1a6b898571edef96960ef269c916eba
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6698753
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5590}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from 178e8d67b095 to 618bc3081be2
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/178e8d67b095..618bc3081be2
Generated by: http://go/bbid/8710647937979601089
Change-Id: I29fd81f9492b1a553d9e3e799c54c50ccc75f544
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6689286
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5589}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS][ssm] Fix race condition
This CL fixes a threading issue, by using locks to prevent racy access.
(cherry picked from commit e9e247c09b76dc6813c70d2c7007438c830bea56)
Bug: 421471016
Change-Id: If41796b9eb49aa3f27df175c6be198f47947c4c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6620528
Reviewed-by: Jean-Philippe Gravel <jpgravel@chromium.org>
Commit-Queue: Thiabaud Engelbrecht <thiabaud@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1470083}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6651573
Reviewed-by: Mohamed Omar <mohamedaomar@google.com>
Reviewed-by: Sean Maher <spvm@chromium.org>
Owners-Override: Mohamed Omar <mohamedaomar@google.com>
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Thiabaud Engelbrecht <thiabaud@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5588}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Enforce SharedWorker::Terminate() procedure order
During the investigation of crbug.com/409059706, we observed that
PerformShutdownOnWorkerThread() is called during the status is
running.
I suppose the root cause is race condition between `Terminate()`
procedure and a child process termination procedure in different
thread. WorkerThread can be terminated if two conditions are met;
`Terminate()` is called and all child worker threads have been
terminated. Both `Terminate()` and the child process termination
procedure may call `PerformShutdownOnWorkerThread()`, and former
is executed regardless of two conditions are met. The latter
is called if `Terminate()` is called and no child processes.
To be clear, "`Terminate()` is called" does not mean
`PrepareForShutdownOnWorkerThread()` is executed. `Terminate()`
queues it after the flag to tell `Terminate()` call. And, when
the issue happen, I am quite sure the flag is set but,
`PrepareForShutdownOnWorkerThread()` won't be executed yet.
The fix is that:
1. The "Terminate() is called" flag to be multi staged.
The flag is used for two purpose; a. avoid re-enter of
`Terminate()`, and b. `PrepareForShutdownOnWorkerThread()` is
in flight. The CL changed the flag to enum to represent
the stage properly.
2. `PerformShutdownOnWorkerThread()` is queued even if it is
called within the child process termination procedure.
It avoid the execution order flip between
`PrepareForShutdownOnWorkerThread()` and
`PerformShutdownOnWorkerThread()`.
In addition, this change ensures `PerformShutdownOnWorkerThread()`
is called once. While `PerformShutdownOnWorkerThread()` touches
fields inside, the fields must not be touched at some point within
the function, the function is actually not re-entrant when it reaches
to the end. Upon mikt@ suggestion, I made
`PerformShutdownOnWorkerThread()` is called only when two conditions
are fulfilled. i.e. `Terminate()` is called and the number of child
threads is 0. Also, the CL uses the enum to show
`PerformShutdownOnWorkerThread()` is in-flight to avoid re-entrance
in this level.
(cherry picked from commit f1e6422a355c016e5f2c22619181f7f121d1f511)
Bug: 409059706
Change-Id: I81a1c3b1a34e827fa75ec2d1a9b37023965dbe27
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6543412
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1463892}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6600489
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Owners-Override: Mohamed Omar <mohamedaomar@google.com>
Reviewed-by: Yoshisato Yanagisawa <yyanagisawa@chromium.org>
Reviewed-by: Mohamed Omar <mohamedaomar@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5587}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Automated Commit: LKGM 16093.108.0 for chromeos.
Uploaded by https://ci.chromium.org/b/8711779371168220641
CrOS-LKGM: 16093.108.0
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8711779371168220641
Change-Id: I44462b74b49c9c569a17d3e9f732d422c9d84429
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6654126
Bot-Commit: ChromeOS Release Bot (Robot) <chromeos-ci-release@chromeos-release-bot.iam.gserviceaccount.com>
Commit-Queue: ChromeOS Release Bot (Robot) <chromeos-ci-release@chromeos-release-bot.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5586}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] CCNS: make sure the cookie listener is added for prerendered document
Previously the cookie listen is not added for the prerendered document
because we only check IsInPrimaryMainFrame(), this will lead to serious
security problem since we won't be notified when the cookie changes
throughout the life time of that document.
This CL fixes the check and update the browser test with prerendering
case. Only a subset of the tests are updated but that should provide
enough coverage for the scenarios we are caring about.
(cherry picked from commit c287a87a87fd8b223af761746252ae03292024af)
Change-Id: Ia538f6f9e72c1096f1d0b4ed5ade7e2bd56e5523
Bug: 417215501
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6550761
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Mingyu Lei <leimy@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1462580}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6579105
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5585}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Incrementing VERSION to 132.0.6834.227
Change-Id: I73ed0289dbb388da323f36d176296db471beb9af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6653189
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5584}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] vt/cc: Post a callback task instead of a synchronous call
The callback can end up calling more script to start view transitions
which can add more requests, and re-enter into modifying the vector.
So, instead, unwind the task to post the task.
R=khushalsagar@chromium.org
(cherry picked from commit 02ddca5de087c833fede8c46fb971acdc42a7e91)
Bug: 411573532
Change-Id: I80880e9e3ecf41c346910fb5cb6f44609ee5ef17
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6542846
Commit-Queue: Vladimir Levin <vmpstr@chromium.org>
Reviewed-by: Khushal Sagar <khushalsagar@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1460048}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6575520
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Vladimir Levin <vmpstr@chromium.org>
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5583}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Update Hunspell d6a5ae5 -> v1.7.1
https://github.com/hunspell/hunspell/commit/v1.7.1
No conflicts, but we have to patch three additional Hunspell commits to
fix a test failure in Fuchsia:
- https://github.com/hunspell/hunspell/commit/f67ffdeea4504cc94d6d8a0caeb68838fc0811c9
- https://github.com/hunspell/hunspell/commit/aa90d7bd61e85ff357472636c1513bf437b07f74
- https://github.com/hunspell/hunspell/commit/edb619100791110d3e34f09ec35392ad327c1135
(cherry picked from commit a38c741b322b056d799103e022f650c0d494da91)
Bug: b:325123679
Change-Id: I7a38d2cdb9a2947b85c75fbd217189c2f76c28cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6490833
Reviewed-by: Michael Cui <mlcui@google.com>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1453088}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6515515
Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5582}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Update Hunspell 76d6ea9 -> d6a5ae5 (1 commit)
https://github.com/hunspell/hunspell/commit/d6a5ae5
This commit makes MAXSUGGESTION overridable by a compile time
define, so we no longer need to patch in our override as long
as we add a define.
(cherry picked from commit dcaebb0bbe95b8d7300c55e553a36d988299fb35)
Bug: b:325123679
Change-Id: I132e6498b303787ac814374c8d08ded4be911ea7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6493329
Reviewed-by: Michael Cui <mlcui@google.com>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1453087}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6516878
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/branch-heads/6834@{#5581}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Update Hunspell v1.7.0 -> 76d6ea9
https://github.com/hunspell/hunspell/commit/76d6ea9
No conflicts. The next CL will have a conflict.
(cherry picked from commit fe28e0c204e89e4842e16ebcaac206c5e5a7cfaf)
Bug: b:325123679
Change-Id: Ic2048865d4f6764bcad18d161780889e8ae6fe64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6491771
Reviewed-by: Michael Cui <mlcui@google.com>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1453086}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6515260
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/branch-heads/6834@{#5580}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Update Hunspell third_party update instructions.
Fix some typos and ensure that new upstream files are being added
to Chromium.
(cherry picked from commit 05fa5d4a8a3a68a1926bf4449725e60a797542f0)
(cherry picked from commit 51ffb457ccb6c0f28b25d95bc034e5eb6de52261)
Bug: b:325123679
Change-Id: I31d4946fda5c5f27a80b5c9d9f6fbed78d0c8e9d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6497482
Reviewed-by: Michael Cui <mlcui@google.com>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Original-Original-Commit-Position: refs/heads/main@{#1453081}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6515131
Cr-Original-Commit-Position: refs/branch-heads/7151@{#386}
Cr-Original-Branched-From: 8e0d32ed6e49a2415b16e5ed402957cac2349ce2-refs/heads/main@{#1453031}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6515259
Reviewed-by: Darren Shen <shend@chromium.org>
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5579}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Close watchers: ensure stable group in response to Esc key
(cherry picked from commit 7c0883253bda9bccf3e68f3e5fbbe37325d45ae9)
Change-Id: I251a548f4ad9451fc7abac813aa39352feb78539
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6458381
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Auto-Submit: Domenic Denicola <domenic@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1448404}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6483547
Auto-Submit: Gyuyoung Kim (xWF) <qkim@google.com>
Commit-Queue: Giovanni Pezzino <giovax@google.com>
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5578}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Use a dedicated node type to maintain the list of cached RVTs
While evaluating a stylesheet, result value trees (result tree fragments
in the XSLT spec) are represented as xmlDocs and cached on the transform
context in a linked list, using xmlDoc's prev and next pointers to
maintain the list.
However, XPath evaluations can inadvertently traverse these links, which
are an implementation detail and do not reflect the actual document
structure. Using a dedicated node type avoids these unintended
traversals.
(cherry picked from commit abf266b28588e4533242ca562ecb4be778d3e246)
Bug: 416535738
Change-Id: Iaacbe617905a3f844367cc56b2cbcf525d4818b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6621828
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1470251}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6636654
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5577}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from 0de272468034 to 178e8d67b095
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/0de272468034..178e8d67b095
Generated by: http://go/bbid/8711821924207663409
Change-Id: I7bba2452d37c0f39ea11fe00998af0297a10ee34
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6651609
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5576}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from a47e49dea052 to 0de272468034
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/a47e49dea052..0de272468034
Generated by: http://go/bbid/8712261695248926753
Change-Id: I5d6852c41895d4643897e2ae9d5057c13dba7884
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6641466
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5575}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from 792fdb390bde to a47e49dea052
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/792fdb390bde..a47e49dea052
Generated by: http://go/bbid/8712271134253266929
Change-Id: I66e1e9b158f2cfb543d57797f44933c7dc12b87d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6638514
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5574}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from 5e1dc1e04373 to 792fdb390bde
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/5e1dc1e04373..792fdb390bde
Generated by: http://go/bbid/8712274907545480705
Change-Id: Ife50e6c231d1820617b0a8efb88ca71a7de16165
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6638021
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5573}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Automated Commit: LKGM 16093.107.0 for chromeos.
Uploaded by https://ci.chromium.org/b/8713038115508807985
CrOS-LKGM: 16093.107.0
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8713038115508807985
Change-Id: I4c9308cf02b9888b23955bb6a85e3da9fd2c7dd0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6621302
Bot-Commit: ChromeOS Release Bot (Robot) <chromeos-ci-release@chromeos-release-bot.iam.gserviceaccount.com>
Commit-Queue: ChromeOS Release Bot (Robot) <chromeos-ci-release@chromeos-release-bot.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5572}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Incrementing VERSION to 132.0.6834.226
Change-Id: I514dd2f1ce602d42f994d68b399619ec4f5992ac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6619713
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5571}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from d44a761d5318 to 5e1dc1e04373
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/d44a761d5318..5e1dc1e04373
Generated by: http://go/bbid/8713095943286676193
Change-Id: I1405284e20fb91026be2b8a3bcdeddeb3083f855
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6616800
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5570}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from f91c0bbeea01 to d44a761d5318
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/f91c0bbeea01..d44a761d5318
Generated by: http://go/bbid/8713154455249637697
Change-Id: I0a86d9fec544e631bc42258523955796450a5c90
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6611850
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5569}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Set `referrerpolicy: "no-referrer"` in link loads from subresources
This CL overwrites the referrerpolicy attribute on Link header in sub-
resource loads.
See the bug for details.
(cherry picked from commit c3568ceda9d8aa3d9e5b80d1aaa02cba547224a5)
Bug: 415810136
Change-Id: I750e1043ecbd2ce63e827cdbdd2a2a22661ffea7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6522070
Commit-Queue: Takashi Nakayama <tnak@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1457510}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6579306
Owners-Override: Artem Sumaneev <asumaneev@google.com>
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Reviewed-by: Artem Sumaneev <asumaneev@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5568}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Automated Commit: LKGM 16093.106.0 for chromeos.
Uploaded by https://ci.chromium.org/b/8714217205374154193
No-Presubmit: true
Bug: 416288779
CrOS-LKGM: 16093.106.0
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8714217205374154193
Change-Id: Ice609118d832f81f514d1c5a920f49f02bcb190d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6575268
Owners-Override: Min Chen <minch@chromium.org>
Commit-Queue: Min Chen <minch@chromium.org>
Reviewed-by: Min Chen <minch@chromium.org>
Cr-Commit-Position: refs/branch-heads/6834@{#5567}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132] Add chromeos-ci-release@chromeos-release-bot to KNOWN_ROBOTS
This account is being used to land LKGM CLs for ChromeOS and
needs to be able to skip the author check for presubmits.
(cherry picked from commit e5664ef9e848fc2eefb897a30be9b369eaec03d8)
Bug: 416288779
Change-Id: I8beef28460ce126b1d94b416d8c064fad89b15df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6522306
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Auto-Submit: Rachael Newitt <renewitt@google.com>
Commit-Queue: Andrew Grieve <agrieve@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1457552}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6578705
Commit-Queue: Jeffrey Young <cowmoo@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5566}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Incrementing VERSION to 132.0.6834.225
Change-Id: I5a207ed294e1ceb7e1ded10e5efa0cb399cf4b40
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6574901
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5565}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Reland "[M132 Merge]Prevent restart of admin-installed extensions."
This is a reland of commit 4705223227c15647310239fd34f2a046a8952065
The differences with the original CL are the non ChromeOS lines in `extension_info_generator.cc`. This file had been refactored after M132 branched, and I missed using the `->` operator outside of ChromeOS.
Original change's description:
> [M132 Merge]Prevent restart of admin-installed extensions.
>
> Multiple exploits use changing an extension setting value to force the
> extension restart. This CL blocks the change to the setting value and
> applies the new value after Chrome restarts. This new flow is limited
> only to admin-installed extensions on ChromeOS devices.
>
> This is a stopgap solution until a more holistic solution to this
> problem is identified.
>
> (cherry picked from commit b3aeed90ef25d7fad54913f3cb724b4c609836fc)
>
> Fixed: 403199183
> Test: autotest c/b/extensions/delayed_setting_change_browsertest.cc c/test/data/webui/extensions/extensions_browsertest.cc
> Test: autotest c/b/e/api/developer_private/extension_info_generator_unittest.cc c/b/e/extension_prefs_unittest.cc
> Change-Id: Ic1f71c04f31d810ff071e8cde7e04c9e6643207c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6263692
> Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
> Auto-Submit: Giovanni Pezzino <giovax@google.com>
> Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
> Commit-Queue: Giovanni Pezzino <giovax@google.com>
> Cr-Original-Commit-Position: refs/heads/main@{#1427397}
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6487991
> Reviewed-by: Michael Ershov <miersh@google.com>
> Cr-Commit-Position: refs/branch-heads/6834@{#5562}
> Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Change-Id: Ief29696e9d1040841994907031a4069a2bea196d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6543450
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Auto-Submit: Giovanni Pezzino <giovax@google.com>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Reviewed-by: Fahad Mansoor <fahadmansoor@google.com>
Commit-Queue: Giovanni Pezzino <giovax@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5564}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Revert "[M132 Merge]Prevent restart of admin-installed extensions."
This reverts commit 4705223227c15647310239fd34f2a046a8952065.
Reason for revert: build fails https://ci.chromium.org/ui/p/chrome-m132/builders/ci/linux64/3542/overview
Original change's description:
> [M132 Merge]Prevent restart of admin-installed extensions.
>
> Multiple exploits use changing an extension setting value to force the
> extension restart. This CL blocks the change to the setting value and
> applies the new value after Chrome restarts. This new flow is limited
> only to admin-installed extensions on ChromeOS devices.
>
> This is a stopgap solution until a more holistic solution to this
> problem is identified.
>
> (cherry picked from commit b3aeed90ef25d7fad54913f3cb724b4c609836fc)
>
> Fixed: 403199183
> Test: autotest c/b/extensions/delayed_setting_change_browsertest.cc c/test/data/webui/extensions/extensions_browsertest.cc
> Test: autotest c/b/e/api/developer_private/extension_info_generator_unittest.cc c/b/e/extension_prefs_unittest.cc
> Change-Id: Ic1f71c04f31d810ff071e8cde7e04c9e6643207c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6263692
> Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
> Auto-Submit: Giovanni Pezzino <giovax@google.com>
> Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
> Commit-Queue: Giovanni Pezzino <giovax@google.com>
> Cr-Original-Commit-Position: refs/heads/main@{#1427397}
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6487991
> Reviewed-by: Michael Ershov <miersh@google.com>
> Cr-Commit-Position: refs/branch-heads/6834@{#5562}
> Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Change-Id: I7fe33b6898554389ed4f8381dac1ec53de7214b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6540588
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Commit-Queue: Feras Aldahlawi <frs@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/branch-heads/6834@{#5563}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132 Merge]Prevent restart of admin-installed extensions.
Multiple exploits use changing an extension setting value to force the
extension restart. This CL blocks the change to the setting value and
applies the new value after Chrome restarts. This new flow is limited
only to admin-installed extensions on ChromeOS devices.
This is a stopgap solution until a more holistic solution to this
problem is identified.
(cherry picked from commit b3aeed90ef25d7fad54913f3cb724b4c609836fc)
Fixed: 403199183
Test: autotest c/b/extensions/delayed_setting_change_browsertest.cc c/test/data/webui/extensions/extensions_browsertest.cc
Test: autotest c/b/e/api/developer_private/extension_info_generator_unittest.cc c/b/e/extension_prefs_unittest.cc
Change-Id: Ic1f71c04f31d810ff071e8cde7e04c9e6643207c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6263692
Reviewed-by: Demetrios Papadopoulos <dpapad@chromium.org>
Auto-Submit: Giovanni Pezzino <giovax@google.com>
Reviewed-by: Devlin Cronin <rdevlin.cronin@chromium.org>
Commit-Queue: Giovanni Pezzino <giovax@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1427397}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6487991
Reviewed-by: Michael Ershov <miersh@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5562}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Automated Commit: LKGM 16093.105.0 for chromeos.
Uploaded by https://ci.chromium.org/b/8715584936954882497
No-Presubmit: true
CrOS-LKGM: 16093.105.0
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8715584936954882497
Change-Id: I269e46af2c13240de35971053c19e17147902c59
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6517797
Commit-Queue: Xiqi Ruan <xiqiruan@chromium.org>
Reviewed-by: Xiqi Ruan <xiqiruan@chromium.org>
Owners-Override: Xiqi Ruan <xiqiruan@chromium.org>
Reviewed-by: Piotr Pawliczek <pawliczek@chromium.org>
Cr-Commit-Position: refs/branch-heads/6834@{#5561}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Incrementing VERSION to 132.0.6834.224
Change-Id: Ieaaf3a91724c4ed68e1b43b3dd6e56c6c5793a8e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6517373
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5560}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS][PartitionAlloc] Crash in AddressPoolManager when decommit fails.
(cherry picked from commit b378ec0015c58b0458ca95296df7fb123f8f6b7b)
Bug: 409243443
Change-Id: I2f693d66721a49f1badaae0799531c12683a73f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6439196
Commit-Queue: Benoit Lize <lizeb@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1444055}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6499046
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Giovanni Pezzino <giovax@google.com>
Owners-Override: Giovanni Pezzino <giovax@google.com>
Commit-Queue: Roger Felipe Zanoni da Silva (xWF) <rzanoni@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5559}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/v8 in M132 from d8e44cad29ef to f91c0bbeea01
Commits rolled:
https://chromium.googlesource.com/v8/v8.git/+log/d8e44cad29ef..f91c0bbeea01
Generated by: http://go/bbid/8716096967609448289
Change-Id: Id21903b11a895c2c5582f361ba2a837f438c762b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6504909
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5558}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Automated Commit: LKGM 16093.104.0 for chromeos.
Uploaded by https://ci.chromium.org/b/8716677540708724113
Merge-Approval-Bypass: Automated LKGM update
Cr-Original-Build-Id: 8716677540708724113
Change-Id: Ibaa86d98a9c494d03e09b376b0f5ffa7d61eb05b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6490564
Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5557}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Incrementing VERSION to 132.0.6834.223
Change-Id: I19f3218343a083090edf10c9775b62cdb20fd1d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6489836
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5556}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] usb: Use GlobalRenderFrameHostId in UsbChooserController
The UsbChooserController currently holds a raw pointer to the requesting
RenderFrameHost. This can lead to use-after-free issues if the
RenderFrameHost is destroyed before the chooser controller. This CL
replaces the raw pointer with a `GlobalRenderFrameHostId`. This ID can
be used to retrieve the RenderFrameHost when needed, and checks are
added to ensure the RenderFrameHost is still valid before accessing it.
(cherry picked from commit 0333ecde91425e518cd898614c7b018209a18511)
Bug: 405292639
Change-Id: Ifedaf80f6700d57ea28691abfaf4d2ff9cdbb448
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6440254
Commit-Queue: Alvin Ji <alvinji@chromium.org>
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1444224}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6450383
Reviewed-by: Alvin Ji <alvinji@chromium.org>
Reviewed-by: Mohamed Omar <mohamedaomar@google.com>
Owners-Override: Mohamed Omar <mohamedaomar@google.com>
Commit-Queue: Gyuyoung Kim (xWF) <qkim@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5555}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Revert "KeyPermissions: Improve the migration code"
This reverts commit 0f18d1c1620407689f3cdf07e7f91f964977998d.
Reason: root cause for crbug.com/389295348
Do not revert the enums.xml file, it shouldn't affect anything
and it's better to not remove UMA entries.
(cherry picked from commit e1871b0afe396c2cc9f7c95d9f613e8e32feae85)
Test: Manual on the internal setup that reproduces crbug.com/389295348
Bug: b:266071150, b:389295348
Change-Id: I2c52c27d8e456fbb342a5c67e57e593a84ad7a60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6425426
Feels: Alexander Hartl <alexanderhartl@google.com>
Reviewed-by: Oleksandr Sarapulov <olsa@google.com>
Commit-Queue: Michael Ershov <miersh@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1441525}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6432260
Commit-Queue: Mohamed Omar <mohamedaomar@google.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5554}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[M132-LTS] Notify LoginUnlockThroughputRecorder if full restore is not triggered.
LoginUnlockThroughputRecord waits for the event from full restore
service, but it may be disabled, e.g. by policy.
As short term workaround, this CL explicitly notifies the recorder
during session initialization.
BUG=b:404281256
TEST=Tryjob. Tested locally.
(cherry picked from commit 588911669179d86c65b378b2a9da5262039aea03)
Change-Id: I07d2b225684e6ae4323be3b60fa937ffd935323f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6369034
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Hidehiko Abe <hidehiko@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1434282}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6418888
Commit-Queue: Josh Horwich <jhorwich@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Cr-Commit-Position: refs/branch-heads/6834@{#5553}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/internal in M132 from b55ab50cf6a1 to b20b0f5bfb8c
Commits rolled:
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b55ab50cf6a1..b20b0f5bfb8c
Generated by: http://go/bbid/8717276616818678225
Change-Id: Id209588b05f9418ff47b2e329c98f5378598d8b6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6469798
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5552}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/internal in M132 from 32a8caa769ce to b55ab50cf6a1
Commits rolled:
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/32a8caa769ce..b55ab50cf6a1
Generated by: http://go/bbid/8717320027853492513
Change-Id: I319e7182496307629d23014ff3ff8f4902d584c9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6469776
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5551}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
Roll commits from side projects in M132
Roll src/internal in M132 from 1d0b27985fab to 32a8caa769ce
Commits rolled:
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1d0b27985fab..32a8caa769ce
Generated by: http://go/bbid/8717333238371873505
Change-Id: Ic1a4b36bfdc1e78660dd4db08d51d0214b79a672
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6469732
Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/6834@{#5550}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}
[m132] infra: Replace Reclient with Siso's builtin RBE client on Linux/Android/CrOS/Fuchsia CI builders
Most tryjobs have switched from Reclient to Siso's builtin RBE client.
This CL replaces the RBE client on the major CI builders on Linux host.
(cherry picked from commit e1487f6bcab09daa586856439a8102633dd16638)
Bug: 379584977
Change-Id: I7d0c70a29b0f9996e027fc2012c7454387eae964
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6242315
Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: Junji Watanabe <jwata@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1421240}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6467914
Auto-Submit: Junji Watanabe <jwata@google.com>
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/branch-heads/6834@{#5549}
Cr-Branched-From: 47a3549fac11ee8cb7be6606001ede605b302b9f-refs/heads/main@{#1381561}