- 03 Feb, 2018 40 commits
-
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=govind@chromium.org Change-Id: I8f16904f331848466d4fcfef6d2680f829120970 Reviewed-on: https://chromium-review.googlesource.com/900225Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#534255}
-
Morten Stenshorne authored
Let the layout algorithm for a child figure out the size of the child, instead of estimating it in LayoutNewFormattingContext(). Gets rid of the "fixed inline size" case. This also means that we're trusting legacy layout more than before to correctly size legacy objects (such as tables, flexbox and replaced content), so we need to be more careful to provide legacy layout with the correct input data, i.e. the containing block size override. In particular, we cannot always use the percentage resolution size from the constraint space to resolve widths and heights on the child (only do that if the specified size is indeed a percentage; otherwise use available size, which has been adjusted for adjacent floats). Some work was also needed to make sure that legacy layout also respects this override to a greater extent than before. Absolutely positioned objects are still not allowed to size themselves (legacy or not). Not sure if that's good in the long run (then again, sizing of absolutely positioned objects is rather special). There was one missing check for content logical height override for abspos objects, which suddenly became an issue, and had to be fixed. Remove margin hacks for LayoutTable. Similar hacks would have been needed for flexbox, grid, etc. anyway. Instead, have LayoutNewFormattingContext() add the child's inline margins to the layout opportunity, so that all algorithms resolve auto inline sizes correctly (typically by subtracting margins from available space). Even pure NG layout algorithms need this. If it turns out (after layout) that the child won't fit within the layout opportunity found, find a new opportunity and lay out again. Repeat this step until we find something that fits. This potentially results in more layout passes than before, but we're going to have to do this for block fragmentation anyway, so better be consistent about it. Quite a few tests started to pass. Then, also, two tests regressed, both pertaining to the non-standard width:-webkit-fill-available declaration. One of the changes almost looks like an improvement, but it's not compatible with other engines. The spec is unclear. Bug: 807708, 807830 Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng Change-Id: Idf9f20c89640ea1c8d7659865a265e889c8211fd Reviewed-on: https://chromium-review.googlesource.com/888059Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#534254}
-
Kevin Bailey authored
We "ping" (with http) queries that might be host names. Some TLDs respond as hosts. Filter these out from pinging. (Assume the user would not want to navigate there.) Bug: 669785 Change-Id: I11905edf854e52f346048f7f705acab913d02984 Reviewed-on: https://chromium-review.googlesource.com/886562 Commit-Queue: Kevin Bailey <krb@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#534253}
-
Wenzhao Zang authored
The new wallpaper picker has two main differences with the old one: 1) The images are fetched from a different server (it's already implemented in backdrop_wallpaper_handlers). 2) The style changes. The general logic in *.js files are the same, so we prefer to reuse the existing code and add flag checks here and there. (We'll be able to clean up the code only used by the old picker when it's mature.) Bug: 800945 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Icf48369e86644046fee0f220a212661daefa495d Reviewed-on: https://chromium-review.googlesource.com/898205Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org> Cr-Commit-Position: refs/heads/master@{#534252}
-
Emily Hanley authored
Bug: 744679 Change-Id: Idc3ca11a2a3cf80e18f8da45c6943232672d8890 Reviewed-on: https://chromium-review.googlesource.com/897347Reviewed-by:
Ned Nguyen <nednguyen@google.com> Commit-Queue: Emily Hanley <eyaich@chromium.org> Cr-Commit-Position: refs/heads/master@{#534251}
-
https://chromium.googlesource.com/angle/angle.git/+log/df9ad2be8c97..9a608c0e1f8c $ git log df9ad2be8..9a608c0e1 --date=short --no-merges --format='%ad %ae %s' 2018-02-02 ynovikov Vulkan: request coherent memory for StagingImage Created with: roll-dep src/third_party/angle The AutoRoll server is located here: https://angle-chromium-roll.skia.org 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=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=jmadill@chromium.org Change-Id: I39129b1d10f5de0e0eebf73cb8a8ea0c9bafde25 Reviewed-on: https://chromium-review.googlesource.com/900422 Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#534250}
-
Gyuyoung Kim authored
If updated files don't use base::WrapUnique, base/memory/ptr_util.h includes are changed to <memory>. Bug: 755727 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: Ib2b82ee10c9c4367896055e882df9b241edc666f Reviewed-on: https://chromium-review.googlesource.com/890575 Commit-Queue: Gyuyoung Kim <gyuyoung.kim@lge.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Elliot Glaysher <erg@chromium.org> Reviewed-by:
Ben Wells <benwells@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#534249}
-
Kenneth Russell authored
This reverts commit 173bbfd7. Reason for revert: one of the new tests is failing on the chromium.gpu.fyi waterfall; see https://bugs.chromium.org/p/chromium/issues/detail?id=804043#c6 . Original change's description: > Deduplicate WebXR tests > > Deduplicates most WebVR/WebXR tests into one test implementation that > takes different arguments for WebVR and WebXR. > > Bug: 804043 > Change-Id: I1486a4d8e75d91fe98c1298f3b528df4bc01d938 > Reviewed-on: https://chromium-review.googlesource.com/896800 > Commit-Queue: Brian Sheedy <bsheedy@chromium.org> > Commit-Queue: Michael Thiessen <mthiesse@chromium.org> > Reviewed-by: Michael Thiessen <mthiesse@chromium.org> > Cr-Commit-Position: refs/heads/master@{#533890} TBR=mthiesse@chromium.org,bsheedy@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 804043 Change-Id: I1ec02deb49bcdbb26940f95b80a9df45ba63d585 Reviewed-on: https://chromium-review.googlesource.com/900463Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#534248}
-
https://chromium.googlesource.com/native_client/src/native_client.git/+log/b48266b051f5..8ad1515975c0 $ git log b48266b05..8ad151597 --date=short --no-merges --format='%ad %ae %s' 2018-02-02 dschuff Update revision for PNaCl Created with: roll-dep src/native_client BUG=<none> The AutoRoll server is located here: https://nacl-roll.skia.org 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=mseaborn@chromium.org Change-Id: I06a7d80c9ebd08933d673723432716460b8a1e4a Reviewed-on: https://chromium-review.googlesource.com/899932 Commit-Queue: nacl-chromium-autoroll <nacl-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
nacl-chromium-autoroll <nacl-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#534247}
-
Shimi Zhang authored
This CL 1) Increased the frequency of #handleDragSTartedOrMoved() call of InsertionSelectionHandleObserver by introducing #onDragUpdate() to SelectionPopupControllerImpl, so the movement of the observer will be more smooth. 2) Make the observer follow the gesture of user's finger other than stick it to the insertion/selection handles. 3) Fixed a bug that longpress selection triggers InsertionSelectionHandleObserver. Bug: 798017, 806960 Change-Id: Ibdbfd994a15ad9ddc6632cec0f0457a3e5225022 Reviewed-on: https://chromium-review.googlesource.com/894855 Commit-Queue: Shimi Zhang <ctzsm@chromium.org> Reviewed-by:
Mohsen Izadi <mohsen@chromium.org> Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Pedro Amaral <amaralp@chromium.org> Cr-Commit-Position: refs/heads/master@{#534246}
-
dpapad authored
Bug: 738611 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: Icfcf0ee1b46ff4b16fd8ace0e21de6f27bef0f1a Reviewed-on: https://chromium-review.googlesource.com/898242Reviewed-by:
Hector Carmona <hcarmona@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#534245}
-
iOS Autoroller authored
TBR=smut Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I03363dc2eb8f4e543443fc7493835c8a76830e83 Reviewed-on: https://chromium-review.googlesource.com/899225 Commit-Queue: iOS Autoroller <ios-autoroller@chromium.org> Reviewed-by:
iOS Autoroller <ios-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#534244}
-
https://skia.googlesource.com/skia.git/+log/dd3eca1fc5e7..5bb82cbecd74 $ git log dd3eca1fc..5bb82cbec --date=short --no-merges --format='%ad %ae %s' 2018-02-02 bsalomon Revert "Revert "Revert "Revert "Redefine the meaning of sample counts in GPU backend."""" 2018-02-02 angle-skia-autoroll Roll skia/third_party/externals/angle2/ c7295f4d3..df9ad2be8 (1 commit) 2018-02-02 reed center frame to make hairline more repo on gpus 2018-02-02 egdaniel Update GrYUVGenerator to upload to texture vs use writePixels 2018-02-02 benjaminwagner Add MacBookAir jobs. Created with: roll-dep src/third_party/skia The AutoRoll server is located here: https://autoroll.skia.org 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=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel TBR=bungeman@chromium.org Change-Id: Icbb9b5542789912016a002a8211d87e30b4d2542 Reviewed-on: https://chromium-review.googlesource.com/899510 Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#534243}
-
Mohamad Ahmadi authored
TBR=jam@chromium.org Bug: 808578 Change-Id: Id77a3e997b96405ac6c7198f5a78d79b729ab987 Reviewed-on: https://chromium-review.googlesource.com/899471Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#534242}
-
Lei Tian authored
Now BrowserActionActivity is only available for canary, dev and default, make it available for all channels. Bug: 808540 Change-Id: Ifd96fcb972febd95efc10ad834290fef40c019fd Reviewed-on: https://chromium-review.googlesource.com/899875Reviewed-by:
Ted Choc <tedchoc@chromium.org> Commit-Queue: Lei Tian <ltian@chromium.org> Cr-Commit-Position: refs/heads/master@{#534241}
-
Trent Apted authored
crbug/788271 is a mystery, crashing in objc_msgSend without triggering any zombie warnings. crbug/808318 points to a leaked WidgetObserver affecting all platforms, but has no indication of what the observer is, or what window it observes. Record class names and the window title in crash keys. The window title is usually set by the framework, even if it is not displayed anywhere. Bug: 788271, 808318 Change-Id: I09f9697bfca4e91c8f3b0e8dba125c1eb39cde4b Reviewed-on: https://chromium-review.googlesource.com/896774 Commit-Queue: Trent Apted <tapted@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#534240}
-
Findit authored
This reverts commit e7ac3400. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 534238 as the culprit for failures in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2U3YWMzNDAwYTUyM2EwMDIwMGQwZjg5ZTY0NWY2OGFjNWRiYTZlZjUM Sample Failed Build: https://ci.chromium.org/buildbot/chromium/Mac/37728 Original change's description: > Update //url/mojo to use standard naming conventions. > > <component>/mojom and <type>_mojom_traits.{cc,h} are now the standard > names that should be used for directories containing mojom interface > definitions and type mapping traits respectively. > > Bug: 806965 > Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_mojo > Change-Id: I814f5b2de365b27e722dd5c87f241238d5c0fff2 > Reviewed-on: https://chromium-review.googlesource.com/894630 > Reviewed-by: Jochen Eisinger <jochen@chromium.org> > Reviewed-by: Ken Rockot <rockot@chromium.org> > Commit-Queue: Daniel Cheng <dcheng@chromium.org> > Cr-Commit-Position: refs/heads/master@{#534238} Change-Id: Iebcf43f129254cb5d6bbb785bcce660543b010ec No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 806965 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_mojo Reviewed-on: https://chromium-review.googlesource.com/900502 Cr-Commit-Position: refs/heads/master@{#534239}
-
Daniel Cheng authored
<component>/mojom and <type>_mojom_traits.{cc,h} are now the standard names that should be used for directories containing mojom interface definitions and type mapping traits respectively. Bug: 806965 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_mojo Change-Id: I814f5b2de365b27e722dd5c87f241238d5c0fff2 Reviewed-on: https://chromium-review.googlesource.com/894630Reviewed-by:Jochen Eisinger <jochen@chromium.org> Reviewed-by:
Ken Rockot <rockot@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#534238}
-
Hwanseung Lee authored
CSSUnitValue.unit should be immutable to prevent cyclic references Bug: 803687 Change-Id: I35f79ec2491277fcb2d02ce85a2e9c6ecd8c3a07 Reviewed-on: https://chromium-review.googlesource.com/897177Reviewed-by:
Darren Shen <shend@chromium.org> Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com> Cr-Commit-Position: refs/heads/master@{#534237}
-
Steve Kobes authored
These baseline paths are no longer applicable now that the REF is status: experimental (http://crrev.com/533694). Bug: 417782 Change-Id: I9712a2da081252cc1aa159418f40cbc9a0d309d6 Reviewed-on: https://chromium-review.googlesource.com/897824 Commit-Queue: Steve Kobes <skobes@chromium.org> Reviewed-by:
Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#534236}
-
Sadrul Habib Chowdhury authored
Set up a startup sampling-profiler for the compositor thread in the renderer process. Notable changes: . Callback to the RendererClient when the compositor-thread is created. The client uses this callback to set-up the sampling profiler. . Allow the renderer processes to connect to the browser to report the profiler data over mojom. Add the --start-stack-profiler flag to the renderer's cmd-line so that it can initiate sampling profiler. Select every fifth renderer for collecting the profile data from, so that we can still get enough useful data, but don't overburden bandwidth or memory usage. BUG=788808 Change-Id: I478184502a17f4dbb83f03a67a7ef482c92c0a78 Reviewed-on: https://chromium-review.googlesource.com/894848Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Mike Wittman <wittman@chromium.org> Reviewed-by:
Tom Sepez <tsepez@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#534235}
-
Nico Weber authored
Fixes a bug where middle mouse clicks where ignored when remoting into a Chrome OS device. Also found https://chromium-review.googlesource.com/c/chromium/src/+/899585 Bug: 177475,808537 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_vr;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I64e259f1e2d2c817364ee9249e72cb24abc395be Reviewed-on: https://chromium-review.googlesource.com/899984 Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Reviewed-by:
Lambros Lambrou <lambroslambrou@chromium.org> Cr-Commit-Position: refs/heads/master@{#534234}
-
Kevin Marshall authored
Fuchsia tests run under two layers of virtualization which carries a significant performance penalty. The DiskCacheBackendTest load tests specified values which were too computationally intensive, causing the tests to time out. Bug: 807882 Change-Id: I1f44436a9f0967b072aa9da160b5fc15bc7f730f Reviewed-on: https://chromium-review.googlesource.com/898006 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by:
Maks Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#534233}
-
rbpotter authored
- Make dialog fixed height - Remove show all button - Improve highlighting speed - Do not scroll search box - Fix problem with footer disappearing Bug: 773928 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I4d19b7fa4b2e8246eb34e8c60d10382688e6a747 Reviewed-on: https://chromium-review.googlesource.com/898347 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#534232}
-
Ryan Tseng authored
* recipes.cfg no longer exists here * jbudorick@ approves cq.cfg changes, so it'd make sense if he was an owner. * dpranke@ should be in here too. Bug: Change-Id: I6540c1f6f39c92e76abc301f67987096f50ada95 Reviewed-on: https://chromium-review.googlesource.com/899511 Commit-Queue: Ryan Tseng <hinoka@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Reviewed-by:
Andrii Shyshkalov <tandrii@chromium.org> Cr-Commit-Position: refs/heads/master@{#534231}
-
Thomas Anderson authored
This reverts commit a3dd29b2. Reason for revert: Causing DownloadContentTest.DownloadAttributeBlobURL to fail on Linux Tests, Linux Tests (dbg)(1), and Linux Tests (dbg)(1)(32). https://ci.chromium.org/buildbot/chromium.linux/Linux%20Tests/66991 https://ci.chromium.org/buildbot/chromium.linux/Linux%20Tests%20%28dbg%29%281%29%2832%29/47823 https://ci.chromium.org/buildbot/chromium.linux/Linux%20Tests%20%28dbg%29%281%29/70044 Original change's description: > Bounce Blob URL revoking through the UI thread to give navigation a chance. > > Navigation IPCs are handled on the UI thread so if a blob URL is revoked > immediately after navigating the revocation will almost always happen before > the navigation code has had a chance to post a task back to the IO thread to > actually perform the request. With this change revocation is hopefully > delayed just long enough to make navigation work again. > > Bug: 807639 > Change-Id: I2afde86dd203c61cbb03cc02ac62ec21c7e7d704 > Reviewed-on: https://chromium-review.googlesource.com/899666 > Reviewed-by: Jochen Eisinger <jochen@chromium.org> > Commit-Queue: Marijn Kruisselbrink <mek@chromium.org> > Cr-Commit-Position: refs/heads/master@{#534119} TBR=mek@chromium.org,jochen@chromium.org Change-Id: Ia460136d52f214d3d2914a8004ebe65c87e90bc3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 807639 Reviewed-on: https://chromium-review.googlesource.com/900442Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Commit-Queue: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#534230}
-
https://chromium.googlesource.com/native_client/src/native_client.git/+log/476698afdd0b..b48266b051f5 $ git log 476698afd..b48266b05 --date=short --no-merges --format='%ad %ae %s' 2018-02-02 dschuff PNaCl: Update llvm revision in pnacl/COMPONENT_REVISIONS 2018-02-01 dschuff Update gsutil used by gsd_storage on the buildbots 2018-02-01 dschuff Fix CMake C_COMPILER_LAUNCHER command 2018-02-01 dschuff Update Goma command for toolchain host build Created with: roll-dep src/native_client BUG=none The AutoRoll server is located here: https://nacl-roll.skia.org 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=mseaborn@chromium.org Change-Id: I8eb7860327e6d0b72ce5c775bc0201be904a2f1b Reviewed-on: https://chromium-review.googlesource.com/899958 Commit-Queue: nacl-chromium-autoroll <nacl-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
-
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/5d5f22ce9d6f..3a998d1b232f $ git log 5d5f22ce9..3a998d1b2 --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/depot_tools The AutoRoll server is located here: https://depot-tools-chromium-roll.skia.org 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=agable@chromium.org Change-Id: I4a2b41468c3611b57f8758f7824119ae249abe5b Reviewed-on: https://chromium-review.googlesource.com/900292 Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#534228}
-
https://pdfium.googlesource.com/pdfium.git/+log/bbeb10daef8b..b1d7872faacb $ git log bbeb10dae..b1d7872fa --date=short --no-merges --format='%ad %ae %s' 2018-02-02 thestig Teach the presubmit check to look for checkdeps in other places. 2018-02-02 thestig Remove third_party/build/build_config.h. Created with: roll-dep src/third_party/pdfium The AutoRoll server is located here: https://pdfium-roll.skia.org 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=dsinclair@chromium.org Change-Id: Idb5eca6dc20419a3aec04d1777e87421e178f95f Reviewed-on: https://chromium-review.googlesource.com/900313 Commit-Queue: pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
pdfium-chromium-autoroll <pdfium-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#534227}
-
Stefan Zager authored
BUG=808341 R=skobes@chromium.org Change-Id: I298ffd2134ec5021682bc443a5c6a9ba4a9cc13c Reviewed-on: https://chromium-review.googlesource.com/899928Reviewed-by:
Steve Kobes <skobes@chromium.org> Commit-Queue: Stefan Zager <szager@chromium.org> Cr-Commit-Position: refs/heads/master@{#534226}
-
v8-autoroll authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/0f936675..ac7384b3 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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org Change-Id: I3968c6930e40e08e22f70186c9938c30e478ca1d Reviewed-on: https://chromium-review.googlesource.com/900245Reviewed-by:
v8 autoroll <v8-autoroll@chromium.org> Commit-Queue: v8 autoroll <v8-autoroll@chromium.org> Cr-Commit-Position: refs/heads/master@{#534225}
-
Tim Brown authored
This is to simplify our status icon code. Ubuntu Zesty has been EOL'd, so that has been removed too. Bug: 799144 Change-Id: I325144461a330b6321a087e4357e9033d7fdd880 Reviewed-on: https://chromium-review.googlesource.com/899867Reviewed-by:
-
dpapad authored
Bug: 738611 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I7da1eb6af56c5a6dbf6c8c6ea73d1e738df26de0 Reviewed-on: https://chromium-review.googlesource.com/898203Reviewed-by:
Scott Chen <scottchen@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#534223}
-
Bence Béky authored
This will be used by HttpStreamFactoryImpl::Job to find a SpdySession that supports Websocket over HTTP/2. Bug: 801564 Change-Id: Idac6a13743094c59a7ffa2a43e1fed7554361dd8 Reviewed-on: https://chromium-review.googlesource.com/896982 Commit-Queue: Bence Béky <bnc@chromium.org> Reviewed-by:
Helen Li <xunjieli@chromium.org> Cr-Commit-Position: refs/heads/master@{#534222}
-
Jinsuk Kim authored
In preparation of moving the class ContentView out of content, this CL makes the interface SmartClipProvider implemented by ContentView public, and updates dependencies accordingly. With this change, ContentView doesn't use non-public class any more. Also found that there's no embedder using the public interface SmartClipCallback. So deleted it. Bug: 807155 Change-Id: Icac5956ccab217095d2216d65176e2e0d1665184 Reviewed-on: https://chromium-review.googlesource.com/894967Reviewed-by:
Changwan Ryu <changwan@chromium.org> Reviewed-by:
-
https://webrtc.googlesource.com/src.git/+log/cc7125f2400b..8eca1ff5107e $ git log cc7125f24..8eca1ff51 --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc The AutoRoll server is located here: https://webrtc-chromium-roll.skia.org 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=master.tryserver.chromium.linux:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng;master.tryserver.chromium.win:win-msvc-dbg TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I825d48a891f789647b25b1501bf87759e7065c0b Reviewed-on: https://chromium-review.googlesource.com/899652 Commit-Queue: webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
webrtc-chromium-autoroll <webrtc-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#534220}
-
Menglu Huang authored
Change-Id: Ice14942fc6f16198a62d6aaa15d1ba5a80f9c040 Reviewed-on: https://chromium-review.googlesource.com/896369 Commit-Queue: Menglu Huang <huangml@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#534219}
-
Peter Boström authored
Bug: chromium:807886 Change-Id: I1050d89178fb6682cafa3a03327a9c1245203b26 Reviewed-on: https://chromium-review.googlesource.com/900064Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#534218}
-
Peter Boström authored
Also removes a stale promo string that has been replaced. Bug: chromium:807886 Change-Id: I63d64ec65573eb2742fcb59cea790a720fae0a41 Reviewed-on: https://chromium-review.googlesource.com/900053Reviewed-by:
-
Miguel Casas authored
Gpu FeatureInfo::FeatureFlags.chromium_image_xr30 doesn't work on Swiftshader because it doesn't support GL_BGRA(_EXT) for glImage2D(), making our texture uploads fail. This failure is legit because GLES 3.0 supports only GL_RGBA data format. So this CL disables chromium_image_xr30 until the swiftshader bug is addressed (adding a TODO), and also corrects the OpenGL version where GL_EXT_texture_type_2_10_10_10_REV was inlined, which is 3.3 and not 4.2 as I wrote erroneously before, oops! (see http://go/gl3.3) Bug: 808172, swiftshader:95 Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Change-Id: I0c6952b14ff53fb504bf292c51a8bc2ffe612918 Reviewed-on: https://chromium-review.googlesource.com/899462Reviewed-by:
-
