- 07 Dec, 2020 40 commits
-
-
Jae Hoon Kim authored
Bug is fixed and stale logging + TODO lingering. BUG=chromium:851151 Change-Id: I9366d12c40a37fb55fa0c099c1dbf89c3dfb740e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575878Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Jae Hoon Kim <kimjae@chromium.org> Cr-Commit-Position: refs/heads/master@{#834371}
-
Adam Langley authored
https://github.com/w3c/webauthn/pull/1530 specifies a method for encoding language and direction information in strings that will be stored on authenticators. Since we may start to see this in credentials in the wild, this change adds examples to the UI test so that we see what they'll look like. (On Linux, at least, they at least don't render as garbage or crash. However the zh-Hant example doesn't display, possibly because I'm missing suitable fonts.) Change-Id: I9e778a08df85b8ae34032341c6bcd84291ff210c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576795 Commit-Queue: Martin Kreichgauer <martinkr@google.com> Auto-Submit: Adam Langley <agl@chromium.org> Reviewed-by:
Martin Kreichgauer <martinkr@google.com> Cr-Commit-Position: refs/heads/master@{#834370}
-
Ben Pastene authored
Many of these were disabled during failures while the tests were fixed. And after fixing, they were never re-enabled. So this aggressively re-enables any that are now passing. Bug: 1097630 Bug: 1051059 Bug: 1062289 Bug: 1056163 Bug: 1059426 Bug: 1073084 Bug: 1114654 Bug: 1098810 Bug: 1114752 Bug: 1131304 Bug: 11484015 Change-Id: If3270bdfc4f4516af762ae1d92b3215e4b3cffa3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570538 Commit-Queue: Ben Pastene <bpastene@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#834369}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1607341806-34092e6e948e6283aae1770f567faca0b14a9512.profdata to chrome-linux-master-1607363880-fd3f1baf2a5dc6b74a86d40eb9ec18d09a3815d8.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: Ie02b3d373fcf71ed8e53d217a2c2a5602ba83005 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575773Reviewed-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@{#834368}
-
Moe Ahmadi authored
A previous CL with the same title added trial testing config for Desktop only. This CL adds the same config for Android. Prestable experiment: http://shortn/_ZyDTi78UyT Bug: 1096615 Change-Id: I2fb5b8752b814d70e1ad549f95381e3c9aa17947 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575041Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#834367}
-
Moe Ahmadi authored
This reverts commit 3bfb8a37. Reason for revert: crbug.com/1156059 Fixed: 1156059 Original change's description: > [realbox] Makes all text in realbox impossible to select > > crrev.com/c/2566505 made all text in realbox dropdown unselectable. > > This CL extends that to the realbox placeholder as well. Note that > non-placeholder text in the realbox input remains selectable after > this change. > > Fixed: 1154576 > Change-Id: I80d13521680a165c56e2a7d98eff82c885ff3da4 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572680 > Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> > Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> > Auto-Submit: Moe Ahmadi <mahmadi@chromium.org> > Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#833512} TBR=mahmadi@chromium.org,tiborg@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com # Not skipping CQ checks because original CL landed > 1 day ago. Change-Id: Ic569859f08ba8ee7bc0d82cd4671088f3f4348d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577600Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#834366}
-
Morten Stenshorne authored
We *should* indeed consider moving the code for handling hits outside of atomic inlines, but NGPhysicalBoxFragment::PositionForPoint() isn't the right place for it. If we have an inline-block with a child text node that overflows it, and we hit such overflowing text, we'll perform NGPhysicalBoxFragment::PositionForPoint() directly on the inline block (from HitTestResult::GetPosition()), even if it's the text that we hit. We cannot require that we are within the border box of the inline-block in such cases. This check needs to be performed before entering non-atomic inline children - probably in NGInlineCursor::PositionForPointInChild(). At some point, that code should stop calling LayoutObject::PositionForPoint(), and rather call NGPhysicalBoxFragment::PositionForPoint(). That would be a good time to clean up this. Bug: 1155948 Change-Id: I0391f87d4bbf97c7cdd6a15ab2648aefa2d2abbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577199Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#834365}
-
Chris Thompson authored
The new Sogou hostname supports HTTPS without certificate errors. Bug: 869667 Change-Id: I6e8d9e8149bb995be4d91aae12eeda6dfb4d6ccc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570118Reviewed-by:
Orin Jaworski <orinj@chromium.org> Commit-Queue: Chris Thompson <cthomp@chromium.org> Cr-Commit-Position: refs/heads/master@{#834364}
-
CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-betty-pi-arc-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-eve-chrome CQ_INCLUDE_TRYBOTS=luci.chrome.try:chromeos-kevin-chrome TBR=chrome-os-gardeners@google.com Change-Id: I57985e0d4c6c14f46583b8d882cf232874a52e04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575600Reviewed-by:
ChromeOS bot <3su6n15k.default@developer.gserviceaccount.com> Reviewed-by:
-
Reid Kleckner authored
The compile step currently takes around 10 hours. We get more value from this bot cycling more quickly than we get from the extra coverage of building all targets. Make this bot build the chromium_builder_asan target instead of `all` to match the Windows ASan bots and the main Mac ASan bot. R=aeubanks@google.com, hans@chromium.org Bug: 1151435 Change-Id: I1b954427126e36f5f83826b259d785bd84c8ff86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2555699Reviewed-by:
Nico Weber <thakis@chromium.org> Commit-Queue: Reid Kleckner <rnk@chromium.org> Cr-Commit-Position: refs/heads/master@{#834362}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/c56ea91f6bd1..e1502e7972cb If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I353eab6f3e9169af9b6e8a678230ff3c4b8184f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577604Reviewed-by:
-
Alison Maher authored
It was decided that the containing block chain goes directly from a column spanner to the multi-column container. Thus, if an absolute positioned element is nested inside a spanner, we should begin looking for its containing block starting with the multi-column container, as well. This is an update to the previous legacy behavior, and the related web test has been updated to reflect the new behavior. Bug: 1079031 Change-Id: Ia9f60107417158c32d78e12a1d414181411ecb0a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568852 Commit-Queue: Alison Maher <almaher@microsoft.com> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#834360}
-
Norman Rosas authored
and removed duplicated metadata from OWNERS files Bug: 1113033 Change-Id: I51e9d4560200bfe305c4bdbfd6ecdf9c1c78f802 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2573676Reviewed-by:
Dirk Pranke <dpranke@google.com> Commit-Queue: Norman Rosas <normando@google.com> Cr-Commit-Position: refs/heads/master@{#834359}
-
Robbie McElrath authored
This CL renames most of WebLayer's Site Settings files to just Settings in preparation of introducing more Settings UIs. This introduces a new ISettingsFragment rather than renaming ISiteSettingsFragment because renaming the interface results in a "SecurityException: Binder invocation to an incorrect interface" exception when launching Site Settings. Bug: 1106393 Change-Id: Ifbeb15a8ff51776a901e0136dfbdcb4b19543a39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572689 Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#834358}
-
Reilly Grant authored
The manual data transfer tests are known to work on all platforms while the tests which generate error conditions do not. Break these up in order to simplify regression testing. Bug: 884928 Change-Id: I8b8e5559fe7babf21395b3c836ff8ff0f60be8b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576080 Commit-Queue: James Hollyer <jameshollyer@chromium.org> Reviewed-by:
James Hollyer <jameshollyer@chromium.org> Auto-Submit: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#834357}
-
Ben Pastene authored
crrev.com/i/3452789 allocates the machines for this. Bug: 1146481 Change-Id: I0c271016eae64d0e99f205b31efe635cf707cd4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576949Reviewed-by:
Haiyang Pan <hypan@google.com> Commit-Queue: Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#834356}
-
Jan Wilken Dörrie authored
This change prepares //mojo and //ipc for the upcoming switch of base::string16 to std::u16string by replacing current Windows only usages of base::string16 with std::wstring. Furthermore, it adds a std::wstring specialization of IPC::ParamTraits. Bug: 911896 Change-Id: If09078ba43a381f7210f89bba04a729024812d1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572842Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#834355}
-
Azeem Arshad authored
This fixes issue with eSIM networks incorrectly appearing in pSIM group. This was caused because the eid property was not being checked properly. Bug: 1093185 Change-Id: I9c3f2f72810e186dd35f47dedff61bf7efd2c06b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575149Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Azeem Arshad <azeemarshad@chromium.org> Cr-Commit-Position: refs/heads/master@{#834354}
-
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: I1924d3f068ef89f8c5b48a5e628083c020056700 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575766Reviewed-by:
-
Tibor Goldschwendt authored
This is a reland of 0b7367ff with a fix for msan builders, which failed on the original change. See https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20MSan%20Tests/26482/steps?succeeded=false&debug=false Original change's info: > Change-Id: I735506c3e0efff1f92582498400bea0a914cf215 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566374 > Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> > Reviewed-by: Moe Ahmadi <mahmadi@chromium.org> > Reviewed-by: Caitlin Fischer <caitlinfischer@google.com> > Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> > Cr-Commit-Position: refs/heads/master@{#833561} TBR=caitlinfischer@chromium.org,mahmadi@chromium.org Bug: 1110075 Change-Id: Ic311a03eb09860d0cc8b40c55f93bb97caa095bb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576788Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#834352}
-
Ken Rockot authored
Bug: 1004256 Change-Id: I5e835e779fcd6e6096886d7bf38869ae19e25bd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2569384Reviewed-by:
calamity <calamity@chromium.org> Reviewed-by:
Daniel Rubery <drubery@chromium.org> Commit-Queue: Daniel Rubery <drubery@chromium.org> Auto-Submit: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#834351}
-
manukh authored
This does not enable the drive feature by default as it's currently limited to enterprise users. Sets: - DocumentUseClientScore to true - DocumentProviderMaxQueryLength to 200 - DebounceDocumentProviderDelayMs to 300 Change-Id: Idf85fcf6b25a844b196fa5ae82d5ac7617e6dad9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575378 Commit-Queue: manuk hovanesian <manukh@chromium.org> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Cr-Commit-Position: refs/heads/master@{#834350}
-
Shawn Gallea authored
This removes the burden of parsing from the client. Bug: b/169054926 Test: On device Change-Id: If02b37169aca921429658305284e94738350a822 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574999Reviewed-by:
Kevin Schoedel <kpschoedel@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Shawn Gallea <sagallea@google.com> Cr-Commit-Position: refs/heads/master@{#834349}
-
Shrek Shao authored
Reland "Fix readPixels incorrectly allowing RGBA / UNSIGNED_SHORT without EXT_texture_norm16 support" This is a reland of 80b096ab The culprit was identified in Issue 1154356. Original change's description: > Fix readPixels incorrectly allowing RGBA / UNSIGNED_SHORT without EXT_texture_norm16 support > > Add readPixels validation for RGBA / UNSIGNED_SHORT combination. This is > only valid with EXT_texture_norm16 extension enabled. > > Bug: 1152259 > Change-Id: I0e10b7d29f3b362c4054500270bbad87dcde599f > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2559797 > Commit-Queue: Shrek Shao <shrekshao@google.com> > Reviewed-by: Kenneth Russell <kbr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#832141} Bug: 1152259, 1154356 Change-Id: Ie9ceed14e705380e9d1d07f008f4ec86ea7b7421 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575048Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Jamie Madill <jmadill@chromium.org> Reviewed-by:
James Darpinian <jdarpinian@chromium.org> Commit-Queue: Jamie Madill <jmadill@chromium.org> Cr-Commit-Position: refs/heads/master@{#834348}
-
Sebastien Lalancette authored
- Increased LinkGeneration timeout from 200ms to 500ms, - Added a new kTimeout LinkGenerationError enum value, - Added LinkGeneration latency UMA logging. - Lots of plumbing of the latency value to allow logging from the same scenario-aware location. - Added a way to force timing out JavaScript execution requests in the FakeFrame class. Bug: 1155329 Change-Id: I396457db946a756c799a4fddb0d7185c3e12b30b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577002Reviewed-by:Tommy Martino <tmartino@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
sebsg <sebsg@chromium.org> Commit-Queue: Sebastien Lalancette <seblalancette@chromium.org> Cr-Commit-Position: refs/heads/master@{#834347}
-
Caroline Rising authored
Bug: 1109316 Change-Id: Id8f9c23c6b1526800ae7366c68cc4c8b4c02a23b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577484 Auto-Submit: Caroline Rising <corising@chromium.org> Reviewed-by:
Charlene Yan <cyan@chromium.org> Commit-Queue: Charlene Yan <cyan@chromium.org> Cr-Commit-Position: refs/heads/master@{#834346}
-
Evan Stade authored
Having a target named "browsertests" means that trying to compile browsertests from the command line, i.e. ninja -C out/Release browsertests will work, when the user probably meant to type ninja -C out/Release browser_tests So the name of the payments target is changed to browser_tests, which is one of two conventions throughout the rest of Chrome. (The other being myfeature_browsertests, which also avoids the afore-mentioned issue.) Now if the user tries to compile `browsertests`, they will see ninja: error: unknown target 'browsertests' Bug: none Change-Id: Ia6b679847744d7edfbfae3b0e20e395e9a4e226b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574751 Auto-Submit: Evan Stade <estade@chromium.org> Reviewed-by:
Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#834345}
-
Alice Gong authored
Expand OAuth2ApiCallFlow class to allow multiple lines of headers & customizable expected http response code BUG=1154032 Change-Id: Ia92533a9e8d0fa08d1156940d232314633057f08 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577004 Commit-Queue: Alice Gong <alicego@google.com> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#834344}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1607341806-857507b5a91b3ce5824fe454e7d197a8b05189bf.profdata to chrome-mac-master-1607363880-e91185c7ee902dd489788046475ba4c3a284e8fb.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: I9211eb9e11042827de3f701504748e4f400c753d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577697Reviewed-by:
-
Leonid Baraz authored
Bug: 1078512 Change-Id: I2a49977934366c11f5d7a5d41f59162f6b93a2c7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574804 Commit-Queue: Leonid Baraz <lbaraz@chromium.org> Reviewed-by:
Sergey Poromov <poromov@chromium.org> Reviewed-by:
Zach Trudo <zatrudo@google.com> Cr-Commit-Position: refs/heads/master@{#834342}
-
Becca Hughes authored
We need the favicon of the page that hosted the Media Feed for the UI so this stores the URL of the favicon in the Media History store. Change-Id: I98148726a2734fadb8106fa124624a37474d9035 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568754 Commit-Queue: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Tommy Steimel <steimel@chromium.org> Reviewed-by:
-
Lijin Shen authored
If a11y is enabled when password is submitted, show infobar instead. Bug: 1153946 Change-Id: Ic5dc35b2596b995e62493fae211aad0c1e191362 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566727 Commit-Queue: Lijin Shen <lazzzis@google.com> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Pavel Yatsuk <pavely@chromium.org> Cr-Commit-Position: refs/heads/master@{#834340}
-
David Tseng authored
R=dmazzoni@chromium.org Change-Id: Ic8c51de3c4ac96cdcc496842a9a3698a976778e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2577543Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: David Tseng <dtseng@chromium.org> Auto-Submit: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#834339}
-
Jeremy Roman authored
This will do a single allocation of the right size. Bug: None Change-Id: I777f61ff740f5d375c8aa461431f92dee1fbb6f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2570412 Auto-Submit: Jeremy Roman <jbroman@chromium.org> Commit-Queue: Daniel Rubery <drubery@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/e1502e7972cb..48b2aad780bf 2020-12-07 lalitm@google.com Merge "perfetto_cmd: remove reference to legacy dropbox" 2020-12-07 eseckler@google.com Merge "Add json_agent_label_filter to chrome_config proto configuration." 2020-12-07 primiano@google.com Merge "GN: Add standalone build rules for Windows" 2020-12-07 lalitm@google.com Merge "ui: improve perf of query for CPU stack samples" 2020-12-07 eseckler@google.com Merge "processor: Fix memory leak in MemoryTrackerSnapshotParser" 2020-12-07 lalitm@google.com Merge "Add new dynamic table to look up ancestors of CPU stack samples." If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: Ic3baf8c291f643144cad59ddf3d5663e3a0e9eaf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575762Reviewed-by:
-
Jeffrey Young authored
Privacy notice that searches are powered by assistant is no longer necessary as of crbug.com/1103703. Users now see a single assistant search result with a visible assistant icon that makes it clear that specific search result is powered by assistant. BUG=b:174506130 TEST=Open launcher on new account, search, see no assistant privacy disclosure Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Change-Id: I7a587218cddeb23aec0004478861ec156d29ee72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567093 Commit-Queue: Jeffrey Young <cowmoo@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Reviewed-by:
Rachel Wong <wrong@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/heads/master@{#834336}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/0f0bcb39f3fc..bc7e5ac1c908 2020-12-07 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 29886952..c24aab83 (834077:834189) 2020-12-07 sprang@webrtc.org Update how FEC handles protection parameters for key vs delta frames. 2020-12-07 alessiob@webrtc.org AGC2: Fix GetAvailableCpuFeatures() If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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: webrtc-chromium-sheriffs-robots@google.com Change-Id: I9480c297858830dbd5b0d24bb525513e2fee77e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576014Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/95a2d3216488..9f2e7d4d1359 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 ellyjones@google.com,avi@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: ellyjones@google.com,avi@google.com Change-Id: I52eaad6c75961e5b2dccfba194be5cba60592023 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2576015Reviewed-by:
chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#834334}
-
John Abd-El-Malek authored
Change-Id: Ib46c3dfbcbd26ec3338d5aace58a670c9eaf33d0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2574753 Commit-Queue: John Abd-El-Malek <jam@chromium.org> Commit-Queue: Robbie McElrath <rmcelrath@chromium.org> Auto-Submit: John Abd-El-Malek <jam@chromium.org> Reviewed-by:
Robbie McElrath <rmcelrath@chromium.org> Cr-Commit-Position: refs/heads/master@{#834333}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/88efddc6a162..4565794f5eda 2020-12-07 cduvall@chromium.org Add ProcessCreateToApplicationStart metric to androidStartup If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC wenbinzhang@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:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: chromium:1150600 Tbr: wenbinzhang@google.com Change-Id: I9a2b627e8cfc841d9d4d906a480169c83c56865b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2575834Reviewed-by:
-
