- 21 Jan, 2020 40 commits
-
-
Weiliang Chen authored
For Andorid Pre-SurfaceControl, overlay processor can send the overlay candidates directly. This is CL 6/? for sending the overlay candidates directly to gpu thread. R=rjkroege Bug: 979788 Change-Id: I76d97e8c8cfece078f6ea8d90bf8d3e7ae02dbfc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985305 Commit-Queue: weiliangc <weiliangc@chromium.org> Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Cr-Commit-Position: refs/heads/master@{#733619}
-
Jonathan Ross authored
Some of the bugs on Android's vulkan_content_browsertests have been fixed so we will re-enable them. TBR=backer@chromium.org TEST=vulkan_content_browsertests Bug: 1037939, 1043934 Change-Id: I43f0890fb13fdf1abbbd89ce267ca9e40933b8c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008362Reviewed-by:
Jonathan Ross <jonross@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#733618}
-
Henrique Nakashima authored
It is now unused. This was a transitory class to move downstream references to ChromeFeatureList without causing breakages. This is CL 5/5 for moving ChromeFeatureList to the .flags package. Bug: 1041468 Change-Id: Iab7b13219bbd9b808c53f23e40d5e5b064ba20f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003450Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Henrique Nakashima <hnakashima@chromium.org> Cr-Commit-Position: refs/heads/master@{#733617}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/b7dc45f8e811..ccbe95fd8a9e git log b7dc45f8e811..ccbe95fd8a9e --date=short --first-parent --format='%ad %ae %s' 2020-01-21 mbonadei@webrtc.org Reformat GN files. 2020-01-21 kron@webrtc.org Add RtpPacketInfo and RtpPacketInfos to RTC_EXPORT 2020-01-21 hbos@webrtc.org [Overuse] Setting encoder configurations through the interface. Created with: gclient setdep -r src/third_party/webrtc@ccbe95fd8a9e 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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I5834fc1e51cd8e335f46579d2dd1220a02b2ff9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011745Reviewed-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@{#733616}
-
Fredrik Söderquist authored
In SVGImages scripts don't run, so there will be no event handlers there to do anything with the events. There's also no "internal" processing that uses the actual events. This avoids wasting memory when the animation processing ends up with a backlog. Bug: 1021630 Change-Id: Ibf7b3e998b8c130568c359bc284645556b952d4f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012020Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#733615}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/c533f76b91f8..c8ebd366bc29 git log c533f76b91f8..c8ebd366bc29 --date=short --first-parent --format='%ad %ae %s' 2020-01-21 phoglund@google.com Move to protobuf lite. Created with: gclient setdep -r src/third_party/catapult@c8ebd366bc29 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 sadrul@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:1029452 Tbr: sadrul@google.com Change-Id: Ifa9bd872922f275ea5b5ce8ec1ce2e1df860ba42 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012504Reviewed-by:
-
Omer Katz authored
If the v8 marker is fast it can help Oilpan with marking. This is a good opportunity to restart any concurrent markers that died. Bug: 986235 Change-Id: I47cbde413e875206d0cd468699f6309d06222f6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002614 Commit-Queue: Omer Katz <omerkatz@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#733613}
-
Nina Satragno authored
This reverts commit 01116522. Reason for revert: suspected of causing PointerLockBrowserTestWithOptions.UnadjustedMovement to be flaky See bug: 1043985 Original change's description: > Exo: Undo conflation of relative-pointer and pointer-constraints > > When it was first implemented, adding a relative-pointer-delegate would > also enable pointer capture (locking the pointer). > > This change makes it so that the pointer can only be locked through the > pointer-constraints protocol. > > Bug: b/124059008 > Test: exo_unittests, manual testting using ArcPointerCaptureTestApp > Change-Id: Ied0f1c658aa713026e622f4ce26009e261d4f653 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1992355 > Reviewed-by: Mitsuru Oshima <oshima@chromium.org> > Commit-Queue: Prabir Pradhan <prabirmsp@chromium.org> > Auto-Submit: Prabir Pradhan <prabirmsp@chromium.org> > Cr-Commit-Position: refs/heads/master@{#733497} TBR=mukai@chromium.org,oshima@chromium.org,prabirmsp@chromium.org Change-Id: I8581f298f099cb7a9a006a1b578f6345184da1d3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: b/124059008 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012517Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Commit-Queue: Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#733612}
-
Nico Weber authored
`gn format` recently changed its formatting behavior for deps, source, and a few other elements when they are assigned (with =) single-element lists to be consistent with the formatting of updates (with +=) with single-element. Now that we've rolled in a GN binary with the change, reformat all files so that people don't get presubmit warnings due to this. This CL was uploaded by me. Bug: 1041419 Change-Id: I872f425930fdc439c8b807abd87199cea0c058c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012601 Auto-Submit: Nico Weber <thakis@chromium.org> Reviewed-by:
Luke Halliwell (slow) <halliwell@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#733611}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/215c34be2bd3..447a4e0982e0 git log 215c34be2bd3..447a4e0982e0 --date=short --first-parent --format='%ad %ae %s' 2020-01-21 fmalita@chromium.org [skottie] Ensure malformed scalar properties are initialized 2020-01-21 nifong@google.com Don't apply android device clip restriction, only show the viz of it. 2020-01-21 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial). Created with: gclient setdep -r src/third_party/skia@447a4e0982e0 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 benjaminwagner@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: benjaminwagner@google.com Change-Id: Ib16b1438c323a9ff4260dcb646bfe0edbda4f9ba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012501Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ba8cd45333c4..fa01d48c5ced Created with: gclient setdep -r src-internal@fa01d48c5ced 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: I1e7d3aeec5ca47277233faceee307d816ee76145 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012502Reviewed-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@{#733609}
-
Nina Satragno authored
This reverts commit cf53cf16. Reason for revert: suspected of making telemetry.internal.actions.scroll_unittest.ScrollActionTest.testScrollDistanceFastTouch flaky. See bug: 1043966 Original change's description: > Enable scroll resampling on ToT > > Feel free to revert if it causes any regressions. > > Bug: 1000682 > Change-Id: Ia65f85a763d20f906e5bcba1f4c3e565dcb64b15 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011135 > Reviewed-by: David Bokan <bokan@chromium.org> > Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#733458} TBR=bokan@chromium.org,nzolghadr@chromium.org Change-Id: I9afc5803f6604220fc658e4e63776711f51ee190 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1000682 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012507Reviewed-by:
-
Robbie Gibson authored
The last time I changed this line, the CSS was incorrect, so it didn't do anything. Now, it's the correct CSS syntax. I ran this test on the device bot 8 times (5 on upstream bot), and each time, the test in question passed. Fixed: 1041873 Change-Id: I2291330fc8af189322e42ec033097104b26c7faf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003850 Commit-Queue: Robbie Gibson <rkgibson@google.com> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#733607}
-
Stephen Nusko authored
This reverts commit efbba2c9. Reason for revert: We've fixed the release iOS build in http://aosp/1209091 Original change's description: > Revert "Add fake typed TRACE_EVENT macros for IOS and NACL builds." > > This reverts commit 60dfcf2f. > > Reason for revert: > > FAILED: > ../../third_party/perfetto/src/protozero/message_unittest.cc:298:40: error: expected '(' for function-style cast or type construction > MessageHandle<FakeRootMessage> handle(msg); > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ > ../../third_party/perfetto/src/base/test/utils.h:34:30: note: expanded from macro 'EXPECT_DCHECK_DEATH' > GTEST_EXECUTE_STATEMENT_(statement, "PERFETTO_CHECK") > ^~~~~~~~~ > 1 error generated. > > https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8891267197314487504/+/steps/compile/0/stdout > > Original change's description: > > Add fake typed TRACE_EVENT macros for IOS and NACL builds. > > > > This allows users to not care if tracing is supported on their system. > > > > Bug: 916074 > > Change-Id: I69aa8178bb19f1a65186a2aba4f08699b6ba6ee3 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1953210 > > Reviewed-by: Stephen Nusko <nuskos@chromium.org> > > Reviewed-by: Eric Seckler <eseckler@chromium.org> > > Commit-Queue: Stephen Nusko <nuskos@chromium.org> > > Auto-Submit: Stephen Nusko <nuskos@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#731514} > > TBR=eseckler@chromium.org,nuskos@chromium.org > > Change-Id: Ia0cc5d2a330a408898c6248378726e43ddd8a732 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 916074 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2000964 > Reviewed-by: Dan Beam <dbeam@chromium.org> > Commit-Queue: Dan Beam <dbeam@chromium.org> > Cr-Commit-Position: refs/heads/master@{#731531} TBR=dbeam@chromium.org,eseckler@chromium.org,nuskos@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 916074 Change-Id: Ide0558b46058869eb252f1ff7be8b10c99dac13c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003678Reviewed-by:
Stephen Nusko <nuskos@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Commit-Queue: Stephen Nusko <nuskos@chromium.org> Auto-Submit: Stephen Nusko <nuskos@chromium.org> Cr-Commit-Position: refs/heads/master@{#733606}
-
Lucas Gadani authored
CSP is not enforced while processing a redirect, so the DCHECK needs to reflect that we are doing a redirect (not a response check) or that we are not enforcing frame-ancestors in the browser process. Bug: 1041711 Change-Id: Ib4872e0f8d96c944f14b5b6ed26b9b07008697dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011744 Commit-Queue: Lucas Gadani <lfg@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#733605}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=jlebel@chromium.org Bug: 1042208 Change-Id: I626922c1e97a34e8270e11e2108526c114dc6504 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010785 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Jérôme Lebel <jlebel@chromium.org> Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#733604}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/bfa7cd62..d9e36f4a 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: I94ea8e6ec689baa8023188aa06ec5f1502e10c22 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012042Reviewed-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@{#733603}
-
Lucas Gadani authored
Bug: 1041133 Change-Id: Id870fb9d34debfce3ebfbaacca0dff73290cf296 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011281Reviewed-by:
-
Andreas Haas authored
The ArrayBuffer is the destination here, so, it the destination is bigger than expected until now, it should not be a problem. R=haraken@chromium.org Bug: chromium:1008840 Change-Id: I36cc5d708411c586665a9c498ff4fe624efee610 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1975879Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Adam Rice <ricea@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/master@{#733601}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/b24ca5ac742e..8effa4d0637c git log b24ca5ac742e..8effa4d0637c --date=short --first-parent --format='%ad %ae %s' 2020-01-21 tandrii@chromium.org git cl: warn when landing on chromium/src branch-heads. Created with: gclient setdep -r src/third_party/depot_tools@8effa4d0637c 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 agable@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/+/master/autoroll/README.md Bug: chromium:1043225,chromium:753213 Tbr: agable@chromium.org Change-Id: I3194ebbb4e88cf2a9ce8b6d1204cd1bab3134a9f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012239Reviewed-by:
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. Bug: 1042208 Change-Id: I027bdc72608c52aed8414ce1926fe5b4edd7c074 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011820 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#733599}
-
sandromaggi authored
After this change it is possible to completely disable all code execution / changes by disabling the AutofillAssistantChromeEntry feature. This also goes for the AutofillAssistant code, waiting for initial navigation. This CL also removes the temporary workaround that was setting the fallback URL in code if it was missing in the intent. Bug: b/145195894 Change-Id: Ic35b799603c633a310171d9f40574e3ff8d79b7f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007696 Commit-Queue: Sandro Maggi <sandromaggi@google.com> Reviewed-by:
Mathias Carlen <mcarlen@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#733598}
-
Sylvain Defresne authored
Instead of forward declaring ChromeBrowserState in the ios namespace, use a header. This will allow moving the class to the global namespace without having to change all the forward declaration at the same time. This CL was uploaded by git cl split. R=jlebel@chromium.org Bug: 1042208 Change-Id: I9890a8a1f34b406148f8f6c37d22a6839b03a5db Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007727 Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
-
Sylvain Defresne authored
https://gn.googlesource.com/gn/+log/0c5557d173..83dad00afb 83dad00 Add a sample project that allow to target iOS abea271 Consider Xcode console as not a tty a09ec16 Improve support for frameworks in gn e214b5d Add support for ':' in --gtest_filter to gn_unittests Bug: 1037607, crbug.com/gn/119 Change-Id: I0d722f9b66a34c2bc641b8266e4160002b988288 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010951 Commit-Queue: Nico Weber <thakis@chromium.org> Auto-Submit: Sylvain Defresne <sdefresne@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#733596}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/e07936314c2b..215c34be2bd3 git log e07936314c2b..215c34be2bd3 --date=short --first-parent --format='%ad %ae %s' 2020-01-21 reed@google.com SkMScalar is obsolete -- use SkScalar Created with: gclient setdep -r src/third_party/skia@215c34be2bd3 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 benjaminwagner@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: benjaminwagner@google.com Change-Id: Iae1bb65a1eae779f1bb85d4f5a67ae787d226abc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012231Reviewed-by:
-
Rushan Suleymanov authored
Add SharingMessageBridge without wiring it. The bridge does not store any data on persistent storage. Bug: 1034930 Change-Id: I0b19a136a2cc8a3e9ec11b7c1bb0f0b629996e52 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002524Reviewed-by:
Alex Chau <alexchau@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Reviewed-by:
vitaliii <vitaliii@chromium.org> Commit-Queue: Rushan Suleymanov <rushans@google.com> Cr-Commit-Position: refs/heads/master@{#733594}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/cda267031787..b5315e84d143 git log cda267031787..b5315e84d143 --date=short --first-parent --format='%ad %ae %s' 2020-01-21 aerotwist@chromium.org Revert "Updates node to latest LTS" Created with: gclient setdep -r src/third_party/devtools-frontend/src@b5315e84d143 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: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I85496d6aa34dec9f03d4bfb895fc2415219e842c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012236Reviewed-by:
-
Peter Marshall authored
The V8 CPU profiler schedules SIGPROF signals. It is very likely that the signal handler for these will run while the throttling signal handler is already running. V8 can't properly read the stack when there is already a signal handler present. Fix this by using sa_mask to block V8's SIGPROFs while the throttling handler is running. This makes more sense overall as well. Our CPU samples would be skewed by whichever stacks we encounter during throttling pauses. Bug: 1027242 Change-Id: I80e856ce1e7b4744a9af7e36c2022b6d8610cf60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012280Reviewed-by:
Sigurd Schneider <sigurds@chromium.org> Reviewed-by:
Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Peter Marshall <petermarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#733592}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/6c13fd907145..b7dc45f8e811 git log 6c13fd907145..b7dc45f8e811 --date=short --first-parent --format='%ad %ae %s' 2020-01-21 mbonadei@webrtc.org Update check_package_boundaries. 2020-01-21 mbonadei@webrtc.org Remove android_junit_tests from the main BUILD.gn file. Created with: gclient setdep -r src/third_party/webrtc@b7dc45f8e811 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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I286f6c7631e3e436d7188e2a1e40e8f332952b23 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012232Reviewed-by:
-
Omer Katz authored
Restarting the markers only checked if the marking worklist is not empty and ignored the write barrier worklist. Also, moved the check so that it's physically next to the concurrent marking method so hopefully if someone changes one in the future, they will the next one right next ot it and change that too. Bug: 986235 Change-Id: I8ce9dc66f0da4bfb1a4f0a37f56b3cdecdb0d0d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006351 Commit-Queue: Omer Katz <omerkatz@chromium.org> Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1fcd8171290b..ba8cd45333c4 Created with: gclient setdep -r src-internal@ba8cd45333c4 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: Ib110a619cd3d6be291611b74b7c1d1b6e673c919 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012233Reviewed-by:
-
Mohamed Amir Yosef authored
This CL introduce the method PasswordFormManagerForUI::MoveCredentialsToAccountStore() which would be called upon user invocation of the migration flow in the UI, and wires the call to the PasswordSaveManager. This CL doesn't introduce the invocation logic or the UI pieces. Bug: 1032992 Change-Id: I6e887bb1a363d45fc15152a52e6cec5db0e00c59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012022 Commit-Queue: Mohamed Amir Yosef <mamir@chromium.org> Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#733588}
-
Pâris MEULEMAN authored
Follow up of https://chromium-review.googlesource.com/c/chromium/src/+/2007821 Add an expectation for bug tracked by crbug.com/1040059. The test case was split in two and the crash wrongly assumed to occur only on half of the splited test. Also remove a related test that does not timeout anymore. Bug: 1042199 Change-Id: I133b4205cb6348ea32864498634c58731da12c6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012282Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/056f1769..bfa7cd62 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: I3550637be078dc32a5c9b23a1c553a9dfc666bc3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012041Reviewed-by:
-
Nazerke authored
This CL modernizes the SendTabToSelfCoordinator - to use the superclass -initWithBaseViewController:browser: initializer, instead of -initWithBaseViewController:browserState:. - to remove the public property for dispatcher and use the dispatcher from self.browser with HandlerForProtocol. Bug: 1029346 Change-Id: Ie5e0c65148fe374bf388a2eb4e85c7e070e3f0b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011104Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Nazerke Kalidolda <nazerke@google.com> Cr-Commit-Position: refs/heads/master@{#733585}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/8265f5d3dc2a..cda267031787 git log 8265f5d3dc2a..cda267031787 --date=short --first-parent --format='%ad %ae %s' 2020-01-21 aerotwist@chromium.org Updates node to latest LTS Created with: gclient setdep -r src/third_party/devtools-frontend/src@cda267031787 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: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I5dfa4dc0a4539f01be6008bdb7ae4687f33d529b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012226Reviewed-by:
-
Chromium WPT Sync authored
Using wpt-import in Chromium 8294a64a. With Chromium commits locally applied on WPT: 0f8fd66b "[WPT/common/security-features] Support sub projects and split referrer-policy 4K tests" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: jochen@chromium.org, estark@chromium.org: external/wpt/referrer-policy NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: Id0c8c2f6272adbba982892ec6db8dc4d60f9fbf9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012040Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#733583}
-
Maksim Moskvitin authored
PeopleHandler somehow gets destroyed after ProfileSyncService shutdown, so |auth_manager_| is nullptr during its destruction. This caused the crash in GetDisableReasons(). Fix is to simply check |auth_manager_| before dereferencing. Avoiding PSS usages after shutdown would be cleaner fix, but it's not clear why they happen atm. Bug: 1043642, 906995 Change-Id: Id6d54a2edee1210a579e36b2b771d360c8c40474 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011220 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
-
Vadym Doroshenko authored
PasswordFormManager needs to be updated for the subsequent projects: 1.Suggesting saving in case when there is no HTML submission. 2.Saving manual fallbacks. Bug: 1042196 Change-Id: Ie0bc33b1a7974930a65ddce611b3444542a35fcb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007412Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#733581}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/73a7576e7efb..1fcd8171290b Created with: gclient setdep -r src-internal@1fcd8171290b 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: I6b75c84283fa544a293ec63cad85f313cc6a2eb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2012224Reviewed-by:
-
