- 13 Nov, 2018 39 commits
-
-
Tarun Bansal authored
Change-Id: Ib7a70bf6d4921aafdd3786f7402f79547cee70de Bug: 903978 TBR: ryansturm@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/1330338Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Reviewed-by:
Doug Arnett <dougarnett@chromium.org> Commit-Queue: Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#607416}
-
Eric Aleshire authored
The type action allows for text to be typed into a field, enabling more autofill scenarios, and additionally enabling for password manager automation, which I am working on extending autofill automation to support. There are a great deal many more flows needed for password automation compared to autofill (i.e. save password on login, don't save password on login, update password on change, etc), and "save password" is just the first of them - but this change lays important groundwork by adding AX IDs to the confirm infobar so that automation can tap them. Change-Id: I5368fabfbc1a450341969b63936960dce2de6246 Reviewed-on: https://chromium-review.googlesource.com/c/1332008 Commit-Queue: ericale <ericale@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/master@{#607415}
-
Jared Saul authored
When a card has max strikes on desktop, instead of showing the offer-to-save bubble, only the omnibox icon is shown. This metric tracks these occurrences. Bug: 884817 Change-Id: I43f5cf0b1c9d6a3431790e8a2788bbf489fcdbe6 Reviewed-on: https://chromium-review.googlesource.com/c/1330898Reviewed-by:
Fabio Tirelo <ftirelo@chromium.org> Commit-Queue: Jared Saul <jsaul@google.com> Cr-Commit-Position: refs/heads/master@{#607414}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/85604c46..d5f26302 Please follow these instructions for assigning/CC'ing issues: https://github.com/v8/v8/wiki/Triaging%20issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I3514d813ee12fb0cbcec3ec005db1b73950e59da Reviewed-on: https://chromium-review.googlesource.com/c/1331575Reviewed-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@{#607413}
-
Koji Ishii authored
This patch impements inline fragmentation for BiDi. When BiDi reorder fragments an inline box; e.g., <span>T1 T2</span>T3 becomes after BiDi reorder: <span>T1</span> T3 <span>T2</span> this change creates two box fragments, one for T1 and another for T2. Unfortunately, one test starts failing: fast/css/css-properties-position-relative-as-parent-fixed.html In this test, when absolute/fixed positioned container is fragmented, the position becomes incorrect. As far as I checked, the fragment tree looks correct, so I suppose computing positioned objects get confused by multiple fragments for a LayoutObject within a line. Bug: 636993 Change-Id: Id1055e411e7cb59a8c8e731e5ad7c74b0c7fd246 Reviewed-on: https://chromium-review.googlesource.com/c/1323989 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Emil A Eklund <eae@chromium.org> Cr-Commit-Position: refs/heads/master@{#607412}
-
Sadrul Habib Chowdhury authored
BUG=894440 Change-Id: I0757af5f6a2058d0c98b68ff1e71c3083a1a76f2 Reviewed-on: https://chromium-review.googlesource.com/c/1332249 Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#607411}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/49e1239f94fe..fd1fd279a353 git log 49e1239f94fe..fd1fd279a353 --date=short --no-merges --format='%ad %ae %s' 2018-11-12 scroggo@google.com Remove unused exposedInAndroidJavaAPI 2018-11-12 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 635c9b33fe7c..1147fc2a5dac (1 commits) 2018-11-12 rmistry@google.com Remove usage of EnsureCQIncludeTrybotsAreAdded 2018-11-12 herb@google.com Move adding a glyph to a subRun from Run to SubRun 2018-11-12 reed@google.com New plan -- aa and lcd DO belong on SkFont 2018-11-12 herb@google.com Make SubRunInfo a subclass of GrTextBlob and rename to SubRun 2018-11-12 halcanary@google.com SkPDF: fix BUG:chromium:900562 2018-11-12 mtklein@google.com Revert "remove old name for SkCodec::kNoFrame" 2018-11-12 mtklein@google.com Revert "put kNone back too" 2018-11-12 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 50bf0429394d..48f63f90f6f3 (1 commits) Created with: gclient setdep -r src/third_party/skia@fd1fd279a353 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-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;master.tryserver.blink:linux_trusty_blink_rel TBR=rmistry@chromium.org Change-Id: I1826586602f3f80aed3014f4c315e6c70548bde7 Reviewed-on: https://chromium-review.googlesource.com/c/1332609Reviewed-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@{#607410}
-
Malay Keshav authored
This patch is a temporary fix to reduce the delay before occlusion tracker is unpaused after overview mode is dismissed. It is a temporary fix to load web contents immediately instead of waiting on the occlusion tracker for 5 seconds. Bug: 904617 Change-Id: Ib1d4957638965fd34ffa719c057d234a058d7e08 Component: Window selector controller Reviewed-on: https://chromium-review.googlesource.com/c/1332778Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Commit-Queue: Malay Keshav <malaykeshav@chromium.org> Cr-Commit-Position: refs/heads/master@{#607409}
-
Mike Wasserman authored
Use the ash::Shell aura::Env in single-process mash ui_devtools. Keep a TODO for initializing ui_devtools in Ash for multi-process Mash. Encapsulate server init, and the switch and port definitions. Bug: 896977 Test: ui_devtools works well on Chrome OS single-process Mash. Change-Id: I3cc285d5f8ee465d45795a3521e7e4eafa354414 Reviewed-on: https://chromium-review.googlesource.com/c/1324373 Commit-Queue: Michael Wasserman <msw@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#607408}
-
Shakti Sahu authored
Change-Id: I3acdd151cb7330eb62b9f8ba484aa47483fb6dee Reviewed-on: https://chromium-review.googlesource.com/c/1330750 Commit-Queue: Ilya Sherman <isherman@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Cr-Commit-Position: refs/heads/master@{#607407}
-
Ehsan Karamad authored
This API should not be public, because: 1- BrowserPluginGuest is internal to content. 2- The use cases are all within content/ - so it does not need to be in the WebContents interface. Bug: None Change-Id: Ia0206bb305e851742a7d71e64882c8fdf51a53b2 Reviewed-on: https://chromium-review.googlesource.com/c/1329302Reviewed-by:
Ehsan Karamad <ekaramad@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Commit-Queue: Ehsan Karamad <ekaramad@chromium.org> Cr-Commit-Position: refs/heads/master@{#607406}
-
Jacob Dufault authored
Bug: 898696 Change-Id: I0d9dd064a69cc54f8e983f0447a2388024bb5745 Reviewed-on: https://chromium-review.googlesource.com/c/1311127Reviewed-by:
Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Stefan Kuhne <skuhne@chromium.org> Commit-Queue: Jacob Dufault <jdufault@chromium.org> Cr-Commit-Position: refs/heads/master@{#607405}
-
Robert Ogden authored
time_before_main_frame_request_sent is the best estimate for the amount of time spent following redirects and any computational overhead in the browser. Bug: 902063 Change-Id: Ie958cf6b749d00cb2bb47d0d1a7d0434b04c3788 Reviewed-on: https://chromium-review.googlesource.com/c/1330687 Commit-Queue: Robert Ogden <robertogden@chromium.org> Reviewed-by:
Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Cr-Commit-Position: refs/heads/master@{#607404}
-
Ted Choc authored
BUG=898522 Change-Id: Ifd8c5748dd46e0a8417f9cd1bd80cf7f5a115965 Reviewed-on: https://chromium-review.googlesource.com/c/1330704 Commit-Queue: Ted Choc <tedchoc@chromium.org> Reviewed-by:
Pedro Amaral <amaralp@chromium.org> Cr-Commit-Position: refs/heads/master@{#607403}
-
Doug Arnett authored
This UMA will help us see a breakdown of actual ECT values for slow page previews that have a higher connection speed threshold. Bug: 895581 Change-Id: I0b976f5d03f91e2b626ed64aacd39b581b944a39 Reviewed-on: https://chromium-review.googlesource.com/c/1327235Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Doug Arnett <dougarnett@chromium.org> Cr-Commit-Position: refs/heads/master@{#607402}
-
Paul Meyer authored
Intent to ship: https://groups.google.com/a/chromium.org/forum/#!msg/blink-dev/ryK8SHcBzZw/2cjTF_OCBwAJ Bug: 898860 Change-Id: I25325827f7432dc141ae8cfe0d50e587a8f32664 Reviewed-on: https://chromium-review.googlesource.com/c/1320205 Commit-Queue: Avi Drissman <avi@chromium.org> Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Rick Byers <rbyers@chromium.org> Cr-Commit-Position: refs/heads/master@{#607401}
-
Zhuoyu Qian authored
Move: build/scripts/{ => core/style}/make_computed_style_base.py build/scripts/{ => core/style}/templates/computed_style_base.h.tmpl build/scripts/{ => core/style}/templates/computed_style_base.cc.tmpl build/scripts/{ => core/style}/templates/computed_style_base_constants.h.tmpl core/{css => style}/computed_style_diff_functions.json5 core/{css => style}/computed_style_extra_fields.json5 This CL has no behavior changes. Bug: 732657 Change-Id: Ic984e33c0b1815e99e6c5fb24dfdfba54fafc1dd Reviewed-on: https://chromium-review.googlesource.com/c/1331106Reviewed-by:Kent Tamura <tkent@chromium.org> Commit-Queue: Zhuoyu Qian <zhuoyu.qian@samsung.com> Cr-Commit-Position: refs/heads/master@{#607400}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/ddbeac1c06a9..332c9ff5a98e git log ddbeac1c06a9..332c9ff5a98e --date=short --no-merges --format='%ad %ae %s' 2018-11-12 iannucci@chromium.org [led] Roll led to pick up new kitchen CLI args. Created with: gclient setdep -r src/third_party/depot_tools@332c9ff5a98e The AutoRoll server is located here: https://autoroll.skia.org/r/depot-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. BUG=chromium:904478 TBR=agable@chromium.org Change-Id: I9ff7281e1b3c956dfa0f0c705b0b429545ce0714 Reviewed-on: https://chromium-review.googlesource.com/c/1331808Reviewed-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@{#607399}
-
Gabriel Charette authored
R=etienneb@chromium.org, oysteine@chromium.org Bug: 899897 Change-Id: I3fc881493ee2934ae15b43f4cb3089d98e460fcb Reviewed-on: https://chromium-review.googlesource.com/c/1321189Reviewed-by:
Etienne Bergeron <etienneb@chromium.org> Reviewed-by:
oysteine <oysteine@chromium.org> Commit-Queue: Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#607398}
-
manuk authored
Bug: 891303 Change-Id: Ic5ad4fc57347db7632ba753eafe67eb37281061f Reviewed-on: https://chromium-review.googlesource.com/c/1330281Reviewed-by:
Tommy Li <tommycli@chromium.org> Commit-Queue: manuk hovanesian <manukh@chromium.org> Cr-Commit-Position: refs/heads/master@{#607397}
-
Kurt Horimoto authored
This CL updates BVC's SnapshotGeneratorDelegate implementation such that the insets returned by |-snapshotEdgeInsetsForWebState:| are in the coordinate system of the view returned by |-viewForWebState:|. This CL also updates the WebState::TakeSnapshot() to convert the rect parameter to the coordinate system of the WKWebView before snapshotting. Bug: 898227 Change-Id: Ic6edb8ee50c182f738e20fc7f6c84174fffee01a Reviewed-on: https://chromium-review.googlesource.com/c/1331584 Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Reviewed-by:
edchin <edchin@chromium.org> Cr-Commit-Position: refs/heads/master@{#607396}
-
chromium-autoroll authored
The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast TBR=cr-fuchsia+bot@chromium.org Change-Id: I4e5c96a85d0f2d2fbd3128fa45e23d44e3241450 Reviewed-on: https://chromium-review.googlesource.com/c/1332827Reviewed-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@{#607395}
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. The AutoRoll server is located here: https://autoroll.skia.org/r/afdo-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=gbiv@chromium.org Change-Id: I99aaf539ac5fcf25402e62266d2eb97328ab4550 Reviewed-on: https://chromium-review.googlesource.com/c/1332808Reviewed-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@{#607394}
-
Lily Chen authored
This reverts commit 668af6e3. Reason for revert: Bug in RespectLimits where a ConnectJob with the IGNORE_LIMITS flag set is associated with a Request that does not have that flag set. Original change's description: > Add reprioritization to TransportConnectJobs > > This change makes it possible to reprioritize socket pool ConnectJobs > to match their corresponding Requests. For TransportConnectJobs that are > reprioritized while undergoing host resolution, the corresponding host > resolver request is also reprioritized to match the connect job. > > Bug: 166689 > Change-Id: Icaed423c6f363fa15e9e379aa135a3b98330d1a1 > Reviewed-on: https://chromium-review.googlesource.com/c/1320210 > Commit-Queue: Lily Chen <chlily@chromium.org> > Reviewed-by: Matt Menke <mmenke@chromium.org> > Cr-Commit-Position: refs/heads/master@{#606129} TBR=mmenke@chromium.org,chlily@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 166689 Change-Id: I02f58f99a9391871962b0c96df643e2a85403330 Reviewed-on: https://chromium-review.googlesource.com/c/1331141Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#607393}
-
Nektarios Paisios authored
Handles list markers (including NG) when finding the containing DOM node of an AXLayoutObject that has no associated node We need to have a generic function that given an AXLayoutObject will return either the associate DOM Node, or if the layout object has no node attached, the containing DOM node. This functionality is required in cases such as the following: 1. An accessibility selection has one of its endpoints at a list marker and the user asks us to select the closest DOM selection possible. We need to move the endpoint that is on the list marker to an object that has a DOM node attached, e.g. the containing DOM node of the AXLayoutObject representing the list marker. 2. A user wants to know if a layout object is editable. We need to find if the attached or containing block node is editable. R=aboxhall@chromium.org, dmazzoni@chromium.org Change-Id: I4572b7b024f61518b7da61a61e6916c623d4d3dc Bug: 639340 Reviewed-on: https://chromium-review.googlesource.com/c/1331131 Commit-Queue: Nektarios Paisios <nektar@chromium.org> Reviewed-by:
Dominic Mazzoni <dmazzoni@chromium.org> Reviewed-by:
Aaron Leventhal <aleventhal@chromium.org> Cr-Commit-Position: refs/heads/master@{#607392}
-
Alex Newcomer authored
When the tablet mode transition was added to Apps.AppListShowSource, the enum was not updated. Just add a third enum entry. Bug: 904131 Change-Id: Icaee0f359b42621381c19f8d5cfe9a62ef2cd51d Reviewed-on: https://chromium-review.googlesource.com/c/1331034Reviewed-by:
Alex Newcomer <newcomer@chromium.org> Reviewed-by:
Weidong Guo <weidongg@chromium.org> Commit-Queue: Alex Newcomer <newcomer@chromium.org> Cr-Commit-Position: refs/heads/master@{#607391}
-
Alexis Hetu authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/4169b31..1147fc2 BUG= TBR=kbr@chromium.org TEST=bots 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 Change-Id: I793c8f0c4613fc7080991c082b6e8190765f7f25 Reviewed-on: https://chromium-review.googlesource.com/c/1331947Reviewed-by:
Alexis Hétu <sugoi@chromium.org> Commit-Queue: Alexis Hétu <sugoi@chromium.org> Cr-Commit-Position: refs/heads/master@{#607390}
-
siyua authored
Uploaded screenshots in the bug (comment#16) Bug: 897998 Change-Id: I83aaf75efaf49ed2adda3a4773aacdc10caedb32 Reviewed-on: https://chromium-review.googlesource.com/c/1330756Reviewed-by:
Sebastien Seguin-Gagnon <sebsg@chromium.org> Commit-Queue: Siyu An <siyua@chromium.org> Cr-Commit-Position: refs/heads/master@{#607389}
-
David Black authored
Previously the URLs for Assistant Settings/Reminders were not asserted, only their presence was checked. That is now fixed. Also added a helper method for creating a localized GURL. Bug: b:119280255 Change-Id: Id01594919940fc96f90892d6adbc91ebf7e1cd29 Reviewed-on: https://chromium-review.googlesource.com/c/1328221 Commit-Queue: David Black <dmblack@google.com> Reviewed-by:
Xiaohui Chen <xiaohuic@chromium.org> Cr-Commit-Position: refs/heads/master@{#607388}
-
Ahmed Fakhry authored
Temporarily disable Feedback in the login screen until we're able to delete the signin profile once logged in. See more details on the bug. BUG=899092 Change-Id: Ib1045d3e460ab39391e2da8dd9cbb5afea056ace Reviewed-on: https://chromium-review.googlesource.com/c/1332264 Commit-Queue: Ahmed Fakhry <afakhry@chromium.org> Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Cr-Commit-Position: refs/heads/master@{#607387}
-
Eugene But authored
Now SadTabCoordinator will be used instead SadTabLegacyCoordinator for SadTab UI presentation. SadTabLegacyCoordinator does not use view controller and presents SadTab UI with WebState::ShowTransientView, which is misuse of WebState API. SadTabCoordinator is disabled by default and can be enabled via kPresentSadTabInViewController feature flag. Bug: 901563 Change-Id: I34dd6ae99255e5fe0b3ef100265c78169d619a50 Reviewed-on: https://chromium-review.googlesource.com/c/1329924 Commit-Queue: Eugene But <eugenebut@chromium.org> Commit-Queue: Kurt Horimoto <kkhorimoto@chromium.org> Reviewed-by:
Kurt Horimoto <kkhorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#607386}
-
David Roger authored
Remove whitespace at end of lines. Vertically align the columns. Change-Id: I6dbcb667c82c58f26a25c0d07d3ba3eeb8f2ad12 Reviewed-on: https://chromium-review.googlesource.com/c/1331390Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Commit-Queue: David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#607385}
-
Philip Rogers authored
This patch fixes a typo where kTouchStartOrMoveEventBlocking was used instead of kTouchStartOrMoveEventBlockingLowLatency. Change-Id: I33e739c95755514517b4107b0f4fc662ffdcb4ac Reviewed-on: https://chromium-review.googlesource.com/c/1332388Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Commit-Queue: Philip Rogers <pdr@chromium.org> Cr-Commit-Position: refs/heads/master@{#607384}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/cb830a07e835..7f1ac04ec34e git log cb830a07e835..7f1ac04ec34e --date=short --no-merges --format='%ad %ae %s' 2018-11-12 shapiroc@chromium.org chromite: Make most release hwtests async Created with: gclient setdep -r src/third_party/chromite@7f1ac04ec34e 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. TBR=chrome-os-gardeners@chromium.org Change-Id: Icc47bba8ac063c5d52866a6cb4a7913b303c308b Reviewed-on: https://chromium-review.googlesource.com/c/1331582Reviewed-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@{#607383}
-
Wenzhao Zang authored
Bug: None Change-Id: Iea33829fefcc53f868d0021e1e9b3786b2285329 Reviewed-on: https://chromium-review.googlesource.com/c/1332416Reviewed-by:
Jacob Dufault <jdufault@chromium.org> Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org> Cr-Commit-Position: refs/heads/master@{#607382}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/b6521150ae99..6374fa323c0e Created with: gclient setdep -r src-internal@6374fa323c0e 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. TBR=mmoss@chromium.org Change-Id: I1c86d93caa52dbf400a7a27114312cd83c0e8cd2 Reviewed-on: https://chromium-review.googlesource.com/c/1332348Reviewed-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@{#607381}
-
Olivier Robin authored
Chrome iOS stopped supporting ios10. Bug: 904393 Change-Id: I89e9cfe5cc27e8ef94feb5e8b404e1fc8d8264d7 Reviewed-on: https://chromium-review.googlesource.com/c/1329968 Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Reviewed-by:
Patrik Höglund <phoglund@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#607380}
-
Charlie Harrison authored
There was way too much nesting in ContentSettingBlockedImageModel. This CL tries to tease apart some of the logic, and reduce nesting via early-return pattern. Bug: None Change-Id: Ida0acf144bf4b6d1217541feb7b7e304e89fc12c Reviewed-on: https://chromium-review.googlesource.com/c/1330346 Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by:
Raymes Khoury <raymes@chromium.org> Cr-Commit-Position: refs/heads/master@{#607379}
-
Justin Cohen authored
This test is getting close to 30 minutes. There are 6 test cases, so sharding it to 2 tests cases per will use 3 machines, and bring test runs closer to ten minutes. This also renames the test cases to end in TestCase, which is how sharding does it's math. Change-Id: I7c4f58e89534b1d526fbfc026cbecb76c61a745e Reviewed-on: https://chromium-review.googlesource.com/c/1331130Reviewed-by:
John Budorick <jbudorick@chromium.org> Reviewed-by:
edchin <edchin@chromium.org> Reviewed-by:
Sergio Collazos <sczs@chromium.org> Commit-Queue: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#607378}
-
- 12 Nov, 2018 1 commit
-
-
Maggie Chen authored
The histogram GPU.GPUProcessSoftwareRendering recorded in GpuProcessHost::LaunchGpuProcess() does not have a correct software rendering status. GpuInit::InitializeAndStartSandbox() is where we check if we are doing software rendering. A new histogram GPU.GLImplementation is added to record all GL modes. If the GPU.GLImplementation mode is kGLImplementationSwiftShaderGL, the GPU process is running with software rendering. Bug:899361 Change-Id: Ie2ef9b84c4055a2407128c3f4f27fbd802445485 Reviewed-on: https://chromium-review.googlesource.com/c/1317923Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Reviewed-by:
Kenneth Russell <kbr@chromium.org> Reviewed-by:
kylechar <kylechar@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Reviewed-by:
Alexis Hétu <sugoi@chromium.org> Commit-Queue: Maggie Chen <magchen@chromium.org> Cr-Commit-Position: refs/heads/master@{#607377}
-