- 15 May, 2018 40 commits
-
-
https://webrtc.googlesource.com/src.git/+log/5702736f7e46..59216ec4a415 $ git log 5702736f7..59216ec4a --date=short --no-merges --format='%ad %ae %s' Created with: roll-dep src/third_party/webrtc BUG=chromium:None,chromium:None 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 TBR=webrtc-chromium-sheriffs-robots@google.com Change-Id: I6549be88db6a4034fee7a2ae8ac98357efd7813b Reviewed-on: https://chromium-review.googlesource.com/1059575 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@{#558722}
-
Ricky Liang authored
We should discard the incoming capture GpuMemoryBuffer and return when VideoCaptureDeviceClient::OnIncomingCapturedGfxBuffer fails to reserve the I420 output buffer. Otherwise we'll end up crashing. BUG=b:79729317 R=emircan Change-Id: I616d97ca618ad9cc40abdf9d1a8f06ce568cfbb0 Reviewed-on: https://chromium-review.googlesource.com/1059495Reviewed-by:
Emircan Uysaler <emircan@chromium.org> Commit-Queue: Ricky Liang <jcliang@chromium.org> Cr-Commit-Position: refs/heads/master@{#558721}
-
Robert Sesek authored
When the browser detects that a renderer is hung (via not ack'ing input events), it displays a hung-page dialog. On Windows, if the user chooses to kill the page, the browser will generate a minidump for the hung process for post-mortem analysis. This CL implements the same on Mac. Bug: 842806 Change-Id: I2d50fc7395fc6c4fe080a5cc05bfcee8f4f36e79 Reviewed-on: https://chromium-review.googlesource.com/1058009 Commit-Queue: Robert Sesek <rsesek@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Reviewed-by:
Scott Graham <scottmg@chromium.org> Cr-Commit-Position: refs/heads/master@{#558720}
-
skia-chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/6bbd386a0e4b..81f60ecd9cc0 $ git log 6bbd386a0..81f60ecd9 --date=short --no-merges --format='%ad %ae %s' 2018-05-15 reed Allow slides/gms to extend the UI 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: Ie5bab037e74f8928abc8fc0ec0f04254d231b3d6 Reviewed-on: https://chromium-review.googlesource.com/1059577Reviewed-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@{#558719}
-
Rayan Kanso authored
Bug: N/A Change-Id: I8874134483806c01323042ad7593125e1e2c7b35 Reviewed-on: https://chromium-review.googlesource.com/1059782Reviewed-by:
Makoto Shimazu <shimazu@chromium.org> Commit-Queue: Rayan Kanso <rayankans@chromium.org> Cr-Commit-Position: refs/heads/master@{#558718}
-
Allen Bauer authored
GetOpacity() didn't handle the active tab case where the close button should be always visible. Bug: 822061 Bug: 842218 Change-Id: Id91e5ab402fb1e9e249f8cb60d1a26a3c9a3c46e Reviewed-on: https://chromium-review.googlesource.com/1055648 Commit-Queue: Allen Bauer <kylixrd@chromium.org> Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#558717}
-
Hans Wennborg authored
It's already excluded manually from almost all Android bots. For some reason this also enables it on some chromium.clang and chromium.memory bots. If it turns out to fail there, we can add exclusions. Bug: 842698, 840756, 843134 Change-Id: I6c119b5272163a41676f1a0f8b7a2081631c9564 Reviewed-on: https://chromium-review.googlesource.com/1059780Reviewed-by:
-
A Olsen authored
Right now we use only single-line textboxes. It is difficult for admins to make a large JSON dict fit into a single line textbox, so this change displays a multiline textbox instead in the following situations: - Only in Chrome OS policies - not for Windows. (We could also turn this on for windows once we have checked for side effects.) - Whenever an policy of type 'dict' or 'external' is expected. - Whenever a policy of type 'string' that is actually JSON is expected. As of this change, we will also still show a single-line textbox along with the multiline, so that admins can still see the old single-line value, since the two types of textboxes aren't completely compatible. Eventually, we can stop showing the single-line textboxes. See the attached bug for more information. Also: Show more example values in help-text - - for dicts and external, not just for list + string. Bug: 829328 Change-Id: Ic095d0e54dd324437dcfe89ef60c34a31f8ae16b Reviewed-on: https://chromium-review.googlesource.com/1007082 Commit-Queue: A Olsen <olsen@chromium.org> Reviewed-by:
Lutz Justen <ljusten@chromium.org> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#558715}
-
Erik Staab authored
R=tandrii@chromium.org Bug: 731967 Change-Id: Ie0d2a57cfb398032a9278324791dba6167b74aa0 Reviewed-on: https://chromium-review.googlesource.com/1058531Reviewed-by:
Andrii Shyshkalov <tandrii@chromium.org> Commit-Queue: Erik Staab <estaab@chromium.org> Cr-Commit-Position: refs/heads/master@{#558714}
-
Michael Lippautz authored
Instead of emitting write barriers for single writes in HashTable, conservatively emit a barrier for the backing store during rehashing. This moves us in the tradeoff space: - Removes 40KiB of binary bloat - Avoids emitting barriers when re-inserting single elements which improves throughput for the case where incremental marking is off - Emits a single conservative barrier at the end of RehashTo. This potentially means that we (re-)scan more objects when incremental marking is on Bug: chromium:839514, chromium:757440 Change-Id: Ib5495c9e2210836424d7b26f2138d852f8dafec7 Reviewed-on: https://chromium-review.googlesource.com/1055400 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#558713}
-
Ben Wagner authored
This updates SkFontConfigInterface::SetGlobal calls to use the smart pointer version. This removes the awkward trailing ->unref and will allow Skia to remove the old non-smart version of this method. Change-Id: Icf67a1976820f5f0f07243ab1539e90e18db2ef4 Reviewed-on: https://chromium-review.googlesource.com/1058019Reviewed-by:
Avi Drissman <avi@chromium.org> Commit-Queue: Ben Wagner <bungeman@chromium.org> Cr-Commit-Position: refs/heads/master@{#558712}
-
Miguel Casas authored
Simplify logic around |enable_canvas_2d_image_chromium| in runtime_features.cc. Bug: 839970 Change-Id: I7371c6ce22e7a2c73013b75c8545e5fc91b983c7 Reviewed-on: https://chromium-review.googlesource.com/1057388Reviewed-by:
Daniele Castagna <dcastagna@chromium.org> Reviewed-by:
-
Joel Einbinder authored
This makes VSCode a lot faster in the DevTools codebase by only autocompleting over the files depended on by this file. Change-Id: I94421969291a135a46673c02722e77f0d6709426 Reviewed-on: https://chromium-review.googlesource.com/1058680 Commit-Queue: Joel Einbinder <einbinder@chromium.org> Reviewed-by:
Erik Luo <luoe@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#558710}
-
Hans Wennborg authored
It's already excluded manually from almost all Android bots in test_suite_exceptions.pyl, and fails if we try to run it on [1]. It seems this test simply does not reliably work on Android, and so excluding it by default makes more sense. For some reason, this move also enables it on some chromium.clang bots. I'm not sure whether disabling it for those bots was intentional, but we'll find out. [1] https://ci.chromium.org/buildbot/chromium.clang/ToTAndroid/3343 Bug: 840756, 842698, 843124 Change-Id: I4c40bbfe66943ad77e6f970f4ca3fa1a218166d3 Reviewed-on: https://chromium-review.googlesource.com/1059514 Commit-Queue: Hans Wennborg <hans@chromium.org> Reviewed-by:
-
Florent Castelli authored
This is part of the onion soup efforts. Bug: 787254 Change-Id: If099833448584243d4b03586f100faf1939c4887 Reviewed-on: https://chromium-review.googlesource.com/1057309 Commit-Queue: Florent Castelli <orphis@chromium.org> Reviewed-by:
Henrik Boström <hbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#558708}
-
Alex Sakhartchouk authored
BUG=none TEST=flash device run through flings. Change-Id: Icb6363c8418df76d868cdf1cefa4268e0eebc980 Reviewed-on: https://chromium-review.googlesource.com/1059696Reviewed-by:
Kevin Schoedel <kpschoedel@chromium.org> Commit-Queue: Alex Sakhartchouk <alexst@chromium.org> Cr-Commit-Position: refs/heads/master@{#558707}
-
John Chen authored
Replace "no alert open" error with "no such alert", as specified in W3C spec. Bug: chromedriver:2420 Change-Id: Ide525e18bde7d6163e8a171e7574e9157846f16b Reviewed-on: https://chromium-review.googlesource.com/1054156Reviewed-by:
Jonathon Kereliuk <kereliuk@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#558706}
-
Chromium WPT Sync authored
Using wpt-import in Chromium ac8e3260. Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/17650 Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md Directory owners for changes in this CL: foolip@chromium.org, robertma@chromium.org, smcgruer@chromium.org: external/wpt/infrastructure hta@chromium.org: external/wpt/webrtc mkwst@chromium.org, andypaicu@chromium.org: external/wpt/content-security-policy TBR=markdittmer No-Export: true Change-Id: I129f9043c5a90700469da2da4a57342b66931a64 Reviewed-on: https://chromium-review.googlesource.com/1059713 Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Reviewed-by:
Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> Cr-Commit-Position: refs/heads/master@{#558705}
-
Dmitry Gozman authored
This class has generic purpose and is used in many places. At the same time, it has no relation to the rest of platform/text. This also reverses dependency between TextStream and geomtry primitives. Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_layout_ng;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: Id3fd58afc94e25a2fad10ae2c49dc6494d80684b Reviewed-on: https://chromium-review.googlesource.com/1058267Reviewed-by:
-
catapult-chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/075ca3000abf..35cefb8d8a2f $ git log 075ca3000..35cefb8d8 --date=short --no-merges --format='%ad %ae %s' 2018-05-15 csharrison Introduce a BrowserOption for seeding a default profile Created with: roll-dep src/third_party/catapult BUG=chromium:823982 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: Ibe75061d90cddd4ed6e48831254b094521feaa76 Reviewed-on: https://chromium-review.googlesource.com/1059695 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@{#558703}
-
John Chen authored
The default color profile on Mac causes some adjusts to displayed colors, so that screenshots have different colors from expected. This caused some screenshot tests to fail. Fix by forcing srgb color profile. Bug: chromedriver:1857 Change-Id: I65aa784836e527fe8d1fa5ee3f45e50f19cdc9d3 Reviewed-on: https://chromium-review.googlesource.com/1058985Reviewed-by:
-
rbpotter authored
- Regenerate only for destination change, not id and capabilities - Try to reduce unnecessary updates of settings availability, by splitting updates that are based on document info from those based on destination. - Do not regenerate if media size vendor ID or name changes, since this is irrelevant to the preview generation, or when changing to custom margins. - Also fix the destinations dialog size, so that it does not change height as destinations load or when a search query is entered. Bug: 773928 Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: I6d8f7052dca89a7894160d9e4eaf32e1184c5072 Reviewed-on: https://chromium-review.googlesource.com/1054140 Commit-Queue: Rebekah Potter <rbpotter@chromium.org> Reviewed-by:
Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#558701}
-
Max Moroz authored
Bug: 833912 Change-Id: Ie6bff55a2f3af2c670367315efd21d063e0c317d Reviewed-on: https://chromium-review.googlesource.com/1054425 Commit-Queue: Max Moroz <mmoroz@chromium.org> Reviewed-by:
Abhishek Arya <inferno@chromium.org> Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Reviewed-by:
Jonathan Metzman <metzman@chromium.org> Cr-Commit-Position: refs/heads/master@{#558700}
-
Eugene But authored
Bug: 842781 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: I001fbaf3d100e173252aacde7b3cc4f28e28fa31 Reviewed-on: https://chromium-review.googlesource.com/1058378Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Eugene But <eugenebut@chromium.org> Cr-Commit-Position: refs/heads/master@{#558699}
-
Emily Stark authored
Bug: 839969 Change-Id: I5c0de5f31d997be815a2c956e279f06dc1047d84 Reviewed-on: https://chromium-review.googlesource.com/1058113Reviewed-by:
Edward Jung <edwardjung@chromium.org> Commit-Queue: Emily Stark <estark@chromium.org> Cr-Commit-Position: refs/heads/master@{#558698}
-
Miguel Casas authored
This CL introduces InSequence and s/const/constexpr/ in the GMB-related Canvas2DLayerBridgeTest cases. This is a minor preparation for crrev.com/c/1056168 where having the expectations in a sequence makes things clearer. Bug: 839970 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I8b43341af1e7bbae50cf9a117e20867bf2628e73 Reviewed-on: https://chromium-review.googlesource.com/1058018Reviewed-by:
Justin Novosad <junov@chromium.org> Commit-Queue: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#558697}
-
Roger McFarlane authored
This CL removes a reference to an expired/obsolete experiment. Bug: 799180 Change-Id: Idaea49886fe8d47e74ec917527b0e7e5a8e65f01 Reviewed-on: https://chromium-review.googlesource.com/1058694 Commit-Queue: Sebastien Seguin-Gagnon <sebsg@chromium.org> Reviewed-by:
Gayane Petrosyan <gayane@chromium.org> Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#558696}
-
Noel Gordon authored
Now make TestCase have single-arg constructor only. Add InGuestMode(), InIncognito() helpers to deal with setting those modes. No change in behavior, no new tests. Bug: 843030 Change-Id: I315b114b7f3a1bd297a0db9916f7f1be1e968219 Reviewed-on: https://chromium-review.googlesource.com/1059493 Commit-Queue: Noel Gordon <noel@chromium.org> Reviewed-by:
Joel Hockey <joelhockey@chromium.org> Cr-Commit-Position: refs/heads/master@{#558695}
-
Jeremy Roman authored
There are no uses aside from the ones in WebFrameOwnerProperties. With that gone, remove web_scrollbar.h, which has become empty. Bug: 841751 Change-Id: I542ba4f26b70feed999f7a108a5a67636fb65e23 Reviewed-on: https://chromium-review.googlesource.com/1054331 Commit-Queue: Jeremy Roman <jbroman@chromium.org> Reviewed-by:
Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#558694}
-
Miguel Casas authored
This CL removes unnecessary BindTexture() calls from CanvasResourceGpuMemoryBuffer::TearDown(). Bug: 839970 Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Change-Id: I0281c30d5c8f18ce95a563767c15e174ced4b3ed Reviewed-on: https://chromium-review.googlesource.com/1058152Reviewed-by:
-
Charlie Harrison authored
These metrics are not being used anymore. Bug: 684240 Change-Id: Ie89ec3bb7185e159f460e6982bfda9345c07a877 Reviewed-on: https://chromium-review.googlesource.com/1058228Reviewed-by:
Yoav Weiss <yoav@yoav.ws> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Commit-Queue: Charlie Harrison <csharrison@chromium.org> Cr-Commit-Position: refs/heads/master@{#558692}
-
Ella Ge authored
When events are not handled on cc, they will be re-coalesced and handled on main thread. Use the original latency instead of coalesced latency in tracing. Bug: 789041 Change-Id: Ie9bfd7339b45c4a78ca8065a63cd6d61d0dfc051 Reviewed-on: https://chromium-review.googlesource.com/1049059Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#558691}
-
Lucas Furukawa Gadani authored
As part of onion soup, this CL removes content/renderer/cache_storage layer and move its functionality into blink by using the mojo interface directly. This change also switches FetchAPIResponse and FetchAPIRequest to use the SerializedBlob mojom types, instead of passing the combination of {uuid,size,Blob}. This allows us to preserves the blob type when creating the mojo types. Bug: 612287 Change-Id: I4a4abaf5607467dd39dbaff83bf43cb0f9c07d4d Reviewed-on: https://chromium-review.googlesource.com/1034005Reviewed-by:Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Joshua Bell <jsbell@chromium.org> Reviewed-by:
-
Findit authored
This reverts commit c50e3ea0. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 558649 as the culprit for failures in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtL2M1MGUzZWEwNzQ5MTRlMTQxMjgyNGIyMmFkNzU4NDNlNWQ5YTI4M2QM Sample Failed Build: https://ci.chromium.org/buildbot/chromium.memory/Linux%20Chromium%20OS%20ASan%20LSan%20Tests%20%281%29/27472 Sample Failed Step: capture_unittests Original change's description: > RELAND: media: implement TakePhoto in Chrome OS camera HAL VideoCaptureDevice > > The original CL broke the component build due to a typo in the export > macro. It should have been CAPTURE_EXPORT instead of MEDIA_EXPORT in > camera_3a_controller.h, and the functions in camera_metadata_utils.h > should be exported as well. > > Original change's description -------------------------------------------------- > > media: implement TakePhoto in Chrome OS camera HAL VideoCaptureDevice > > This CL implements the TakePhoto() API for the Chrome OS camera HAL > VideoCaptureDevice, including the following features: > > - Full size still capture > - Auto-focus, auto-exposure, and auto-white-balancing stabilization > > BUG=chromium:832772 > TEST=Run capture_unittests on DUT > TEST=Make sure TakePhoto() API works on > https://googlechrome.github.io/samples/image-capture/grab-frame-take-photo.html > TBR=wuchengli@chromium.org,emircan@chromium.org > > Change-Id: Ia44506b30315df2aaff9047ff725fff95d3ba118 > Reviewed-on: https://chromium-review.googlesource.com/1058881 > Commit-Queue: Ricky Liang <jcliang@chromium.org> > Reviewed-by: Ricky Liang <jcliang@chromium.org> > Cr-Commit-Position: refs/heads/master@{#558649} No-Presubmit: true No-Tree-Checks: true No-Try: true BUG=chromium:832772 Change-Id: I2c9ede5bc6d18e891210b0070f2332fef9755945 Reviewed-on: https://chromium-review.googlesource.com/1059734 Cr-Commit-Position: refs/heads/master@{#558689}
-
Guido Urdaneta authored
The dependency was used to DCHECK that Core Audio functions run on the same task runner as the AudioManager. However, with the new audio service running on a separate process, the device monitor on the browser process fails the DCHECKs because there is no AudioManager. This CL is to be followed by a CL that moves monitoring to the audio service. Still, such monitoring need not depend on the AudioManager, so the removal of this dependency holds in that case as well. Bug: 843106 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: I988b3bf47219556117ed0ea7545281237db5bdee Reviewed-on: https://chromium-review.googlesource.com/1059653 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Commit-Queue: Olga Sharonova <olka@chromium.org> Reviewed-by:
Olga Sharonova <olka@chromium.org> Cr-Commit-Position: refs/heads/master@{#558688}
-
Rayan Kanso authored
It would be useful to be able to store and reinitialize full fetch request data (not just the url). As a specific example, this is needed for background fetch to resume a fetch after a browser restart. TBR=avi@chromium.org Bug: 826257 Change-Id: I3dd388b94bac0d9fa37477967d556118304dd9c9 Reviewed-on: https://chromium-review.googlesource.com/1057271 Commit-Queue: Rayan Kanso <rayankans@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Cr-Commit-Position: refs/heads/master@{#558687}
-
Joel Hockey authored
Bug: 834103 Tbr: noel@chromium.org Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation Change-Id: If1e8186e560ef53674fe1a2a5c1bc05d443aac7d Reviewed-on: https://chromium-review.googlesource.com/1059633Reviewed-by:
-
Jonathan Backer authored
This will add ".RenderWorker-0x0123456789ABCDE" to debug annotations, both tracing and --enable-gpu-service-logging debug logging. Mostly just copy-pasta from GLES2. 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: I1c824c09ab3f1c6f75412bb2222273d32d3b93f6 Reviewed-on: https://chromium-review.googlesource.com/1058121Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Jonathan Backer <backer@chromium.org> Cr-Commit-Position: refs/heads/master@{#558685}
-
Anders Hartvoll Ruud authored
The return value is useless, so might as well use the generated function. R=futhark@chromium.org Bug: 807503 Change-Id: I402edb2b2a70e5ec14e06c3be0fcf5836b46c083 Reviewed-on: https://chromium-review.googlesource.com/1057710Reviewed-by:
Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#558684}
-
Moe Ahmadi authored
Bug: 842746 Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs Change-Id: Ie69687c50368a84ae97f1d648ce33645ce94402b Reviewed-on: https://chromium-review.googlesource.com/1057895 Commit-Queue: Peter Lee <pkl@chromium.org> Reviewed-by:
Peter Lee <pkl@chromium.org> Cr-Commit-Position: refs/heads/master@{#558683}
-
