- 01 Apr, 2019 40 commits
-
-
Avi Drissman authored
BUG=554299 Change-Id: I92a368dac9a618e070c893072d75c8769e13dd03 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546162Reviewed-by:
Sidney San Martín <sdy@chromium.org> Commit-Queue: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#646460}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/e160126c..32a51a79 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I895d3d3d329fee64250cad3f9a8dae86bc525b93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547947Reviewed-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@{#646459}
-
Arnaud Mandy authored
OnDeviceAdded() and OnDeviceRemoved() abstract. destructor being protected. Change-Id: Ibc348d6565b6d2627ae53a34f05a63c08f68a8e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546308Reviewed-by:
Dan Sanders <sandersd@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Cr-Commit-Position: refs/heads/master@{#646458}
-
dpapad authored
Bug: 947926 Change-Id: I14d96dc424c6edc7073d7d8135c67ac42fd7ff92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546062Reviewed-by:
Adam Langley <agl@chromium.org> Auto-Submit: Demetrios Papadopoulos <dpapad@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#646457}
-
Tien Mai authored
Bug: 932737 Change-Id: Ica1e081aca23aa0195d965f8583ae44b60a7d80b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1531165 Commit-Queue: Tien Mai <tienmai@chromium.org> Reviewed-by:
Roger Tawa <rogerta@chromium.org> Cr-Commit-Position: refs/heads/master@{#646456}
-
manuk authored
This is the 3rd refactoring CL aimed at reducing duplication and inconsistency for classifying omnibox results. This CL 1) Creates a autocomplete_match_classification file to group static classification methods. This organizes related code adjacently, promotes code reuse instead of duplicated code per provider, and avoids providers calling into other providers' static classification methods. 2) Renames HistoryProvider::SpansFromTermMatch to ClassifyTermMatches and moves it to autocomplete_match_classification. It is responsible for creating ACMatchClassifications from TermMatches. 3) Previously, SpansFromTermMatches accepted the bool param is_url which determined how to style matches and non-matches. To make the method reusable by the search provider, which uses reversed styling compared to other providers for non-URL text, ClassifyTermMatches is overloaded with a more generic signature that parameterizes the match and non-match styles. Bug: 366623 Change-Id: I60dfb82305f6e81fa00ff86662e63d2f9e24bb99 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546783 Commit-Queue: manuk hovanesian <manukh@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#646455}
-
Johannes Henkel authored
I've been seeing a revert due to this test being flaky. Root cause appears to be that sometimes, the Window's node name is just "Window", and sometimes it's "Window / file://". So I'm thinking this can be cured by making it always Window. Change-Id: I89e57f248d24462fdcb79e6db4e278e58f93c473 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546939Reviewed-by:
Alexei Filippov <alph@chromium.org> Commit-Queue: Johannes Henkel <johannes@chromium.org> Cr-Commit-Position: refs/heads/master@{#646454}
-
James Zern authored
aa65f89a HistogramCombineStochastic: fix free of uninit value previously if the mappings allocation failed histo_queue->queue would be uninitialized; split the conditionals Change-Id: I1b50b987e734393893dc8a83a3f314522ccd0c83 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546932 Commit-Queue: Urvang Joshi <urvang@chromium.org> Reviewed-by:
Urvang Joshi <urvang@chromium.org> Cr-Commit-Position: refs/heads/master@{#646453}
-
Jared Saul authored
Also split popup_constants.h into a new popup_payments_constants.h Bug: 940042 Change-Id: If0bdc26860a5ff35b44c323aa0b99f7404eb6019 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535259 Commit-Queue: Jared Saul <jsaul@google.com> Reviewed-by:
David Roger <droger@chromium.org> Reviewed-by:
Fabio Tirelo <ftirelo@chromium.org> Cr-Commit-Position: refs/heads/master@{#646452}
-
Anushruth authored
Removing linux-blink-heap-incremental-marking as the feature that the bot was used for has already been enabled. R=bpastene@chromium.org, jbudorick@chromium.org Bug: 943044 Change-Id: Ie6116738ed4bbd977cc20db9d55f35ccad76be2c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1542683Reviewed-by:
Ben Pastene <bpastene@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: Anushruth <anushruth@chromium.org> Cr-Commit-Position: refs/heads/master@{#646451}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/096bd921bbab..d7d8b4c6d219 Created with: gclient setdep -r src-internal@d7d8b4c6d219 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. CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome TBR=shimazu@chromium.org,dgozman@chromium.org,hbos@chromium.org Change-Id: Id5dfb8fc9086c607f89d107de2144aee7d8305c2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547306Reviewed-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@{#646450}
-
Matthew Jones authored
Bug: 930785 Change-Id: I06fa29a5136a7b69d6abbc2822239d9a9ce6aef3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546523Reviewed-by:
Ian Vollick <vollick@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#646449}
-
Maggie Chen authored
WebglConformance_conformance_glsl_misc_shader_with_non_reserved_words fails at Mac FYI Retina Debug (NVIDIA) bot Bug: 948218 Change-Id: I057b5d431af758a8b85c301490891ef32e04b91f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547948Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Maggie Chen <magchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#646448}
-
Ben Kelly authored
In crrev.com/c/1321209 for crbug.com/902488 we made cache_storage hold backend disk_cache objects open as long as the blink CacheStorage object is in existence. The idea was that if a context has used cache_storage once it is likely to do so again. It turns out, however, that the blink CacheStorage object is often garbage collected before the context is destroyed. This makes our logic to keep backends warmed less effective. This CL fixes the problem by implementing HasPendingActivity() to keep the CacheStorage blink objects that have been used alive until the context is destroyed. This also allows us to remove a number of explicit CacheStorage references held by Cache and during operations. Bug: 947512 Change-Id: Iee1fa152ec597038e7c90030e9861a2814e0579c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1545932 Commit-Queue: Ben Kelly <wanderview@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#646447}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/f6cbd3926d95..02df81c0a28f git log f6cbd3926d95..02df81c0a28f --date=short --no-merges --format='%ad %ae %s' 2019-04-01 mikenichols@chromium.org cros_tryjob: Schedule production tryjobs in release bot group Created with: gclient setdep -r src/third_party/chromite@02df81c0a28f The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md If the roll is causing failures, please contact the current sheriff, who should be CC'd on the roll, and stop the roller if necessary. CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@chromium.org Change-Id: I7e227f36a5a78bd0df1bd3b140d95b45714b789c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547307Reviewed-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@{#646446}
-
Paul Jensen authored
Disable detectUntaggedSockets when creating a socket in NetworkChangeNotifierAutoDetect. The socket isn't used for sending or receiving data so it doesn't need to be tagged. All other sockets in Chrome are created in C++ where detectUntaggedSockets doesn't detect violations. Bug: 946531 Change-Id: I1f7f6bd5ad7e4e8e73df527e69371d335708e8cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546061Reviewed-by:
Richard Coles <torne@chromium.org> Commit-Queue: Paul Jensen <pauljensen@chromium.org> Auto-Submit: Paul Jensen <pauljensen@chromium.org> Cr-Commit-Position: refs/heads/master@{#646445}
-
John Chen authored
In a sequence of mouse pointerDown, pointerUp, and pointerMove actions, the mouse button saved by the first two actions needs to be cleared while processing the last action, as no button is pressed. Fixes the following Selenium Java test: CombinedInputActionsTest.testControlClickingOnMultiSelectionList Bug: chromedriver:1897 Change-Id: I0bd7b377fa0c977c8c20c5c0e306f772ee30ca98 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547130 Auto-Submit: John Chen <johnchen@chromium.org> Reviewed-by:
Lan Wei <lanwei@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#646444}
-
Xiaohui Chen authored
TBR=wutao@chromium.com,llin@google.com Bug: None Change-Id: I4c630c6cdd4a635e70fcfa699f8cf9d46ea8099d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548131Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#646443}
-
John Budorick authored
Follow-up to crrev.com/i/1125563 Bug: 947242 Change-Id: If6cabd80831ae17c28942a1676a82340620d780e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547944Reviewed-by:
-
Sammie Quon authored
It originally send key down on tap down, and key up on tap, but this was changed to just key down on tap, because some gestures send the tap event and the browser listens to just the key up. But ARC apps need the entire sequence, so this sends both on click. Original bug: https://bugs.chromium.org/p/chromium/issues/detail?id=943154 Test: manual Bug: b/129248267 Change-Id: I5e5d16f4dc6a675d1a96936ad938e5201ad74aa1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1542224 Commit-Queue: Sammie Quon <sammiequon@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#646441}
-
Jason Chase authored
- Removed expected.txt files for InstalledApp tests, in favour of runtime flag check, similar to other tests. - Removed WASM tests entirely, since feature is shipped and tests were marked as skip. Change-Id: I4a4c292c1a756c7744ee1386f4ccaf0696f478ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546135Reviewed-by:
Ian Clelland <iclelland@chromium.org> Commit-Queue: Jason Chase <chasej@chromium.org> Cr-Commit-Position: refs/heads/master@{#646440}
-
Anatoliy Potapchuk authored
The bug appeared after enabling SingleProcessMash by default. Temporally using shell::Get() as of not being able to add a window observer by other way. Bug: 940004 Change-Id: I5e3cb099757a451063c1259adfa729f60efff550 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547701 Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#646439}
-
Dave Tapuska authored
The test failed because a promise was uncaught. Ensure that either a rejected or allowed promise will allow the test to pass provided Change-Id: I604ab23fe32a1dee1ed60182dd25e4ffbd60a688 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548032Reviewed-by:
Robert Ma <robertma@chromium.org> Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Cr-Commit-Position: refs/heads/master@{#646438}
-
Tibor Goldschwendt authored
+ Move tab management resources into its DFM. Bug: 944115 Change-Id: If14cdcfeb6bca94b9f1b040049c0f659831b193b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1534777Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Peter Wen <wnwen@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Commit-Queue: Tibor Goldschwendt <tiborg@chromium.org> Auto-Submit: Tibor Goldschwendt <tiborg@chromium.org> Cr-Commit-Position: refs/heads/master@{#646437}
-
Wez authored
Tests wishing to launch components in Environments containing only test- provided services (i.e. without inheriting access to all services from the test fixture's sandbox), need to explicitly provide the fuchsia.sys.Loader service otherwise no components can be loaded in the new Environment. To pass the Loader service into the new environment, the test fixture must itself have access to that service through its own sandbox. Change-Id: I570b930dbd4002d061222fe4b449e92b24733894 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548049 Auto-Submit: Wez <wez@chromium.org> Reviewed-by:
Fabrice de Gans-Riberi <fdegans@chromium.org> Commit-Queue: Fabrice de Gans-Riberi <fdegans@chromium.org> Cr-Commit-Position: refs/heads/master@{#646436}
-
Cathy Li authored
Resolve CL comments from https://chromium-review.googlesource.com/c/chromium/src/+/1535227 Bug: 936050 Change-Id: Ia5a8223577cfa43a5ea38a9a6165f7fd0d266993 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1545194 Commit-Queue: Cathy Li <chili@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Cr-Commit-Position: refs/heads/master@{#646435}
-
Andrew Grieve authored
Also fixes our runner scanning the same under-test apk for tests multiple times, and skips scanning of system apks Bug: 917426 Change-Id: I3dc56e87d971cdfb9dca785ad30726afcd1e1372 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1535353 Commit-Queue: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Eric Stevenson <estevenson@chromium.org> Reviewed-by:
-
Brandon Wylie authored
Bug: 936052 Change-Id: Ied38dd673b37a296211694a58018aaab9f25a736 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546852Reviewed-by:
Sky Malice <skym@chromium.org> Reviewed-by:
-
Nicolás Peña Moreno authored
The element ID helps developers and analytics providers determine which element the PerformanceElementTiming entry is referring to. While we have other ways to find out the element for Image Element Timing (for\ example, we can use the image requested URL), for text the available resources will be much limited and thus ID is needed. Bug: 879270, 942033 Change-Id: I0f20609cf4edc7eb6431448c439b9cf911f89fb9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1544948 Commit-Queue: Nicolás Peña Moreno <npm@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#646432}
-
Harley Li authored
It should not just clean the main target's storage. Change-Id: I580a23267e8cd7ca14938debc6f5a8754e59c646 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546620 Commit-Queue: Haihong Li (Harley) <hhli@chromium.org> Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Cr-Commit-Position: refs/heads/master@{#646431}
-
rajendrant authored
This reverts commit 452c35d1. Reason for revert: <INSERT REASONING HERE> Original change's description: > Change 502 response with no bypass info to block-once > > CORB failures could block any response headers being sent to the rendere. These > are treated as a random 1-5 minute bypass, since Chrome-Proxy is not in the > response. This CL changes those bypasses to a block-once. > > Bug: 947736 > Change-Id: I83c6a9874ccb26e4f17d8dccf7e9eeac8dd7f535 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546678 > Commit-Queue: rajendrant <rajendrant@chromium.org> > Reviewed-by: Tarun Bansal <tbansal@chromium.org> > Cr-Commit-Position: refs/heads/master@{#646136} TBR=tbansal@chromium.org,rajendrant@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 947736 Change-Id: Ie2fafbf28cb2549d3e4b0d056b420af198dd5cb7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546886Reviewed-by:
rajendrant <rajendrant@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: rajendrant <rajendrant@chromium.org> Cr-Commit-Position: refs/heads/master@{#646430}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/320a7de5c9a5..0300a464a4cc git log 320a7de5c9a5..0300a464a4cc --date=short --no-merges --format='%ad %ae %s' 2019-04-01 33432579+alan-baker@users.noreply.github.com Maintain inst to block mapping in merge return (#2469) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@0300a464a4cc 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: Iffe6d8e6bb5970c69861ad8aff72bcdeb104f597 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547303Reviewed-by:
-
Victor Costan authored
This CL removes 0003-fts3-Disasble-fts3_tokenizer-and-fts4.patch. The patch disables the following bits of functionality from SQLite's FTS3 extension: * The fts4 virtual table mode. * The fts3_tokenizer() function. Both bits of functionality were disabled to avoid exposing them to WebSQL. However, the custom authorizer [1] in our WebSQL implementation uses a whitelist that doesn't include fts4 virtual tables or the fts3_tokenizer() functions. So, at this point, the patch only serves to disable the features for use in Chrome features. Blocking Chrome feature code from using FTS features is mildly desirable, as it makes it more likely that we'll be able to disable FTS3 entirely after we stop supporting WebSQL. However, this benefit isn't sufficient to justify carrying a patch on top of SQLite. [1] https://www.sqlite.org/c3ref/set_authorizer.html Bug: 945204 Change-Id: I23fc2a54895dd2063a50d8f9f45636d29dfa19cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1545686 Commit-Queue: Victor Costan <pwnall@chromium.org> Auto-Submit: Victor Costan <pwnall@chromium.org> Reviewed-by:
Chris Mumford <cmumford@google.com> Cr-Commit-Position: refs/heads/master@{#646428}
-
Emily Hanley authored
Bug: 948142 Change-Id: Ib64633b03bd1d12c5e3d1571ad6d8ba43b1405d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1539857 Commit-Queue: Emily Hanley <eyaich@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Kunihiko Sakamoto <ksakamoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#646427}
-
Hui(Andy) Wu authored
When script finishes normally, AssistantCoordinator.setVisible(false) is not triggered anywhere, hence the listener to keyboard visibility is not removed. If the previous state is to hide keyboard, it will keep trying to hide keyboard after autobot finishes. Before patch: https://drive.google.com/file/d/13Nw5Tr_PHVeo5qkrBB0VA5RmkGl3ZyKe/view?usp=sharing After patch: https://drive.google.com/file/d/1DXKmblltiz4tEoDqaGHWRgFOiNeJXmIz/view?usp=sharing Change-Id: I1d2efa5739471aaeb7fe0a966e3f11c46a69d092 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546235Reviewed-by:
Jordan Demeulenaere <jdemeulenaere@chromium.org> Commit-Queue: Hui Wu <wuandy@chromium.org> Cr-Commit-Position: refs/heads/master@{#646426}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/de206c75c2c8..b6a3a3b245a5 git log de206c75c2c8..b6a3a3b245a5 --date=short --no-merges --format='%ad %ae %s' 2019-04-01 bsalomon@google.com Make lazy proxies have 2 modes for proxy/surface key management. Created with: gclient setdep -r src/third_party/skia@b6a3a3b245a5 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-blink-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 TBR=jlavrova@chromium.org Change-Id: I5bb680baf21fd43a5ebc6f2b8e4d1d506180b3b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547302Reviewed-by:
-
Sergey Ulanov authored
Previously VulkanImplementation defined functions for semaphore import/export from/to file descriptors. This approach doesn't work on platforms that don't support FDs for semaphores, specifically on Fuchsia and Windows. This CL: 1. Adds cross-platform gpu::SemaphoreHandle that allows to represent semaphore handle on any platforms. 2. Replaces ImportSemaphoreFdKHR() with ImportSemaphoreHandle(). 3. Replaces GetSemaphoreFdKHR() with GetSemaphoreHandle() This allows to remove dependency on ScopedFD in gpu::ExternalVkImageFactory, which will make it easier to reuse that class on Fuchsia and Windows. Bug: 934526 Change-Id: I16b1a9f3a606683b76a73c4e68a33b3294f25a90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1540724 Commit-Queue: Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Auto-Submit: Sergey Ulanov <sergeyu@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Reviewed-by:
Antoine Labour <piman@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Cr-Commit-Position: refs/heads/master@{#646424}
-
Josh Karlin authored
It's a big method that can easily be broken up into smaller methods. This will make it easier to review downstream changes. Also, rather than create a TextWrapper every time it's needed, I instantiated one for the class. That winds up saving about .3 seconds when running histograms pretty_print.py. Bug: 1538783 Change-Id: I4bb697c74472e8729060828e29a2f67766fa4f43 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1543248 Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Cr-Commit-Position: refs/heads/master@{#646423}
-
Paul Jensen authored
Ignore network interfaces with just link-local addresses when computing a computer's network connection type. Mac assigns link local addresses to several different types of interfaces even when they are not connected. Internal bug b/128444384. Change-Id: Iee6f3143903c5f2f7e4c3b3942221ab4251854d2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1546877 Commit-Queue: Paul Jensen <pauljensen@chromium.org> Reviewed-by:
Josh Karlin <jkarlin@chromium.org> Cr-Commit-Position: refs/heads/master@{#646422}
-
chromium-autoroll authored
https://pdfium.googlesource.com/pdfium.git/+log/21d000094ade..010a4da72d17 git log 21d000094ade..010a4da72d17 --date=short --no-merges --format='%ad %ae %s' 2019-04-01 tsepez@chromium.org Limit input size in pdf_fx_date_helpers_fuzzer. 2019-04-01 thestig@chromium.org Avoid premature decoding completion in CJBig2_ArithDecoder. Created with: gclient setdep -r src/third_party/pdfium@010a4da72d17 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. BUG=chromium:947780,chromium:947622 TBR=dsinclair@chromium.org Change-Id: I42f2ec103277a13cfb9dbae2cd0cb0a200375a0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547300Reviewed-by:
-
