- 02 Dec, 2019 40 commits
-
-
Guido Urdaneta authored
Mark GpuProcess_feature_status_under_swiftshader as RetryOnFailure The test has been flaking considerably on Linux. Bug: 1028974 Change-Id: I355dcbac4e5e06508d049c6592930ab366d15caf TBR: kbr@chromium.org No-Try: True Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944681Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Commit-Queue: Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#720525}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/684d2057..6d4b96eb 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,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I1bd35db1c768dc97d00f62308ebd713e4fea1a7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946625Reviewed-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@{#720524}
-
Fredrik Söderquist authored
Move the entries to the Paint section of the file. Change-Id: I4d0e21a96aefe548ced153665c01ee7866ca0e9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944478Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#720523}
-
Joe Downing authored
Change-Id: I54bc8d52aca117778519780ca6abce2622910954 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1926540 Commit-Queue: Joe Downing <joedow@chromium.org> Reviewed-by:
Jamie Walch <jamiewalch@chromium.org> Cr-Commit-Position: refs/heads/master@{#720522}
-
Guido Urdaneta authored
Bug: 1028477 Change-Id: Ib5a18c349023f9db77a2325981f20a21d65b8c01 TBR: petermarshall@chromium.org No-Try: True Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944479Reviewed-by:
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/f6ccb0551532..27076e27131f git log f6ccb0551532..27076e27131f --date=short --first-parent --format='%ad %ae %s' 2019-12-02 hjd@google.com Merge "perfetto-cmd: Reset guardrail state on boot" 2019-12-02 taylori@google.com Merge "Create a reusable thread_state table" Created with: gclient setdep -r src/third_party/perfetto@27076e27131f 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: I8305af4e15ba912c3298dd9f24e51559a82df312 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945357Reviewed-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@{#720520}
-
Daniel McArdle authored
+ Adds 'const' to casts where appropriate + Fixes an unsafe write through one of these non-const pointers Bug: 10278398 Change-Id: I6e7b30806143cbf38109de174e799521f7d1a1cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944282 Commit-Queue: Dan McArdle <dmcardle@chromium.org> Reviewed-by:
Paul Jensen <pauljensen@chromium.org> Cr-Commit-Position: refs/heads/master@{#720519}
-
Finnur Thorarinsson authored
Also use srcCompat instead of src to avoid crash on KitKat. Bug: 1029749, 1029056, 656015 Change-Id: I38cd630dadfc73868dfbca961d0eff0fa4bcce3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944490 Auto-Submit: Finnur Thorarinsson <finnur@chromium.org> Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Commit-Queue: Finnur Thorarinsson <finnur@chromium.org> Cr-Commit-Position: refs/heads/master@{#720518}
-
Raphael Kubo da Costa authored
IWYU. Follow-up to commit 376a18cd ("events: ozone: Remove implicit init from GetKeyboardLayoutEngine"), which broke the non-libc++ non-ozone build: ../../chrome/test/chromedriver/keycode_text_conversion_ozone.cc:34:12: error: no member named 'make_unique' in namespace 'std' std::make_unique<ui::StubKeyboardLayoutEngine>(); ~~~~~^ ../../chrome/test/chromedriver/keycode_text_conversion_ozone.cc:34:52: error: expected '(' for function-style cast or type construction std::make_unique<ui::StubKeyboardLayoutEngine>(); ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^ ../../chrome/test/chromedriver/keycode_text_conversion_ozone.cc:34:54: error: expected expression std::make_unique<ui::StubKeyboardLayoutEngine>(); ^ Bug: 957519 Change-Id: I54d132875ffc65495cde651d40b1ea87b5b0b284 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945176 Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Commit-Queue: John Chen <johnchen@chromium.org> Reviewed-by:
John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#720517}
-
Gordon Guan authored
This fixes two issues with the discardable memory backing trial unit tests: 1. The return value of GetDiscardableMemoryBacking() was memoized on a per-process basis, persisting across tests. This caused the tests to erroneously fail. Since the function was not heavy in the first place, remove the memoization. 2. The ScopedFeatureList was mistakenly initialized after querying trial state, causing the tests to vacuously pass. Move the initialization before the query. This change does not affect the field trial behaviour, and only fixes the unit tests. Bug: 1014513 Change-Id: I200ddd87e4a8dd52ceba730a9e242f2f7167c029 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944607Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Gordon Guan <gordonguan@google.com> Cr-Commit-Position: refs/heads/master@{#720516}
-
Mihai Sardarescu authored
For every account available in the account tracker service, both the Gaia ID and the email are available. The GCM AccountTracker was fetching again the gaia ID from the server on every start-up and every time a new account was added to the profile. This CL removes this useless fetch and changed the GCM AccountTracker to reuse the information already available in the IdentityManager. Additional clean-up to completely remove the GCM AccountTracker would also be good, but I do not know this code well enough to do this cleanup. Fixed: 1028522 Change-Id: I77790a3203a94ea8c7baf19ca0eb2449b096b630 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944492Reviewed-by:
Colin Blundell <blundell@chromium.org> Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#720515}
-
Guido Urdaneta authored
Due to flakiness, disabling this test on Mac and Linux ASAN/TSAN Bug: 1029238 Change-Id: I49d27dffff9b54b03308e1586822f148e9044e44 TBR: altimin@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945177 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by:
-
Sylvain Defresne authored
A framework bundle does not require public headers, so change the ios_framework_bundle template to work if public_headers is empty or undefined. Bug: none Change-Id: Ieac39fd98220d23f5ae6bf99908d19112ef2eb0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944476 Commit-Queue: Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/master@{#720513}
-
Alexander Timin authored
Allow error pages to get a different instance if ProactivelySwapBrowsingInstances flag is enabled. R=nasko@chromium.org,alexmos@chromium.org CC=arthursonzogni@chromium.org, BUG=1026101 Change-Id: Ib3332c5040dc2385e7e9adf1d1f0630a2cbc0071 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1929033 Commit-Queue: Alexander Timin <altimin@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#720512}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/4a339a15d536..b8ec8ea1910d git log 4a339a15d536..b8ec8ea1910d --date=short --first-parent --format='%ad %ae %s' 2019-12-02 chrome-bot@chromium.org Update config settings by config-updater. 2019-12-02 chrome-bot@chromium.org Update config settings by config-updater. Created with: gclient setdep -r src/third_party/chromite@b8ec8ea1910d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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:chromeos-kevin-rel Bug: None Tbr: chrome-os-gardeners@google.com Change-Id: I281b0aeb7ee3f5c399b6f9bb60a75058244d4309 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945356Reviewed-by:
-
Juan Antonio Navarro Perez authored
Bug: 1029008 Change-Id: Iac83b38ae8d0fed31a3717559793607506c3add4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940110Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#720510}
-
Andy Paicu authored
This CL removes the HEADS_UP_NOTIFICATION and QUIET_NOTIFICATION user-facing UI surfaces, namely the "chrome://flags" screen and the chrome notification channels settings screen. This ensure that either by user-intervention or auto-embargo logic, only the mini-infobar will be selected when a quiet UI needs to be shown. Follow-up CL will remove/refactor all the code that has now become useless, related to the ability to display the permission request prompt as a notification. Bug: 1029718 Change-Id: Ib01e50209184c81abb53770e21a3deda9a2228ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946469 Commit-Queue: Andy Paicu <andypaicu@chromium.org> Reviewed-by:
Peter Beverloo <peter@chromium.org> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#720509}
-
Lan Wei authored
When we are handling the consequence touch move events, sometimes, we will coalesce them together, and we need the events' timestamp to decide to which one dispatch first. I use the actual timestamp when the event is generated and about to dispatch in Input.DispatchTouchEvent function. Bug: 1020674 Change-Id: I8a56f6f532df3ca6182c323c6f8c14f4825589e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943107Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/227ae8212a3d..4b5276f1ad99 git log 227ae8212a3d..4b5276f1ad99 --date=short --first-parent --format='%ad %ae %s' 2019-12-02 machenbach@chromium.org [deps] Fix depot_tools url Created with: gclient setdep -r src/third_party/devtools-frontend/src@4b5276f1ad99 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:1026215 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Id7e065938353ed64841fe9d594c619ff8ebe6da3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945354Reviewed-by:
-
Friedrich Horschig authored
This cl increases the height of the touch to fill sheet to show a second suggestion by default. To keep the height consistent, the peeking height for the third suggestion was reduced. It now looks according to the mocks linked in the linked bug. Bug: 1029704 Change-Id: I52bbb15c3ee6cf9bc423a4745168addced02d69d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945172Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Commit-Queue: Friedrich [CET] <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#720506}
-
Stephen Chenney authored
Switch the Render Core UKM sample rate, the number of frames between samples, to be an exponentially decaying value designed to get more early frame samples and exponentially fewer samples as time moves on. This is designed to limit the total sample count while prioritizing updates early in the page lifetime. The parameters have been tuned to give an effectively maximum sample count of 40-50, which is the value indicated as suitable by previous analysis of UKM sample counts. Bug: 1014195 Change-Id: Ic2004030be69514f6499ff6df18dcaac0588785b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1918159 Commit-Queue: Stephen Chenney <schenney@chromium.org> Reviewed-by:
vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#720505}
-
Abhijeet Kandalkar authored
This CL has two goals, 1. Use To<SVGClipPathElement> as new downcast helper 2. Use IsA<SVGClipPathElement>(element) in place of IsSVGClipPathElement(element) Bug: 891908 Change-Id: Ic2972f94fc26db68a5beca96d9ec23ca2ecb218b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1936571 Commit-Queue: Abhijeet | Igalia <abhijeet@igalia.com> Reviewed-by:Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#720504}
-
file:///Maks Orlovich authored
These were discovered by a fuzzer hitting a (recently fixed) DCHECK in consistency checking of browser vs. renderer-side computation. The highest impact of this is just the DCHECK, since it seems like it would get hit on fuzzers a lot (since full-browser ones use file:/// URLs a lot). There is also an actual corner case bug on Android WebView this affects (someone using file:/// URLs and explicitly setting their cookies to have restrictive SameSite); that needs some additional changes which will likely be rolled into refactoring to give site_for_cookies a more sensible type. Bug: 1024615 Change-Id: I766c324960f5e279a6d14743f0d629f99c9c19a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1917965 Commit-Queue: Maksim Orlovich <morlovich@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Lily Chen <chlily@chromium.org> Cr-Commit-Position: refs/heads/master@{#720503}
-
David Roger authored
The unconsented primary account doesn't necessarily change when the Sync confirmation dialog is cancelled. In particular this is the case when PrimaryAccountMutator::ClearPrimaryAccount is called with RemoveAccountOptions::kKeepAll. This CL stops resetting the unconsented primary account as part of the signout process. The unconsented primary account is recomputed anyway when GoogleSignedOut is called. Fixed: 1029701 Change-Id: Id46bb468952efe63170a13872519fcaded076cb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944862 Commit-Queue: David Roger <droger@chromium.org> Reviewed-by:
Monica Basta <msalama@chromium.org> Cr-Commit-Position: refs/heads/master@{#720502}
-
Lucas Furukawa Gadani authored
Bug: 759184 Change-Id: I920cfba1b382c13982531fadb5632dec5b8329f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1942708 Commit-Queue: Lucas Gadani <lfg@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#720501}
-
Mohamed Amir Yosef authored
Bug: 1012203 Change-Id: Ia9c8c9c5ff3b1af120490b52ff153313863ebfd5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944470Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Cr-Commit-Position: refs/heads/master@{#720500}
-
Carlos Caballero authored
MessageLoop is going away soon. This CL was uploaded by git cl split. R=estade@chromium.org Bug: 891670 Change-Id: If3b8d4261b100d60a2788cb1d1a43d2f10d0b170 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944151 Auto-Submit: Carlos Caballero <carlscab@google.com> Reviewed-by:
Evan Stade <estade@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#720499}
-
Andy Paicu authored
Bug: 1028166 Change-Id: I982d2d9b5bba2107df62fa1132af249c004dac10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1932446Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
-
Julie Jeongeun Kim authored
This CL cleans up old Mojo types for mojom::VideoEncodeAcceleratorProvider using PendingRemote instead of InterfacePtr and InterfacePtrInfo. Bug: 955171 Change-Id: Ib2e251f4b690c8b25634da89f586331d7f72d20c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1939134Reviewed-by:
Yuri Wiitala <miu@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#720497}
-
Abhijeet Kandalkar authored
This CL has goal to use IsA<SVGSetElement>(element) in place of IsSVGSetElement(element) Bug: 891908 Change-Id: I88613d67d85f96821fc70441cc24e341b70ce19b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1936620Reviewed-by:
-
Rayan Kanso authored
Bug: 1012339 Change-Id: I82c767d6ae912ce54bebe3d96a29b4878e9854f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1928773 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/3d978726cc5a..ded19c4711b5 Created with: gclient setdep -r src-internal@ded19c4711b5 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:None Tbr: jbudorick@google.com Change-Id: Ib1a75381fc2990610b1f653e8d96f7245f29acc8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946145Reviewed-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@{#720494}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/bc82fb14aab4..8784a9284f65 git log bc82fb14aab4..8784a9284f65 --date=short --first-parent --format='%ad %ae %s' 2019-12-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/SwiftShader fb7ca1d5aca5..b64fbfec4dcd (3 commits) 2019-12-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/spirv-tools/src b334829a91d6..47f3eb42641b (1 commits) 2019-12-02 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/glslang/src 38b4db48f98c..83af46951202 (1 commits) 2019-11-29 amaiorano@google.com Use Vulkan rectangle lines to emulate OpenGL multisampled lines 2019-11-29 syoussefi@chromium.org Ignore .git_cl_description_backup 2019-11-29 syoussefi@chromium.com Update flex and bison binaries for Windows. 2019-11-29 syoussefi@chromium.org Update flex and bison binaries for Linux. 2019-11-29 syoussefi@chromium.org Infrastructure for uploading flex/bison binaries 2019-11-29 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/vulkan-validation-layers/src 61050599ec0f..4fde9b750992 (1 commits) 2019-11-29 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/SwiftShader d6e903bdc9ef..fb7ca1d5aca5 (13 commits) Created with: gclient setdep -r src/third_party/angle@8784a9284f65 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 geofflang@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_optional_gpu_tests_rel Bug: chromium:None,chromium:None,chromium:None,chromium:None,chromium:3419,chromium:3419,chromium:None,chromium:None Tbr: geofflang@google.com Change-Id: I50845379bdf33ffad22c64afa291e5e7c6d64ed3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946261Reviewed-by:
-
Ali Juma authored
This deletes unused content/ #includes in components/safe_browsing. This is a small step towards refactoring this component to make it usable in ios/, where content/ dependencies are forbidden. Bug: 1028755 Change-Id: I0f6888872e7901f944a73ac18c89b573c87046ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940953Reviewed-by:
Varun Khaneja <vakh@chromium.org> Commit-Queue: Ali Juma <ajuma@chromium.org> Cr-Commit-Position: refs/heads/master@{#720492}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/1236f9cb9e83..f6ccb0551532 git log 1236f9cb9e83..f6ccb0551532 --date=short --first-parent --format='%ad %ae %s' 2019-12-02 lalitm@google.com Merge "trace_processor: Replace FATAL with error stat" Created with: gclient setdep -r src/third_party/perfetto@f6ccb0551532 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: I72613a368a178af398f42cdfb421cf2df7eb9743 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946144Reviewed-by:
-
Abhijeet Kandalkar authored
This CL has two goals, 1. Use To<SVGRadialGradientElement> as new downcast helper 2. Use IsA<SVGRadialGradientElement>(element) in place of IsSVGRadialGradientElement(element) Bug: 891908 Change-Id: I2ae9b50ca2eb0617da5fd2838bf95a991fe00a33 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1936617Reviewed-by: -
Guido Urdaneta authored
Add Timeout to http/tests/devtools/compiler-script-mapping.js expectations since the test times out flakily. Bug: 1016772 Change-Id: I3b2b148d03df3c02b94e30f8943c11e30bfde343 TBR: rreverser@google.com No-Try: True Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1946478Reviewed-by:
-
Geoff Lang authored
This test is flaky, most likely because initialization is not occuring. TBR=ynovikov@chromium.org NOTRY=true BUG=1017162 Change-Id: I252aed96b39a7dba2e71257090e48f10d7a1bce4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1944281Reviewed-by:
Geoff Lang <geofflang@chromium.org> Commit-Queue: Geoff Lang <geofflang@chromium.org> Cr-Commit-Position: refs/heads/master@{#720488}
-
Jan Scheffler authored
This cl adds the tests for crrev.com/c/1944331. Fixed: 1029489 Change-Id: I35214f184a1ef53ea8f17b74923f48bd76200102 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943142 Commit-Queue: Jan Scheffler <janscheffler@chromium.org> Reviewed-by:
Tim van der Lippe <tvanderlippe@chromium.org> Cr-Commit-Position: refs/heads/master@{#720487}
-
Carlos Caballero authored
MessageLoop is going away soon. This CL was uploaded by git cl split. R=mcasas@chromium.org Bug: 891670 Change-Id: Ib0e7dffcd366ce0a98793231e11386a83620828c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1945169 Auto-Submit: Carlos Caballero <carlscab@google.com> Reviewed-by:
Miguel Casas <mcasas@chromium.org> Commit-Queue: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#720486}
-
