- 23 Oct, 2019 40 commits
-
-
Henrique Ferreiro authored
Convert the implementation and all users of the ui::ozone::mojom::GesturePropertiesService interface. Bug: 955171 Change-Id: I8a70b91624fef3f7e94e25e2f7071d85a4dec42a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864776Reviewed-by:
Robert Kroeger <rjkroege@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Commit-Queue: Henrique Ferreiro <hferreiro@igalia.com> Cr-Commit-Position: refs/heads/master@{#708759}
-
Maggie Chen authored
Once GPU hang is detected in the GPU watchdog V2, the watchdog will try to load/unload a file from the hard drive and create/destroy a thread to see if the GPU has made any progress in the current task. This will give a hint if the system is busy. If the GPU is still stuck, Wait until 60 seconds has passed and check again the GPU status. After this, the watchdog kill the GPU main thread. This is to see whether the GPU thread is killed too early and to compare with V2 on the number of hangs. This piece of code can be deleted after the data is collected. Bug:949839 Change-Id: I3a6afeed21776553d7416682baf6eed2d521286c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872166Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Maggie Chen <magchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#708758}
-
Hui Yingst authored
Change-Id: If554173ce7a75ecbcbb0464288875a3a5510e6bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869941Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Hui Yingst <nigi@chromium.org> Cr-Commit-Position: refs/heads/master@{#708757}
-
Rakesh Soma authored
Bug: 1013208 Change-Id: I74316f804e253516821bd4ae24a478e203f4914a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870011Reviewed-by:
Tien Mai <tienmai@chromium.org> Commit-Queue: Rakesh Soma <rakeshsoma@google.com> Auto-Submit: Rakesh Soma <rakeshsoma@google.com> Cr-Commit-Position: refs/heads/master@{#708756}
-
Elly Fong-Jones authored
This change moves ContentSettingBubbleContents from overriding CreateExtraView to using SetExtraView. Since the code for creating the extra view needs to store quite a few internal parts of the created view, it is left as a method on ContentSettingBubbleContents. Bug: 1011446 Change-Id: I8c14fffdfe742e3223dbb9431c6ef27761623419 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876747Reviewed-by:
Peter Boström <pbos@chromium.org> Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#708755}
-
rbpotter authored
Web UIs using Polymer 3 generally have resources in two different directories: the original source directory (for data files) and a corresponding generated directory (for UI elements). This results in the resources map having paths of the form: @out_folder@/<gen_path>/path/to/ab/a.js as well as path/to/ab/b.js However, for bundling, all resources should live in the same directory structure in the unpak folder. This CL adds logic to correctly map the generated resources paths to their corresponding location in the source paths when unpacking, so that the resulting unpak folder will hold all files side by side, i.e. a.js and b.js will both be located in: <unpak_path>/path/to/ab/ Bug: 965770 Change-Id: I0f8ac02727a721f4ddc6c67d4e1788c2ce30f3f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875029Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#708754}
-
Jimmy Gong authored
- Adds a feature flag for the print server UI for consumers in printer settings. Bug: 1015628 Change-Id: I9b761e23d930775c35198fb072ba2664539476d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866860Reviewed-by:
Bailey Berro <baileyberro@chromium.org> Commit-Queue: jimmy gong <jimmyxgong@chromium.org> Cr-Commit-Position: refs/heads/master@{#708753}
-
Nate Fischer authored
No change to logic. This is a code cleanup for some subfolders of //aw/browser/. This was guided by chromium's copy of cpplint.py, fixing most of the errors it raised for these two subfolders. Test: /path/to/depot_tools/cpplint.py android_webview/browser/network_service/* Test: /path/to/depot_tools/cpplint.py android_webview/browser/safe_browsing/* Change-Id: Ib71092570a1123e4c3a12cca9febc250d5c803e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873350Reviewed-by:
Tim Volodine <timvolodine@chromium.org> Commit-Queue: Nate Fischer <ntfschr@chromium.org> Cr-Commit-Position: refs/heads/master@{#708752}
-
Nigel Tao authored
This isn't enabled by default yet. This commit should not change the generated binaries. Bug: 1014044 Change-Id: I1edd29dc6533f7407043bee4d3399fb6c39b4068 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874412Reviewed-by:
Leon Scroggins <scroggo@chromium.org> Commit-Queue: Nigel Tao <nigeltao@chromium.org> Cr-Commit-Position: refs/heads/master@{#708751}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/1c5bed7f..17e452a6 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: Ib7b72b69d13a0091db4c254bc0d3ed158c421c3e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876487Reviewed-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@{#708750}
-
Tomasz Wiszkowski authored
This change updates EntitySuggestion mechanism to rely on common mechanism for all suggestions. Doc: http://doc/1aL_UcW1gdeSLqNzuJZlQPBqMG0XAwVaoa05UTyVulp8 Bug: 982818 Change-Id: I4562e777f2e899a1863e0e8179c9d4b6c5dc7a72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866988 Commit-Queue: Ender <ender@google.com> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Brandon Wylie <wylieb@chromium.org> Reviewed-by:
Patrick Noland <pnoland@chromium.org> Cr-Commit-Position: refs/heads/master@{#708749}
-
Rune Lillesveen authored
Remove the remaining test failures for writing-mode propagation to viewport from TestExpectations. One of the tests had a missing period in the test text that caused it to fail, and the other one was fixed in the github repo, now passing. Bug: 988585 Change-Id: I307eb4453479a71529f6c96d87b299f22a7a2c36 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875263Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#708748}
-
Dominik Röttsches authored
Add known DWrite error codes and NTSTATUS type failures that are commonly returned when IDWriteFont::CreateFontFace fails and returns a failure error code. Adding these to enums.xml helps interpret UMA results for the existing DirectWrite.Fonts.Proxy.CreateFontFaceResult metric, because HResult enum values are recorded for this metric. Currently, the mentioned error codes show up as hard-to-identify integer values. Adding them to enums.xml will make the metric easier to analyse. Bug: 1009402 Change-Id: I40e5bf8b8c8eebff4841cedf03eb848e296db821 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876091 Commit-Queue: Dominik Röttsches <drott@chromium.org> Auto-Submit: Dominik Röttsches <drott@chromium.org> Reviewed-by:
-
Rune Lillesveen authored
Incorrect js file included, which made the tests fail. Bug: 1013965 Change-Id: Ie716a6c1734d96c0090752e9b88274d70643bf57 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875754Reviewed-by:
-
Avery Musbach authored
When the MultiDisplayOverviewAndSplitView feature flag is disabled, during transition to unified desktop mode, the destructors of BackdropController and ShelfLayoutManager should call SplitViewController::RemoveObserver on the split view controller for the old primary root window rather than for the new primary root window. The present CL addresses the problem by adjusting the timing of when Shell::GetPrimaryRootWindow stops returning the old primary root and starts returning the new primary root. The child CL has some LOG(ERROR) code useful for verifying that the present CL serves its purpose. Bug: 970013 Change-Id: I81074d4883a7d252d1da6a808976b47ad22cfc32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869838 Commit-Queue: Avery Musbach <amusbach@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Cr-Commit-Position: refs/heads/master@{#708745}
-
James Cook authored
This reverts commit 87fc2374. Relanding after fixing initialization in the chrome crash-and-restore case. The old code missed a call to OnProfileInitialized() in that crash-and-restore case. Instead of relying on chrome to call OnProfileInitialized() in all startup code paths, we now observe the IdentityManager for when the primary account information becomes available. Original change's description: > Revert "Migrate the Chrome OS device_sync service off of the mojo pref service" > > This reverts commit 671afa99. > > Reason for revert: Breaks proximity auth in the crash-and-restore > login flow (e.g. if chrome crashes during the session and logs you > back in automatically on restart). See crbug.com/1015215 > > Original change's description: > > Migrate the Chrome OS device_sync service off of the mojo pref service > > > > DeviceSyncService runs in the browser process on the UI thread. It can > > directly use the Profile's PrefService*. This simplifies the code, and > > will reduce the amount of work rockot@ has to do for Service Manager > > cleanup. > > > > Delete the DeviceSyncService mojo interface and implementation object. > > They primarily existed to support wiring up the mojo pref service. > > Instead, directly connect the DeviceSyncClientImpl to the backing > > DeviceSyncImpl. > > > > Explicitly initialize the DeviceSyncImpl when the user's profile is > > ready. The old code had startup timing dependencies that assumed that > > DeviceSyncImpl was created after IdentityManager had information about > > the primary profile. The new code instantiates the DeviceSyncImpl > > object earlier, and IdentityManager may not be ready yet. > > > > Bug: 977637, 1012941 > > Test: bots > > Change-Id: Ia32b687404e5b68980cb3aecd3003e6f7e48ffcd > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849217 > > Commit-Queue: James Cook <jamescook@chromium.org> > > Reviewed-by: Greg Kerr <kerrnel@chromium.org> > > Reviewed-by: Josh Nohle <nohle@chromium.org> > > Reviewed-by: Scott Violet <sky@chromium.org> > > Reviewed-by: Ken Rockot <rockot@google.com> > > Cr-Commit-Position: refs/heads/master@{#706181} > > TBR=jamescook@chromium.org,sky@chromium.org,rockot@google.com,kerrnel@chromium.org,hansberry@chromium.org,nohle@chromium.org > > # Not skipping CQ checks because original CL landed > 1 day ago. > > Bug: 977637, 1012941 > Change-Id: Id6cf5f43aac57415dae266a7871c08e4954fa24b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1865602 > Reviewed-by: James Cook <jamescook@chromium.org> > Commit-Queue: James Cook <jamescook@chromium.org> > Cr-Commit-Position: refs/heads/master@{#707000} TBR=jamescook@chromium.org,sky@chromium.org,rockot@google.com,kerrnel@chromium.org,hansberry@chromium.org,nohle@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 977637, 1012941 Change-Id: I1fff46240f3b34a7d1276edb7e79a264150ceb73 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869576Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Josh Nohle <nohle@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#708744}
-
Mohammad Refaat authored
This method clears WK WebSiteDataStore default store data including wk forward/back cache Bug: 987646 Change-Id: I64bbb8015cc12a623c8a2096981d16198adc5a6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876732 Commit-Queue: Mohammad Refaat <mrefaat@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#708743}
-
Greg Thompson authored
It appears that this was supposed to have been disabled from initial commit. BUG=1001597 R=wfh@chromium.org Change-Id: I28eafadc31d7a8416263c35dccba89f579fd84b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876030 Auto-Submit: Greg Thompson <grt@chromium.org> Reviewed-by:
Will Harris <wfh@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#708742}
-
Shawn Gallea authored
This prevents crashes when web_contents_window_ was null. Bug: b/136460199 Test: Compile cast_shell Change-Id: I6f48801e69745bcfc5fb29a7db0632e10a0bd8a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876890Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Shawn Gallea <sagallea@google.com> Cr-Commit-Position: refs/heads/master@{#708741}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/370eefceab98..75647d9e1ae7 git log 370eefceab98..75647d9e1ae7 --date=short --no-merges --format='%ad %ae %s' 2019-10-23 lamontjones@chromium.org paygen: Don't remove all the locks all the time. 2019-10-23 vapier@chromium.org alerts: get it working under Python 3 Created with: gclient setdep -r src/third_party/chromite@75647d9e1ae7 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 TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I74d137fe1926b4e2a0e0a81a525a830b2e6b86a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876076Reviewed-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@{#708740}
-
Xinghui Lu authored
Password Reuse Detection is not fully functional on Android because it doesn't capture SetComposingText events and FinishComposingText events. In this CL, password manager listens to these two events. Also, since composing text may not be committed eventually, OnKeyPressed() is splitted based on the value of is_committed. If is_committed is false, the text is not concatenated in input_characters_. Bug: 1006430 Change-Id: Ibf3e17c5e86895e7b9aee32463455333c24a1759 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873144 Commit-Queue: Xinghui Lu <xinghuilu@chromium.org> Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#708739}
-
Danan S authored
Bug: 943901 Change-Id: I8917e05092856f5f909c8a4e1b60c73ac7e58739 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876490Reviewed-by:
Brian White <bcwhite@chromium.org> Commit-Queue: Dan S <danan@chromium.org> Cr-Commit-Position: refs/heads/master@{#708738}
-
Stephen McGruer authored
It seems like this is causing consistent failures on Mac10.10 tests; not sure why it was created by the WPT importer in the first place. https://ci.chromium.org/p/chromium/builders/ci/Mac10.10%20Tests/48035 TBR=klausw@chromium.org Bug: None Change-Id: I89cf2d8c0e7ec47f80952310b746c3a904bef863 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876889Reviewed-by:
Stephen McGruer <smcgruer@chromium.org> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#708737}
-
Wei-Yin Chen (陳威尹) authored
PseudoTab represents Tab-like cards in the Grid Tab Switcher. It can be used to represent a card before the Tab objects are constructed. Bug: 1016952 Change-Id: I908dbe70dae6af691ae45ab3342701b4995220bd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874708 Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Cr-Commit-Position: refs/heads/master@{#708736}
-
Oriol Brufau authored
Since https://crrev.com/c/1477255, when you type something but the caret has been scrolled out of view, the scroll container only scrolls the minimum amount to make the caret become fully visible. The search field for languages has some line-height, min-height and padding-top values that make it taller than the caret. So there is some space above the caret which is not automatically scrolled into view when typing in the search field. The scroll container is later scrolled to the very top by some script, so it looks like it gets momentarily stuck while scrolling up. This patch fixes that by calling scrollIntoViewIfNeeded() on the search field when something is typed in it, so the scroll container is scrolled to the very top. Fixed: 1013556 Change-Id: I5524ad85e14d5d38a1aa31eb3ae061051ccc8dbb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1873758 Commit-Queue: Oriol Brufau <obrufau@igalia.com> Reviewed-by:
-
Garrett Beaty authored
Change-Id: Ica03d95af30be8221b67648578460ba2c7ce4a64 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869682 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Reviewed-by:
Aaron Gable <agable@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/heads/master@{#708734}
-
Wez authored
- Remove thakis@ and scottmg@, who should be OWNERS-of-last-resort, since they are already //build/OWNERS. - Remove jamesr@, who works on Fuchsia, not Chromium. - Correct the COMPONENT to Fuchsia. Change-Id: I25d41f0454522bf9d7fe0e025c623aed4b59d0a4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876869 Auto-Submit: Wez <wez@chromium.org> Reviewed-by:
Scott Graham <scottmg@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#708733}
-
Ian Struiksma authored
Some issue is happening on the bot for this site that I haven't been able to reproduce locally, but disabling for now as I figure out what's happening. Bug: 1017266 Change-Id: Ia6387ca4bd03bd866040d96ff24e2d35075da660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876728 Auto-Submit: Ian Struiksma <ianstruiksma@google.com> Commit-Queue: Caleb Rouleau <crouleau@chromium.org> Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#708732}
-
Lucas Furukawa Gadani authored
Bug: 984550 Change-Id: I2bf27ce77287394c782692483117ee105e214563 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875385Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Lucas Gadani <lfg@chromium.org> Cr-Commit-Position: refs/heads/master@{#708731}
-
liberato@chromium.org authored
Change-Id: I6a15ad00706fe31ffb8484ff5a65607b7e4d55ef Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874723Reviewed-by:
Ted Meyer <tmathmeyer@chromium.org> Commit-Queue: Frank Liberato <liberato@chromium.org> Cr-Commit-Position: refs/heads/master@{#708730}
-
Dominic Mazzoni authored
This is a small fix for a subtle bug. The way touch exploration works on Android is complicated: * When the user taps or drags their finger, our View gets a hover event. * Accessibility code sends a hit test action to the renderer process * The renderer process fires a HOVER accessibility event on the accessibility node at that coordinate * WebContentsAccessibilityImpl.handleHover is called with that node. We fire an Android TYPE_VIEW_HOVER_ENTER event on that node and a TYPE_VIEW_HOVER_EXIT event on the previous node. * Finally, TalkBack sets accessibility focus to that node. As the user continues to drag their finger, we get lots of hover events on the view, but often the finger is over the same node. To prevent repeatedly firing TYPE_VIEW_HOVER_ENTER on the same node, we keep track of the last hover id in mLastHoverId. The problem with this was that if you moved accessibility focus somewhere else - like tapping outside of the web view, or swiping to a different element, we weren't clearing mLastHoverId, so if you subsequently tapped on the same element, we'd suppress it (incorrectly). The fix is just to clear mLastHoverId and fire the TYPE_VIEW_HOVER_EXIT whenever we're told to clear accessibility focus from the last node that was hovered. Then if the user subsequently taps on that node we'll send the right event and let them focus it again. Bug: 769736 Change-Id: I68f4c522bd6fe76657a5624abe291a45e7aafe58 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1874502Reviewed-by:
David Tseng <dtseng@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#708729}
-
Oksana Zhuravlova authored
Bug: 1010364 Change-Id: I3e96e02bc1067afd3d33ab5873cf6ec0a2f17756 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1864468 Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#708728}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/a1ed9d1a8492..08af1c80188f git log a1ed9d1a8492..08af1c80188f --date=short --no-merges --format='%ad %ae %s' 2019-10-23 tobine@google.com Vulkan:Store full 64bit handle in GarbageObject Created with: gclient setdep -r src/third_party/angle@08af1c80188f 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 jonahr@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 TBR=jonahr@google.com Bug: None Change-Id: I7fce211f0d2e8390f71d9242363e82354886a717 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875280Reviewed-by:
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/e792f87ded42..794ed818b893 git log e792f87ded42..794ed818b893 --date=short --no-merges --format='%ad %ae %s' 2019-10-23 nigi@chromium.org Add a fuzzer for the public methods of CFX_ScanlineCompositor. Created with: gclient setdep -r src/third_party/pdfium@794ed818b893 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC pdfium-deps-rolls@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 TBR=pdfium-deps-rolls@chromium.org Bug: None Change-Id: I3be5b2eb3ec448c3cffb989509c3fb3d17161a2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876834Reviewed-by:
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/1f6c8c4d5495..402fbcca936b git log 1f6c8c4d5495..402fbcca936b --date=short --no-merges --format='%ad %ae %s' 2019-10-23 shaobo.yan@intel.com Enable UpdateDynamicOffsetsMultipleTimesComputePipeline case Created with: gclient setdep -r src/third_party/dawn@402fbcca936b If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel TBR=cwallez@google.com Bug: None Change-Id: I1fb02dc8daccad2ed3eb0d80f8a314a1f90d08f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876450Reviewed-by:
-
Anton Bikineev authored
This patch moves incremental marking steps in Oilpan from safe points to V8 task runner thereby letting scheduler know about GC existence. This is expected to regress atomic-pause duration, since incremental steps are not as prioritized as they used to be, but at the same time latency should improve. Bug: 1002998 Change-Id: I1f0fa3468160a3505fcf71f85655c0fd41dc1c67 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1607642 Commit-Queue: Anton Bikineev <bikineev@chromium.org> Reviewed-by:
Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#708724}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/1342a6ae6285..9fb9a722fb28 git log 1342a6ae6285..9fb9a722fb28 --date=short --no-merges --format='%ad %ae %s' 2019-10-23 treehugger-gerrit@google.com Merge "perfetto: change gen_andorid_bp to use static libs for host tools" 2019-10-23 lalitm@google.com Merge "Revert "traceconv: ignore userspace events for traces with Android data"" 2019-10-23 lalitm@google.com Merge "traceconv: ignore userspace events for traces with Android data" 2019-10-23 treehugger-gerrit@google.com Merge "processor: Extract graphics event parsing into an importer module" 2019-10-23 eseckler@google.com Merge "processor: Refactor ExportJson() to rely on tracks rather than reftypes" 2019-10-23 lalitm@google.com Merge "trace_processor: add option to force a full sort of traces" Created with: gclient setdep -r src/third_party/perfetto@9fb9a722fb28 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 TBR=perfetto-bugs@google.com Bug: None Change-Id: I94f4a228d4dde45953d0f7a0eaf761bd4a1b39ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876075Reviewed-by:
-
Peter Kasting authored
Bug: 82078 Change-Id: I5bec95398951e1e1e453b7ab3114e1fcff106198 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1875269 Commit-Queue: Yuwei Huang <yuweih@chromium.org> Reviewed-by:
Yuwei Huang <yuweih@chromium.org> Auto-Submit: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#708722}
-
David Tseng authored
Bug: 865575 Reland of https://chromium-review.googlesource.com/c/chromium/src/+/1852414 This change differs in: - only show the viewport widget once all associated state is ready to respond to events. This fixes a potential crash. - only observe focus events on controls. Change-Id: I1addbfb4a9d89e738ca6992c3ccd1f88e9546104 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876688 Commit-Queue: David Tseng <dtseng@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/61a1e81e89bd..577977ad233c git log 61a1e81e89bd..577977ad233c --date=short --no-merges --format='%ad %ae %s' 2019-10-23 bsheedy@chromium.org Add localhost warning comment to Telemetry 2019-10-23 khokhlov@google.com Revert "[Telemetry] New intermediate file format" 2019-10-23 khokhlov@google.com [Telemetry] New intermediate file format Created with: gclient setdep -r src/third_party/catapult@577977ad233c 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 TBR=sadrul@google.com Bug: chromium:1005971,chromium:981349,chromium:981349 Change-Id: Iefd9ddef7b2cbd3e8a470c4252c176377cd5cbf7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1876074Reviewed-by:
-
