- 20 May, 2018 2 commits
-
-
https://chromium.googlesource.com/angle/angle.git/+log/9b1a90845291..42cf958ce8fa $ git log 9b1a90845..42cf958ce --date=short --no-merges --format='%ad %ae %s' 2018-05-17 jmadill Make UNIMPLEMENTED a warning. 2018-05-17 jmadill dEQP: Use overload of CreateWindow. 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=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: I8615be45d9fed12790e35d0154df6f6d2fb326d0 Reviewed-on: https://chromium-review.googlesource.com/1067130Reviewed-by:
angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: angle-chromium-autoroll <angle-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#560188}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/da816f070842..04d6ced50cd8 $ git log da816f070..04d6ced50 --date=short --no-merges --format='%ad %ae %s' 2018-05-19 angle-skia-autoroll Roll third_party/externals/angle2/ 78b7f3a8e..42cf958ce (3 commits) 2018-05-19 angle-skia-autoroll Roll third_party/externals/angle2/ a9ab0f37c..78b7f3a8e (1 commit) 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;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=herb@chromium.org Change-Id: I017293cbc3122ee0c068c9869e5e9423b4cdab13 Reviewed-on: https://chromium-review.googlesource.com/1067086Reviewed-by:
skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#560187}
-
- 19 May, 2018 38 commits
-
-
catapult-chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/669dcb14ae89..1d08c644fb9a $ git log 669dcb14a..1d08c644f --date=short --no-merges --format='%ad %ae %s' 2018-05-18 dtu [pinpoint] Specify the Swarming pool through the dimensions. Created with: roll-dep src/third_party/catapult The AutoRoll server is located here: https://catapult-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=sullivan@chromium.org Change-Id: I57792ceac981b669f456341a9b1f5227ac8b90dc Reviewed-on: https://chromium-review.googlesource.com/1067089 Commit-Queue: catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Reviewed-by:
catapult-chromium-autoroll <catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#560186}
-
Ken Rockot authored
Reland fixes a simple merge conflict which caused a non-existent header to be included. Original CL is https://chromium-review.googlesource.com/c/chromium/src/+/1066807 This is a public C API replacement for the EDK invitation API, i.e. Incoming/OutgoingBrokerClientInvitation et al. Here the new C calls are introduced and covered by unit tests. See the associated bug and the bugs it's blocking for more context and follow-up work. TBR=jcivelli@chromium.org Bug: 844231 Change-Id: If23b70ea381031a4caaed0ba5e6cf45c6b218971 Reviewed-on: https://chromium-review.googlesource.com/1067087Reviewed-by:
Ken Rockot <rockot@chromium.org> Commit-Queue: Ken Rockot <rockot@chromium.org> Cr-Commit-Position: refs/heads/master@{#560185}
-
Scott Violet authored
This moves data structures that are needed at embed points to ClientRoot. BUG=837684 TEST=none Change-Id: I9c404a3e5d076df39d96777b21e858818f93a7c0 Reviewed-on: https://chromium-review.googlesource.com/1066916 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Michael Wasserman <msw@chromium.org> Cr-Commit-Position: refs/heads/master@{#560184}
-
James Darpinian authored
This reverts commit db2744fe. Caused failures on Win7 FYI trybots: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20FYI%20Release%20%28AMD%29/1236 * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_CSS3DBlueBox * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_DirectComposition_Video_VP9 * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_GpuRasterization_ConcavePaths * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_OffscreenCanvasAccelerated2D * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_OffscreenCanvasTransferAfterStyleResize * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_OffscreenCanvasTransferToImageBitmap * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_SolidColorBackground * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_Video_VP9 * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_WebGLGreenTriangle_AA_Alpha * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_WebGLGreenTriangle_NoAA_Alpha * gpu_tests.pixel_integration_test.PixelIntegrationTest.Pixel_WebGL_PremultipliedAlpha_False * gpu_tests.screenshot_sync_integration_test.ScreenshotSyncIntegrationTest.ScreenshotSync_GPURasterWithCanvas * gpu_tests.screenshot_sync_integration_test.ScreenshotSyncIntegrationTest.ScreenshotSync_SWRasterWithCanvas * gpu_tests.screenshot_sync_integration_test.ScreenshotSyncIntegrationTest.ScreenshotSync_SWRasterWithDivs Bug: 844849 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 Change-Id: I57da87a7242d332af1d3642e4161c61fb20b7836 Reviewed-on: https://chromium-review.googlesource.com/1067083 Commit-Queue: James Darpinian <jdarpinian@chromium.org> Commit-Queue: Kenneth Russell <kbr@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Cr-Commit-Position: refs/heads/master@{#560183}
-
Marcin Wiacek authored
Desktop Chrome / Firefox are decoding % sequences in URLs in the status bar, additionally desktop Chrome is omitting HTTP scheme there. Patch is including this functionality in the Android Chrome in the context menu URL and is replacing or extending: 1. crrev.com/2774143002/ 2. https://chromium-review.googlesource.com/c/chromium/src/+/877759 3. https://chromium-review.googlesource.com/c/chromium/src/+/1015229 BUG=705233 Change-Id: I70509448108e267b66413a9c8869518706375b68 Reviewed-on: https://chromium-review.googlesource.com/1037123 Commit-Queue: Marcin Wiącek <marcin@mwiacek.com> Reviewed-by:
Maria Khomenko <mariakhomenko@chromium.org> Reviewed-by:
Christopher Thompson <cthomp@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#560182}
-
Saman Sami authored
If fallback SurfaceId was used during aggregation and a newer Surface becomes available later on, make sure we mark the display as damaged to force a draw and swap. Bug: 843290 Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel Change-Id: Ie0d46b547ab0c983c21c0fe003af3fbf90759aba Reviewed-on: https://chromium-review.googlesource.com/1062585Reviewed-by:
Fady Samuel <fsamuel@chromium.org> Commit-Queue: Saman Sami <samans@chromium.org> Cr-Commit-Position: refs/heads/master@{#560181}
-
Emilio Cobos Álvarez authored
...instead of replacing if the property is already set. This matches the spec[1] which was changed as a resolution from[2]. Intent thread: https://groups.google.com/a/chromium.org/d/msg/blink-dev/lzBoa1EAQpI/strfpNczAwAJ [1]: https://drafts.csswg.org/cssom/#set-a-css-declaration [2]: https://github.com/w3c/csswg-drafts/issues/1898 Bug: 782407 Change-Id: I4b72c0207a4cf734fc2e415bd62c7863103ec309 Reviewed-on: https://chromium-review.googlesource.com/1054867 Commit-Queue: Emilio Cobos Álvarez <emilio@chromium.org> Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/master@{#560180}
-
https://chromium.googlesource.com/angle/angle.git/+log/78b7f3a8e813..9b1a90845291 $ git log 78b7f3a8e..9b1a90845 --date=short --no-merges --format='%ad %ae %s' 2018-05-17 jmadill dEQP: Format display factory and clean up style. 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=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: I049f29b17cf4ed17705b04e5ebe7722c85aae342 Reviewed-on: https://chromium-review.googlesource.com/1067073Reviewed-by:
-
Clemens Hammacher authored
The metric was added to V8 in https://crrev.com/c/1061497 to measure the code size increase of Liftoff and get data to find a good upper limit on the wasm code space. R=mpearson@chromium.org CC=titzer@chromium.org Bug: chromium:787421 Change-Id: I6aee5a5633051be376f81b4e9fffbf036bc44ec1 Reviewed-on: https://chromium-review.googlesource.com/1064238Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#560178}
-
Scott Violet authored
The server assigns LocalSurfaceIds (each window may have a LocalSurfaceId). LocalSurfaceIds change any time the size changes. This means the server needs to notify the client any time the bounds change. Normally when a client requests a change that succeeds the server acks it, and that is it. What we've done with bounds of roots (where LocalSurfaceIds matter), is when the client requests the change the server responds with OnWindowBoundsChanged(), which includes the LocalSurfaceId, and then the server returns false. By returning false the client applies the LocalSurfaceId that was just sent from the server. services/ui/ws had this logic, this makes ws2 have the same logic. This is at least part of the problem as to why painting isn't working. BUG=837684 TEST=covered by test Change-Id: Ia66d3e5b4120adce2a5d033563a0c387c3bd7b7e Reviewed-on: https://chromium-review.googlesource.com/1066828 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
-
Alex Moshchuk authored
This CL fixes a reordering problem between sizing changes and cross-process postMessages. Previously, it was possible for a frame to resize its child frame (forcing layout to guarantee the sizing IPC is sent), then send it a postMessage, and have the message delivered before the sizing change. This is because the browser process might throttle resizes, in particular if there had been another pending resize which hadn't been acked by the (child) renderer. To fix this, this CL flushes any pending sizing info to the child renderer before forwarding the postMessage. Bug: 822958, 828529 Change-Id: I49252ed6f91b5c25be96b210fd3e3c6248f14da6 Reviewed-on: https://chromium-review.googlesource.com/1063310 Commit-Queue: Fady Samuel <fsamuel@chromium.org> Commit-Queue: Charlie Reis <creis@chromium.org> Reviewed-by:
Charlie Reis <creis@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Cr-Commit-Position: refs/heads/master@{#560176}
-
Ken Rockot authored
This reverts commit a523cf48. Reason for revert: Bad rebase, conflicted with another change Original change's description: > Mojo: Invitation API > > This is a public C API replacement for the EDK invitation API, i.e. > Incoming/OutgoingBrokerClientInvitation et al. Here the new C calls > are introduced and covered by unit tests. > > See the associated bug and the bugs it's blocking for more context > and follow-up work. > > Bug: 844231 > Change-Id: Iffa2e5b08eefbe3476430eb420efe2f52f4ad195 > Reviewed-on: https://chromium-review.googlesource.com/1066807 > Commit-Queue: Ken Rockot <rockot@chromium.org> > Reviewed-by: Jay Civelli <jcivelli@chromium.org> > Cr-Commit-Position: refs/heads/master@{#560164} TBR=jcivelli@chromium.org,rockot@chromium.org Change-Id: I798545dc19a146fe40a9e1ad7ff95a41d0d5dd25 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 844231 Reviewed-on: https://chromium-review.googlesource.com/1067053Reviewed-by:
-
Steve Kobes authored
Bug: 823365 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I07e34f6e26394c073124886eef08d93a667918f5 Reviewed-on: https://chromium-review.googlesource.com/1066615 Commit-Queue: Steve Kobes <skobes@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#560174}
-
Jan Krcal authored
This CL removes the bridge pointer from the ModelReadyToSync function of the ModelTypeChangeProcessor interface.The CL finishes the larger effort of hiding the bridge interface from the internals of sync. When already touching all the files, it also removes the gMock hacks for move-only types from MockModelTypeChangeProcessor. The outcome is still not optimal because some standard actions as Invoke or SaveArg do not support move-only types; we have to use lambdas/WithArg, instead. Bug: 819993 Change-Id: I0f4db6c2b7b36d317b69a25a651180c1f63d9269 Reviewed-on: https://chromium-review.googlesource.com/1064612Reviewed-by:
Lei Zhang <thestig@chromium.org> Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Reviewed-by:
Eric Noyau <noyau@chromium.org> Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Commit-Queue: Jan Krcal <jkrcal@chromium.org> Cr-Commit-Position: refs/heads/master@{#560173}
-
Steve Kobes authored
Bug: 823365 Change-Id: I5951f7a868c11901d36cad63a24cfd4a39209ad3 Reviewed-on: https://chromium-review.googlesource.com/1066178Reviewed-by:
Stefan Zager <szager@chromium.org> Commit-Queue: Steve Kobes <skobes@chromium.org> Cr-Commit-Position: refs/heads/master@{#560172}
-
Devlin Cronin authored
All callers except the fileManagerPrivate API have been updated to not rely on GetAssociatedWebContentsDeprecated(). The fileManagerPrivate issue is being tracked separately. Remove the function GetAssociatedWebContentsDeprecated() and move it to be directly in the fileManagerPrivate API to avoid having usage spread. Bug: 461394, 844654 Change-Id: I69adc7f3534d4908497bf73d3fcab0f7443450e7 Reviewed-on: https://chromium-review.googlesource.com/1066733Reviewed-by:
Istiaque Ahmed <lazyboy@chromium.org> Commit-Queue: Devlin <rdevlin.cronin@chromium.org> Cr-Commit-Position: refs/heads/master@{#560171}
-
Pavol Marko authored
Moves the factory ping embargo check from rlz_lib::RlzValueStoreChromeOS to the function chromeos::system::GetFactoryPingEmbargoState. This avoids a dependency from chromeos to rlz_lib. Bug: 839353 Test: chromeos_unittests && rlz_unittests Change-Id: Ia20c9a268d1030a77b1e138632005866c24d0788 Reviewed-on: https://chromium-review.googlesource.com/1059409 Commit-Queue: Pavol Marko <pmarko@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Achuith Bhandarkar <achuith@chromium.org> Reviewed-by:
Roger Tawa <rogerta@chromium.org> Cr-Commit-Position: refs/heads/master@{#560170}
-
Shakti Sahu authored
Fixed initialization of pending_state_ in SavePageRequest. Bug: 844652 Change-Id: I8c4b2134dc74155330bc918be5e02e614610b2a9 Reviewed-on: https://chromium-review.googlesource.com/1066694Reviewed-by:
Cathy Li <chili@chromium.org> Commit-Queue: Shakti Sahu <shaktisahu@chromium.org> Cr-Commit-Position: refs/heads/master@{#560169}
-
Philip Rogers authored
EventSender only needs to update the lifecycle to PrePaint and does not need to paint. Two tests have been updated that relied on EventSender's paints for invalidation tracking. TBR=pfeldman@chromium.org Bug: 841423 Change-Id: I8a1ef02870241d9b4adecf3a3f905272f845ef0f Reviewed-on: https://chromium-review.googlesource.com/1062907 Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#560168}
-
Mitsuru Oshima authored
Initialize the frame color if the color is already set on the window. Moved the default frame color to ash_constnats.h and changed the default value of the frame color properties to use it. Bug: b/79470588 Test: covered by unittest Change-Id: I7964596b92796eddcd33ca4c8f7be6a39c12b355 Reviewed-on: https://chromium-review.googlesource.com/1063591 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Tao Wu <wutao@chromium.org> Cr-Commit-Position: refs/heads/master@{#560167}
-
Mitsuru Oshima authored
BUG: 33693796 TEST: covered by unittests Change-Id: I033769e2d2a2671152bcb0227f7ce5f2876c9f05 Reviewed-on: https://chromium-review.googlesource.com/1063522 Commit-Queue: Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Jun Mukai <mukai@chromium.org> Cr-Commit-Position: refs/heads/master@{#560166}
-
Dominic Mazzoni authored
Bug: 651614 TBR=alexst@chromium.org Change-Id: I77ef290a193bd3dbb3dafdf0de5670a7deec6c86 Reviewed-on: https://chromium-review.googlesource.com/1063007 Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/master@{#560165}
-
Ken Rockot authored
This is a public C API replacement for the EDK invitation API, i.e. Incoming/OutgoingBrokerClientInvitation et al. Here the new C calls are introduced and covered by unit tests. See the associated bug and the bugs it's blocking for more context and follow-up work. Bug: 844231 Change-Id: Iffa2e5b08eefbe3476430eb420efe2f52f4ad195 Reviewed-on: https://chromium-review.googlesource.com/1066807 Commit-Queue: Ken Rockot <rockot@chromium.org> Reviewed-by:
Jay Civelli <jcivelli@chromium.org> Cr-Commit-Position: refs/heads/master@{#560164}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/ba5b5f517168..da816f070842 $ git log ba5b5f517..da816f070 --date=short --no-merges --format='%ad %ae %s' 2018-05-19 angle-skia-autoroll Roll third_party/externals/angle2/ 8688bf46f..a9ab0f37c (4 commits) 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;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=herb@chromium.org Change-Id: I2d1438e086aa2d05bfe0509008c0968414cb1d02 Reviewed-on: https://chromium-review.googlesource.com/1066976Reviewed-by:
-
Philip Rogers authored
This patch removes the paint properties for LocalFrameView as they are stored on the LayoutView now. Bug: 823365 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I7d138e6435d7af9fc2344853a2fd41c0294c09e4 Reviewed-on: https://chromium-review.googlesource.com/1066709 Commit-Queue: Philip Rogers <pdr@chromium.org> Reviewed-by:
Steve Kobes <skobes@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#560162}
-
chromeos-commit-bot@chromium.org authored
BUG=762641 TBR=oshima@chromium.org Change-Id: I17f3d7036eb9226608928d1e9bcbabf5ca7ce66a Reviewed-on: https://chromium-review.googlesource.com/1067031Reviewed-by:
ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Commit-Queue: ChromeOS Commit Bot <chromeos-commit-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#560161}
-
afdo-chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 The AutoRoll server is located here: https://afdo-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=gbiv@chromium.org Change-Id: Id024b74f8bcb81abd3fe7f39970bab5837ec4cfc Reviewed-on: https://chromium-review.googlesource.com/1066285Reviewed-by:
afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Commit-Queue: afdo-chromium-autoroll <afdo-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#560160}
-
Zhenyao Mo authored
The motivation is we fail to process ARM Mali drivers. I scanned through gpuinfo.org and tested against almost all GL_VERSION patterns. BUG=839609,839618 TEST=gl_unittests,gpu_unittests R=piman@chromium.org,kbr@chromium.org 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 Change-Id: I65d8cc09b5547d40812a6f7ae8aa204416d28705 Reviewed-on: https://chromium-review.googlesource.com/1065191 Commit-Queue: Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Cr-Commit-Position: refs/heads/master@{#560159}
-
Pavel Feldman authored
This reverts commit 589b7b02. Reason for revert: https://ci.chromium.org/buildbot/chromium.memory/Linux%20MSan%20Builder/11941 Original change's description: > Reduce number of different test suite configurations. > > - Remove all the "non_clang" and "_fyi" configs -- the clang > waterfall and the FYI waterfall should default to running the > same tests as the real waterfalls unless explicitly opted out. > Deviations here were very likely not intentional. > - This requires running chrome_cleaner_unittests on the regular > win bots, which seems like a good change anyhow. > - Just include angle_unittests in chromium_gtests instead of > spuriously adding it here and there (but on all platforms). > We've had issues with this test unintentionally running on too > few bots. > - Rename aura_gtests to non_android_and_mac_gtests > - Include gl_tests in the normal chromium_linux_gtests and > chromium_android_gtests suites instead of having separate > _and_gl configs > - Add gcm_unit_tests to chromium_gtests since it effectively > ran everywhere already, this allows deleting > non_android_and_cast_chromium_gtests. Use similar tactics to > remove non_android_and_cast_and_chromeos_chromium_gtests. > - Address most "TODO: merge back to X" TODOs > > The main effect is that this adds many tests to the chromium.clang > waterfall, making it more consistent with the main waterfall. > It also adds a couple of binaries to other waterfalls. > > Bug: 843511,843726,843729,843731,843732,843734,831999,844582 > TBR=disabled test owners > > 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 > Change-Id: I67c3980009fc07897f1f6bab424ef6c5f11d4830 > Reviewed-on: https://chromium-review.googlesource.com/1061795 > Commit-Queue: Nico Weber <thakis@chromium.org> > Reviewed-by: Nico Weber <thakis@chromium.org> > Reviewed-by: Dirk Pranke <dpranke@chromium.org> > Reviewed-by: Kenneth Russell <kbr@chromium.org> > Cr-Commit-Position: refs/heads/master@{#560147} TBR=thakis@chromium.org,dpranke@chromium.org,kbr@chromium.org Change-Id: I645e08d0ae374f181836e5d3749f39e17e54d9f5 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 843511, 843726, 843729, 843731, 843732, 843734, 831999, 844582 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 Reviewed-on: https://chromium-review.googlesource.com/1067052Reviewed-by:
Pavel Feldman <pfeldman@chromium.org> Commit-Queue: Pavel Feldman <pfeldman@chromium.org> Cr-Commit-Position: refs/heads/master@{#560158}
-
Ken Rockot authored
This reverts commit a9ba958e. Reason for revert: Seems there's still a leak here somewhere. Original change's description: > Reland: Mojo EDK: Improve internal process handle ownership > > Reland of r555117 with process handle leak fixed. Original commit > message follows. > > Mojo passes around base::ProcessHandle values for various reasons. On > most systems this is fine, but at least on Windows, a ProcessHandle > refers to an owned reference to a system process object, and if not > careful it's possible for a base::ProcessHandle value to inadvertently > change meaning over time. > > This CL introduces the concept of a move-only ScopedProcessHandle > within Mojo, which on most platforms is just a base::PlatformHandle. > On Windows, this represents an owned base::ProcessHandle which closes > on destruction and clones correctly using DuplicateHandle rather than > merely copying the raw handle value. > > ScopedProcessHandle is used in a few places where process handle > ownership semantics were previously weaker than necessary, or were > correct but implemented ad hoc. > > This also updates ScopedPlatformHandle (and supporting code like > Channel::RewriteHandles) such that the |owning_process| field (if not > the current process) is always an owned process handle. This ensures > that when such handles are closed in unsent messages, they can be > safely closed in the target process (from within the source process) > without any risk of raciness against target process termination. > > TBR=jcivelli@chromium.org > > Bug: 837612 > Change-Id: I28aaa04ca09f483e7e6f073db2edb762893a8b17 > Reviewed-on: https://chromium-review.googlesource.com/1065129 > Commit-Queue: Ken Rockot <rockot@chromium.org> > Reviewed-by: Ken Rockot <rockot@chromium.org> > Cr-Commit-Position: refs/heads/master@{#559777} TBR=jcivelli@chromium.org,rockot@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 837612 Change-Id: Id0e326686cecd305f315b4a67bbda5e9f7c52b34 Reviewed-on: https://chromium-review.googlesource.com/1067051Reviewed-by:
-
Shuotao Gao authored
This reverts commit 9dd28324. Reason for revert: Caused to consistent test failiures HeadlessProtocolBrowserTest.VirtualTimeErrorLoop HeadlessProtocolBrowserTest.VirtualTimeAdvance https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Linux%20Tests%20%28dbg%29%281%29/72102 https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.13%20Tests%20%28dbg%29/2474 Original change's description: > Headless: introduce protocol test harness for nice and elegant headless testing > > Change-Id: Ie171eb4fdddda28136f287d22a8de451a7ce9482 > Reviewed-on: https://chromium-review.googlesource.com/1065495 > Commit-Queue: Pavel Feldman <pfeldman@chromium.org> > Reviewed-by: Alex Clarke <alexclarke@chromium.org> > Reviewed-by: Eric Seckler <eseckler@chromium.org> > Reviewed-by: Dmitry Gozman <dgozman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#560024} TBR=dgozman@chromium.org,caseq@chromium.org,pfeldman@chromium.org,alexclarke@chromium.org,eseckler@chromium.org,johannes@chromium.org Change-Id: I10fc46e5f1a56abd421e4427faff2d56920a3230 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/1066951 Commit-Queue: Pavel Feldman <pfeldman@chromium.org> Reviewed-by:
Shuotao Gao <stgao@chromium.org> Cr-Commit-Position: refs/heads/master@{#560156}
-
Pavel Feldman authored
This reverts commit 84c8813f. Reason for revert: headless debug tests fail Original change's description: > Headless: port even more virtual time tests to the protocol harness. > > Change-Id: Ie619816b44b7dbd6c5becfa7307c758c1b18246e > TBR: alexclarke > Reviewed-on: https://chromium-review.googlesource.com/1066806 > Reviewed-by: Pavel Feldman <pfeldman@chromium.org> > Commit-Queue: Pavel Feldman <pfeldman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#560112} TBR=dgozman@chromium.org,pfeldman@chromium.org Change-Id: I4ff2a852bd2b859082fe84aa80047c58f0e9ae46 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/1067050Reviewed-by:
-
Pavel Feldman authored
This reverts commit fec1b5f7. Reason for revert: headless bots failing Original change's description: > Headless: don't use the copy of the protocol test harness, reference the original. > > Change-Id: If7796d2a698243b89a9ee7ff9603cf3e04338be3 > TBR: eseckler > Reviewed-on: https://chromium-review.googlesource.com/1066683 > Reviewed-by: Dmitry Gozman <dgozman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#560103} TBR=dgozman@chromium.org,pfeldman@chromium.org,johannes@chromium.org Change-Id: I962809483fd18c2635cb4f963b215b69b47c5efe No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/1066746Reviewed-by:
-
Andrey Kosyakov authored
Change-Id: Ie3a61cbf483075183459c95136bd6d37265ca77a Reviewed-on: https://chromium-review.googlesource.com/1066983Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#560153}
-
Findit authored
This reverts commit 6a7ccf89. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 560074 as the culprit for flakes in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/flake/flake-culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyQwsSDEZsYWtlQ3VscHJpdCIxY2hyb21pdW0vNmE3Y2NmODk4MTdlYzQ4MzBkZWNiYTg5OTBjYjRhNTc2MjE3M2M1Ngw Sample Failed Build: https://ci.chromium.org/buildbot/chromium.mac/Mac10.10%20Tests/32310 Sample Failed Step: headless_browsertests on Mac-10.10 Sample Flaky Test: HeadlessProtocolBrowserTest.VirtualTimeNoBlock404 Original change's description: > Headless: port more tests to the new protocol harness. > > Change-Id: I4746041f5ff8285e21322c99c897fb9e2e2da19c > Reviewed-on: https://chromium-review.googlesource.com/1066700 > Reviewed-by: Dmitry Gozman <dgozman@chromium.org> > Cr-Commit-Position: refs/heads/master@{#560074} Change-Id: I9e6bbed1371415f0f5c79538868c6d36a99ff8ac No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 844827 Reviewed-on: https://chromium-review.googlesource.com/1066745 Cr-Commit-Position: refs/heads/master@{#560152}
-
Sadrul Habib Chowdhury authored
The client code no longer needs to care about the swap-ids for swap-buffer-ack or presentation callbacks. So remove the associated plumbing. TBR=boliu@chromium.org for trivial change in android_webview/ Bug: 811961, 776877 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;master.tryserver.blink:linux_trusty_blink_rel Change-Id: I7e6431d1a39229e5f139ab0e9c98ab0b734d223e Reviewed-on: https://chromium-review.googlesource.com/1065465 Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
-
chrome-release-bot authored
# This is an automated release commit. # Do not revert without consulting chrome-pmo@google.com. NOAUTOREVERT=true TBR=mmoss@chromium.org Change-Id: Ied1a5a16c57270b826a8cca2609f5c904df8469f Reviewed-on: https://chromium-review.googlesource.com/1067030Reviewed-by:
chrome-release-bot@chromium.org <chrome-release-bot@chromium.org> Cr-Commit-Position: refs/heads/master@{#560150}
-
Ella Ge authored
This cl add schedule fake mouse move after visual viewport change. And changes last_know_mouse_position to viewport coordinates to fire the fake mouse move to correct location after pinch zoom. Bug: 669742 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I85405ce1b24969b3b63038c59180df3610832f7a Reviewed-on: https://chromium-review.googlesource.com/1026081Reviewed-by:
enne <enne@chromium.org> Reviewed-by:
David Bokan <bokan@chromium.org> Commit-Queue: Ella Ge <eirage@chromium.org> Cr-Commit-Position: refs/heads/master@{#560149}
-
