- 24 Jul, 2019 40 commits
-
-
Mustafa Emre Acer authored
Also add meacer@ as an additional owner to this code. Change-Id: Ie11671ebe049b8c1ac28bc5d63cb24f394d7c17d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717331Reviewed-by:
Tommy Li <tommycli@chromium.org> Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#680638}
-
Daniel Rubery authored
This feature is able to be controlled directly by enterprise policy. This CL adds the prefs and enterprise policy to do so. It also does some restructuring of the RealTimePolicyEngine so that it can check preferences on a per-profile basis. Bug: 986343 Change-Id: I41374f6084aee744a4c828ab912d3e4e092e16c4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713565 Commit-Queue: Daniel Rubery <drubery@chromium.org> Reviewed-by:
Dominic Battré <battre@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Reviewed-by:
Varun Khaneja <vakh@chromium.org> Cr-Commit-Position: refs/heads/master@{#680637}
-
jonross authored
The root cause of compositing/reflections/reflection-on-composited.html failing with Vulkan SwiftShader has been fixed. This updates the test expectations accordingly TBR=backer@chromium.org TEST=compositing/reflections/reflection-on-composited.html TEST=vulkan_swiftshader_blink_web_tests Bug: 979652 Change-Id: I2979d1018b81c0a3d406bd6a822c07c2eac09423 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716618Reviewed-by:
Jonathan Ross <jonross@chromium.org> Commit-Queue: Jonathan Ross <jonross@chromium.org> Cr-Commit-Position: refs/heads/master@{#680636}
-
Aleks Totic authored
Bug: 986567 Change-Id: I0b69e747023a289280de75bfe54003e5fecb5b1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1714151 Commit-Queue: Aleks Totic <atotic@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#680635}
-
Wei-Yin Chen (陳威尹) authored
Bug: 971802 Change-Id: I2453fbb92e9d0e81bf1e42179e664cd9539595b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1705017Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Cr-Commit-Position: refs/heads/master@{#680634}
-
Stefan Zager authored
PaintLayer holds a persistent pointer to PaintLayerScrollableArea, so it's guaranteed that the PaintLayer will be destructed before the PLSA pre-finalizer is called. PLSA::Dispose is called by the PaintLayer destructor to clean up state, and this is the appropriate time to run complex finalizer code such as RunScrollCompleteCallbacks. The other ScrollableArea sub-classes are RootFrameViewport and VisualViewport. They only get destructed when the entire page is being torn down, in which case it's pointless to try and run scroll complete callbacks; so remove that code path for those classes. BUG=983809 R=omerkatz@chromium.org,pdr@chromium.org Change-Id: I28bee057db042ba92bacea62aeeae130b7594fdb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713593Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#680633}
-
Alberto Herrera authored
The PeripheralBatteryTracker is instantiated by ash::Shell and creates one instance of GattBatteryController. The latter creates a GattBatteryPoller object for each new connected Bluetooth Device. Design doc at go/cros-bt-battery. Bug: 785758 Change-Id: If7cda46a95afb36cc631f88047c6a117f0675894 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660098 Commit-Queue: Alberto Herrera <ahrfgb@google.com> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#680632}
-
Christian Biesinger authored
GDB has been updated to version 8.1, so this should not be necessary aymore. Bug: 957374 Change-Id: Id372c263c73eb9447fde1ef68c1e31174875a22e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717240 Auto-Submit: Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#680631}
-
Dana Fried authored
Previous to this change, neither the tabbed pane itself nor its contents pane would report a meaningful accessible name/title. When using accessible keyboard navigation (tab, arrows) to navigate a dialog that had a tabbed pane (such as the site cookies dialog), when entering the tabbed pane a screen reader user would simply hear "tabbed pane", and when using the arrow keys to select the tab, the user would hear the (unspecified) accessible title of the pane view inside the tab, which was usually just "pane" or nothing at all. This CL makes the following changes: - the title of the entire TabbedPane now reflects the currently active tab title - by default, the contents pane of each tab is assigned the same accessible name/title and role as the tab (it can be overridden later if necessary) Now, for example, when using NVDA, when the user first enters the cookies dialog, they hear: "allowed tab control". When navigating between tabs using the arrow keys, they will continue to hear "allowed tab" and "blocked tab" as they switch back and forth. Bug: 962966 Change-Id: I805281bf5429e03ca77f98e167041a5df3cbee8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717228Reviewed-by:
Allen Bauer <kylixrd@chromium.org> Commit-Queue: Dana Fried <dfried@chromium.org> Cr-Commit-Position: refs/heads/master@{#680630}
-
chrome://resourcesdpapad authored
Repro: ninja -C out/<out>/ ui/webui/resources/js:closure_compile_modules Bug: 970885 Change-Id: I2cb9a90b942e8f301f97501f613bbd442f405f5c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1705053Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#680629}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/material-components/material-components-ios/+log/37626243b283..d57b1482fc27 git log 37626243b283..d57b1482fc27 --date=short --no-merges --format='%ad %ae %s' 2019-07-24 wenyuz@google.com Merge branch 'release-candidate' into stable Created with: gclient setdep -r src/ios/third_party/material_components_ios/src@d57b1482fc27 The AutoRoll server is located here: https://autoroll.skia.org/r/material-components-ios-chromium Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:ios-internal-mdc TBR=bling-p10-rolls@google.com Bug: None Change-Id: I1b44cdeb91d44fe11392324c3a9cb96288443d6d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716939Reviewed-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@{#680628}
-
Matt Wolenetz authored
Extends these 4 metrics' expirations to M85. As MSE explicit (and soon, implicit) codec switching becomes more common and as decoders mature (such as AV1), these metrics are useful to monitor basic decoder reconfiguration delays. Media.MSE.CodecChangeTime.Audio.HW Media.MSE.CodecChangeTime.Audio.SW Media.MSE.CodecChangeTime.Video.HW Media.MSE.CodecChangeTime.Video.SW BUG=986527,986528 Change-Id: I71fdcd21d3cff8cd71718b31ee46c9d268ad89fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715913Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: Matthew Wolenetz <wolenetz@chromium.org> Cr-Commit-Position: refs/heads/master@{#680627}
-
Nicolas Ouellet-Payeur authored
This reverts commit 17ccf43e. Reason for revert: suspecting that this makes the presubmit check not run on most CLs (crbug/949382) Original change's description: > [Traffic Annotation] Remove function_context from extractor output > > The new extractor can't trivially determine the name of the enclosing > function, and it didn't bring much value anyways. > > Bug: 966883 > Change-Id: I7b52050730186c6972754d3b9e577d4c4740d5dc > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1686621 > Reviewed-by: Nico Weber <thakis@chromium.org> > Reviewed-by: Ramin Halavati <rhalavati@chromium.org> > Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> > Cr-Commit-Position: refs/heads/master@{#675223} TBR=thakis@chromium.org,rhalavati@chromium.org,nicolaso@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 966883 Change-Id: I0c326313df18b7b05f7a41cd58e6d1e491277ae5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715423Reviewed-by:
Nicolas Ouellet-Payeur <nicolaso@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#680626}
-
Axel Antoine authored
1€ Filter is a simple speed-based low-pass filter for noisy input in interactive systems. See the public page: http://cristal.univ-lille.fr/~casiez/1euro/ It is added to filter the prediction in blink. Bug: 981888 Change-Id: I46687dfd98ef6341edfefaf4782fa537106a283b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691088 Commit-Queue: Axel Antoine <axantoine@google.com> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#680625}
-
Mei Liang authored
Change-Id: I64b96e9121f200a808771ab792e5fe4dac064813 Bug: 987361 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716963Reviewed-by:
Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Mei Liang <meiliang@chromium.org> Cr-Commit-Position: refs/heads/master@{#680624}
-
Jun Mukai authored
The current code nicely creates and destroys the layer of individual app-list item view when dragging the app-list to reveal. This actually invalidates the parent layer and causes during the drag. Creating the layers of all items when the drag starts keeping them as long as the drag continues actually reduce unnecessary repainting because of this. This CL does not change the LauncherDragTest numbers, but it actually decreases the presentation time of dragging significantly on nocturne with my test account -- mean ~110msec to ~65msec. Bug: 987095 Test: manually / ash_unittests Change-Id: Ib26fb9f192832b91237ed155d30f56bae80d76d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717424 Commit-Queue: Jun Mukai <mukai@chromium.org> Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#680623}
-
Livvie Lin authored
Bug: 987407 Change-Id: Ifaa7d2fc1066ef6fe033bf1e93d9bce4284b682b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717426Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Livvie Lin <livvielin@chromium.org> Cr-Commit-Position: refs/heads/master@{#680622}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/9f89d086a26b..aa1f05f439db git log 9f89d086a26b..aa1f05f439db --date=short --no-merges --format='%ad %ae %s' 2019-07-24 benjhayden@chromium.org Remove benjhayden from OWNERS Created with: gclient setdep -r src/third_party/catapult@aa1f05f439db The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. 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 TBR=skyostil@google.com Bug: None Change-Id: Ieee0d2f3820572b6c096a62d2a7f803869cd91ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716938Reviewed-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@{#680621}
-
Rob Schonberger authored
This adds a palm detection filter that interacts with the concept of "held" items. The filters will be used in TouchEventConverterEvdev to either hold or cancel touches, in addition to the behavior from device firmware. The two implementations are: 1. An always "open" detection, that doesn't mark anything to hold/cancel. 2. A simple heuristic that is based on interaction with stylus touches. Both implementations have unit tests that cover 100% of the code. Identical to https://chromium-review.googlesource.com/c/chromium/src/+/1708148 except uses an EXPECT_DCHECK_DEATH instead of EXPECT_DEATH since that fails (obviously) sometimes. Revert of revert https://chromium-review.googlesource.com/c/chromium/src/+/1716389 . Bug: 982118 Change-Id: I3712b905f49218149082c352b939e7b9b6b23c29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715287 Auto-Submit: Rob Schonberger <robsc@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Commit-Queue: Rob Schonberger <robsc@chromium.org> Cr-Commit-Position: refs/heads/master@{#680620}
-
siyua authored
Use the same flag which controls android UI. Bug: 980716 Change-Id: Ief150b48c3894682bbb64cbf50b0689c83a02179 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1709165Reviewed-by:
Evan Stade <estade@chromium.org> Reviewed-by:
Jared Saul <jsaul@google.com> Commit-Queue: Siyu An <siyua@chromium.org> Cr-Commit-Position: refs/heads/master@{#680619}
-
Gayane Petrosyan authored
Record color from the predefined set when color is applied and when theme prefs are loaded. Bug: 985002 Change-Id: I748221b93747453cc7bc73d25b97cc88ac6c1ee1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710001Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Reviewed-by:
Kyle Milka <kmilka@chromium.org> Reviewed-by:
Gayane Petrosyan <gayane@chromium.org> Commit-Queue: Gayane Petrosyan <gayane@chromium.org> Cr-Commit-Position: refs/heads/master@{#680618}
-
Kurt Horimoto authored
This is the first step to moving the WebStateDelegate implementation out of BVC. The only pure virtual function on WebStateDelegate is OnAuthRequired(), so a no-op implementation is added here. Bug: 986956 Change-Id: I431142cbadcfe4e7cb4a6a9ce77de4ca11d9bb3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716165Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#680617}
-
Ce Chen authored
The UMA metrics are added to measure the performance (runtime) and suggest coverage of on device head provider. Bug: 925072 Change-Id: I84a96d514b916698678e07192eecb14c8bf9218a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1710827 Commit-Queue: Ce Chen <cch@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#680616}
-
Jordy Greenblatt authored
By searching the settings/chromeos folder [1] for the string "<if" [2], I determined that there are only 4 files in it that have conditional tags that require preprocessing, namely -settings/chromeos/os_settings.html -settings/chromeos/os_about_page/os_about_page.js -settings/chromeos/os_about_page/os_about_page.html -settings/chromeos/os_privacy_page/os_privacy_page.html I suspect that the preprocess attributes were just not deleted when those files were branched from browser settings. This CL removes the preprocess=true attribute from every file from the chromeos folder [1] in os_settings_resources.grd other than the 4 aforementioned files. It also adds preprocess="true" to os_privacy_page.html, which has "<if expr..." conditional content but did not have the attribute. [1] https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/chromeos/ [2] http://screen/X7uR9d0LJPf Bug: 987384 Change-Id: Ifcf42add56ac4b79a41dfe783678236e58b5584c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715261Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Reviewed-by:
May Lippert <maybelle@chromium.org> Commit-Queue: Jordy Greenblatt <jordynass@chromium.org> Cr-Commit-Position: refs/heads/master@{#680615}
-
Emil A Eklund authored
Bug: 905315 Change-Id: I9cd7acf733ab096e0b5c2d360acc4d21e03d538e Tbr: kojii@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717199 Commit-Queue: Emil A Eklund <eae@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#680614}
-
Rakib M. Hasan authored
_RunGpuIntegrationTests permanently sets sys.argv and gpu_project_config.CONFIG to test values for all tests. This is the state leak that is causing the test expectations conflict checker to miss the conflict in pixel_tests_expectations.txt. Since gpu_project_config.CONFIG is set to a test value, the start directories it contains are set to test values. Therefore the conflict checker cannot find the PixelIntegrationTest class. Bug: chromium:986538 Change-Id: I25e478fd95bbe42e63b11cdf7408e12ada345a9d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1714147 Commit-Queue: Rakib Hasan <rmhasan@google.com> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#680613}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/b88be03bab49..d3987e3e2798 git log b88be03bab49..d3987e3e2798 --date=short --no-merges --format='%ad %ae %s' 2019-07-24 tcwang@google.com afdo: Clean up orderfile-verify-toolchain and add schedule. Created with: gclient setdep -r src/third_party/chromite@d3987e3e2798 The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I4efbabeb5939b83eadd8a7a8b7dbc1adf810529a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716935Reviewed-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@{#680612}
-
ssid authored
While we figure out better solutions for interning, to make traces useful we can decrease interning interval. Make this configurable by experiments. Change-Id: I9ad99ab3184362f81d9b7ba5bc217e9c8b1914bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716601 Commit-Queue: ssid <ssid@chromium.org> Reviewed-by:
oysteine <oysteine@chromium.org> Cr-Commit-Position: refs/heads/master@{#680611}
-
Brian Sheedy authored
This reverts commit a258547a. Reason for revert: Issue fixed without reverting root cause CL, so re-landing this. Original change's description: > Revert "viz: Create SchedulerSequence for SkiaOutputSurfaceDependency" > > This reverts commit 0fbaf768. > > Reason for revert: Blocking revert of https://chromium-review.googlesource.com/c/chromium/src/+/1708418 > > Original change's description: > > viz: Create SchedulerSequence for SkiaOutputSurfaceDependency > > > > Share SchedulerSequence implementation between command buffer task > > executor and skia output surface dependency. Also refactor Android > > WebView to make sure skia output surface dependency there does not > > need to be depended on command buffer task executor. > > > > Bug: 979788 > > Change-Id: I0ae966397a93cd82945ffa249328b28fc6da7dd8 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715084 > > Commit-Queue: weiliangc <weiliangc@chromium.org> > > Reviewed-by: Peng Huang <penghuang@chromium.org> > > Reviewed-by: Bo <boliu@chromium.org> > > Cr-Commit-Position: refs/heads/master@{#680474} > > TBR=penghuang@chromium.org,boliu@chromium.org,weiliangc@chromium.org,ericrk@chromium.org > > Change-Id: I76e694f1030ab526d91f8a2d62d55ea3a2da3650 > No-Presubmit: true > No-Tree-Checks: true > No-Try: true > Bug: 979788 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715473 > Reviewed-by: Brian Sheedy <bsheedy@chromium.org> > Commit-Queue: Brian Sheedy <bsheedy@chromium.org> > Cr-Commit-Position: refs/heads/master@{#680596} TBR=penghuang@chromium.org,boliu@chromium.org,weiliangc@chromium.org,bsheedy@chromium.org,ericrk@chromium.org Change-Id: I248dcd08ccf255c61b10cbcb8cd20e11b1504c81 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 979788 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717394Reviewed-by:
Brian Sheedy <bsheedy@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#680610}
-
John Delaney authored
Now that memory cache resources are reported to PLM, we should also record those resources in the Ads.ResourceUsage.Size.Cache.* metrics. This change versions this histogram and all suffixes. Bug: 968141 Change-Id: Ic2d56cc28be6111180c7d463fbd158e3970bcfb0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715779Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Commit-Queue: John Delaney <johnidel@chromium.org> Cr-Commit-Position: refs/heads/master@{#680609}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/87259987f65e..efe03fe27df3 Created with: gclient setdep -r src-internal@efe03fe27df3 The AutoRoll server is located here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None,chromium:None,chromium:None Change-Id: I6d5b6478c3c8afbf763f0b9f2dc07d687d74cbd3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716932Reviewed-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@{#680608}
-
Becca Hughes authored
Set default position. BUG=987381 Change-Id: I12fa8599c6b5a9630a252412261fc0edd24aadf2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717306 Auto-Submit: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
Patrick Monette <pmonette@chromium.org> Commit-Queue: Becca Hughes <beccahughes@chromium.org> Cr-Commit-Position: refs/heads/master@{#680607}
-
Kayce Basques authored
Bug: 986998 Change-Id: Ib01f7cdfd2f9d47833695f62b7baad7b759c0eed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716153 Auto-Submit: Kayce Basques <kayce@google.com> Commit-Queue: Joel Einbinder <einbinder@chromium.org> Reviewed-by:
Joel Einbinder <einbinder@chromium.org> Cr-Commit-Position: refs/heads/master@{#680606}
-
rbpotter authored
Port tests for the shared JS resources migrated to modules in https://crrev.com/c/1682889. Note: Tests only run if optimize_webui is false, since these resources only exist in this case. Bug: 965770 Change-Id: Ic98c7fcf47149a96a21311fbc52cc8192cc60bf1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716947 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#680605}
-
Sinan Sahin authored
Bug: 987101 Change-Id: I46a33fcad060551b9f6216efab47147b0dfe8baf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1716261Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Sinan Sahin <sinansahin@google.com> Cr-Commit-Position: refs/heads/master@{#680604}
-
Matthew Mourgos authored
- This change will ensure proper spacing with shelf constants that have been changed for the new dense shelf ui. Bug: 973483 Change-Id: I4790a9e602ee592c15637f4a7cd300bb52dda3a2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1708011Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Commit-Queue: Matthew Mourgos <mmourgos@chromium.org> Cr-Commit-Position: refs/heads/master@{#680603}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/776f729a..6c48f74f 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: Id7d4bf02257cbd720c154b01902d070bf3ba5cb2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715421Reviewed-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@{#680602}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/a76f3b0bce96..397e783df69a git log a76f3b0bce96..397e783df69a --date=short --no-merges --format='%ad %ae %s' 2019-07-24 fmayer@google.com Merge "Change "Frame too large" from DLOG to LOG." Created with: gclient setdep -r src/third_party/perfetto@397e783df69a The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. TBR=perfetto-bugs@google.com Bug: None Change-Id: I19bdd48d788360a41e12a924eaf41828c0ba4939 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715260Reviewed-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@{#680601}
-
Rakesh Soma authored
Bug: 987291 Change-Id: Ibdb1dfa5de51aa130c7853f12290889740ea7b86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1715742 Auto-Submit: Rakesh Soma <rakeshsoma@google.com> Reviewed-by:
Tien Mai <tienmai@chromium.org> Commit-Queue: Rakesh Soma <rakeshsoma@google.com> Cr-Commit-Position: refs/heads/master@{#680600}
-
Yue Li authored
Bug: None Test: Manual test Change-Id: Ib88c098855428a0e96e66ba4fe18988afec05ebf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1717234Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Yue Li <updowndota@chromium.org> Cr-Commit-Position: refs/heads/master@{#680599}
-