- 14 Nov, 2018 40 commits
-
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/fca8fd620190..ccad5e333472 git log fca8fd620190..ccad5e333472 --date=short --no-merges --format='%ad %ae %s' 2018-11-14 geofflang@chromium.org GL: Work around driver returning negative GL_MAX_SERVER_WAIT_TIMEOUT 2018-11-14 syoussefi@chromium.org Vulkan: Implement EXT_texture_filter_anisotropic Created with: gclient setdep -r src/third_party/angle@ccad5e333472 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=cwallez@chromium.org Change-Id: Ica902bb9614c10b21750d5e1b8c8ba6ad7d2a044 Reviewed-on: https://chromium-review.googlesource.com/c/1336267Reviewed-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@{#608134}
-
Wei Li authored
When the browser starts in Kiosk mode, it should enter into full screen mode without top Chrome UI. This CL fixes this, and also re-enables a browser test that relied on this behavior. BUG=470724 Change-Id: Icb043b1000d29908c7f4114c327c1d7355585bd4 Reviewed-on: https://chromium-review.googlesource.com/c/1334942 Commit-Queue: Wei Li <weili@chromium.org> Reviewed-by:
Elly Fong-Jones <ellyjones@chromium.org> Cr-Commit-Position: refs/heads/master@{#608133}
-
Sorin Jianu authored
Bug: 881076 Change-Id: I41d7f87d46225ebc919473e8bd165268d699e45e Reviewed-on: https://chromium-review.googlesource.com/c/1334411 Commit-Queue: Sorin Jianu <sorin@chromium.org> Reviewed-by:
Minh Nguyen <mxnguyen@chromium.org> Reviewed-by:
Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#608132}
-
Christopher Grant authored
--hash-style=gnu can be moved into the common shared library template. While merging these, I noticed that one instance uses mips64el, while the other uses mipsel64. This is suspect. BUG= Change-Id: I09e8db4f4c049da69a96f9afd442f2dbd5296252 Reviewed-on: https://chromium-review.googlesource.com/c/1331632Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Reviewed-by:
Tibor Goldschwendt <tiborg@chromium.org> Reviewed-by:
David Turner <digit@chromium.org> Commit-Queue: Christopher Grant <cjgrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#608131}
-
Mathieu Perreault authored
Bug: None Change-Id: Iaf37dc41d24d3fb28d0f26ceab8691145126a019 Reviewed-on: https://chromium-review.googlesource.com/c/1334292Reviewed-by:
Cait Phillips <caitkp@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Commit-Queue: Mathieu Perreault <mathp@chromium.org> Cr-Commit-Position: refs/heads/master@{#608130}
-
Oystein Eftevaag authored
Fixes a theoretical race where tracing could be stopped and immediately started again, and as we PostTask the destruction of the tracing session in theory the new tracing session could be destroyed rather than the old one. R=eseckler@chromium.org Bug: 900920 Change-Id: I2763100bb0915718cf1f1f0f685172d12fc24600 Reviewed-on: https://chromium-review.googlesource.com/c/1335953 Commit-Queue: Eric Seckler <eseckler@chromium.org> Reviewed-by:
Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#608129}
-
Alexei Svitkine authored
Previously, the code would create a set from all the known flags and compare the specified flags against them. But actually this is less efficient than just the O(n*m) search, because n being the number of flags set by the user and m being the number of available flags, since n will likely be small or 0 and then we don't need to do a lot of work. In particular, this also avoids copying a bunch of strings. Bug: 904575 Change-Id: I63e59d439c432338aea71eb6258e8f8b42f04921 Reviewed-on: https://chromium-review.googlesource.com/c/1334413 Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
ssid <ssid@chromium.org> Cr-Commit-Position: refs/heads/master@{#608128}
-
Martin Kreichgauer authored
Rather than only forwarding USB requests to the Windows WebAuthn API, we are going to forward all requests. This consequently renames the FidoAuthenticator subclass to WinWebAuthnApiAuthenticator. The corresponding FidoDiscovery is instantiated for all requests where the WebAuthn API is available (i.e., the feature is flag enabled, and the DLL can be loaded and is at least version 1). When it is indeed available, all other discoveries are disabled and the UI is suppressed via a newly introduced option in the TransportAvailabilityInfo struct relayed to embedders via the TransportAvailabilityObserver interface. Note this temporarily breaks caBLE whenever the Windows API is flag-enabled and available. (But the OS would presumably block the device communication in that case anyway.) Bug: 898718 Change-Id: If2bddac4bac519d1aa5aa9cb5d8fdc326297de73 Reviewed-on: https://chromium-review.googlesource.com/c/1330897 Commit-Queue: Martin Kreichgauer <martinkr@chromium.org> Reviewed-by:
Jun Choi <hongjunchoi@chromium.org> Reviewed-by:
Adam Langley <agl@chromium.org> Cr-Commit-Position: refs/heads/master@{#608127}
-
David Bertoni authored
Added a unit test to track performance of icon visibility checking. Also optimized the functions to exit early in the expected case. Added UMA to track elapsed time of the function. Bug: 805600 Change-Id: I01fbbfd44fe6c903d8c1326c36138d37ec30663d Reviewed-on: https://chromium-review.googlesource.com/c/1324849 Commit-Queue: David Bertoni <dbertoni@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#608126}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/fdc635d2a8ff..24643488d40a git log fdc635d2a8ff..24643488d40a --date=short --no-merges --format='%ad %ae %s' 2018-11-14 srte@webrtc.org Don't reset RTT Backoff timeout on route change. Created with: gclient setdep -r src/third_party/webrtc@24643488d40a 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: I3861e0e50e87dadba42add98701f8579ebff73fb Reviewed-on: https://chromium-review.googlesource.com/c/1335779Reviewed-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@{#608125}
-
Yue Cen authored
Bug: 904373 Change-Id: Ie1cbc2df7b63aca2ddc5b0686e666d16dd2b5f2d Reviewed-on: https://chromium-review.googlesource.com/c/1332407Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Yue Cen <rsgingerrs@chromium.org> Cr-Commit-Position: refs/heads/master@{#608124}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/a6150a3fe778..dc9d155d6216 git log a6150a3fe778..dc9d155d6216 --date=short --no-merges --format='%ad %ae %s' 2018-11-14 stevenperron@google.com Fix folding of volatile store. (#2048) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@dc9d155d6216 The AutoRoll server is located here: https://autoroll.skia.org/r/spirv-tools-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=dsinclair@chromium.org Change-Id: I0406b560139f9213b5d117496462133318f5e03c Reviewed-on: https://chromium-review.googlesource.com/c/1335842Reviewed-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@{#608123}
-
John Rummell authored
Also add some new tests to verify Initialize() failures. BUG=883620 TEST=new tests pass Change-Id: I8ed3ca04b37fcdca4b9c9c3483b1d7c696bf232a Reviewed-on: https://chromium-review.googlesource.com/c/1336059Reviewed-by:
Dan Sanders <sandersd@chromium.org> Commit-Queue: John Rummell <jrummell@chromium.org> Cr-Commit-Position: refs/heads/master@{#608122}
-
Danyao Wang authored
These test failures are not caused by SlimNav. Passing in the correct flags allow them to pass with --enable-features=SlimNavigationManager. Bug: 904885 Change-Id: I1d45cd4c68aedd478a04bf02830e2223424b92ba Reviewed-on: https://chromium-review.googlesource.com/c/1336056Reviewed-by:
Justin Cohen <justincohen@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Commit-Queue: Danyao Wang <danyao@chromium.org> Cr-Commit-Position: refs/heads/master@{#608121}
-
Anand K. Mistry authored
This revision is 2.7.5 plus a few build fixes. BUG=904655,903690,902860 Change-Id: Ie71481e1e7c423c0bc292ec108fb1a0e3fc12caa Reviewed-on: https://chromium-review.googlesource.com/c/1335052 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Noel Gordon <noel@chromium.org> Cr-Commit-Position: refs/heads/master@{#608120}
-
Tom Tan authored
Bug: 893460 Change-Id: I9def3ef624b5121c7e902efc01a18754f448b8ce Reviewed-on: https://chromium-review.googlesource.com/c/1332698Reviewed-by:
Mike Wittman <wittman@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Commit-Queue: Tom Tan <Tom.Tan@microsoft.com> Cr-Commit-Position: refs/heads/master@{#608119}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/6b8b30c8a1b1..35d4c6c88f92 git log 6b8b30c8a1b1..35d4c6c88f92 --date=short --no-merges --format='%ad %ae %s' 2018-11-14 benjhayden@chromium.org Fix merging single-bin Histograms with multi-bin Histograms. Created with: gclient setdep -r src/third_party/catapult@35d4c6c88f92 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:902009 TBR=sullivan@chromium.org Change-Id: I08f4ca7cdf79e02e8e00ec1142f6c7cabad841e9 Reviewed-on: https://chromium-review.googlesource.com/c/1335843Reviewed-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@{#608118}
-
Xiaohui Chen authored
Bug: b:79879622 Test: run autotest in chromeos chroot Test: test_that test_samus assistant_Startup Change-Id: Ia354f4a75fac904c813f8fb379ab88a95500f391 Reviewed-on: https://chromium-review.googlesource.com/c/1330698Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#608117}
-
Owen Min authored
The error option determines whether we show the error dialog when the token enrollment is failed. Bug: 904983 Change-Id: If43e4a3fdc71501ceb1feae16da0f87b88e84828 Reviewed-on: https://chromium-review.googlesource.com/c/1334408 Commit-Queue: Owen Min <zmin@chromium.org> Reviewed-by:
Georges Khalil <georgesak@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#608116}
-
Mathias Carlen authored
This patch implements the terms and services according to the current UI spec. It introduces a new, light blue to use for the box around the checkbox. Further, we want to highlight the domain, which is accomplished via Html.fromHtml and wrapping the domain in bold tags. Screenshot: https://screenshot.googleplex.com/H5PLFhvuUgK.png Bug: 806868 Change-Id: I362ab9f76ebdefbf485f0e3389188a2d8e18710f Reviewed-on: https://chromium-review.googlesource.com/c/1333817 Commit-Queue: Mathias Carlen <mcarlen@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#608115}
-
mrefaat authored
-view used by the BVC - so instead move the functionality to viewForTab Bug: 899832 Change-Id: I9958174df2468a7be4d1ab13c4f29cff3f81b2fb Reviewed-on: https://chromium-review.googlesource.com/c/1313282 Commit-Queue: Mohammad Refaat <mrefaat@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Reviewed-by:
edchin <edchin@chromium.org> Cr-Commit-Position: refs/heads/master@{#608114}
-
Christian Biesinger authored
LayoutNG never calls IncrementLayoutPassCount, so that value is not correct. We need to call it from NGBlockNode, not LayoutNGBlockFlow, because we can enter layout for a node from a parent NG node and not go through LayoutNGBlockFlow. (Legacy calls this in LayoutBlockFlow::UpdateBlockLayout) Fixes LayoutCountTest.SimpleBlockLayoutIsOnePass R=ikilpatrick@chromium.org Change-Id: I10e4f6fdad7102ebb582f6fcb260b917af9c19cc Reviewed-on: https://chromium-review.googlesource.com/c/1331416Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Christian Biesinger <cbiesinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#608113}
-
bsheedy authored
Adds the ability to press the app button via the Chrome VR native controller input code and switches all uses of app button presses over to it. This is should fix all the flakiness we've been seeing with the app button-related tests, as we're no longer relying on the flaky VrCore-side controller emulation. As a side-effect, also adds gesture detection capabilities when using the controller input code since app button short/long presses require it. This currently only supports button click detection, but could be easily extended later on to support scrolling, etc. Bug: 902938 Change-Id: I36dcb3b0b9e34adb92ade8a1a08d0d53536148ce Reviewed-on: https://chromium-review.googlesource.com/c/1324829Reviewed-by:
Christopher Grant <cjgrant@chromium.org> Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Cr-Commit-Position: refs/heads/master@{#608112}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/93345bb86e3d..ee14affed4c5 Created with: gclient setdep -r src-internal@ee14affed4c5 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. TBR=mmoss@chromium.org Change-Id: I852425bd2a0f9e8f62d669716ce7e219e7526e0c Reviewed-on: https://chromium-review.googlesource.com/c/1335783Reviewed-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@{#608111}
-
sczs authored
Since now InfobarContainer is a VC we no longer need to get this info from the parent VC. Bug: 892376 Change-Id: I04a7af0676437e20ebe0c31db16f0bf88c7b4ec6 Reviewed-on: https://chromium-review.googlesource.com/c/1331171Reviewed-by:
Mark Cogan <marq@chromium.org> Commit-Queue: Sergio Collazos <sczs@chromium.org> Cr-Commit-Position: refs/heads/master@{#608110}
-
Misha Efimov authored
Bug: 905262 Change-Id: I84199aa390a7b67e996d9022e94a826363084796 Reviewed-on: https://chromium-review.googlesource.com/c/1335954Reviewed-by:
Eric Orth <ericorth@chromium.org> Commit-Queue: Misha Efimov <mef@chromium.org> Cr-Commit-Position: refs/heads/master@{#608109}
-
Bret Sepulveda authored
A recent change caused the caption buttons to stop responding to touch. When I investigated, the change caused Windows to send WM_NCPOINTERDOWN and WM_NCPOINTERUP in that area (which we don't handle), where previously it was sending WM_POINTERDOWN and WM_POINTERUP. Since the change in question is fixing a different critical issue, this patch implements handling for WM_NCPOINTERDOWN, WM_NCPOINTERUP, and WM_NCPOINTERUPDATE, by delegating to the existing touch event handler. This patch also modifies the workaround frin crrev.com/c/1260507, since the type of messages being translated into ui::ET_TOUCH_RELEASED events is now different. Bug: 897662 Change-Id: I6fd052211b91a9a78834573deac830883972092b Reviewed-on: https://chromium-review.googlesource.com/c/1330838Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#608108}
-
Tom Tan authored
Bug: 893460 Change-Id: I69914310f35a1b21159da701447651aba4f1b888 Reviewed-on: https://chromium-review.googlesource.com/c/1334934 Commit-Queue: Tom Tan <Tom.Tan@microsoft.com> Reviewed-by:
Chris Blume <cblume@chromium.org> Cr-Commit-Position: refs/heads/master@{#608107}
-
Shawn Gallea authored
This CL only moves code around. Bug: 896710 Test: Built on ChromeOS Change-Id: Id9567918d751a9768d00489b5532a1abea3490e6 Reviewed-on: https://chromium-review.googlesource.com/c/1318083 Commit-Queue: Shawn Gallea <sagallea@google.com> Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/master@{#608106}
-
Tarun Bansal authored
This reverts commit 290d578e. Reason for revert: Crashes renderer Original change's description: > Include anchor element metrics that differ from one from document URL > > Currently, the render process sends the statistics of > only the anchor elements that are in the viewport to > the browser. This CL changes it to also include the > anchor elements whose target URL is one digit different > from the document URL. > > Note that there is still a limit of 40 on the count of anchor > elements that are sent from the render to the browser process. > > Change-Id: I4083e3605095a44700cc2178615713ede6e0dde2 > Bug: 850624 > TBR: ryansturm@chromium.org > Reviewed-on: https://chromium-review.googlesource.com/c/1329848 > Commit-Queue: Tarun Bansal <tbansal@chromium.org> > Reviewed-by: Tarun Bansal <tbansal@chromium.org> > Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> > Cr-Commit-Position: refs/heads/master@{#607328} TBR=kinuko@chromium.org,tbansal@chromium.org,ryansturm@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 850624,905224 Change-Id: I8fe41adb0434d410eb6fd2244e525c05037585f2 Reviewed-on: https://chromium-review.googlesource.com/c/1335664Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#608105}
-
Bo Liu authored
Put webview_cts_tests behind public_android_sdk since system_webview_apk dependency is behind public_android_sdk. Remove override on Picture.writeToStream which has been removed. Bug: 904912 Change-Id: Idcda7dbcb31d5bb02926e2b6743f369f988426d6 Reviewed-on: https://chromium-review.googlesource.com/c/1335955Reviewed-by:
Shimi Zhang <ctzsm@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#608104}
-
Justin Cohen authored
Bug: 783192 Change-Id: I54f44ee294418a5de54ba59456e0e672893697f4 Reviewed-on: https://chromium-review.googlesource.com/c/1334854 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Peter Lee <pkl@chromium.org> Cr-Commit-Position: refs/heads/master@{#608103}
-
Justin Cohen authored
Corrected cases found with: git grep -h "#import <.*>" ios | sort | uniq Bug: 904101 Change-Id: I17903375ef18d77bfd6f76052d6ea483a933ce56 Reviewed-on: https://chromium-review.googlesource.com/c/1335876 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#608102}
-
Camillo Bruni authored
This CL was created automatically with tools/perf/update_wpr script Bug: 878390 R=perezju@chromium.org Change-Id: I65300d654439ed65591691f5881cd8b1002c913c Reviewed-on: https://chromium-review.googlesource.com/c/1329665 Commit-Queue: Camillo Bruni <cbruni@chromium.org> Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#608101}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/ebedb7eb..5986b744 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: I3f6ecedb85aa3929fd670e994034f7852a7658c3 Reviewed-on: https://chromium-review.googlesource.com/c/1336050Reviewed-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@{#608100}
-
Sunny Sachanandani authored
This reverts commit b44653f9. Reason for revert: Broke the tree due to a typo :( Original change's description: > viz: DCHECK that clients don't send empty frames > > The service rejects a CompostiorFrame if it has an empty render pass > list, or an empty output rect. Add a DCHECK to ensure that clients > don't send these. > > Change-Id: I2a1a25fab8b2e01f5355eaf0378c98d730490863 > Reviewed-on: https://chromium-review.googlesource.com/c/1335268 > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Fady Samuel <fsamuel@chromium.org> > Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> > Cr-Commit-Position: refs/heads/master@{#608087} TBR=dcheng@chromium.org,fsamuel@chromium.org,sunnyps@chromium.org Change-Id: I95c5f1a54a39f5ae482aa311caaf0c5fdc8df094 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/1336207Reviewed-by:
Sunny Sachanandani <sunnyps@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/master@{#608099}
-
Ryan Meier authored
Change-Id: Ic64d8059a0cad7b831044151d822a912d71718de Reviewed-on: https://chromium-review.googlesource.com/c/1334551 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#608098}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/a89ef2b38df0..e3b7b56f6bc3 git log a89ef2b38df0..e3b7b56f6bc3 --date=short --no-merges --format='%ad %ae %s' 2018-11-14 thestig@chromium.org Break up ASSERT statements with ands. Created with: gclient setdep -r src/third_party/pdfium@e3b7b56f6bc3 The AutoRoll server is located here: https://autoroll.skia.org/r/pdfium-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=dsinclair@chromium.org Change-Id: I5612bcb9520da5db3f12f908b398c4c950d2bc6d Reviewed-on: https://chromium-review.googlesource.com/c/1335839Reviewed-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@{#608097}
-
Justin Cohen authored
--enable-features overwrites eg_tests.json's own set of overrides, which breaks ios_chrome_manual_fill_egtests. Instead, directly import and expand eg_tests.json and set --enable-features directly. Change-Id: Ia3e03bad59c6d3e9745037666a0b16cfe3da90e7 Reviewed-on: https://chromium-review.googlesource.com/c/1335873Reviewed-by:
Sergey Berezin <sergeyberezin@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#608096}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/d7157b2ccf53..bb9844ef69e7 git log d7157b2ccf53..bb9844ef69e7 --date=short --no-merges --format='%ad %ae %s' 2018-11-14 benjaminwagner@google.com Add client code search to docs. 2018-11-14 reed@google.com impl SkFont::getPath 2018-11-14 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 02ce5830e7db..d5f1489286b8 (7 commits) 2018-11-14 halcanary@google.com SkPDF: store indirect references in object Created with: gclient setdep -r src/third_party/skia@bb9844ef69e7 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=rmistry@chromium.org Change-Id: Ic3dd7bbc8234810035ec1ef12c6c3c66e0e8503e Reviewed-on: https://chromium-review.googlesource.com/c/1335778Reviewed-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@{#608095}
-