- 26 Nov, 2020 40 commits
-
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1606348564-2a10d807907a5e3f733f66553645eebe78051ddf.profdata to chrome-win64-master-1606359294-62d028a106a735635e7aae23a8570d72056d7dc7.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 Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I8e2b7389995359eb13d0ccc7ee78c50d7f83ea76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561836Reviewed-by:
chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#831291}
-
Nico Weber authored
We need one subprocess for the python invocation anyhow, and plist_util.py can do the conversion without calling another subprocess. No intended behavior change. Bug: 1147069 Change-Id: Iaa46e4e35d8469853e1c454dcd0d11c38c8f6756 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561420 Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Auto-Submit: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#831290}
-
Koji Ishii authored
This patch unifies multiple variants of names that mean the containing |NGPhysicalBoxFragment| to |ContainerFragment|. Bug: 982194 Change-Id: Ie07751d2b0dd9819ee3c829dd06b22613c80d06a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2544328 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#831289}
-
Tal Pressman authored
Change-Id: I4cf8a4123d6a5075b38ffc11ca8cb576a35b981c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560705 Commit-Queue: Tal Pressman <talp@chromium.org> Commit-Queue: Kouhei Ueno <kouhei@chromium.org> Auto-Submit: Tal Pressman <talp@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#831288}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/39b4c86fe914..48a99420a249 2020-11-26 skia-autoroll@skia-public.iam.gserviceaccount.com Roll ANGLE from 130597e10299 to 5850c748b480 (15 revisions) 2020-11-26 skia-autoroll@skia-public.iam.gserviceaccount.com Roll Dawn from 33f29ea9b251 to 9175f00eec91 (8 revisions) 2020-11-26 reed@google.com move local function inside build-flag If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC michaelludwig@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: michaelludwig@google.com Change-Id: I07f43073d12bf3859041446704c98deb5b56c8ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561834 Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/939fcd1a14f5..5850c748b480 2020-11-26 syoussefi@chromium.org Vulkan: Emulated RGB copies in compute 2020-11-26 syoussefi@chromium.org Add a sample shading test to verify FS invocation per sample If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jmadill@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: jmadill@google.com Change-Id: Icd997fc6d0f73e28bc32799a18a4cace701e6d97 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561837Reviewed-by:
-
Kenichi Ishibashi authored
This CL adds retry support for the following methods: * CreateNewRegistration * CreateNewVersion * FindRegistrationForClientUrl * FindRegistrationForScope * GetRegistrationsForOrigin * GetAllRegistrationsInfos * DeleteRegistration * UpdateToActiveState * UpdateLastUpdateCheckTime * UpdateNavigationPreloadEnabled * UpdateNavigationPreloadHeader As a side effect, an expectation in ServiceWorkerContextCoreTest.DeleteForOrigin_UnregisterFail is updated from kErrorFailed to kErrorAbort. This change comes from the fact that the retry mechanism serializes storage operations. Before this CL, the callback of GetRegistrationsForOrigin() in ServiceWorkerContextCore::DeleteForOrigin() was executed before disabling the storage (since tasks could run concurrently). After this CL, the callback is executed after disabling the storage. When the storage is disabled GetRegistrationsForOrigin() returns kErrorAbort. Bug: 1133143 Change-Id: I5409dd70f1eded5f7969766811cd209a0258f59e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2550108 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#831285}
-
Johannes Kron authored
The color space of a received video stream is set differently depending on the codec that is used. Most of the times the webrtc::ColorSpace is set to unspecified, which gets converted to gfx::ColorSpace it becomes BT709. This CL adds a feature flag to make it possible to ignore the color space on the receive side if it's set to unspecified. The change only applies to video frames that are decoded in software. Bug: 1129243 Change-Id: I8a4cc3b62b14b5966e98205eb80050918b6095e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560584Reviewed-by:
Henrik Boström <hbos@chromium.org> Reviewed-by:
Markus Handell <handellm@google.com> Reviewed-by:
Jeremy Roman <jbroman@chromium.org> Commit-Queue: Johannes Kron <kron@chromium.org> Cr-Commit-Position: refs/heads/master@{#831284}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1606348564-46558a518073e70dc3e85439edab882c7abb26f5.profdata to chrome-mac-master-1606370078-7d885d98b006b088405f2200061ab790cdd684ac.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 Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I6dbc4e1013073f41dfb0cd62ca2877665533d8f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562024Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1606348564-f9ad4c8126c0686f48279a254d0d8ff9696d692f.profdata to chrome-linux-master-1606370078-7c7501e8b487527fe67d7dfe908ad76e1903c2ea.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 Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I754ffa95cd14d8019bd27e471f7383a0b87b0481 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562025Reviewed-by:
-
Keishi Hattori authored
std::move(settings) was getting executed before the ThreadControllerWithMessagePumpImpl constructor. This did not cause problems with raw pointers because std::move doesn't clear the source. But when converted to BackupRefPtr, this caused Settings::clock to be null in the ThreadControllerWithMessagePumpImpl constructor. Bug: 1080832 Change-Id: I6a79b0050356dcac81ef42eb9c87ad36fecae588 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2558078Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Bartek Nowierski <bartekn@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/master@{#831281}
-
David Roger authored
This CL merges duplicate sections to simplify the structure of the file Change-Id: I5721bef7c952f4f0f3c5ff946b31d8badcf99004 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560106 Auto-Submit: David Roger <droger@chromium.org> Commit-Queue: Jan Krcal <jkrcal@chromium.org> Reviewed-by:
Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#831280}
-
chromium-autoroll authored
Roll ChromeOS Bigcore AFDO profile from 89-4324.9-1606129869-benchmark-89.0.4335.0-r1 to 89-4324.9-1606129869-benchmark-89.0.4336.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-bigcore-chromium Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: If579bb1f16255eeaf43a3654590e8d2d7afff679 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562023Reviewed-by:
-
Wei Lee authored
This reverts commit 388430e9. Original change's description: > Revert "[CCA] Retained pinned status after migrating to SWA" > > This reverts commit 7e541959. > > Reason for revert: b/173092399 > > Original change's description: > > [CCA] Retained pinned status after migrating to SWA > > > > This CL fixes a bug that the pinned status might be lost after migrating > > CCA to SWA. > > > > Bug: 1144678 > > Test: Manually > > > > Change-Id: I9bf2fd846645a77d8b7a47cbd7b9afc043950943 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516659 > > Commit-Queue: Wei Lee <wtlee@chromium.org> > > Reviewed-by: Alan Cutter <alancutter@chromium.org> > > Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org> > > Reviewed-by: Ben Wells <benwells@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#825255} > > TBR=benwells@chromium.org,alancutter@chromium.org,ortuno@chromium.org,wtlee@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 1144678 > Change-Id: Ib55441a7ef81924a0256429ab5ccd1526cb754ce > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2537739 > Reviewed-by: Wei Lee <wtlee@chromium.org> > Commit-Queue: Wei Lee <wtlee@chromium.org> > Cr-Commit-Position: refs/heads/master@{#827576} TBR=benwells@chromium.org,alancutter@chromium.org,ortuno@chromium.org,wtlee@chromium.org Bug: 1144678, b/173092399, b/173669072 Change-Id: I9aa319659eb81f11b222404c13126d672323001b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2536422Reviewed-by:
Wei Lee <wtlee@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Wei Lee <wtlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#831278}
-
chromium-autoroll authored
Roll ChromeOS Atom AFDO profile from 89-4324.9-1606128713-benchmark-89.0.4335.0-r1 to 89-4324.9-1606128713-benchmark-89.0.4336.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-atom-chromium Please CC c-compiler-chrome@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I7f8e761d6fc26fd6c97f940172250ead52bdba6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2562020Reviewed-by:
-
Minoru Chikamune authored
[The goals of this CL] - kForceWithoutContextObserver should be removed because this is a safe mode during the code freeze. - ApplicationCacheHost will be instantiated before ExecutionContext becomes available. So we can't supply ExecutionContext to HeapMojoRemote. |document_loader->GetFrame()->DomWindow()| returns null when ApplicationCacheHost is instantiated. Bug: 1049056 Change-Id: I55dbe93b7752b4c11153b46965a9f89458ec203d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2291302Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
-
Anton Bikineev authored
Bug: 11297512 Change-Id: Ib368d3f1be9218f418a832624020d6ff4dac33d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560948 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Auto-Submit: Anton Bikineev <bikineev@chromium.org> Reviewed-by:
-
Hitoshi Yoshida authored
Bug: 839389 Change-Id: I8a46b776fef32838bb80dc7235cadf1d63c1db26 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560182 Commit-Queue: Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Auto-Submit: Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#831274}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/fe46597d..1166840d Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I2fff34fab2ebc6ef149381e65fafcce28d7debf4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561787Reviewed-by:
v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: v8-ci-autoroll-builder <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#831273}
-
Wei Lee authored
Since currently it will crash Chrome when launching CCA (SWA version) in guest mode. Since for platform app version of CCA, it is not in the guest mode either, temporarily remove CCA from guest mode until we solve the crash issue. Bug: b/174223194 Test: Enter guest mode and CCA is not in the launcher Change-Id: I10aca86664e84fb70c61d1bc0bef0f8d5da31004 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560348 Commit-Queue: Wei Lee <wtlee@chromium.org> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Auto-Submit: Wei Lee <wtlee@chromium.org> Reviewed-by:
-
Curtis McMullan authored
Add the assistive multi word suggestions flag to CrOS. BUG=1146266 Change-Id: I0409a4efd5de44a7ad4c20e422691b248c317af9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560702Reviewed-by:
Darren Shen <shend@chromium.org> Commit-Queue: Curtis McMullan <curtismcmullan@chromium.org> Cr-Commit-Position: refs/heads/master@{#831271}
-
Lukasz Anforowicz authored
The feature has been in the disabled state since r731113 (Jan 2020) and we don't have any plans to change this - we plan to continue attaching `Origin: chrome-extension://...` request header to POST requests initiated from an extension background page. Bug: 966223 Change-Id: If82600be0f615afd3b5737a8bdc5e3f5b130440a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2557732Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#831270}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-aemu-chromium-autoroll Please CC chrome-fuchsia-gardener@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: Ib92daffdf39d2d8287e168e60b3b9158ec85b057 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561829Reviewed-by:
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1606316157-945260897cb0815b47df3e1edecdf8b6cf6cb896.profdata to chrome-win64-master-1606348564-2a10d807907a5e3f733f66553645eebe78051ddf.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 Please CC pgo-profile-sheriffs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ie914725eb5494621640a999ceb73a13da5139d92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2559978Reviewed-by:
-
Bartek Nowierski authored
There are PartitionRoot::Re/DecommitSystemPages functions that wrap base::Re/DecommitSystemPages and update total_size_of_committed_pages, thus suitable for data pages (as opposed to meta-data, bitmaps, ...). However, the wrappers weren't always used where they could, and this CL makes it more consistent. Also, rename them, to disambiguate from base:: APIs. Change-Id: I0e0e21dc71408294d5f59e3395a133c5a70a1d5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2552328 Commit-Queue: Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
-
Ramin Halavati authored
Web Applications tests are updated to cover ephemeral Guest profiles. Please see go/ephemeral-guest-profiles for more context. Bug: 1125474 Change-Id: Ie60624795a286f0cfbcb6dfed2e8c605d61e6136 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560125Reviewed-by:
Eric Willigers <ericwilligers@chromium.org> Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/master@{#831266}
-
Austin Tankiang authored
Bug: 1139247 Change-Id: I462fcdf8c6c7674fe5b7b5ef03937cd1f7ad80fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560346Reviewed-by:
Noel Gordon <noel@chromium.org> Commit-Queue: Austin Tankiang <austinct@chromium.org> Cr-Commit-Position: refs/heads/master@{#831265}
-
Yunke Zhou authored
Bug: 1152763 Change-Id: I325417cca237f876c77619a22be9ed095b098d5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560626Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Yunke Zhou <yunkez@google.com> Cr-Commit-Position: refs/heads/master@{#831264}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/b9a5e83e55ee..e62621d2eb86 2020-11-26 yyanagisawa@chromium.org Roll out new goma client binary VERSION=209 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC ehmaldonado@google.com,sokcevic@google.com,ajp@google.com,apolito@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: ehmaldonado@google.com,sokcevic@google.com,ajp@google.com,apolito@google.com Change-Id: If9aefe38a36085f918f9c1016ea0c663ee1f8f9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560677Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/goldctl-linux-chromium-autoroll Please CC bsheedy@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: bsheedy@chromium.org Change-Id: I2316b6d53e9c98417998416839a4bd505c6c9041 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2559981Reviewed-by:
-
Yutaka Hirano authored
...as a preparation step to the Transferable Streams optimization. Bug: 1146396 Change-Id: Iaec17e0e96bfc0a9dc0f96f0c0dd2245c5d56db8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2546312 Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#831261}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/4dba276776bd..939fcd1a14f5 2020-11-26 syoussefi@chromium.org Vulkan: Pass in emulated alpha value to ConvertVertex If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC jmadill@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: jmadill@google.com Change-Id: I12cfadeab826ab19f0d26382ab24eec57457750f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561827Reviewed-by:
-
Bartek Nowierski authored
Super pages and direct map have been so far allocated in a fully committed state and most of the pages are made inaccessible immediately after. This CL reverses the process and commits only necessary pages. Change-Id: I136c6ac4e1a0d96564739542e82d65ee1562b2c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2531796 Commit-Queue: Bartek Nowierski <bartekn@chromium.org> Reviewed-by:
Benoit L <lizeb@chromium.org> Reviewed-by:
-
Leo Lai authored
The fact that InstallAttributes gets the owner password could lead potential leak of such an important secret. Thus, while replacing the crypthome API with tpm manager's, we use a more light-weighted status query to only tell if the owner password s present. To test the CL, some test items were added and they are: 1. check the UMA of interest gets reported w/ ownre password. 2. check the UMA of interest gets reported w/o ownre password. 3. fail to check TPM status. BUG=b:172748724 BUG=b:168852740 TEST=chromeos_unittests. Change-Id: I804d94cd0c6a86149ebda293a053d4ffb3cc0492 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2557938 Commit-Queue: Leo Lai <cylai@google.com> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#831258}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/28a1c2ec8223..dee1cdf147f7 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC mxcai@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: mxcai@google.com Change-Id: If22c2766be538da500fd9604aacb748d28f07c80 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2559979Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#831257}
-
Maggie Cai authored
This reverts commit 2b9c5c7c. Reason for revert: This CL is likely the root cause for build failure for linux-chromeos-dbg, starting from https://ci.chromium.org/p/chromium/builders/ci/linux-chromeos-dbg/21474 The failed tests are: InputMethodManagerImplTest.SetLoginDefaultWithAllowedKeyboardLayouts InputMethodManagerImplTest.TestEnableLayoutsNonUsHardwareKeyboard InputMethodManagerImplTest.TestEnableMultipleHardwareKeyboardLayout Original change's description: > Always inject mocks for more hemertic InputMethodManagerImpl unit tests. > > Six InputMethodManagerImpl tests are failing in specific environments > due to mixed usage of test data and CrOS prod configs. Partly caused by > inconsistent usage of MockComponentExtensionIMEDelegateManager. In > particular, parts of Setup() are run without this mock injected. The fix > here ensures the mock and its test data are consistently used throughout. > > With this we manage to un-fail 4 out of 6 tests, but another new test > starts failing! It's unsurprising because these tests still indirectly > depend on deprecated input_methods.txt configs (remnant from before the > migration to extension-based input methods circa 2011). This issue will > be addressed in the next steps. > > Bug: 970790 > Change-Id: I3e76708e34f2b4e021f763654714d157f48a3925 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2550152 > Commit-Queue: Bao-Duy Tran <tranbaoduy@chromium.org> > Reviewed-by: Yuly Novikov <ynovikov@chromium.org> > Reviewed-by: John Palmer <jopalmer@chromium.org> > Reviewed-by: Darren Shen <shend@chromium.org> > Cr-Commit-Position: refs/heads/master@{#831198} TBR=ynovikov@chromium.org,shend@chromium.org,tranbaoduy@chromium.org,jopalmer@chromium.org Change-Id: I4fea5ebf6f46f66ba837d693f7970a0ac8949054 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 970790 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560527Reviewed-by:
Maggie Cai <mxcai@chromium.org> Commit-Queue: Maggie Cai <mxcai@chromium.org> Cr-Commit-Position: refs/heads/master@{#831256}
-
Maggie Cai authored
This reverts commit f42aaef1. Reason for revert: The parent CL of this CL (https://crrev.com/c/2550152) is likely the root cause for build failure for linux-chromeos-dbg, starting from https://ci.chromium.org/p/chromium/builders/ci/linux-chromeos-dbg/21474 The failed tests are: InputMethodManagerImplTest.SetLoginDefaultWithAllowedKeyboardLayouts InputMethodManagerImplTest.TestEnableLayoutsNonUsHardwareKeyboard InputMethodManagerImplTest.TestEnableMultipleHardwareKeyboardLayout Original change's description: > Remove unnecessary ime_list_ in InputMethodManagerImpl unit tests. > > Bug: 1134465 > Change-Id: I32cb2d5d67e6bd102f17578d824028527d1c9bdc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2551869 > Commit-Queue: Bao-Duy Tran <tranbaoduy@chromium.org> > Reviewed-by: Darren Shen <shend@chromium.org> > Reviewed-by: Jing Wang <jiwan@chromium.org> > Cr-Commit-Position: refs/heads/master@{#831202} TBR=shend@chromium.org,tranbaoduy@chromium.org,jiwan@chromium.org Change-Id: I25712769e78d54920f7a80edf316433250012f1d No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1134465 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2560280Reviewed-by:
-
Maggie Cai authored
This reverts commit d1224786. Reason for revert: Suspect this CL breaks the build android-archive-rel. First failure: https://ci.chromium.org/p/chromium/builders/ci/android-archive-rel/16867 Compile error message: expand_owners.Error: The histogram Event.WaylandDragDrop.IncomingDataTransferTime must have a valid primary owner, i.e. a Googler with an @google.com or @chromium.org email address. Original change's description: > [ozone/wayland] Introduced the histogram to track time on data transfer. > > When data is dragged from another application into Chromium, there is a > delay between mouse pointer crossing the window border and the actual > OnDragEnter() called on the window. The delay happens because the > drag drop controller has to get the data, which implies at least one > request to the Wayland server (the actual number of requests equals > number of MIME types available in the data offer). > > Here a histogram is introduced to know what the real delays will be > there in the wild. > > Bug: 1147413 > Change-Id: I2f3acc067f718ccb29d98ea1bf98b9f03efc2f7d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2552864 > Reviewed-by: Robert Kroeger <rjkroege@chromium.org> > Reviewed-by: Alexei Svitkine <asvitkine@chromium.org> > Commit-Queue: Alexander Dunaev <adunaev@igalia.com> > Cr-Commit-Position: refs/heads/master@{#831251} TBR=rjkroege@chromium.org,asvitkine@chromium.org,adunaev@igalia.com Change-Id: I8a9f113d12f7c8ef7e71989cdb3949696a683901 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1147413 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561958Reviewed-by:
-
chromium-autoroll authored
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 a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 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-autoroll Please CC gbiv@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: gbiv@chromium.org Change-Id: I477d29831237a85412b22624a7578ec34858efb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561828Reviewed-by:
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-aemu-chromium-autoroll Please CC chrome-fuchsia-gardener@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: Ie5b1855392623cf850736cb248f05ad31130ccc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2559977Reviewed-by:
-
