- 30 Oct, 2019 40 commits
-
-
Jasper Chapman-Black authored
Thanks to earlier refactoring work, this is super easy! Bug: 1011921 Change-Id: I67e8f68ef0b87092c36e1176b3e8d033e8597db7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891133 Commit-Queue: Jasper Chapman-Black <jaspercb@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#710981}
-
Xiaohan Wang authored
The MockCdmFactory just creates the MockCdm and should not expect what calls will be made on the MockCdm. Hence, replace StrictMock with NiceMock. Test cases that expect calls on MockCdm should get the MockCdm via MockCdmFactory::GetCreatedCdm() and explicitly specify expectations using EXPECT_CALL. This is also consistent with googlemock guidelines [1]: """ Our general recommendation is to use nice mocks (not yet the default) most of the time, use naggy mocks (the current default) when developing or debugging tests, and use strict mocks only as the last resort. """ [1] https://github.com/google/googletest/blob/master/googlemock/docs/cook_book.md#the-nice-the-strict-and-the-naggy-nicestrictnaggy Bug: 1018854 Test: Update test helper classes. No functionality change. Change-Id: I197f83b221296beccd05b82d2b6ae030381178e8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890970 Commit-Queue: Xiaohan Wang <xhwang@chromium.org> Reviewed-by:
John Rummell <jrummell@chromium.org> Cr-Commit-Position: refs/heads/master@{#710980}
-
dpapad authored
Fixed: 1019798 Change-Id: Idfd2502fa32dfa44ad19b105f5d4bc9a54eb15e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891147Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org> Cr-Commit-Position: refs/heads/master@{#710979}
-
Alexander Gaponov authored
Currently, there is no way to set expectetions on SetDelegate function Replaces with MOCK_METHOD1 and moving current function body to ON_CALL().WillByDefault() Bug: internal b/132811177 Change-Id: I58ba51d5a0d3dcead895045009de2821271ccfd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885453Reviewed-by:
Kenneth MacKay <kmackay@chromium.org> Reviewed-by:
Luke Halliwell (slow) <halliwell@chromium.org> Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Commit-Queue: Steven Zhu <jz@chromium.org> Cr-Commit-Position: refs/heads/master@{#710978}
-
Natalie Chouinard authored
Migrate Supervised User preferences to use PrefServiceBridge generic methods, making use of the prefs.h enums. Replace duplicated Java constants for SupervisedUserURLFilter:: FilteringBehavior C++ enum with a generated Java enum. Bug: 1016957 Change-Id: Id0eb0b19464fb6bc487cb7924b68de6f753fba60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885505 Commit-Queue: Natalie Chouinard <chouinard@chromium.org> Reviewed-by:
Aga Wronska <agawronska@chromium.org> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Brandon Wylie <wylieb@chromium.org> Cr-Commit-Position: refs/heads/master@{#710977}
-
Toni Barzic authored
Currently, OnOverviewModeWillStart is called both before and after ending any pending overview exit animations - we should call this only once, after existing animations have ended. Bug: None Change-Id: I87997a79693de59dbafb572d99799a4c3bb42513 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891390Reviewed-by:
Sammie Quon <sammiequon@chromium.org> Commit-Queue: Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#710976}
-
Hiroshige Hayashizaki authored
This CL moves `test_case_name` and `test_js` into test HTML templates, - To merge code from indiviual projects into common/, and - To prepare for merging multiple scenarios into a single HTML file. This CL keeps generated test files unchanged. Bug: 906850 Change-Id: Iad2dd874492b8824f4c97d76a78b09bf8e2ab94f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889476 Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#710975}
-
Dana Fried authored
ThumbnailTabHelper now captures the entire contents of a web page (within the bounds of the window) as the raw thumbnail instead of an image specifically cropped for tab hover cards. The image is scaled down to a size that can be used by both the touch- only tabstrip and hover cards, even when it must be cropped. Observers can now specify a size hint for uncompressed images; so that when the image is received by the observer it is pre-cropped appropriately. We use this new system to ensure that tab hover cards are still getting appropriately-sized thumbnails, but the touch-only tabstrip gets the entire compressed image of the webpage, at approximately the original aspect ratio. Bug: 1013646 Change-Id: If63dc7e13f8ddef09e991fcb20f5bef8cacad302 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1887734 Commit-Queue: Dana Fried <dfried@chromium.org> Reviewed-by:
Collin Baker <collinbaker@chromium.org> Cr-Commit-Position: refs/heads/master@{#710974}
-
Natalie Chouinard authored
Explicitly show soft input keypboard on omnibox focus for search. Fixes an issue with Duet, where the keyboard could be dismissed by the Back or keyboard Action buttons, after which re-clicking the Search button would focus the omnibox, but would not re-open the keyboard by default. Bug: 981682 Change-Id: I1fe14edae4493dd57afe79250ad7fdbc806adcc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869530Reviewed-by:
Ender <ender@google.com> Reviewed-by:
Theresa <twellington@chromium.org> Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Natalie Chouinard <chouinard@chromium.org> Cr-Commit-Position: refs/heads/master@{#710973}
-
Chromium WPT Sync authored
Using wpt-import in Chromium b29385ff. With Chromium commits locally applied on WPT: 1d5b803f "Add WebVTT support for inline styling - Web Platform Tests" 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: creis@chromium.org, lukasza@chromium.org: external/wpt/fetch/corb foolip@chromium.org, lpz@chromium.org, robertma@chromium.org: external/wpt/tools yhirano@chromium.org, mkwst@chromium.org, japhet@chromium.org: external/wpt/fetch NOAUTOREVERT=true TBR=raphael.kubo.da.costa No-Export: true Change-Id: I355970b520a49141c9fc9ca40353ad7fb3f1ac5b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891071Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#710972}
-
Natalie Chouinard authored
Migrate Password Manager preferences to use PrefServiceBridge generic methods, making use of the prefs.h enums. Bug: 1016957 Change-Id: If35d6e14448dff0883bb66e836f67dbe631ae0f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885502Reviewed-by:
Ganggui Tang <gogerald@chromium.org> Commit-Queue: Natalie Chouinard <chouinard@chromium.org> Cr-Commit-Position: refs/heads/master@{#710971}
-
Vladimir Levin authored
This patch updates the code to simplify the if condition. This should a no-op change since the override is considered when getting the intrinsic content logical height. This also adds a test that fails if that if condition is not present, and passes otherwise. The test sizes the flex box based on the unstretched size when the item itself is stretched. R=cbiesinger@chromium.org, chrishtr@chromium.org Bug: 1018395 Change-Id: I16ff62d887110a9b93704160e93f2fbcc764c509 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891012Reviewed-by:
Christian Biesinger <cbiesinger@chromium.org> Commit-Queue: vmpstr <vmpstr@chromium.org> Cr-Commit-Position: refs/heads/master@{#710970}
-
Connie Wan authored
Includes a refactor of TabDragController and TabDragContext to allow dragging of TabSlotViews and not just Tabs. This required renaming many things, but thankfully not many functionality changes. Notable functionality changes: - in tab_strip: Logic is added in MaybeStartDrag() to handle selecting which views to drag. - in tab_strip: Logic is added in GetInsertionIndexFrom() for finding the right insertion index. - in tab_drag_controller: Logic is added in Attach() for dragging headers into new windows. - in tab_drag_controller: Logic is added in CompleteDrag() to deselect the dragged views. - in tab_drag_controller: Gates are added to prevent calling UpdateGroupForDraggedTabs(). Bug: 1004953 Change-Id: Ia334e5c424f9fbba704160239b19e4ca9f13eb9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1866058Reviewed-by:
James Cook <jamescook@chromium.org> Reviewed-by:
Taylor Bergquist <tbergquist@chromium.org> Reviewed-by:
Charlene Yan <cyan@chromium.org> Commit-Queue: Connie Wan <connily@chromium.org> Cr-Commit-Position: refs/heads/master@{#710969}
-
Josh Nohle authored
See analogous change to the device notifier at crrev/c/1888734/2..3. Bug: 951969 Change-Id: I771130dc97718c24b2ea5292086fd80e89ec45ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890001 Auto-Submit: Josh Nohle <nohle@chromium.org> Commit-Queue: Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#710968}
-
Henry Jian authored
Previously, new splash webapks were not masking adaptive icon when it was used in splash screen. This CL fixes that. Bug: 977173 Change-Id: I6a38aec93369d6d7fda4fbba38f483c25b9b5960 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891138Reviewed-by:
Peter Kotwicz <pkotwicz@chromium.org> Commit-Queue: Henry Jian <hzjian@google.com> Cr-Commit-Position: refs/heads/master@{#710967}
-
Josh Nohle authored
The Instance ID is the primary identifier for devices using v2 DeviceSync. This ID is not present in v1 DeviceSync, which used the device public key as the primary ID. The device public key is encrypted in v2 DeviceSync and might not be available during multi-device setup. Bug: 951969 Change-Id: I09c1ebd6016d651deabb7eca6356581c3c69c0fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1882300 Commit-Queue: Josh Nohle <nohle@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Ryan Hansberry <hansberry@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#710966}
-
Brian Sheedy authored
Causes try-nougat-phone-tester, android-oreo-arm64-dbg, and android-pie-arm64-dbg to trigger on CLs that touch VR files since they run VR and AR tests that aren't handled by the Nexus 5Xs. Change-Id: I52599ba5c85a0066afd1e73f391d529f4ba8a06b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889170 Commit-Queue: Brian Sheedy <bsheedy@chromium.org> Reviewed-by:
Ben Pastene <bpastene@chromium.org> Cr-Commit-Position: refs/heads/master@{#710965}
-
Tobias Sargeant authored
If an AIDL file changes (comment and whitespace changes are ignored) then assert that the API version number is incremented by 1. Change-Id: Id7f3a17f9ab2244946d0cf12d7f0af48187172ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1879462 Commit-Queue: Tobias Sargeant <tobiasjs@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Cr-Commit-Position: refs/heads/master@{#710964}
-
Kevin Bailey authored
We had a complicated test to see where to put the cursor, but it turns out that it was unnecessary, and wrong in one case. This CL restores its behavior. Bug: 1019631 Change-Id: I18ed14d12dc55b3ac63c76eb4ed62e3f5624e8df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889999 Commit-Queue: Kevin Bailey <krb@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#710963}
-
dalyk authored
Bug: 10161646 Change-Id: I66061df5533dc00e8c07e354098f6735f366a3c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1870492 Commit-Queue: Katharine Daly <dalyk@google.com> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#710962}
-
Brian Geffon authored
Adding features for ram_vs_swap_weight and extra_free kernel tunables. BUG=chromium:1019806 TESTED=Validated on an octopus device Change-Id: I681e09ba7cae3deeab69a8833fa068ed09f9eaf7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890792Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Commit-Queue: Brian Geffon <bgeffon@chromium.org> Cr-Commit-Position: refs/heads/master@{#710961}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/61cd76748f7c..56981910bb85 git log 61cd76748f7c..56981910bb85 --date=short --no-merges --format='%ad %ae %s' 2019-10-30 rharrison@google.com Rolling 5 dependencies & expectation files (#849) Created with: gclient setdep -r src/third_party/shaderc/src@56981910bb85 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/shaderc-chromium-autoroll Please CC radial-bots+chrome-roll@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/+/master/autoroll/README.md TBR=radial-bots+chrome-roll@google.com Bug: None Change-Id: I261dd92770ed64850d503a9d5655c9fa7f8f1cac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890845Reviewed-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@{#710960}
-
Yulun Wu authored
This is a reland of f2baca71 Original change's description: > Menu Model: fix bug where menu item title was greyed out because it is disabled. > > The old approach of adding title as a disabled item meant that this CL: > > https://chromium-review.googlesource.com/c/chromium/src/+/1788198 > > causes the menu title to be displayed in grey text instead of solid black text. This CL introduces a new menu type that, while still disabled and non-reactive, be displayed in solid black text. > > Bug: 1006203 > Change-Id: I9fa38132160228ebde5bd43d8db9c2f60d5f001c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841583 > Reviewed-by: Scott Violet <sky@chromium.org> > Reviewed-by: Toni Baržić <tbarzic@chromium.org> > Commit-Queue: Yulun Wu <yulunwu@chromium.org> > Auto-Submit: Yulun Wu <yulunwu@chromium.org> > Cr-Commit-Position: refs/heads/master@{#707147} Bug: 1006203 Change-Id: I02ac38b96dea074f8e9c3e8c9a019a53db512513 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1869475 Commit-Queue: Yulun Wu <yulunwu@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#710959}
-
John Chen authored
NOTRY=true TBR=crouleau@chromium.org Bug: 1017244 Change-Id: Ib9c806e675cfe6727cf3e78a36af866b0f6bf2ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891451Reviewed-by:
John Chen <johnchen@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#710958}
-
Mason Freed authored
Prior to this CL, a site could access the thumb of a range input and apply a 3D transform to it: input::-webkit-slider-thumb { transform: translateZ(20px); } That would previously cause a crash, as the code did not expect such a transform. This should work now. Fixed: 1018774 Change-Id: I8ccbbd532129752dd4e76fde4da064041e32a146 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890499Reviewed-by:
Xianzhu Wang <wangxianzhu@chromium.org> Commit-Queue: Mason Freed <masonfreed@chromium.org> Auto-Submit: Mason Freed <masonfreed@chromium.org> Cr-Commit-Position: refs/heads/master@{#710957}
-
Avery Musbach authored
When you are dragging a window to snap in a position for which the divider is not conducive to the window's minimum size, the snap preview shall be adjusted. Test: ash_unittests SplitViewOverviewSession*Test.SnappedWindowBoundsWithMinimumSizeTest/? Bug: 1017464 Change-Id: Iae51058747addd1f994dde62f2baeb123aae3621 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1880201 Commit-Queue: Avery Musbach <amusbach@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#710956}
-
Michael Spang authored
The default configuration of TestScreen is to create one display and one WindowTreeHost with the same size. X11 is now incompatible with this requirement as of b14e13fd ("Reland "X11 and Ozone: DWTHPlatform handles Show/Hide/Max/Restore/Full""). Several aura tests are only passing currently due to another bug in DisplayList::UpdateDisplay, which prevents X11Window from seeing the current display size and enforcing the constraint. Other tests only work because TestScreen resizes the display to match the WindowTreeHost /after/ X11Window deletes the last row and column. i.e., X11Window tries to adjust the size to not match the display, and then TestScreen re-adjusts the display to match the window. This behavior is not convergent and causes small changes in initialization order to affect the dimensions of test windows. This hack should likely be removed altogether and the bug it's addressing fixed another way, but for now disable it in the test harness because it is blocking other changes such as a fix for the UpdateDisplay bug noted above. Bug: 1019015 Change-Id: I79e830b9c35df3df29dc8af50ac424076682d180 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1889294 Commit-Queue: Michael Spang <spang@chromium.org> Reviewed-by:
Michael Spang <spang@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/master@{#710955}
-
Mario Sanchez Prada authored
Convert the remaining bits referencing the video_capture::mojom::Device mojo interface using the old APIs to the new mojo types. Bug: 955171 Change-Id: Ieafd706caa4d9454fc308f10cd109139376253e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1879260 Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Cr-Commit-Position: refs/heads/master@{#710954}
-
Toni Barzic authored
Updates how device transitions to home when home button is tapped and when user clicks in empty space in overview grid when kHomerviewGesture feature is enabled. When overview is active, it should use kFadeOutExit transition (instead of slide out) - this also fixes a bug where transform was not cleared on item windows when bounds were updated without animations (which was causing item window misplacement when the grid was updated while minimizing active window before exiting overview). FadeOutWindowsAndMaybeSlideOnExit is updated to take "slide" as an argument instead of deducing it depending on the animation type, as OVERVIEW_ANIMATION_EXIT_TO_HOME_LAUNCHER should slide if and only if using slide out overview exit transition (the animation can also be used by fade out exit). When clicking home with a window active, the top window is minimized using transform to home screen (the same used during drag from shelf), while the rest of the windows are minimized with no animations. To make this easier, WindowTransformToHomeScreenAnimation is moved to a separate file, and is updated to better handle windows whose origin is not in the screen origin (which is useful for transforming top windows in split view). Is split view, the top windows are transformed to home screen as the split view ends. If overview session is active together with split view, the overview session is ended immediately to avoid showing overview just after ending split view (during duration of the exit transition). BUG=1005366 Change-Id: Ic23893866700f5e5580f4445915d815f188e8c0f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885972 Commit-Queue: Toni Baržić <tbarzic@chromium.org> Reviewed-by:
Xiaoqian Dai <xdai@chromium.org> Reviewed-by:
Xiyuan Xia <xiyuan@chromium.org> Cr-Commit-Position: refs/heads/master@{#710953}
-
sczs authored
Bug: 961343, 1019807 Change-Id: If56d88f4f2548b21fd341a4b2ca8f0bb6a1ea504 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1887431 Commit-Queue: Sergio Collazos <sczs@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Chris Lu <thegreenfrog@chromium.org> Reviewed-by:
Peter Lee <pkl@chromium.org> Cr-Commit-Position: refs/heads/master@{#710952}
-
Wenyu Fu authored
Part of the origin CL (1867431), adding MoreProgressButton class. It can be displayed as a button associated with a runnable, or a process spinner when executing the associated action. Bug: 1001286 Change-Id: I0ad5662690b193597f928de474f9cd303447c89b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1880369Reviewed-by:
Theresa <twellington@chromium.org> Commit-Queue: Wenyu Fu <wenyufu@chromium.org> Cr-Commit-Position: refs/heads/master@{#710951}
-
chromium-autoroll authored
https://chromium.googlesource.com/catapult.git/+log/9fae76312a94..4d322b9e167e git log 9fae76312a94..4d322b9e167e --date=short --no-merges --format='%ad %ae %s' 2019-10-30 dproy@chromium.org Print chrome debug logs Created with: gclient setdep -r src/third_party/catapult@4d322b9e167e 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 zhanliang@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/+/master/autoroll/README.md 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=zhanliang@google.com Bug: chromium:1015942 Change-Id: I2acb5a1526321d778959b306e9d31ad48983bac5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890841Reviewed-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@{#710950}
-
Yuke Liao authored
The coverage builder doesn't run fuzzers anymore, and the corpus has been turned down, therefore, this CL removes the dependency between libfuzzer and the fuzzer corpus. Bug: 990387 Change-Id: I07cbec6629903aa3f2f5b53d3e7692a1e65acca3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1891010Reviewed-by:
Max Moroz <mmoroz@chromium.org> Commit-Queue: Yuke Liao <liaoyuke@chromium.org> Cr-Commit-Position: refs/heads/master@{#710949}
-
shrekshao authored
https://chromium.googlesource.com/external/khronosgroup/webgl.git/+log/2701c13..dd55f3c TBR=kbr@chromium.org Bug: 455150, angleproject:4049, 776222, 891861, 890539 Cq-Include-Trybots: luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64 Change-Id: I184a1a5fb3572f52cb5ac380dbd3a6fa3c981cca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890983Reviewed-by:
Shrek Shao <shrekshao@google.com> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Commit-Queue: Shrek Shao <shrekshao@google.com> Cr-Commit-Position: refs/heads/master@{#710948}
-
Archana Simha authored
Move regular image to chrome/browser/resources/extensions Design Doc: go/extensionscheckup Bug: 1019296 Change-Id: Ic66c31a71751f2ea944ef9ee82e11617126ce418 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1877187 Commit-Queue: Archana Simha <archanasimha@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Reviewed-by:
Samuel Huang <huangs@chromium.org> Cr-Commit-Position: refs/heads/master@{#710947}
-
Stephen Roe authored
The tools are the Fuchsia SDK host tools, qemu, and the llvm-symbolizer. The paths to the tool locations are located in common.py. The x64 tools are used on linux-x64 test build and test run hosts. The arm64 tools are used on linux-arm64 test run hosts. qemu-kvm requires somewhat different arguments for arm64 than x64. For arm64: "-machine virt,gic_version=3" instead of "-machine virt" "-cpu host" instead of "-cpu host,migratable=no" Bug: 1000901 Change-Id: I5fa7fba7a7d556ed08d602fc864daa47c07b545a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1885220Reviewed-by:
Kevin Marshall <kmarshall@chromium.org> Commit-Queue: Stephen Roe <steveroe@google.com> Cr-Commit-Position: refs/heads/master@{#710946}
-
Bailey Berro authored
Also add some comments to describe the various sections Bug: none Change-Id: Ifbe892363fc4f6dfdaa730ce6058752540d94a51 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1880577Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Commit-Queue: Bailey Berro <baileyberro@chromium.org> Cr-Commit-Position: refs/heads/master@{#710945}
-
Yulun Wu authored
Bug: 996006 Change-Id: I2d819b32177ad10da1ad07b5f266a25f4f25d200 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762936 Commit-Queue: Yulun Wu <yulunwu@chromium.org> Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Alexander Alekseev <alemate@chromium.org> Reviewed-by:
Manu Cornet <manucornet@chromium.org> Reviewed-by:
Toni Baržić <tbarzic@chromium.org> Cr-Commit-Position: refs/heads/master@{#710944}
-
Kevin Marshall authored
The MIME sniffing code used by the Content Directory loading system has DCHECKs which prevent it from reading the contents of files larger than 1MB. Sniffing is now limited to the first 10KB of the file. Bug: 1018436 Change-Id: I0b6293ef08ebe7cd2bab30fb57ffd481819cf85e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1879684 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by:
David Dorwin <ddorwin@chromium.org> Cr-Commit-Position: refs/heads/master@{#710943}
-
Junyi Xiao authored
Now this CL: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/1874670 has landed, fix the test and re-enable it. Bug: 842488 Change-Id: Ie436c7574de32e387db74697d2d205e296c4af09 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890498Reviewed-by:
Lorne Mitchell <lomitch@microsoft.com> Commit-Queue: Junyi Xiao <juxiao@microsoft.com> Cr-Commit-Position: refs/heads/master@{#710942}
-