- 29 Oct, 2018 40 commits
-
-
Sergey Ulanov authored
Scenic now expects allocation_size to be set for VMOs. That parameter wasn't set in chromium, so Scenic would fail when trying to use VMOs for images. Bug: 899922 Change-Id: I73c7c7dfa4d4a5e9ba76774c4b69d8125add05c2 Reviewed-on: https://chromium-review.googlesource.com/c/1306174 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#603634}
-
Becca Hughes authored
At the moment there can only be one custom notification view factory which is currently used for ARC. This adds a `custom_view_type` to Notification which can be used to differentiate between different factories. This is part of the media session notification work as we would like to show a notification with media controls and this requires having our own custom view. BUG=897836 Change-Id: I68ffadb3e6e04422a5522fdf302652046a9c5b0f Reviewed-on: https://chromium-review.googlesource.com/c/1294417 Commit-Queue: Becca Hughes <beccahughes@chromium.org> Reviewed-by:
David Tseng <dtseng@chromium.org> Reviewed-by:
Oliver Chang <ochang@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#603633}
-
Yuly Novikov authored
TBR=kbr@chromium.org Bug: angleproject:2941 Change-Id: I041f83bab21f523a12b872e34c7a8b502b163794 Reviewed-on: https://chromium-review.googlesource.com/c/1305240Reviewed-by:
Yuly Novikov <ynovikov@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Yuly Novikov <ynovikov@chromium.org> Cr-Commit-Position: refs/heads/master@{#603632}
-
Adam Langley authored
These devices are obsolete and undocumented. We can't parse the reply from them to replace the attestation so registration always fails when replacement is needed. Rather than fail, this change allows v1 devices to return their reply unaltered so that accounts.google.com can tell the user that they need to reflash the device. Change-Id: Ic3b41210bc7d167b9fe5b9285946b9a9b834d0f8 Reviewed-on: https://chromium-review.googlesource.com/c/1302702Reviewed-by:
Martin Kreichgauer <martinkr@chromium.org> Commit-Queue: Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#603631}
-
Fady Samuel authored
It's no longer used. Bug: 893850 Change-Id: Ibbd613affd364dac728cf00230e0b017dde7d70f Reviewed-on: https://chromium-review.googlesource.com/c/1305882Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Commit-Queue: Fady Samuel <fsamuel@chromium.org> Cr-Commit-Position: refs/heads/master@{#603630}
-
Wei Li authored
Use user action metric UI_DevTools_Connect to record each time a connection to UI DevTools server is established. The frequency of such connections would help us gauge the usage of the UI DevTools. BUG=746562 Change-Id: Icd54da4f23b3cc0268113de48931a803af53632c Reviewed-on: https://chromium-review.googlesource.com/c/1299007 Commit-Queue: Wei Li <weili@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#603629}
-
Anders Hartvoll Ruud authored
As of an imminent spec change, <color> values no longer compute to their specified value, but behave like <color> values in general. Note that color keywords are parsed as CSSIdentifierValue (holding a CSSValueID), and custom idents are parsed as CSSCustomIdentValue (holding a String), which is why the "tomato | <color>" works as it should. R=futhark@chromium.org Bug: 641877 Change-Id: I946536a9d54dbaa7af589cb99acdba72f37fe016 Reviewed-on: https://chromium-review.googlesource.com/c/1303365Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#603628}
-
Eric Karl authored
As written, the allowed namespace/classes list in audit_non_blink_usage.py does not allow for classes in the features:: namespace to be used. These are already frequently used in blink/renderer, however as they are almost always preceded by base::FeatureList::IsEnabled, and the checker only checks the first match on a line, they were previously ignored. This issue was encountered when trying to add a longer features::.+ element that was wrapped to the next line. However, moving any existing features::.+ string to its own line will trigger this issue. This seems like an oversight as the features:: namespace is already in common use in blink/renderer, and base::Feature.* is allowed already. Adding in features::.+ as well. Bug: 899415 Change-Id: I56d453e102988b463d91850d5aa843c93c274517 Reviewed-on: https://chromium-review.googlesource.com/c/1303395Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Eric Karl <ericrk@chromium.org> Cr-Commit-Position: refs/heads/master@{#603627}
-
David Bokan authored
This reverts commit f51a68b0. Reason for revert: breaks scrolling on some pages: https://crbug.com/899161 Original change's description: > Convert scrolling code to use Node > > In https://crrev.com/9f54d240af5d366b1d6a4d9b84438192a9f0a11c we moved > ScrollCustomization from using Elements to Node. This allows us to use > Nodes in the scrolling code which is much more natural since the > viewport scrolls using the LayoutView (document Node)'s scrollable area. > > The main change in this CL is letting the Document node be part of the > scroll chain, instead of using the documentElement in its place. This > removes some special-casing all the way through the scrolling pipeline. > > As a result the Global Root Scroller now sets the viewport scroll > callback on the document node. > > Bug: 897288 > Change-Id: I899e6007b676efb94675d94b3d97702c8f1f2a94 > Reviewed-on: https://chromium-review.googlesource.com/c/1299205 > Commit-Queue: David Bokan <bokan@chromium.org> > Reviewed-by: Steve Kobes <skobes@chromium.org> > Cr-Commit-Position: refs/heads/master@{#602935} TBR=bokan@chromium.org,skobes@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 897288,899161 Change-Id: Ic75c23a1bcde6d86e554c2b5bdb5548b37d57e5f Reviewed-on: https://chromium-review.googlesource.com/c/1305820 Commit-Queue: David Bokan <bokan@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#603626}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/12048c71501a..a0677d14c17f git log 12048c71501a..a0677d14c17f --date=short --no-merges --format='%ad %ae %s' 2018-10-29 Peter) Slatala Add MediaTransportSettings struct for configuring media transport. Created with: gclient setdep -r src/third_party/webrtc@a0677d14c17f The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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:linux_chromium_archive_rel_ng;luci.chromium.try:mac_chromium_archive_rel_ng TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I6b14125d7bfd82b22459e9ea8391576692453b73 Reviewed-on: https://chromium-review.googlesource.com/c/1305293Reviewed-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@{#603625}
-
Akihiro Ota authored
Talkback would previously report nesting level for single-level lists, which was considered unnecessary. Added functionality in the IsHierarchical() method to determine if a list contains other lists, or if it is contained within a list, to help determine if it is hierarchical. Also modified DumpAccessibilityTree test expected output files to check for new desired behavior. R=dmazzoni@chromium.org Bug: 591255 Change-Id: Idd995c5fae426b191825996cf02ee51bd6753607 Reviewed-on: https://chromium-review.googlesource.com/c/1300076 Commit-Queue: Akihiro Ota <akihiroota@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#603624}
-
Koji Ishii authored
This patch revives the lost code during the refactoring in r603011 (CL:1299609). Bug: 834653 Change-Id: Ibbe49c00eb3623f5bcefbcfda28651400cc81090 Reviewed-on: https://chromium-review.googlesource.com/c/1304282 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#603623}
-
Evan Stade authored
Tests fixed in 7768d47c Behavior fixed in 9cfb85d4 Bug: 640365 Change-Id: I92d955c5c450d672f5d8c6fd263c44169051eb66 Reviewed-on: https://chromium-review.googlesource.com/c/1303235Reviewed-by:
James Cook <jamescook@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#603622}
-
Peter Boström authored
This experiment is no longer intended to roll out and never made it past Dev / Canary. This change removes the animated icon from BrowserAppMenuButton and removes supporting classes. Bug: chromium:738608 Change-Id: I69e29ba29e4689b88913fcf17aff3d83eede5d81 Reviewed-on: https://chromium-review.googlesource.com/c/1299923 Commit-Queue: Peter Boström <pbos@chromium.org> Reviewed-by:
Trent Apted <tapted@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#603621}
-
Erik Språng authored
This CL adds support for the new GetEncoderInfo() method which will replace GetScalingSettings(), SupportsNativeHandle() and ImplementationName(). These methods will be removed in a follow-up cl. It also removes assignment of CodecSpecificInfo.codec_name, which is also going away. Bug: webrtc:9890 Change-Id: I9d910dde4fefb054a04f9585579992f1cfc696c6 Reviewed-on: https://chromium-review.googlesource.com/c/1301514Reviewed-by:
Emircan Uysaler <emircan@chromium.org> Commit-Queue: Erik Språng <sprang@chromium.org> Cr-Commit-Position: refs/heads/master@{#603620}
-
David Bienvenu authored
This implements native window occlusion tracking on windows, under flag/experiment control. It uses WinEvent event hooks and EnumWindows to track and calculate occlusion. It is not yet hooked up to the code that treats occluded windows differently. Bug: 813093 Change-Id: Ic9b473b8cad38e7b1653566f28917164bc92e21c Reviewed-on: https://chromium-review.googlesource.com/c/1140752 Commit-Queue: David Bienvenu <davidbienvenu@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#603619}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/6d65cf959e1d..b0874f87a68d Created with: gclient setdep -r src-internal@b0874f87a68d The AutoRoll server is located here: https://autoroll-internal.skia.org/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. BUG=chromium:790153,chromium:790158,chromium:790159,chromium:790163,chromium:790153,chromium:790158,chromium:790159,chromium:790163 TBR=mmoss@chromium.org Change-Id: I5ba0f9c3d55238531d4ebc835f60270386cd5702 Reviewed-on: https://chromium-review.googlesource.com/c/1305251Reviewed-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@{#603618}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/ca9994a1..bb933756 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I7f1cb9400d33ca060da14987d4b375514b492a7d Reviewed-on: https://chromium-review.googlesource.com/c/1305210Reviewed-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@{#603617}
-
Vlad Tsyrklevich authored
This allocator is adapted from the GuardedPageAllocator in tcmalloc. The allocator is intended to be a 'debug' allocator to help catch memory errors like buffer overflows and use-after-frees. It does so by giving allocations an entire page and left- or right- aligning them between guard pages (to catch both underflows and overflows). It also sets pages inaccessible once they have been freed to detect use-after-frees and can also detect double frees. Forthcoming changes add an allocator shim to sample allocations to this allocator and to add additional debugging context when crashes due to GWP-ASan occur. GWP-ASan is going to be launched on Windows first; however, if it’s successful it will be ported to other platforms (and therefore also be used by different embedders.) Bug: 896019 Change-Id: I358e1b6f91569d1d448fc7ee16d5df27ed2467aa Reviewed-on: https://chromium-review.googlesource.com/c/1284699 Commit-Queue: Vlad Tsyrklevich <vtsyrklevich@chromium.org> Commit-Queue: Vitaly Buka <vitalybuka@chromium.org> Reviewed-by:
Cait Phillips <caitkp@chromium.org> Reviewed-by:
Albert J. Wong <ajwong@chromium.org> Reviewed-by:
Vitaly Buka <vitalybuka@chromium.org> Cr-Commit-Position: refs/heads/master@{#603616}
-
Fabrice de Gans-Riberi authored
This adds the http service package to a new CIPD archive. Bug: 874155 Test: Locally, build still works. Change-Id: I44937c496a1af342d0bf7f67581cef4c0fb83cb9 Reviewed-on: https://chromium-review.googlesource.com/c/1300674 Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org> Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Cr-Commit-Position: refs/heads/master@{#603615}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/25224e786ffe..0da64b5e1009 git log 25224e786ffe..0da64b5e1009 --date=short --no-merges --format='%ad %ae %s' 2018-10-29 tobine@google.com Add build-id to tests for Android Created with: gclient setdep -r src/third_party/angle@0da64b5e1009 The AutoRoll server is located here: https://autoroll.skia.org/r/angle-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: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=ynovikov@chromium.org Change-Id: I0fdce42fd43316ffe506372fe4c3cc107ca033ec Reviewed-on: https://chromium-review.googlesource.com/c/1305894Reviewed-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@{#603614}
-
Mark Pearson authored
It's enabled by default these days. Bug: 783500,364301 Change-Id: I72cedea29df687672bcc4e3a87cc984b1e3c42d5 Reviewed-on: https://chromium-review.googlesource.com/c/1066794 Commit-Queue: Mark Pearson <mpearson@chromium.org> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Cr-Commit-Position: refs/heads/master@{#603613}
-
Patrick Monette authored
The feature was incorrectly committed as enabled by default in this CL: https://chromium-review.googlesource.com/c/chromium/src/+/1241563 Bug: 884075 Tbr: sky@chromium.org Change-Id: I8d7df2adcd4d774684d1e24ce3b109ea43e7e7cb Reviewed-on: https://chromium-review.googlesource.com/c/1305879Reviewed-by:
Patrick Monette <pmonette@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Patrick Monette <pmonette@chromium.org> Cr-Commit-Position: refs/heads/master@{#603612}
-
Stephen Martinis authored
This bot is totally broken at the moment. Remove it so it doesn't block CQ. TBR=jbudorick NOTRY=true Bug: 899908 Change-Id: Ie6eca4c1bf8a67821e5a6570a59255fc6a87f54d Reviewed-on: https://chromium-review.googlesource.com/c/1306396 Commit-Queue: Stephen Martinis <martiniss@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#603611}
-
Quan Nguyen authored
Bug: 890912 Change-Id: I4e58b038a6ff288d47e9c37c6b733e6586d48773 Reviewed-on: https://chromium-review.googlesource.com/c/1300097 Commit-Queue: Quan Nguyen <qnnguyen@chromium.org> Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Cr-Commit-Position: refs/heads/master@{#603610}
-
rbpotter authored
Previously, it was not possible to refresh Print Preview using dev tools. However, it is now possible to do so, and as a result renderer/compositor messages can return to a refreshed Print Preview page that is not expecting any messages, leading to a renderer kill. Since the preview ui id is used only for routing messages from the PrintPreviewMessageHandler back to the appropriate PrintPreviewUI instance, which then forwards them to the PrintPreviewHandler that ultimately sends them to the Print Preview Web UI, it should not be initialized until the web UI is ready to receive messages. It should also be reset whenever the web UI is reloaded. This can be accomplished by setting the preview ui id in OnJavascriptAllowed() and clearing it in OnJavascriptDisallowed() or the PrintPreviewUI destructor, whichever occurs first. Refreshed Preview UIs will then have a different unique identifier after each refresh, which ensures renderer messages intended for previous instances of the web UI page will be dropped instead of being received by the handler and causing a renderer kill. Bug: 874744 Change-Id: Ia43aa9abb97e7952ec3761e5fb016f6513c1c982 Reviewed-on: https://chromium-review.googlesource.com/c/1302676Reviewed-by:
Lei Zhang <thestig@chromium.org> Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Cr-Commit-Position: refs/heads/master@{#603609}
-
Dominic Mazzoni authored
This reverts commit 9a0f2af8. Reason for revert: Chrome OS compile failure: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/linux-chromeos-dbg/8596 Original change's description: > Create TouchSelectionMenuViews to separate Menu > > views::TouchSelectionMenuRunnerViews::Menu should be better by > separating it on their own class, this CL introduces > TouchSelectionMenuViews. > > Bug: None > Test: Build. > Change-Id: I6e23c379abc7eb746713dde1b9224389a98014e6 > Reviewed-on: https://chromium-review.googlesource.com/c/1300054 > Commit-Queue: David Jacobo <djacobo@chromium.org> > Reviewed-by: Mohsen Izadi <mohsen@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Cr-Commit-Position: refs/heads/master@{#603576} TBR=sky@chromium.org,mohsen@chromium.org,djacobo@chromium.org Change-Id: I8891d3b3c2df888e8de21ddc391b01871ecd33d3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: None Reviewed-on: https://chromium-review.googlesource.com/c/1306393Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#603608}
-
James Hawkins authored
There is no longer a trial run in the new setup flow. R=hansberry@chromium.org Bug: 899324 Test: none Change-Id: Ic466140fbe18890e707f3338a38b58f385af0f2f Reviewed-on: https://chromium-review.googlesource.com/c/1302704 Commit-Queue: James Hawkins <jhawkins@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Reviewed-by:
Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#603607}
-
Andrey Kosyakov authored
Bug: 899303 Change-Id: Ibefd04bab772724105d64b9d83a2fafddd1c85a5 Reviewed-on: https://chromium-review.googlesource.com/c/1305494 Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#603606}
-
Kevin Strohbehn authored
This is a reland of 0b107635 Includes changes to fix MSAN issues Bug: 898712, 899158 Original change's description: > Makes wallpaper dim in tablet mode, without relying on app_list_shield > > Bug: 898712 > Change-Id: I96ba08fec3f7df8547d753ff4d31366345be0ac8 > Reviewed-on: https://chromium-review.googlesource.com/c/1298507 > Reviewed-by: Weidong Guo <weidongg@chromium.org> > Reviewed-by: Xiyuan Xia <xiyuan@chromium.org> > Commit-Queue: Kevin Strohbehn <ginko@google.com> > Cr-Commit-Position: refs/heads/master@{#602938} Bug: 898712 Change-Id: Ief534b6dc58b5d36b3f96952141a51312c50a79f Reviewed-on: https://chromium-review.googlesource.com/c/1303233 Commit-Queue: Kevin Strohbehn <ginko@google.com> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#603605}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/625dca84765d..25da2e8be18d git log 625dca84765d..25da2e8be18d --date=short --no-merges --format='%ad %ae %s' 2018-10-29 dtu@chromium.org [pinpoint] Temporarily remove auth from gerrit_service.GetChange(). 2018-10-29 erikchen@chromium.org Reduce verbosity of logging for ADB commands. Created with: gclient setdep -r src/third_party/catapult@25da2e8be18d 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 BUG=chromium:899427,chromium:891898 TBR=sullivan@chromium.org Change-Id: I78a868219581286ce001a19c20005054e6a50c64 Reviewed-on: https://chromium-review.googlesource.com/c/1305893Reviewed-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@{#603604}
-
David Bokan authored
Bug: 861618 Change-Id: If5f91df67aa66a1292073f051fb551b9193b7078 Reviewed-on: https://chromium-review.googlesource.com/c/1305297Reviewed-by:
Fady Samuel <fsamuel@chromium.org> Commit-Queue: David Bokan <bokan@chromium.org> Cr-Commit-Position: refs/heads/master@{#603603}
-
Wez authored
--brave-new-test-launcher was used to opt-in to TestLauncher batching and parallelization of tests. Suites using TestLauncher now default to that mode, with --single-process-tests used to opt-out runs where necessary, so remove mentions of the old opt-in command-line parameter. Change-Id: I1b0536d707676cd227dc9a03daeecbefb5e709ad Reviewed-on: https://chromium-review.googlesource.com/c/1303861Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#603602}
-
Collin Baker authored
Currently, keyboard focus disappears if the DownloadShelfView is closed while it is focused. This change moves focus to the web contents when it is closing. Bug: 846466 Change-Id: I2fd24d5e918a6be7ce46299b31b53d5fa92aaa97 Reviewed-on: https://chromium-review.googlesource.com/c/1302871 Commit-Queue: Collin Baker <collinbaker@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#603601}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/68825776f4b4..c09dc8ac723f git log 68825776f4b4..c09dc8ac723f --date=short --no-merges --format='%ad %ae %s' 2018-10-29 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 50b105973431..3957b7f8bd86 (1 commits) 2018-10-29 herb@google.com Move files in GN 2018-10-29 benjaminwagner@google.com Update Win10 GTX660/GTX960 drivers. 2018-10-29 mtklein@google.com also catch 1^y == 1 as a special case 2018-10-29 michaelludwig@google.com Reland "Extract per-edge quad vertex tesselation code into reusable interface" 2018-10-29 caryclark@skia.org sync bookmaker docs with canvas 2018-10-29 reed@google.com expose SkFont as public way to use TextBlobBuilder 2018-10-29 halcanary@google.com run infra/skqp/build_apk.sh from any directory 2018-10-29 bsalomon@google.com Remove SrcRectConstraint from drawImageRect overloads with no src rect 2018-10-29 brianosman@google.com Add GrColor4h (half-float), for use in Ops and (eventually) vertices 2018-10-29 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 df73a8e5ffdb..4a22f4b04619 (1 commits) 2018-10-29 reed@google.com add helpers to SkFont (and SkTypeface) Created with: gclient setdep -r src/third_party/skia@c09dc8ac723f The AutoRoll server is located here: https://autoroll.skia.org/r/skia-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-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;master.tryserver.blink:linux_trusty_blink_rel TBR=herb@chromium.org Change-Id: If6bcb4c4c3d5176badc81587f329cf82fcdd378f Reviewed-on: https://chromium-review.googlesource.com/c/1305854Reviewed-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@{#603600}
-
erikchen authored
Previously, Android test results were propagated after all tests finished running. In the event of an Exception, none of the test results would be written to file. This CL slightly changes the control flow of TestRun.RunTests(). Instead of returning a results array, it now receives a results array as input and modifies the array as it receives test results. This allows the json_writer context TearDown() to serialize the partial test results. This CL updates local_device_test_run.py to have the correct flow. The flow of local_device_perf_test_run.py and local_machine_junit_test_run.py are left untouched -- they can be modified in the future if it's deemed necessary. This minimizes the size of this CL. Bug: 895027 Change-Id: I60fe78da993de366d678252b84a91aaff044c10b Reviewed-on: https://chromium-review.googlesource.com/c/1305396 Commit-Queue: Erik Chen <erikchen@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#603599}
-
Andrey Kosyakov authored
Bug: 899303 Change-Id: If13f08e4e45e4f4f4cfc16bd4f2921cab22ecc07 Reviewed-on: https://chromium-review.googlesource.com/c/1303181 Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#603598}
-
Antonio Gomes authored
BUG=889883 Change-Id: Ia37ffc9bc4dfb0247137b6bfa8cf272332efb1e6 Reviewed-on: https://chromium-review.googlesource.com/c/1304573Reviewed-by:
Nathan Parker <nparker@chromium.org> Commit-Queue: Antonio Gomes <tonikitoo@igalia.com> Cr-Commit-Position: refs/heads/master@{#603597}
-
Nate Chapin authored
Previously task.result sometimes returned the result value directly. Making it always return a promise makes it easily to handle in JS. Bug: 879306 Change-Id: I6c0168d828d8234875a20e1128b14f1ab6603d4f Reviewed-on: https://chromium-review.googlesource.com/c/1303100Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Commit-Queue: Nate Chapin <japhet@chromium.org> Cr-Commit-Position: refs/heads/master@{#603596}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/9201a4e1a936..9ab423a548ac git log 9201a4e1a936..9ab423a548ac --date=short --no-merges --format='%ad %ae %s' 2018-10-29 chrome-bot@chromium.org Update config settings by config-updater. 2018-10-29 hungte@chromium.org Remove amd64-generic-goofy build target. 2018-10-29 martinroth@chromium.org chromeos_config: disable grunt firmware branch configs Created with: gclient setdep -r src/third_party/chromite@9ab423a548ac 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. TBR=chrome-os-gardeners@chromium.org Change-Id: I6a3493cb5bf51996ec2b12f09638cdb8ac40fb04 Reviewed-on: https://chromium-review.googlesource.com/c/1305853Reviewed-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@{#603595}
-