- 03 Jun, 2020 38 commits
-
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/ce9a17d4..b952659f 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,vahl@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I693e52569582c7474fed0fd5705268fa4b8ddc7c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225550Reviewed-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@{#774444}
-
zhaoyangli authored
Will observe if there are issues from the experiment then set code coverage as default in iOS CQ builders. Bug: 1090188 Change-Id: I77e58aefbfc4964f63de61cef7bd7a351d11bfc7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227236 Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org> Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Cr-Commit-Position: refs/heads/master@{#774443}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/70b11675ddaf..9172a9f05054 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC dmazzoni@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: chromium:1047629,chromium:1085419,chromium:1087057,chromium:1090082,chromium:1090105,chromium:1090456 Tbr: dmazzoni@google.com Change-Id: I7ca1a2a09cb8262ea1aefde9dd1d8c5d15be9827 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227287Reviewed-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@{#774442}
-
Mason Freed authored
It makes more sense to count this feature at the usage site, which is Element::AttachDeclarativeShadowRoot. Bug: 1042130 Change-Id: I53ffbf6821b56e964dc5ab1eae84a0ed566a96e3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227338 Commit-Queue: Mason Freed <masonfreed@chromium.org> Commit-Queue: Kouhei Ueno <kouhei@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Reviewed-by:
Kouhei Ueno <kouhei@chromium.org> Cr-Commit-Position: refs/heads/master@{#774441}
-
Nick Harper authored
Change-Id: Ibfaaccad7eb871fdeeefa93274b39496ea4b6ecd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227173 Commit-Queue: Nick Harper <nharper@chromium.org> Commit-Queue: Ryan Sleevi <rsleevi@chromium.org> Auto-Submit: Nick Harper <nharper@chromium.org> Reviewed-by:
Ryan Sleevi <rsleevi@chromium.org> Cr-Commit-Position: refs/heads/master@{#774440}
-
Sinan Sahin authored
Bug: 1088069 Change-Id: I37b24a8f374d36f6d49d306748f59187b21e23d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225552Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Sinan Sahin <sinansahin@google.com> Cr-Commit-Position: refs/heads/master@{#774439}
-
Mason Freed authored
This connects the RuntimeEnabledFeature to a base::Feature to allow this feature to be Finch tested. Bug: 901056 Change-Id: I337c46ed04361abb05913678c265489b01038da5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227100 Commit-Queue: Mason Freed <masonfreed@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/master@{#774438}
-
Ian Wells authored
Bug: 1044139 Change-Id: Ib06335cd3ac0f85a0c44a21094457b65585fca64 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220228 Commit-Queue: Ian Wells <iwells@chromium.org> Reviewed-by:
Justin DeWitt <dewittj@chromium.org> Reviewed-by:
Dan H <harringtond@chromium.org> Cr-Commit-Position: refs/heads/master@{#774437}
-
Kent Tamura authored
This CL ports LayoutRubyRun::GetOverhang() to LayoutNG. Overhang values are represented as negative margins of ruby run boxes. Bug: 1069817 Change-Id: I487a633982d40211ee672d71caf00fadd88a07e6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224895 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#774436}
-
Giovanni Ortuño Urquidi authored
This reverts commit 6c7cfb00. Reason for revert: Causing media-unittest failures on win-asan https://ci.chromium.org/p/chromium/builders/ci/win-asan/12503 https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8878571776794508208/+/steps/media_unittests_on_Windows-10-15063/0/logs/Deterministic_failure:_D3D11VideoDecoderTest.DoesNotSupportEncryptionWithFlagOn11_0__status_CRASH_/0 ==12148==ERROR: AddressSanitizer: heap-use-after-free on address 0x11f0e8b56314 at pc 0x7ff697ff598f bp 0x00d00939e830 sp 0x00d00939e878 READ of size 24 at 0x11f0e8b56314 thread T0 #0 0x7ff697ff59b8 in __asan_memcpy C:\b\s\w\ir\cache\builder\src\third_party\llvm\compiler-rt\lib\asan\asan_interceptors_memintrinsics.cpp:22 #1 0x7ff69882a563 in media::GetSupportedD3D11VideoDecoderResolutions C:\b\s\w\ir\cache\builder\src\media\gpu\windows\supported_profile_helpers.cc:222 #2 0x7ff69881fa44 in media::D3D11VideoDecoder::GetSupportedVideoDecoderConfigs C:\b\s\w\ir\cache\builder\src\media\gpu\windows\d3d11_video_decoder.cc:912 #3 0x7ff695f9192c in media::D3D11VideoDecoderTest::CreateDecoder C:\b\s\w\ir\cache\builder\src\media\gpu\windows\d3d11_video_decoder_unittest.cc:189 Original change's description: > Refactor GetResolutionsForDecoders() to support AV1. > > Does the following: > - Internalizes h264 and min resolution details. > - Sets the minimum resolution to 64,64 for both decoders. > - Only loops through the video device profiles once. > - Switches away from an std::pair to a named struct. > - Adds AV1 GUID values and uses them in DXVA decoder. > - Stops D3D11VideoDecoder for enumerating unsupported profiles. > - Stops using the DXVA2_Intel_ModeH264_E for enumeration. > - Gives all resolution tests a square resolution; e.g., 4k x 4k. > - Doesn't test or indicate support for a duplicate portrait resolution. > > R=liberato, tmathmeyer > > Bug: 1073252 > Test: Updated unittests. > Change-Id: I8013e89104c96fad845fdbaecdb1d4b239f9a380 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2223261 > Commit-Queue: Frank Liberato <liberato@chromium.org> > Reviewed-by: Ted Meyer <tmathmeyer@chromium.org> > Reviewed-by: Frank Liberato <liberato@chromium.org> > Auto-Submit: Dale Curtis <dalecurtis@chromium.org> > Cr-Commit-Position: refs/heads/master@{#774317} TBR=dalecurtis@chromium.org,liberato@chromium.org,tmathmeyer@chromium.org Change-Id: Idb9d7d61938860c46ed72cd588d48fb5eeedadf0 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1073252 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227710Reviewed-by:
Giovanni Ortuño Urquidi <ortuno@chromium.org> Commit-Queue: Giovanni Ortuño Urquidi <ortuno@chromium.org> Cr-Commit-Position: refs/heads/master@{#774435}
-
tby authored
The plan for integration testing in the launcher is roughly as follows: 1. Give search providers a method to identify themselves with a search result type (<- this CL). 2. Use the getter to inform the Mixer _which_ search provider is triggering a OnResultsChanged call. 3. Add hooks into the Mixer allowing a RunLoop to wait until a list of providers have created results and called OnResultsChanged. 4. Use the RunLoop hooks to build integration tests that inspect the result of a query after all relevant providers have completed. This CL adds a getter method that lets each SearchProvider identify itself with a particular search result type. Two providers, SettingsShortcutProvider and ArcAppDataSearchProvider, don't appear to have enum entries for their result types. I've given them kUnknown for now, and we can update them if they ever need to be integration tested. Due to the asynchrony of the search backend, we need this kind of "wait until providers are done" system in order to know how long to wait for in a browser test, as browser tests don't support ScopedTasksEnvironments and the like. In future we could use this system to optimize search ranking, as we would know which results are new, and could avoid re-ranking already ranked results. Bug: 1086713 Change-Id: Icac3efaaf963a4b5e445dd0a0de8fd435fd27f61 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2214736Reviewed-by:Jia Meng <jiameng@chromium.org> Commit-Queue: Tony Yeoman <tby@chromium.org> Cr-Commit-Position: refs/heads/master@{#774434}
-
Yuichiro Hanada authored
ArcImeService provides the method, SetArcWindowDelegateForTesting() to inject a fake instance of ArcWindowDelegate for testing. However, the instance of ArcWindowDelegate was generated in the constructor and used in the constructor, so that usage cannot be faked. This CL adds a new constructor for testing to ArcImeService to fix it. Bug: b:148193316 Test: component_unittests Change-Id: Ia3b6c68bbc66fd4d5bc640ecdabbb707143cfff6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2224943 Commit-Queue: Yuichiro Hanada <yhanada@chromium.org> Reviewed-by:
Tetsui Ohkubo <tetsui@chromium.org> Cr-Commit-Position: refs/heads/master@{#774433}
-
zhaoyangli authored
This is to only instrument CL affected files for iOS coverage try builder for efficiency. Bug: 1090188 Change-Id: I386dcafef9ee174a7b22cbc0073ee58118f4ed6b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227305Reviewed-by:
Yuke Liao <liaoyuke@chromium.org> Commit-Queue: Zhaoyang Li <zhaoyangli@chromium.org> Cr-Commit-Position: refs/heads/master@{#774432}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/fc0efae149cb..a40746d97615 2020-06-02 treehugger-gerrit@google.com Merge "trace_processor_shell: don't quit on CTRL-C" If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel Bug: None Tbr: perfetto-bugs@google.com Change-Id: Ic408846d2fd2243b9688572b514bc6e5905f07f8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227283Reviewed-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@{#774431}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/907433b9f820..e817aaa40954 2020-06-02 bclayton@google.com libVulkan: Use new marl::Scheduler::Config API. 2020-06-02 bclayton@google.com Kokoro: Test LLVM 10 backend for macos 2020-06-02 bclayton@google.com Merge changes I5eaceebc,I4d78c011,I7d01a3c8 2020-06-02 caio.oliveira@intel.com Update VkStringify for VK_EXT_subgroup_size_control 2020-06-02 caio.oliveira@intel.com Update Vulkan headers to version 1.2.141 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;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:linux-swangle-try-x64;luci.chromium.try:win-swangle-try-x86 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I52a4d194907046bada444db98c853ef199aeb072 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227275Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/76a2918f55cd..cf77d6e387b6 2020-06-02 vapier@chromium.org repo: update to 2.8 launcher If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll Please CC agable@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: agable@chromium.org Test: Test: `repo sync` still works Change-Id: I4d6b3983bda93e662507076df2a4ad9781810b7a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227281Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/88bc40da7991..9f2374511ab3 2020-06-02 chrche@microsoft.com Add customization to i18n.js 2020-06-02 cjamcl@chromium.org Update the fallback revision for remote modules. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I55982b72cb119c3db08625d8ce4f287a086a88e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227284Reviewed-by:
-
Robert Liao authored
Change-Id: Ia30b175784474592469f9a862592125416d15726 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227310 Auto-Submit: Robert Liao <robliao@chromium.org> Reviewed-by:
Wei Li <weili@chromium.org> Commit-Queue: Wei Li <weili@chromium.org> Cr-Commit-Position: refs/heads/master@{#774427}
-
Yuwei Huang authored
Currently ftl_echo_message_listener_ is never explicitly freed, and it calls `signal_strategy_->RemoveListener(this)` in its dtor, while signal_strategy_ is freed in HostProcess::OnHostOfflineReasonAck. This causes a use-after-free issue when the ftl_echo_message_listener_ is explicitly freed, which means the host would crash in shutdown and soft restart. This CL frees ftl_echo_message_listener_ before signal_strategy_ is freed. Bug: 1090595 Change-Id: Ie546a9084fdf21545ecd9158b9830cc93335ecb7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227265 Commit-Queue: Yuwei Huang <yuweih@chromium.org> Commit-Queue: Jamie Walch <jamiewalch@chromium.org> Auto-Submit: Yuwei Huang <yuweih@chromium.org> Reviewed-by:
Jamie Walch <jamiewalch@chromium.org> Cr-Commit-Position: refs/heads/master@{#774426}
-
Peter Kasting authored
This simplifies some code that no longer needs to worry about whether they're supported. Bug: none Change-Id: I728fb9a93373d6cb3674c5dbaecccce341774780 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227101 Auto-Submit: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Allen Bauer <kylixrd@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#774425}
-
Tina Wang authored
- Add customized item and cell for settings which has a toggle switcher once not managed by policy. - Apply to "Save Password" setting. - Add corresponding method to handle click action of the info button. Screenshot: https://screenshot.googleplex.com/6doUPsk0Dmj Bug: 1087223 Change-Id: I3140c7cfb99dbaf46f8679c4e675b9ab0002d6c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2219569 Commit-Queue: Tina Wang <tinazwang@chromium.org> Reviewed-by:
Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#774424}
-
Bo Liu authored
Change-Id: I975b7d0bbd7bc7c002954939563d5e54cdcbc1f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227375Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#774423}
-
Scott Violet authored
To fully support onScrollOffsetOrExtentChanged() comes at a performance cost. As very few places actually need this, this creates a new interface with onScrollOffsetOrExtentChanged() and converts the places that need it to the new interface. BUG=1087480 TEST=none Change-Id: I1f54bdf74ee0b6006fc92284bc761ed6992a0d55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225548 Commit-Queue: Scott Violet <sky@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#774422}
-
Sammie Quon authored
Test: added test Bug: 1077922 Change-Id: Id596f604a24e230c818fa81c930782c9fa4841eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227289Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Commit-Queue: Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#774421}
-
Rouslan Solomakhin authored
Before this patch, Android integration tests for payment handler capabilities used the internals of ServiceWorkerPaymentApp.java, which prevented moving the payment handler logic from Java to the C++ service_worker_payment_app.cc. This patch replaces one Android integration test for capabilities with a cross-platform browser test. After this patch, fewer tests depend on ServiceWorkerPaymentApp.java internals, so its logic can be moved from Java to C++ easier. Design: https://bit.ly/cross-platform-pay-app-factory TBR=yusufo@chromium.org Bug: 1022512 Change-Id: I5d2bd943f079f501a681a5ef03d12329d3d91d04 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2223650 Commit-Queue: Rouslan Solomakhin <rouslan@chromium.org> Reviewed-by:
Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:
-
Brandon Maslen authored
This change adds telemetry to the Storage Access API with the goal of tracking the utilization of the API and how the API is being used. This includes the following metrics: - UseCounter for document.hasStorageAccess and document.requestStorageAccess methods. - Histogram API.StorageAccess.AllowedRequests to track how often requests for storage access are allowed/blocked and specifically allowed due to the API. - Histogram API.StorageAccess.GrantIsImplicit to track how often requests generate an implicit vs explicit grant. - Histogram API.StorageAccess.RequestStorageAccess to track how the main method for the API is utilized and how frequently usage is successful or fails for various reasons. Various tests have been added where possible to validate the associated telemetry items have been fired. Bug: 989663 Change-Id: I44ecf8240ccfd50fee445e1782e9a578354ab68a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2211135 Commit-Queue: Brandon Maslen <brandm@microsoft.com> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Reviewed-by:
Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Mike West <mkwst@chromium.org> Reviewed-by:
Maksim Orlovich <morlovich@chromium.org> Cr-Commit-Position: refs/heads/master@{#774419}
-
Yoichi Osato authored
This CL relands the patch crrev.com/c/2172724, which was reverted as crrev.com/c/2224218 due to 1. linux-blink-cors-rel failure 2. http/tests/loading/bad-server-subframe.html failing on mac bots I fixed #1 by updating FlagExpectations/disable-features=OutOfBlinkCors. For #2, it is reported flaky: https://analysis.chromium.org/p/chromium/flake-portal/flakes/occurrences?key=ag9zfmZpbmRpdC1mb3ItbWVyTwsSBUZsYWtlIkRjaHJvbWl1bUBibGlua193ZWJfdGVzdHNAaHR0cC90ZXN0cy9sb2FkaW5nL2JhZC1zZXJ2ZXItc3ViZnJhbWUuaHRtbAw (guessed crrev.com/c/2219088 the culprit). Now this CL passes the bots. Bug: 688906 Cq-Include-Trybots: chromium/try:mac10.10-blink-rel,mac10.11-blink-rel Change-Id: I9d64f917014096f79b224369fc719e9743086b45 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226103Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Yoichi Osato <yoichio@chromium.org> Cr-Commit-Position: refs/heads/master@{#774418}
-
Garrett Beaty authored
Bug: 944108 Change-Id: I940c98b23f028d1f6e62d7880284f5dae6e82fe4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227509 Auto-Submit: Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Stephen Martinis <martiniss@chromium.org> Reviewed-by:
Stephen Martinis <martiniss@chromium.org> Cr-Commit-Position: refs/heads/master@{#774417}
-
Reilly Grant authored
UsbServiceLinux, HidServiceLinux and SerialDeviceEnumeratorLinux each only care about devices from a particular subsystem. This change avoids processing other devices which should decrease the time it takes to perform the initial enumeration. Change-Id: I3535b5e6ecbb8c013957197cff151011a19a6097 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227094 Commit-Queue: Reilly Grant <reillyg@chromium.org> Commit-Queue: Matt Reynolds <mattreynolds@chromium.org> Reviewed-by:
Matt Reynolds <mattreynolds@chromium.org> Auto-Submit: Reilly Grant <reillyg@chromium.org> Cr-Commit-Position: refs/heads/master@{#774416}
-
Bill Budge authored
Bug: chromium:1089352 Change-Id: I4730c417100532410e9355a8fdf5551ee130138f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225591 Commit-Queue: Kentaro Hara <haraken@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Auto-Submit: Bill Budge <bbudge@chromium.org> Cr-Commit-Position: refs/heads/master@{#774415}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/cd6894f0a29e..bbbe9134378d 2020-06-02 bpastene@chromium.org devil: Remove special EBUSY error logging when mkdir'ing on devices If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/catapult-autoroll Please CC wenbinzhang@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-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:739899 Tbr: wenbinzhang@google.com Change-Id: Ic5194f779e084d7255796fac4396b738d391a33e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2227274Reviewed-by:
-
Sammie Quon authored
Re-try of crrev.com/c/2182409. The change is the same but this time I was able to locally repro the original failure (and have no failures running this) and some fixes have landed since the last attempt. Test: none Bug: 1035356 Change-Id: Idc53b58a70f68be05b7ad36efb18c6facdb3ad56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226784Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Commit-Queue: Sammie Quon <sammiequon@chromium.org> Cr-Commit-Position: refs/heads/master@{#774413}
-
Khushal Sagar authored
This histogram is needed to track the proportion of devices with accelerated rasterization (drivers haven't been blacklisted) for which we want to have continuous monitoring. Bug: 1089346 Change-Id: I7b2dc36216fc91980c26ee34870be48eda952812 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226783 Commit-Queue: Khushal <khushalsagar@chromium.org> Commit-Queue: Alexei Svitkine <asvitkine@chromium.org> Auto-Submit: Khushal <khushalsagar@chromium.org> Reviewed-by:
-
Jinsuk Kim authored
Once theme change happens, the old StatusBarColorController needs to stop referencing the tab which is now being handled by a new instance after the reparenting. This CL makes sure to null out the reference. Bug: 1087257 Change-Id: Ib58f74b78fec84b197e501169be07f60a5532ce5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2217724Reviewed-by:
Matthew Jones <mdjones@chromium.org> Reviewed-by:
Jinsuk Kim <jinsukkim@chromium.org> Commit-Queue: Jinsuk Kim <jinsukkim@chromium.org> Cr-Commit-Position: refs/heads/master@{#774411}
-
tby authored
Change-Id: I7a20e77790f3ec4ffbdad575ef018617a84d85eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226482Reviewed-by:
Charles . <charleszhao@chromium.org> Commit-Queue: Tony Yeoman <tby@chromium.org> Cr-Commit-Position: refs/heads/master@{#774410}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1591084785-bc7c0a51a37ede3908243e746df6ba544dcec5c7.profdata to chrome-win32-master-1591113598-40e58c4b4405dc23a9940215457135cbcc33e410.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium Please CC jeffyoon@google.com,liaoyuke@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md Cq-Include-Trybots: chrome/try:win-chrome Tbr: jeffyoon@google.com,liaoyuke@google.com Change-Id: I7a89a6feb3e33d1a9811ab1ddda6708594e69ec7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226953Reviewed-by:
-
Fred Mello authored
Extending the expiry date for all DFM "Android.FeatureModules." in tools/metrics/histograms/histograms.xml. These are still needed while we continue to troubleshoot a small number of issues. Changed owners to reflect a more up-to-date set. Bug: 1086211 Change-Id: Ie5d2f14a93af008134c4742cc8c59edbfb017ec4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2225386 Commit-Queue: Fred Mello <fredmello@chromium.org> Auto-Submit: Fred Mello <fredmello@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#774408}
-
Austin Eng authored
Tbr=kainino@chromium.org Bug: dawn:449, dawn:323, dawn:399 Change-Id: I3f1892acad7c636e8c10f852510ed89972411f62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2226914 Commit-Queue: Kai Ninomiya <kainino@chromium.org> Reviewed-by:
Kai Ninomiya <kainino@chromium.org> Reviewed-by:
Austin Eng <enga@chromium.org> Auto-Submit: Austin Eng <enga@chromium.org> Cr-Commit-Position: refs/heads/master@{#774407}
-
- 02 Jun, 2020 2 commits
-
-
Carlos Frias authored
ChromeBackForwardCacheBrowserTest.WebBluetooth Test is flaky. It is reported as a hidden flake as it passes on retries. Cause identified: The test configures a mock Bluetooth adapter first and then performs a web Bluetooth API call. Although in some executions, it is observed that the browser has already started the initialization of the default Bluetooth adapter, when the test configures the mock adapter changing the adapter pointer, causing that the callbacks from the default adapter try to use an already released adapter pointer, thus reading from a nullptr, and crashing the test. Fix proposed: Move the MockBluetoothAdapter out from being configured at the specific test and instead be a class member and configured at test setup. By doing this the mock adapter is configured from the beginning avoiding the callback issue observed with the default Bluetooth adapter. Bug: 1087190 Change-Id: I3f2e8bd4159f072712f1082f05e35ec24f9b2f5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2220627 Commit-Queue: Carlos Frias <carlos.frias@microsoft.com> Reviewed-by:
Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#774406}
-
Max Li authored
This will now be enabled by default, but disabled on specific problematic boards. See go/tethering-client-expansion for details. Change-Id: Ia9988e3d6ad3b249f9a80d78b8f8607129218137 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2222296 Commit-Queue: Max Li <themaxli@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Cr-Commit-Position: refs/heads/master@{#774405}
-
