- 16 Apr, 2020 40 commits
-
-
Rainhard Findling authored
* This is done as preparation for a subsequent refactoring of the safety check WebUi code. It moves the source of truth for the safety check parent status from the JS side to the C++ side. This removes some of the interdependencies of parent to children (and vice versa), and allows for a subsequent splitting of parent and children into individual parts on the WebUi side. * This CL is part 1 of the change, which adds logic to handle the parent state in C++ and the communication from C++ to JS. Bug: 1015841 Change-Id: I3716457964377ae3177884d5987281fd2c470a2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144022Reviewed-by:
Esmael Elmoslimany <aee@chromium.org> Commit-Queue: Rainhard Findling <rainhard@chromium.org> Cr-Commit-Position: refs/heads/master@{#759692}
-
Nodir Turakulov authored
Move resultdb enablement from CI to all builders. Change-Id: I8e9f3d068bcdf0c00aac2e6050940d6b249a3db9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151181Reviewed-by:
Roberto Carrillo <robertocn@chromium.org> Reviewed-by:
Garrett Beaty <gbeaty@chromium.org> Commit-Queue: Nodir Turakulov <nodir@chromium.org> Cr-Commit-Position: refs/heads/master@{#759691}
-
Colin Blundell authored
Following the pattern of //chrome, we will need to add a new world ID for translate, and the new ID will need to be accessible from the renderer. Bug: 1025620 Change-Id: I8154436d61e35a764f79348ac0ca55e641097989 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152373 Commit-Queue: Colin Blundell <blundell@chromium.org> Commit-Queue: Clark DuVall <cduvall@chromium.org> Auto-Submit: Colin Blundell <blundell@chromium.org> Reviewed-by:
Clark DuVall <cduvall@chromium.org> Cr-Commit-Position: refs/heads/master@{#759690}
-
Mark Yacoub authored
This reverts commit 0e18fd2d. Reason for revert: Atomic modesetting fails on puff for MST HDMI after boot Original change's description: > Reland "Ozone: Implement Atomic Modeset" > > If the device supports KMS Atomic APIs, Enable CRTC using Atomic Modeset > Commit instead of legacy SetCRTC. > > (reverted on crrev.com/c/2080775) > > BUG=987274 > TEST=displays should start and continue to function normally for devices > supporting atomic APIs. > HardwareDisplayControllerTest.CheckModesettingSetsProps > HardwareDisplayPlaneManagerAtomicTest.CheckPropsAfterModeset > > Change-Id: If08b015d1e62f51e9ec3c243c1e5a2965449345e > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2106476 > Commit-Queue: Mark Yacoub <markyacoub@google.com> > Auto-Submit: Mark Yacoub <markyacoub@google.com> > Reviewed-by: Daniel Nicoara <dnicoara@chromium.org> > Cr-Commit-Position: refs/heads/master@{#751717} TBR=dnicoara@chromium.org,markyacoub@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1067121 Change-Id: I777bf3455416f559d35349beda5036a2931b978e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152766Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Mark Yacoub <markyacoub@google.com> Cr-Commit-Position: refs/heads/master@{#759689}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/d113c17a489e..cbdc14be1be4 git log d113c17a489e..cbdc14be1be4 --date=short --first-parent --format='%ad %ae %s' 2020-04-16 tobine@google.com doc: Discuss manual roll in note on Vulkan-Headers repo Created with: gclient setdep -r src/third_party/angle@cbdc14be1be4 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/angle-chromium-autoroll Please CC timvp@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-asan;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: timvp@google.com Change-Id: I5da7ae51d19f97757fa29ff69adeaa36eac6538d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152705Reviewed-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@{#759688}
-
Ben Pastene authored
Bug: 1071166 Change-Id: I94e85ba687b44bb208b4429c3e249865332b6e5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2150978 Commit-Queue: Gabriel Charette <gab@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Cr-Commit-Position: refs/heads/master@{#759687}
-
Mario Sanchez Prada authored
Migrate this test out of blink/web_tests/fast/css-grid-layout and into the WPT-specific directory, adding links to the relevant specs and a test assertion describing its purpose. Bug: 767015, 1063749 Change-Id: I5d2d4771603678a792a37e71fd66cdc2a81f43b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152372Reviewed-by:
Javier Fernandez <jfernandez@igalia.com> Commit-Queue: Mario Sanchez Prada <mario@igalia.com> Cr-Commit-Position: refs/heads/master@{#759686}
-
Kuo-Hsin Yang authored
The tab title may contain PII and should not be in the feedback report. Log the tab resource id and renderer pid to identify the tab. BUG=chromium:1070935 TEST=check the related tab manager logs after tab discard. Change-Id: I0fbbd1f222ba16ad80c431b66790f71df46b0501 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152058Reviewed-by:
François Doray <fdoray@chromium.org> Commit-Queue: Kuo-Hsin Yang <vovoy@chromium.org> Cr-Commit-Position: refs/heads/master@{#759685}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/3c49531fb490..d059dfbc06e0 git log 3c49531fb490..d059dfbc06e0 --date=short --first-parent --format='%ad %ae %s' 2020-04-16 mbonadei@webrtc.org Fix link in documentation. (take 2) Created with: gclient setdep -r src/third_party/webrtc@d059dfbc06e0 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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 Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I6e08f6ef63f3375b2abc2d967a6bd74697a94ea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151433Reviewed-by:
-
Colin Blundell authored
In flows where WebContents detects that a tab should be closed (e.g., on window.close()), it calls out to its delegate. WebLayer's TabImpl currently handles this by calling out to the client via NewTabCallback#onCloseTab(). However, there is no reason to delegate this functionality to the client: instead, WebLayer can directly close the tab, notifying the client of the closure via TabListCallback#onTabRemoved(). This CL makes that change, deprecating NewTabCallback#onCloseTab() as a public API. Embedders should adapt to this change by listening to TabListCallback#onTabRemoved(), and using it on 84 and above to implement the functionality that they are currently implementing in NewTabCallback#onCloseTab(). Note that the latter should still be kept on the embedder side for as long as they are supporting WebLayer impl versions < 84. For an example adaptation, see WebLayerShellActivity.java in this CL (nb: this does not implement any version checks as it's not relevant for WebLayer Shell). Any checks for the closed tab being the active tab that were being done in onCloseTab() should instead become checks for the active tab being null in onTabRemoved(); the latter will be the case if the tab was the active tab prior to being removed. We leave the prior flow in the implementation for clients < 84, since these clients are expecting that flow in order to work correctly. Note that this change opens the possibility that the embedder calls into a Tab object whose impl has been destroyed (e.g., if they fail to take appropriate action on TabListCallback#onTabRemoved()). To harden WebLayer against that case, this CL adds a new ITabClient#onTabDestroyed() API to have Tab null out its impl pointer on TabImpl destruction. This change is a precursor to implementing tab closing in the case where the initial navigation in a tab results in an intent being launched. Bug: 1031465 Change-Id: I88c28a3deb23f192ad1ca09ace0d111ce976e63b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2145877Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#759683}
-
S. Ganesh authored
This CL adds a PolicyManagerInterface that all future Policy Managers will support, as well as a DefaultPolicyManager. Bug: 1068797 Change-Id: Idf70e93a6b084e6a519cb65738f45ed51ecaae29 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2140994Reviewed-by:
Sorin Jianu <sorin@chromium.org> Commit-Queue: S. Ganesh <ganesh@chromium.org> Cr-Commit-Position: refs/heads/master@{#759682}
-
Laís Minchillo authored
Test: none Change-Id: I1441585aa8345bc3fb60504b303635a85d8c9ac3 Fixed: 1061976 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2144072 Commit-Queue: Laís Minchillo <laisminchillo@chromium.org> Auto-Submit: Laís Minchillo <laisminchillo@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Reviewed-by:
Tobias Sargeant <tobiasjs@chromium.org> Cr-Commit-Position: refs/heads/master@{#759681}
-
Mugdha Lakhani authored
PageInfoController is moving to //components soon. This is part of a series of CLs that remove //chrome dependencies from it. This CL moves one such dependency, ContentSettingValues, to components and updates references everywhere it's used. Bug: 1052375 Change-Id: I010f30be5e20a90b1d3746804ef929f0502994b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2150906 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Reviewed-by:
Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/master@{#759680}
-
Joey Scarr authored
This was linking to https://rota-ng.appspot.com/legacy/sheriff_v8.json which has been dead for a while. Bug: 1071344 Change-Id: I58145b96e38dc1e010070db53f22f14c8a1500d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151769Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Garrett Beaty <gbeaty@chromium.org> Auto-Submit: Joey Scarr <jsca@chromium.org> Cr-Commit-Position: refs/heads/master@{#759679}
-
Justin Cohen authored
iOS 13.4 added better logging for finding leaked background tasks, but it requires setting a name. This change also adds a metric to track what backgroundTimeRemaining is for any tasks initiated in the background. Bug: 1064280 Change-Id: I074b7a229b4c9ca91b0f37d583d8a07994546178 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1132097 Commit-Queue: Justin Cohen <justincohen@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Brian White <bcwhite@chromium.org> Reviewed-by:
Eugene But <eugenebut@chromium.org> Auto-Submit: Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#759678}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/d28d4891fbd9..a0c450d5b58f git log d28d4891fbd9..a0c450d5b58f --date=short --first-parent --format='%ad %ae %s' 2020-04-16 aerotwist@chromium.org Adds support for Total Blocking Time in Perf panel Created with: gclient setdep -r src/third_party/devtools-frontend/src@a0c450d5b58f 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/+/master/autoroll/README.md Bug: chromium:1054381 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Ia15e1c11dc65eea015bb7d08ef4b6ac0df6dffe6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152632Reviewed-by:
-
Jeremy Roman authored
This was missed in crrev.com/c/2013473. Bug: 1040627 Change-Id: I1928292ab7f2d9ae2eab7577899300d995c9ca1c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152633Reviewed-by:
Lucas Gadani <lfg@chromium.org> Commit-Queue: Jeremy Roman <jbroman@chromium.org> Cr-Commit-Position: refs/heads/master@{#759676}
-
Aaron Colwell authored
Removing a field that doesn't appear to be used anywhere and cleaned up all the call sites. Bug: 1015882 Change-Id: Ie6ed3db2a56d0416ec61a7f77da454b2fcc15fad Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151683 Commit-Queue: Aaron Colwell <acolwell@chromium.org> Auto-Submit: Aaron Colwell <acolwell@chromium.org> Reviewed-by:
Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#759675}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/7a9c9d66f12c..2d65b73337ee git log 7a9c9d66f12c..2d65b73337ee --date=short --first-parent --format='%ad %ae %s' 2020-04-16 tdenniston@google.com [svg] Fix multiple transforms specified Created with: gclient setdep -r src/third_party/skia@2d65b73337ee If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC kjlubick@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-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 Bug: None Tbr: kjlubick@google.com Change-Id: I5ee8ec4ee73175c63f4978bc4604075c58bf9f91 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152631Reviewed-by:
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/45e5510c53da..ab983012a2d4 git log 45e5510c53da..ab983012a2d4 --date=short --first-parent --format='%ad %ae %s' 2020-04-16 bclayton@google.com Make memoryPageSize() functions thread-safe. 2020-04-16 bclayton@google.com Vulkan: Move SpecializationInfo to own file. Created with: gclient setdep -r src/third_party/swiftshader@ab983012a2d4 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/+/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: I4a38e4532454daffea0e4690eaa4fe009ed9ee60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152629Reviewed-by:
-
Vasiliy Telezhnikov authored
This is a reland of d60e79d1 The problem was that resources were never returned because ScopedBatchReturnResources was in outer scope than ScopedAllowGpuAccess so the state when we don't batch already, but still have access to gpu thread didn't exist. Solution to merge ScopedBatchReturnResources and ScopedAllowGpuAccess to make sure everything happens in right order. Original change's description: > Limit access to gpu thread in DisplayResourceProvider > > This CL makes sure that DisplayResourceProvider return resources only > when GPU Thread is available to make sure ReleaseImageContexts will > complete in finite time. > > This doesn't change anything for Chrome where GPU Thread is always > available, but on webview RenderThread that used for gpu access during > composition is available only during specific times (init, dtor, > DrawAndSwap) > > Bug: 1068716 > > Change-Id: I8fa482ab7399d6ce7639c1d76187be86ce152059 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2138551 > Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> > Reviewed-by: Jonathan Backer <backer@chromium.org> > Cr-Commit-Position: refs/heads/master@{#757967} Bug: 1068716 Change-Id: Idf531b9ee9e10057b571725a256d2af09efbea69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2149377Reviewed-by:
Jonathan Backer <backer@chromium.org> Commit-Queue: Vasiliy Telezhnikov <vasilyt@chromium.org> Cr-Commit-Position: refs/heads/master@{#759672}
-
Thomas Guilbert authored
This CL adds/modifies three tests: 1. Updates the chained video.rAF callback test to also verify the required VideoFrameMetadata fields (e.g. dimensions stay constant, time and presented frames are increasing). 2. Adds a test that makes sure that video.rAF callbacks are executed before window.rAF callbacks, and in the same turn of the event loop (as measured by having identical 'time' callback parameters). 3. Adds a test that verifies that all of the WebRTC optional parameters are present when we expect them to be. Bug: 1012063 Change-Id: I72461dd42f6da1a03faaee61355e7c191fe4c116 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2130643 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Guido Urdaneta <guidou@chromium.org> Reviewed-by:
Dan Sanders <sandersd@chromium.org> Auto-Submit: Thomas Guilbert <tguilbert@chromium.org> Cr-Commit-Position: refs/heads/master@{#759671}
-
Ehimare Okoyomon authored
For cookie settings specifically, change whether the result of AddExceptionPreference is an allow or block exception, depending on the user's current cookie settings state. Bug: 1060118 Change-Id: If1440909ac649015bd8c97c632e5e4f571a41841 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2139663Reviewed-by:
Finnur Thorarinsson <finnur@chromium.org> Commit-Queue: Ehimare Okoyomon <eokoyomon@chromium.org> Cr-Commit-Position: refs/heads/master@{#759670}
-
Erik Staab authored
The large, auto-generated json files can take over ten seconds to parse. Change-Id: I122dc0b7f13bf9bd816a5b6f7fc2f0ad08e0fcc9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151844Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: Erik Staab <estaab@chromium.org> Cr-Commit-Position: refs/heads/master@{#759669}
-
Clemens Arbesser authored
Before this change, going from one ShowGenericUiAction to another one caused a hard layout transition, rather than a smooth one. Bug: b/145043394 Change-Id: I2577c03d9f9c8ebcb9d7f27cb057384f53a3edff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151452Reviewed-by:
Marian Fechete <marianfe@google.com> Commit-Queue: Clemens Arbesser <arbesser@google.com> Cr-Commit-Position: refs/heads/master@{#759668}
-
Robert Sesek authored
This is a very basic check that can be used to verify that the current process is running under any kind of sandbox. Change-Id: Iaee3f2a97c4dae72714297dcdf23b37ff7c6fdf4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2147677 Commit-Queue: Robert Sesek <rsesek@chromium.org> Reviewed-by:
Nasko Oskov <nasko@chromium.org> Reviewed-by:
Alex Gough <ajgo@chromium.org> Reviewed-by:
Matthew Denton <mpdenton@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#759667}
-
Caitlin Fischer authored
Bug: 1068142 Change-Id: I10ba127779a14c9cfa41bdf875ab65a2e6e38395 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151890Reviewed-by:
Alexei Svitkine <asvitkine@chromium.org> Reviewed-by:
Olivier Robin <olivierrobin@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#759666}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/652f83ad..a0a377b4 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: I4956a468109b84a89ac53f892a4f263577ada906 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151551Reviewed-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@{#759665}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/3d687a1e3e31..3c49531fb490 git log 3d687a1e3e31..3c49531fb490 --date=short --first-parent --format='%ad %ae %s' 2020-04-16 mbonadei@webrtc.org Fix link in documentation. 2020-04-16 mbonadei@webrtc.org Remove deprecated VideoSendStream::StreamStats data members. Created with: gclient setdep -r src/third_party/webrtc@3c49531fb490 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/webrtc-chromium-autoroll Please CC webrtc-chromium-sheriffs-robots@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 Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I0699f5c4147abb41c60cdc560a5c1f9147a8dc8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152444Reviewed-by:
-
David Roger authored
This histogram is recorded on multilogin requests to Gaia, and can be useful to debug integration issues between Chrome and Gaia. Fixed: 1059817 Change-Id: Ie1c1ef517050ad5c8372bb697d71c2557b1b452f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151456 Commit-Queue: David Roger <droger@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Cr-Commit-Position: refs/heads/master@{#759663}
-
Omar Morsi authored
https://chromium.googlesource.com/chromiumos/platform2/system_api.git/+log/484e71aca63a..14a2fb015f12 $ git log 484e71aca..14a2fb015 --date=short --no-merges --format='%ad %ae %s' 2020-04-07 omorsi system_api: Add constants for chaps 2020-03-25 kglund power: add ChangeRegDomain method to powerd and shill 2020-04-09 jorgelo system_api, chromeos-login, cryptohome: Extract namespace constant. 2020-04-08 ahassani dlcservice: Add Purge API 2020-01-15 hugobenichi arc: net: DBUS API for system-proxy namespace routing Created with: roll-dep src/third_party/cros_system_api Bug: 1045895 Change-Id: I26610fb2b7f7c1dac00779b0bc45f688c5fbeac6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151589Reviewed-by:
Pavol Marko <pmarko@chromium.org> Commit-Queue: Omar Morsi <omorsi@google.com> Cr-Commit-Position: refs/heads/master@{#759662}
-
mhasank authored
Adding support for sending backup_log argument to session manager when stopping ARC container based on error conditions in Chrome. BUG=b:149874690 TEST=deploy chrome, start and stop arc. Change-Id: Ia1388cea39122c9c19f20641d0c299e709ed97b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2149635 Commit-Queue: Muhammad Hasan Khan <mhasank@chromium.org> Reviewed-by:
Yusuke Sato <yusukes@chromium.org> Reviewed-by:
Ryo Hashimoto <hashimoto@chromium.org> Reviewed-by:
Hidehiko Abe <hidehiko@chromium.org> Auto-Submit: Muhammad Hasan Khan <mhasank@chromium.org> Cr-Commit-Position: refs/heads/master@{#759661}
-
Ioana Pandele authored
Tapping on the toggle in the keyboard accessory will now update the PasswordStore, either by removing the blacklisted entry for the origin if the user re-enables saving, or by re-adding it if the user disables it again. At the moment, the save password infobar is still not shown after saving is enabled via the toggle, because ChromePasswordManagerClient queries the old cache (via PasswordFormManager) which doesn't have the latest store data. This will be changed in the next CL. Bug: 1044930 Change-Id: I0a5cbcc6085fac5070375093b499a3e2ebc7c4e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2135752 Commit-Queue: Ioana Pandele <ioanap@chromium.org> Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#759660}
-
Marc Treib authored
Bug: 1034915 Change-Id: I1216bf20521a43d870dd40a30149d490fb41fc90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151508Reviewed-by:
-
Alex Ilin authored
PromoCardCoordinatorTest#testTextImageBinding is failing on an Android K bot. TBR=twellington@chromium.org Bug: 1071414 Change-Id: If244d8c5caa7c9e08229e1bcbece1504d1acc01d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151568Reviewed-by:
-
David Roger authored
Remove tangltom who is no longer working on Chrome. Add droger. Change-Id: If7cf2d3ed7417485bab3bbb501e040d3d08e115e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152589 Auto-Submit: David Roger <droger@chromium.org> Reviewed-by:
Ramin Halavati <rhalavati@chromium.org> Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Cr-Commit-Position: refs/heads/master@{#759657}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/bb63adbd88be..9036394cfefb git log bb63adbd88be..9036394cfefb --date=short --first-parent --format='%ad %ae %s' 2020-04-16 lalitm@google.com Merge "tp: refactor shell main into multiple functions" 2020-04-16 lalitm@google.com tp: don't associate to any process for sde_tracing_mark_write events 2020-04-16 lalitm@google.com Merge "tp: add EXTRACT_ARG function" Created with: gclient setdep -r src/third_party/perfetto@9036394cfefb 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/+/master/autoroll/README.md Bug: chromium:136635390,chromium:154157553 Tbr: perfetto-bugs@google.com Change-Id: Icbe3c9e2cd094871df35be898c248d2ba5726ba0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152625Reviewed-by:
-
Mihai Sardarescu authored
This CL adds chrome-sign-team@ as owners for histograms Signin.Signin{Started|Completed}AccessPoint. These histograms are used to record how users interact with the Chrome sign-in UIs, and are critical in measuring the CTR for the various UI surfaces. Fixed: 1059819 Change-Id: Ib82fc18a099c6ac69944c610cfdcdc380b51f622 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151511 Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Reviewed-by: -
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@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/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: Id97b7ddfae74389c260639af0131673ba0532006 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2152630Reviewed-by:
-
Javier Ernesto Flores Robles authored
Syncs all passwords if they haven't been sync before. Adds file URL as an arg of CredentialProviderService to test it when app groups are not present. Removes keychainIdentifier from the convenience init. Now it can be grabbed from passwordForm. Adds remove all credentials to the credential store. Moves general credential management to the protocol: add, update and remove. After this sync, observing the password store should be enough to keep data in sync. Coming in a follow up CL. Bug: 1066803 Change-Id: Id5f0289e3fdde908bd9d9be8ae7cc10b26fe5f93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2149653Reviewed-by:
David Jean <djean@chromium.org> Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Javier Ernesto Flores Robles <javierrobles@chromium.org> Cr-Commit-Position: refs/heads/master@{#759653}
-
