Translate README.md to Latin #17
Open
+51,639
−197,792
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Roll Chrome Win64 PGO profile from chrome-win64-6099-1700566288-d9d68951ee89c8c577a55bdbb1e01f0bd9b7f8d2.profdata to chrome-win64-6099-1700589400-a2f6ddea974c96d0d93e72815698673b243cc8cc.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I539f6af0f999c58a0119c8bc1fc458f6d897c3bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5050748 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#957} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Win32 PGO profile from chrome-win32-6099-1700566288-e44af7f9f2a4ab21fa82e042086e857ec411981d.profdata to chrome-win32-6099-1700589400-41c3a18aa07eb598c3bc0508519b9049817dbb4a.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I64d4427debde47dde3a00ace18a65caeb13de52f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5050546 Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#958} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
This CL updates the ash version ['121.0.6140.0'] for Lacros version skew testing. This cl only affect linux-lacros config builders like linux-lacros-tester-rel, linux-lacros-rel. This cl will certainly NOT affect Lacros on-device builders (lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab, etc) or any other platforms. If this CL caused regressions, please revert and stop the autoroller at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller Also please file a bug to OS>LaCrOS>Partner, and CC svenzheng@chromium.org. R=rubber-stamper@appspot.gserviceaccount.com Bug: None Change-Id: Ie62c1755524cf0f4d4e16f993e6412f8c5186e32 Requires-Testing: True Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5050283 Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#959} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Ensure correct market segment assignment by delaying device mode and market segment retrieval until after OOBE completion. BUG=chromium:1502993 (cherry picked from commit dfd327c) Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5041597 Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> Reviewed-by: Pavol Marko <pmarko@chromium.org> Commit-Queue: Hirthanan Subenderan <hirthanan@google.com> Cr-Original-Commit-Position: refs/heads/main@{#1226569} Change-Id: I735ee129af62d23ca93fbc02447d56bb2934de75 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5046162 Cr-Commit-Position: refs/branch-heads/6099@{#960} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I15f64f9a78a2aa9dac19048e7399502996055266 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5052260 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#961} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Linux PGO profile from chrome-linux-6099-1700589400-a06c5ae03c8690a70bafdfc5f83416b7773d5ee9.profdata to chrome-linux-6099-1700610510-bdd196f76cf2aee9c8f4c86cac1b56db59b2eb51.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I840b9a519cef31aba12897c543dc0e61e6df831b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5051724 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#962} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Mac PGO profile from chrome-mac-6099-1700589400-1e374a7dd53cd5be3a8250da67684807492750c9.profdata to chrome-mac-6099-1700610510-44462ba3441c40002307dcae625e000444d96ba4.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I4d04e08feb1a94b3908d4c925fcba0e89ffff38c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5051905 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#963} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Win32 PGO profile from chrome-win32-6099-1700589400-41c3a18aa07eb598c3bc0508519b9049817dbb4a.profdata to chrome-win32-6099-1700610510-ba6802da0f00298dee5ace8057239c49a411f32e.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ice3b88d80fa04e0506bed02ee0fe76b76315f28b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5051389 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#964} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Win64 PGO profile from chrome-win64-6099-1700589400-a2f6ddea974c96d0d93e72815698673b243cc8cc.profdata to chrome-win64-6099-1700610510-6d6af9da448fc682e0d8cf6acb62b055ab232169.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ic980c0eae10a031cfe8b22401b386893c6e41282 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5052030 Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#965} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Mac PGO profile from chrome-mac-6099-1700610510-44462ba3441c40002307dcae625e000444d96ba4.profdata to chrome-mac-6099-1700623542-ca63ea9266491129cca3642b543ac555a5339446.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: If630de8652d96d813a26d57987d6774bde002793 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5051867 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#966} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
…uring iterate We have evidence that this crash is caused by enqueuing new requests within the callback itself. This CL makes the throttle robust to callbacks that enqueue new requests, and adds a unit test for that case. (cherry picked from commit 9288e5a) Bug: 1483454 Change-Id: I452370ea0a90b2586c67c161220dc36f40aaede8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5030755 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Tommy Li <tommycli@chromium.org> Reviewed-by: Marc Treib <treib@chromium.org> Reviewed-by: Sky Malice <skym@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1225601} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5051368 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Tommy Li <tommycli@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/branch-heads/6099@{#967} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Win64 PGO profile from chrome-win64-6099-1700610510-6d6af9da448fc682e0d8cf6acb62b055ab232169.profdata to chrome-win64-6099-1700623542-b6b7047948a2a1bb5e33ac9850f422d2515cc63a.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I9868dfb50e02e72d3e4cd6f6dfe62578ee9857e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5051911 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#968} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Win32 PGO profile from chrome-win32-6099-1700610510-ba6802da0f00298dee5ace8057239c49a411f32e.profdata to chrome-win32-6099-1700623542-c7d119f63ce11d5d9917b598be85f33efdd53a05.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I396fb88bf72661e7842f9889518144ccdc01289c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5052660 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#969} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
…1-merged This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file go/crostc-bug. Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/afdo-chromium-beta Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: Ieb8a0d575e13a4887b52e0c32f078c17693a5c66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5052677 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#970} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I012bec048b8b32d8973ad61516818cf133ccf9b0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053677 Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/branch-heads/6099@{#971} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Linux PGO profile from chrome-linux-6099-1700610510-bdd196f76cf2aee9c8f4c86cac1b56db59b2eb51.profdata to chrome-linux-6099-1700650266-5855f5272a550bde4d6622ecfb6b687db2f33952.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-linux-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I6b50119a14519365c07f8c9033d9e5cb988e7b93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053778 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#972} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Automatic update for 2023-11-22 UTC Change-Id: I7f65e6d971ed4db3645771c525a70c69a8dc0480 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053737 Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Cr-Commit-Position: refs/branch-heads/6099@{#973} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Uploaded by https://ci.chromium.org/b/8763766862862085489 Change-Id: Id1828d8b47bea9b4f0494fdfcf22dc7203bdb3cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053659 Commit-Queue: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Bot-Commit: ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#974} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Mac PGO profile from chrome-mac-6099-1700623542-ca63ea9266491129cca3642b543ac555a5339446.profdata to chrome-mac-6099-1700650266-3b21ab6b167b391b9561b6915cb5303e95b8df2b.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-mac-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ie0e165e89ce624d3e00c3c54f816d5bd7908fa27 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053617 Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#975} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Automatic update for 2023-11-22 UTC Change-Id: Ifb4e20c6f3f26806e58874a651dec1404f270fed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053857 Commit-Queue: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Bot-Commit: PKI Metadata Updates Bot <mdb.chrome-pki-metadata-release-jobs@google.com> Cr-Commit-Position: refs/branch-heads/6099@{#976} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Win64 PGO profile from chrome-win64-6099-1700623542-b6b7047948a2a1bb5e33ac9850f422d2515cc63a.profdata to chrome-win64-6099-1700650266-46fbc798d9e1d51df565c30b35af15a11a8d4e4e.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ie2694899adca3668a6ae1a355590b97e46913f1a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053597 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#977} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Win32 PGO profile from chrome-win32-6099-1700623542-c7d119f63ce11d5d9917b598be85f33efdd53a05.profdata to chrome-win32-6099-1700650266-eff3459bb6b9c2a206d8c83617ad691602f929ad.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ic003692a304fa3fe45402d8124fbc4652fd0e446 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053598 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#978} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
This CL adds metrics that capture the three-dot menu as an entry point, as well as how often a notification is shown. The cherry-pick resolved trivial merge conflicts in app_menu_model.h (changes in the AppMenuAction enum) and enums.xml (changes in the WrenchMenuAction enum). (cherry picked from commit 89040d6) Bug: 1443466, 1503692 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5012653 Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Luc Nguyen <lucnguyen@google.com> Reviewed-by: Peter Boström <pbos@chromium.org> Reviewed-by: Side YILMAZ <sideyilmaz@chromium.org> Reviewed-by: Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Tom Van Goethem <tov@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1225891} Change-Id: Ie5eda6e60964ad03b81a034febb95a1fde09f46a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053878 Auto-Submit: Tom Van Goethem <tov@chromium.org> Reviewed-by: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/branch-heads/6099@{#979} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
(cherry picked from commit 5c31e6f) Bug: 1502872 Change-Id: I9f0cd15d45ccd843bb85975a2b05782207043578 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5038090 Reviewed-by: Adam Langley <agl@chromium.org> Commit-Queue: Friedrich Horschig <fhorschig@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1226095} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5047039 Auto-Submit: Friedrich Horschig <fhorschig@chromium.org> Commit-Queue: Adam Langley <agl@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#980} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
…20.0.6099.33-r1 to 120-6099.25-1700483755-benchmark-120.0.6099.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 c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I7afd81eb14a4f9a768981eb978b293aaa7d0f6a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053622 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#981} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
* Adds metrics for different user interactions with the password sharing flow (password_sharing_metrics.h, enums/histograms.xml) * Adds unit tests for coordinators that are touched by those changes (cherry picked from commit 2b84701) Bug: 1500594 Change-Id: I7e51da39bc7339edcdc4a57b626a881f9d131382 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5012645 Commit-Queue: Rafał Godlewski <rgod@google.com> Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Reviewed-by: Tommy Martino <tmartino@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1225399} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5049886 Cr-Commit-Position: refs/branch-heads/6099@{#982} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
The request initiator for beacons is now whoever chose the destination URL: * For destination enum beacons (including all automatic beacons), this is the reporting worklet's origin. * For destination URL beacons (with macro substitution), this is the reportEvent caller's origin. (cherry picked from commit fb3308f) Bug: 1498474 Change-Id: I426ac8a05f8c197669df72fb6a82394029993029 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5037514 Reviewed-by: Dominic Farolino <dom@chromium.org> Reviewed-by: Matt Menke <mmenke@chromium.org> Commit-Queue: Garrett Tanzer <gtanzer@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1227504} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5050603 Reviewed-by: Nan Lin <linnan@chromium.org> Reviewed-by: Cammie Smith Barnes <cammie@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#983} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
…14-benchmark-120.0.6099.32-r1 to 120-6099.25-1700478669-benchmark-120.0.6099.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-exp-chromium-beta Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I3aa03fa95c1f4a27d31504e085a557ef3ce6a4f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5053609 Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#984} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
This reverts commit d6c704f. This isn't a pure revert due to needing to resolve some conflicts and formatting changes. The issue appears to be that the cleanup of hintAtTabSelection was incomplete it is actually used by ActivityTabProvider which updates the toolbar state. (cherry picked from commit 2d0e025) Bug: 1498377 Change-Id: I991a846660f641db2ddb1ebbff270fb07dcbeb3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5046196 Commit-Queue: Calder Kitagawa <ckitagawa@chromium.org> Auto-Submit: Calder Kitagawa <ckitagawa@chromium.org> Reviewed-by: Patrick Noland <pnoland@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Patrick Noland <pnoland@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1227117} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5054500 Reviewed-by: Brandon Wylie <wylieb@chromium.org> Cr-Commit-Position: refs/branch-heads/6099@{#985} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
…5962074328ab Commits rolled: https://chrome-internal.googlesource.com/devtools/devtools-internal.git/+log/fbedbff432f2..5962074328ab Roll src/third_party/devtools-frontend/src from 0ed0f013eb02 to 934a1853595a Commits rolled: https://chromium.googlesource.com/devtools/devtools-frontend/+log/0ed0f013eb02..934a1853595a Generated by: go/bbid/8763701893774194513 Change-Id: I909ffa3509bf35ce3ed78e497c3799eb4a2041c3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5055346 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#986} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Roll Chrome Win64 PGO profile from chrome-win64-6099-1701163313-bd6eb19a924f639aa41dac6c8da0993a52526667.profdata to chrome-win64-6099-1701193739-9db4b5bec934d46bc4031eada43bdaa8d85a595e.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium-beta Please CC chrome-brapp-engprod@google.com,pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium beta branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome-m120.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I593c95c018311d4bf90992668fdb679b4c3fcad2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5067945 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#1188} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
This CL updates the ash version ['121.0.6154.0'] for Lacros version skew testing. This cl only affect linux-lacros config builders like linux-lacros-tester-rel, linux-lacros-rel. This cl will certainly NOT affect Lacros on-device builders (lacros-amd64-generic-rel, lacros-amd64-generic-chrome-skylab, etc) or any other platforms. If this CL caused regressions, please revert and stop the autoroller at https://luci-scheduler.appspot.com/jobs/chrome/lacros-version-skew-roller Also please file a bug to OS>LaCrOS>Partner, and CC svenzheng@chromium.org. R=rubber-stamper@appspot.gserviceaccount.com Bug: None Change-Id: Iecb60ebe1388a70fea01d9260b1d863a42b3f022 Requires-Testing: True Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5067738 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Auto-Submit: chrome-weblayer-builder <chrome-weblayer-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#1189} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Note: I also wrote some additional information and TODOs in [1]. Introducing a new `hasDefaultValue` setting flag, that represents whether there is a default value of the corresponding policy. The main purpose of this is to fix the current duplex settings problems described in the attached ticket. We basically don't want to apply non-sticky settings (i.e. printing destination defaults, document presets, etc.) if there is a policy default for that setting. There are still some caveats that are mentioned in the doc, that I still need to test, but the main idea should remain the same. [1] https://docs.google.com/document/d/1XFa_7pw2M08y5iojYMOImM1e8rJI2SXwdtsvuvwbx08/edit?resourcekey=0-Vf1wlGIhiuEqavBwSws83g BUG=b:282176891 TEST=./browser_tests --gtest_filter="PrintPreviewTest.ModelSettingsPolicyTest:PrintPreviewPolicyTest.DuplexPolicy:PrintPreviewAppTest.PrintPresets:PrintPreviewModelTest.SetStickySettings" TEST=tast run $DUTIP policy.PrintingDuplexModes (cherry picked from commit 1f699bf) Change-Id: Iae15f03a990bd50cc1675c141d8c2dbbc94b290c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4950117 Reviewed-by: Sparik Hayrapetyan <ust@google.com> Commit-Queue: Andrei Nedoluzhko <nedol@google.com> Reviewed-by: Rebekah Potter <rbpotter@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1225396} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5062755 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#1190} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
This is a reland of commit cc0a1f4 The fix for the cause of the revert is to disable OOPPD for Fuchsia, which is done in https://crrev.com/c/5041289. Original change's description: > Incorporate policy override for OOPPD feature > > Add a policy to allow the out-of-process print drivers feature to be > disabled. > > Remove the lower-level printing::features::ShouldPrintJobOop() call for > determining if the feature is enabled. Replace this with //chrome > level queries that use the feature flags and also take the policy into > account. > > Bug: 1497035 > Change-Id: I8b4f10d275dc41d5fe723b9eb1c5d554f6a6388b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4994508 > Reviewed-by: Lei Zhang <thestig@chromium.org> > Commit-Queue: Alan Screen <awscreen@chromium.org> > Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> > Reviewed-by: Owen Min <zmin@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1225761} (cherry picked from commit 661060f) Bug: 1497035 Change-Id: I381b179fc6d370e8a9c01c3cdb51e9ae2c2c9e70 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5041802 Reviewed-by: Owen Min <zmin@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Code-Coverage: findit-for-me@appspot.gserviceaccount.com <findit-for-me@appspot.gserviceaccount.com> Commit-Queue: Alan Screen <awscreen@chromium.org> Reviewed-by: Igor <igorcov@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1226973} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5067003 Cr-Commit-Position: refs/branch-heads/6099@{#1191} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I16208e70db40d4a26d6ea56946591f3a97918c7d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5069314 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: Ib71b2e3d76c9f9bfb8cd9f7846d0e5c7047b6a7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5076733 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#1} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I062cd1182087b595f169a395999b8c10f9b58cb3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5075975 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#2} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
This feature's release is going to be delayed. This CL turns the reporting attestations changes into its own feature flag to prevent blocking the release of the other 2 features wrapped into the M120 feature flag. (cherry picked from commit b73d29d) Change-Id: I47cd860132f39a55e58e7773b9a8a119e331fa14 Bug: 1505572 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5063592 Commit-Queue: Garrett Tanzer <gtanzer@chromium.org> Reviewed-by: Garrett Tanzer <gtanzer@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1229606} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5075023 Owners-Override: Srinivas Sista <srinivassista@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Srinivas Sista <srinivassista@chromium.org> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#3} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I38057354a73ff15ef9d29eb61e32f7ddb85d2506 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5077765 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#4} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I204c022d21c060793048b6e01335ef979b2fcdb3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5077546 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#5} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I9576a6f54b71330cf4a0687dbbd01baccc81afdb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5075276 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#6} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I3adb10d27e17c0e1d9f3e1d8e742230ffd0614d6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5077547 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#7} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Remove CopySharedImageHelper::ReadPixels src_rect dimensions check which causes issues with plx dashboards that create a canvas. The renderer client should ideally create a new shared image with new scaled size but due to incorrect size mismatch the rect size passed in is greater than expected shared image size due to which it fails validation. This change removes validation as a workaround until the appropriate renderer client is updated at which point it should be added back. (cherry picked from commit 6b05d26) Bug: 1502623 Change-Id: I35c5184296928cd3ebd2229fefede4b2ae19550a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5084967 Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Commit-Queue: Saifuddin Hitawala <hitawala@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1233016} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5089952 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Srinivas Sista <srinivassista@chromium.org> Commit-Queue: Srinivas Sista <srinivassista@chromium.org> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#8} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I4ffd9abc6cf41a83c628cbd25200c30adcc86155 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5089629 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#9} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I69f8d0a585a638a9d55fa45432481d9d15658943 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5089908 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#10} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I23439696778bfb34ca8902469e712ef7d60b50c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5088969 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#11} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I7167c2c57ddd27a50d5df6c15d6d99e537c3bdb2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5090288 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#12} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Change-Id: I84582cdd8aee4b231abe5a10060471cd9508ae00 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5089048 Bot-Commit: Chrome Release Bot (LUCI) <chrome-official-brancher@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099_56@{Pissandshittium#13} Cr-Branched-From: 6c113a6-refs/branch-heads/6099@{#1192} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
Susmaster64
suggested changes
Dec 17, 2023
yotoprules
approved these changes
Dec 17, 2023
Alliegaytor
suggested changes
Dec 18, 2023
|
we need Enchanting table script |
Getting someone who knows Georgian in on this for you, he might be able to help |
|
We should translate to ancient Hungarian instead or translate half of it to Latin and half of it to ancient Hungarian. Promoting equality! (Also check out #60) |
Closed
Aikoyori
pushed a commit
that referenced
this pull request
Dec 18, 2023
…120.0.6092.0-r1 to 120-6045.38-1698665925-benchmark-120.0.6099.0-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-arm-chromium-beta Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium Beta Branch: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: Id02ccd5294bf8982721ae265d439bf9b37d7c58a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4996234 Commit-Queue: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Bot-Commit: Chrome Release Autoroll <chromium-release-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/branch-heads/6099@{#17} Cr-Branched-From: e6ee450-refs/heads/main@{#1217362}
|
I agree with neebooo, we need to promote equality. So I think that every word has to be from a different language on the readme! |
|
I second with neebooo, but I suggest that each new word should be in a different unicode glyph |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
if anyone wants to edate please reply in this thread i am gay