- 18 Dec, 2019 40 commits
-
-
Francois Doray authored
Failures were due to a race in Mojo notifications for renderer tear-down and setup. Let's see if the problem still exists. Bug: 874851 Change-Id: Ia28012b8189a5236879abf444bac9295d9159453 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972532 Commit-Queue: Chris Hamilton <chrisha@chromium.org> Reviewed-by:
Chris Hamilton <chrisha@chromium.org> Cr-Commit-Position: refs/heads/master@{#725966}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ddd35ae7e933..a8a5c96f0b89 Created with: gclient setdep -r src-internal@a8a5c96f0b89 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I977ff88397c8783f2c69169a745e6f07de7bafe5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973935Reviewed-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@{#725965}
-
Kaan Alsan authored
This is a speculative fix to try to deflake the layout test on Mac. Bug: 1034789 Change-Id: I8fff3f743f079ec593fb76f6797f7dc955022aab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973960Reviewed-by:
Majid Valipour <majidvp@chromium.org> Commit-Queue: Majid Valipour <majidvp@chromium.org> Cr-Commit-Position: refs/heads/master@{#725964}
-
Matt Menke authored
Previously, it would make NetworkIsolationKeys replace hostnames with eTLD+1's regardless of scheme. Bug: 1030824 Change-Id: I79889920ed99f8d13d7a470e6aa2b2f7ac480f6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972577Reviewed-by:
Shivani Sharma <shivanisha@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#725963}
-
Robert Sesek authored
Change-Id: I8017b1b14fa3d83abb2dfd3b59dc7ffcc84c0696 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972290Reviewed-by:
ccameron <ccameron@chromium.org> Commit-Queue: Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#725962}
-
Julian Pastarmov authored
BUG=996079 Change-Id: Ifb9ea9b56322ba9cbc0086b94d33894f3b90036e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1952324 Commit-Queue: Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Reviewed-by:
Gustavo Sacomoto <sacomoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#725961}
-
Antonio Gomes authored
... to use the corresponding WTF::Bind constructions. BUG=787254 R=haraken@chromium.org Change-Id: Iec27b7bf28c3c1504cb068383e0196e698e2ca25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973991 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Commit-Queue: Kentaro Hara <haraken@chromium.org> Auto-Submit: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#725960}
-
Alexander Dunaev authored
This CL fixes the logic broken in 1962258 that lead to nullptr dereference. R=thomasanderson@chromium.org Bug: 1014860 Change-Id: Iad723c8ab1468455411b0456f5fb016fc880b12d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973432 Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#725959}
-
Roman Sorokin authored
Bug: 1035376 Change-Id: Ieb26a3441e2595b60f4d4d865c4a3969b3e143ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973911Reviewed-by:
Roman Aleksandrov <raleksandrov@google.com> Commit-Queue: Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#725958}
-
Denis Kuznetsov authored
In order to extract some browser tests to a separate build target we need to reduce circular dependencies in code. This CL is a prerequisite for extracting profile_helper to public part of /c/b/chromeos/BUILD.gn that can be used by child dependencies without introducing dependency cycles. Changes not in c/b/chromeos/profiles fixes "include what you use" errors. TBR=sky@chromium.org Bug: 1030832 Change-Id: I8003412d364554681b4a1a69c0cf45101d184c7e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971925Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Denis Kuznetsov [CET] <antrim@chromium.org> Cr-Commit-Position: refs/heads/master@{#725957}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/2abdc799d974..0a3fbd76a9e7 git log 2abdc799d974..0a3fbd76a9e7 --date=short --first-parent --format='%ad %ae %s' 2019-12-18 bmeurer@chromium.org Remove restriction to eager (popover) evaluation. Created with: gclient setdep -r src/third_party/devtools-frontend/src@0a3fbd76a9e7 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@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/+/master/autoroll/README.md Bug: chromium:1033022,chromium:995036 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I5b26dd5a087473ffa74b792562403b85d1928318 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973934Reviewed-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@{#725956}
-
Mike Wittman authored
pthread_getattr_np requires a following pthread_attr_destroy, which was missing in GetThreadStackBaseAddressImpl(). Change-Id: Ic6a59e5be834a4d4c0f981a3a60cab1b3926cfa2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972264 Auto-Submit: Mike Wittman <wittman@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Reviewed-by:
Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/master@{#725955}
-
Antonio Gomes authored
... to use the corresponding WTF constructions. BUG=787254 R=haraken@chromium.org Change-Id: I596f10d9037e007d703d4ac22cbf885769f05f96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973990 Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Commit-Queue: Kentaro Hara <haraken@chromium.org> Auto-Submit: Antonio Gomes <tonikitoo@igalia.com> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#725954}
-
Yuki Shiino authored
Bug: 839389 Change-Id: I6534da9053796ea18f7dd02aa5673cf4072187c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971665Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#725953}
-
Sylvain Defresne authored
Chrome and WebView shell can use provider from internal. Those provider may be based on private framework that export the same symbols as MaterialComponents framework. Provide gn variable to control whether the framework is linked or not. If MaterialComponents is built but not linked, then it is the responsibility of the provider to export the necessary symbols. Bug: 1017165, 1022981 Change-Id: I374bde66a41c956b3cd14d3bb14f8c8e77bfbe3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971847 Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
Yuwei Huang <yuweih@chromium.org> Cr-Commit-Position: refs/heads/master@{#725952}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/21df075cab00..e6a2ad81ab40 git log 21df075cab00..e6a2ad81ab40 --date=short --first-parent --format='%ad %ae %s' 2019-12-18 rmistry@google.com Build and push skia-release and skia-wasm-release docker images Created with: gclient setdep -r src/third_party/skia@e6a2ad81ab40 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 borenet@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/+/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 Bug: None Tbr: borenet@google.com Change-Id: Ib34926eb4d97c7767c2135facf355c9c332b4644 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973930Reviewed-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@{#725951}
-
Clemens Arbesser authored
This CL also changes potentially problematic vector graphics in a test to standard raster graphics. Bug: 1033877 Change-Id: I46ac4434563693fe7fa6633135efeed44c9085f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972143 Auto-Submit: Clemens Arbesser <arbesser@google.com> Reviewed-by:
Sandro Maggi <sandromaggi@google.com> Commit-Queue: Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#725950}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/5b3d06c520db..3be20911d9a3 git log 5b3d06c520db..3be20911d9a3 --date=short --first-parent --format='%ad %ae %s' 2019-12-18 lalitm@google.com trace_processor: fix compile on Android 2019-12-18 lalitm@google.com trace_processor: fix compile 2019-12-18 lalitm@google.com Merge "trace_processor: migrate heap profile allocation table" 2019-12-18 fmayer@google.com Merge "Use unique_ptr instead of FreeLine." Created with: gclient setdep -r src/third_party/perfetto@3be20911d9a3 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/+/master/autoroll/README.md Bug: None Tbr: perfetto-bugs@google.com Change-Id: I4fde3189e8fad7f8033f5a24cb867e36dc4824d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973933Reviewed-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@{#725949}
-
Alice Wang authored
This CL cleans up the argument resources in ConfirmManagedSyncDataDialog.create. Bug: 1033914 Change-Id: I16dab906eab3612635fd544d12b867b32289fef6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967465 Commit-Queue: Alice Wang <aliceywang@chromium.org> Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Cr-Commit-Position: refs/heads/master@{#725948}
-
Ross McIlroy authored
This CL was created automatically with tools/perf/update_wpr script BUG=1028072 Change-Id: Ieaab4e86a1bb465c7aaa0d757555f4c333fcab1e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971834 Auto-Submit: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#725947}
-
Gyuyoung Kim authored
This CL removes Create() factory functions in //third_party/blink/renderer/modules/push_messaing only when it meets the policy of removing Create() so that we support only one of Create() methods or public constructors in a class. Then, this CL makes all callers use MakeGarbageCollected<Foo> instead. This CL removes below Create() functions, - PushSubscriptionOptions::Create - PushManager::Create Bug: 939691 Change-Id: I2d3d099ceeeea6f027b835ba3229e68d70a4575e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971305Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Rayan Kanso <rayankans@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Cr-Commit-Position: refs/heads/master@{#725946}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a8a2b9c8ebe8..ddd35ae7e933 Created with: gclient setdep -r src-internal@ddd35ae7e933 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: chromium:1032550 Tbr: jbudorick@google.com Change-Id: Iafc9da88ffec4054cdc63a824ad012304a13282c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972428Reviewed-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@{#725945}
-
Gyuyoung Kim authored
This CL removes Create() factory functions in //third_partyb/blink/renderer/core/dom and modules/service_worker only when it meets the policy of removing Create() so that we support only one of Create() methods or public constructors in a class. Then, this CL makes all callers use MakeGarbageCollected<Foo> instead. This CL removes below Create() functions, - TagCollection::Create - TagCollectionNS::Create - NavigationPreloadManager::Create Bug: 939691 Change-Id: I69d62f03aef06174d426f3660847dac7a9ed1041 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973436Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Cr-Commit-Position: refs/heads/master@{#725944}
-
Kaan Alsan authored
The scrolling node's snap container data's snap targets will be updated at the end of scrolling animations (scroll offset animations and snap fling animations) rather than at the start of the animation. This change is necessary because currently if a main-thread scroll offset animation is created it is still possible for an impl-only scroll offset animation to also be created and ticked at the same time; the final offset comes from the animation that ends the latest. Therefore if Animation A starts before Animation B but also ends after Animation B, then the visual offset will be the offset from Animation A, even though the latest snapping target will be from Animation B. This will be followed-up by implementing the same behaviour on the main thread. Bug: 1032717 Change-Id: I6bc2b4ccfa58b935842666c477703ea6131cfdf2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1919422Reviewed-by:
David Bokan <bokan@chromium.org> Reviewed-by:
Majid Valipour <majidvp@chromium.org> Reviewed-by:
Yi Gu <yigu@chromium.org> Commit-Queue: Kaan Alsan <alsan@google.com> Cr-Commit-Position: refs/heads/master@{#725943}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/21be09d8e699..ff3d55c60356 git log 21be09d8e699..ff3d55c60356 --date=short --first-parent --format='%ad %ae %s' 2019-12-18 swiftshader.regress@gmail.com Regres: Update test lists @ 21be09d8 Created with: gclient setdep -r src/third_party/swiftshader@ff3d55c60356 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I569ae9a839a45d5e8ac8d7734dd0a1f1db420f05 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1973647Reviewed-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@{#725942}
-
behdad authored
rendering_representative_perf_tests are added to chromium.gpu for the following bots: - Android Release (Nexus 5X): - "android-marshmallow-arm64-rel" - "gpu-try-android-m-nexus-5x-64" - Mac Release (Intel) & Mac Retina Release (AMD): - "mac-rel" - Win10 x64 Release (NVIDIA): - "win10_chromium_x64_rel_ng" - "win10_chromium_x64_coverage_rel_ng" Bug: chromium:1000837 Change-Id: Ie95539b002c96ffffb055c4fd092a2d4f7d7273f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967928Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Commit-Queue: Behdad Bakhshinategh <behdadb@chromium.org> Cr-Commit-Position: refs/heads/master@{#725941}
-
Yifan Luo authored
Bug: 990862 Change-Id: Ia3e441d6dc9ae53f994d6a6a4080cd46ae4c54e7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1962249 Commit-Queue: Yifan Luo <lyf@google.com> Reviewed-by:
Mike West <mkwst@chromium.org> Cr-Commit-Position: refs/heads/master@{#725940}
-
Christos Froussios authored
We compare a key's creation and last-modified time. A key is intended to be permanent and the two timestamps should always be the same. Bug: 1031797 Change-Id: Icf40993af528f70bea59d168087e67867a08c8bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970315Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Christos Froussios <cfroussios@chromium.org> Cr-Commit-Position: refs/heads/master@{#725939}
-
Santiago Aboy Solanes authored
This CL was created automatically with tools/perf/update_wpr script R=crouleau@chromium.org Bug: 878390 Change-Id: I663d8bfe1b80595ca56c543ec8358565c2a57bbd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1863412 Commit-Queue: Santiago Aboy Solanes <solanes@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#725938}
-
Matt Menke authored
It wasn't being used meaningfully, and we want to remove the class. Bug: 651119 Change-Id: Id4bbde9e44ce2b59f3d1b2bd0936b4938d73c0f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972691Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#725937}
-
Matt Menke authored
It's likely left over from switching the code over to use the network service. Bug: 651119 Change-Id: I2a0a3d6b9973c314a8b82ab7fca5a8b9ef37f644 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972690Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#725936}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b533f1d74117..a8a2b9c8ebe8 Created with: gclient setdep -r src-internal@a8a2b9c8ebe8 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 jbudorick@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I4d0ae3203ee7b254754ca46b6d80fc444482763f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972165Reviewed-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@{#725935}
-
Dan Elphick authored
Pass base_git_hash instead of start_git_hash and end_git_hash since the API has changed: https://chromium-review.googlesource.com/c/catapult/+/1965875 Also changes android bot from android-nexus5x-perf to android-pixel2-perf since the latter has more capacity. Bug: 878390 Change-Id: I6095d549f98cc613be7b0f6d6cb6ec4098e1fc7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971840 Commit-Queue: Dan Elphick <delphick@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#725934}
-
Tim Volodine authored
Add browserstests for testing safebrowsing functionality in weblayer. Tests the following: - that the interstitials are shown for certain threat types, - that no interstitials are shown when the url is considered safe, - interstitials have non-empty html. Note: Currently this kind of testing does not appear to be possible using the weblayer java instrumentation tests. We'll need some testing api infrastructure / helpers for this. BUG=1015418,1034546 TEST=run_weblayer_browsertests --gtest_filter=SafeBrowsingBrowserTest* Change-Id: Ifd6a0659874b9dea0d1ce801091e7e37e38cd4ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970012 Commit-Queue: Tim Volodine <timvolodine@chromium.org> Reviewed-by:
Richard Coles <torne@chromium.org> Cr-Commit-Position: refs/heads/master@{#725933}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/e5c2e047eea2..65e2f03bd23e git log e5c2e047eea2..65e2f03bd23e --date=short --first-parent --format='%ad %ae %s' 2019-12-18 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/SwiftShader fbbfeb700295..21be09d8e699 (17 commits) Created with: gclient setdep -r src/third_party/angle@65e2f03bd23e 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/+/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 Bug: None Tbr: jmadill@google.com Change-Id: Ia651de42be2fd6fe8651bfa29deab1d81135ed6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1972164Reviewed-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@{#725932}
-
Marc Treib authored
It's been enabled by default since M78, time to clean up the code. This also makes ShouldUseActiveSignedInAccount() always return true, so cleaning that up as well. Bug: 983940 Change-Id: I72cc203e374d92839070f0ec5df78ace1db3c9fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1970213Reviewed-by:
Christos Froussios <cfroussios@chromium.org> Reviewed-by:
Jared Saul <jsaul@google.com> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#725931}
-
sandromaggi authored
Aligning the font/color of form expander to the UX for Clank compliance. Before: https://screenshot.googleplex.com/LKXbZ0dWp8m After: https://screenshot.googleplex.com/aiF2i3W3L7w Bug: b/144419528 Change-Id: Ide93f299dbe91c93df65312a9b7074f6ac67a003 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1969572Reviewed-by:
Clemens Arbesser <arbesser@google.com> Commit-Queue: Sandro Maggi <sandromaggi@google.com> Cr-Commit-Position: refs/heads/master@{#725930}
-
Amr Aboelkher authored
A device policy which controls the mouse primary button, whether its the right or the left button on the login screen. Test: 1. Set the login_screen_primary_mouse_button_switch policy to True, check that right click is the primary button. 2. Set the policy to False, check that left button is the primary key. Bug: 956373, 552439 Change-Id: Ia8b949745f06e4c7016c403df44ea06364e36db3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1930803 Commit-Queue: Amr Aboelkher <amraboelkher@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#725929}
-
chrome://safe-browsingDaniel Rubery authored
This CL adds the Safe Browsing reporting events to chrome://safe-browsing. This should help with testing the reporting, since it can now be verified with Chrome alone. Screenshot of new UX: https://screenshot.googleplex.com/Jb47z1BiP1d.png Bug: 1021945 Change-Id: I44b57ed4dca02205f2c5d2d229b0ace7718e8efb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1965018Reviewed-by:
Bettina Dea <bdea@chromium.org> Reviewed-by:
Karan Bhatia <karandeepb@chromium.org> Commit-Queue: Karan Bhatia <karandeepb@chromium.org> Auto-Submit: Daniel Rubery <drubery@chromium.org> Cr-Commit-Position: refs/heads/master@{#725928}
-
Mythri A authored
This CL was created automatically with tools/perf/update_wpr script R=crouleau@chromium.org Change-Id: I40969058290445cafbf6159ee1c746f7cebbf620 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1971922 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#725927}
-