- 03 Sep, 2019 40 commits
-
-
Kamila Śledź authored
Bug: 984021 Change-Id: Idf272b52ea7ae68bd045287a788ebabb4e69e66e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782478 Commit-Queue: Kamila Śledź <kamilasledz@google.com> Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Cr-Commit-Position: refs/heads/master@{#692622}
-
Jan Wilken Dörrie authored
TBR=ulan@chromium.org Bug: 999004 Change-Id: I941cf118d9f0a70d4e714989b0b75d13790fd67d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1778877Reviewed-by:
Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
Ulan Degenbaev <ulan@chromium.org> Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Cr-Commit-Position: refs/heads/master@{#692621}
-
Maksim Moskvitin authored
There are several API entry points, which lead to modification of Nigori data or notify bridge about metadata changes: 1. MergeSyncData(), which leads to UpdateLocalChanges() if we need to change something. 2. ApplySyncChanges(), which can be called with empty |data| and we need to persist metadata in this case. If |data| isn't called update ends in UpdateLocalChanges() as well. 3. SetEncryptionPassphrase(). We need to serialize the data after Put() call to collect right metadata. 4. SetDecryptionPassphrase(). 5. SetKeystoreKeys(). While this method changes local state, it always followed by MergeSyncData() or ApplySyncChanges() unless the server violates protocol or there is a client-side bug, so we don't need to persist data here. Bug: 922900 Change-Id: If68be8dcf58e137efee64b626c002601b21530eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1777804 Auto-Submit: Maksim Moskvitin <mmoskvitin@google.com> Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by:
Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#692620}
-
Jan Wilken Dörrie authored
TBR=steimel@chromium.org Bug: 1000215 Change-Id: I40d7c7c5fc7ccf220b5e17aa554a56866399b0c6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782164Reviewed-by:
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d597c831131e..d59b50bc00dc Created with: gclient setdep -r src-internal@d59b50bc00dc 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 jbudorick@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.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: Ibcaf519981a2401963d578b2fde254f157195341 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782124Reviewed-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@{#692618}
-
Andrei Chulkov authored
This CL adds the necessary code to support the experiment we will be doing later via finch. This is native side only. We will have three "stories", labeled A, B and C, each with their own title and explanation strings. Bug: 983445 Change-Id: I93e1e0a76e0aeff6c2b73b95f9ec2c6beda60379 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781457Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Commit-Queue: Andrei Chulkov <achulkov@google.com> Cr-Commit-Position: refs/heads/master@{#692617}
-
Mugdha Lakhani authored
When a delayed task or a wakeup task attempts to fire ready sync events, don't reschedule delayed processing. This is causing infinite loops in the wild that we're not able to repro. The gap that we leave by not doing this is when the browser is closed on Android after all events are firing on Android, but none has completed. In this case, we won't wake the browser up when the events complete. This is a corner case. In future CLs, we'll schedule a wakeup with a non-zero delay to cover this case while also avoiding infinite loops. Bug:996166, 991326 Change-Id: Ib60ed16a23816624e51612b0dbfa0ae93e5fabc5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781678 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Reviewed-by:
Rayan Kanso <rayankans@chromium.org> Cr-Commit-Position: refs/heads/master@{#692616}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/082696efd9c7..f2773b546476 git log 082696efd9c7..f2773b546476 --date=short --no-merges --format='%ad %ae %s' 2019-09-03 mbonadei@webrtc.org Add webrtc_apprtc_browsertest.cc resource dir to .gitignore. Created with: gclient setdep -r src/third_party/webrtc@f2773b546476 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 TBR=webrtc-chromium-sheriffs-robots@google.com Bug: chromium:997673 Change-Id: I5d498b55bd7648a1b90fe3e3e9e06f401615b6a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781767Reviewed-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@{#692615}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/c26869d540f3..fc508813b05a git log c26869d540f3..fc508813b05a --date=short --no-merges --format='%ad %ae %s' 2019-09-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/glslang/src 92f5afdee0ab..56f61ccceffa (1 commits) Created with: gclient setdep -r src/third_party/angle@fc508813b05a 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 jmadill@chromium.org,jmadill@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=jmadill@chromium.org,jmadill@google.com Bug: chromium:None Change-Id: I8eb3a228313e07d06f396db35ad5dc98d2287cf9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781766Reviewed-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: I146073f8436a83c8d452fe94bda6f0a36bf1bfe5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781768Reviewed-by:
-
Kent Tamura authored
Include lifecycle.mojom-blink-forward.h instead of lifecycle.mojom-blink.h in context_lifecycle_state_observer.h This CL reduces one of full mojom includes from document.h Bug: 242216 Change-Id: I47ded423e137dd9bc11e34c691016fe29a6be848 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781912Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Commit-Queue: Kent Tamura <tkent@chromium.org> Cr-Commit-Position: refs/heads/master@{#692612}
-
Kent Tamura authored
This CL drops css_proprety_id.mojom-blink.h include from document.h Bug: 242216 Change-Id: Idc64408398e987f3608b8d70764864bcc4604ab1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781911Reviewed-by:
-
Jan Wilken Dörrie authored
TBR=kbr@chromium.org Bug: 999327 Change-Id: I28240c209f4599978e0be64376629e5be7cce0c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781641Reviewed-by:
-
Maksim Moskvitin authored
SerializeAsNigoriLocalData() converts state of the Nigori's bridge and processor (i.e. sync metadata) to NigoriLocalData proto, that will be used for persistence. Side changes: Cryptographer interface is extended by adding ToProto() method, NigoriLocalData |keystore_keys| field renamed to |keystore_key| (singular form fits better for repeated proto fields). Bug: 922900 Change-Id: I9535008f221b755a389a6ca74c6d0593304ee3a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1768325Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/b2ea4d05..45f5423a Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ia97f8fda5cf61a0fc6e4a381675ea6355714ab56 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781750Reviewed-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@{#692608}
-
Makoto Shimazu authored
BrowserContext could be nullptr while the process manager is still alive when the browser is being terminated. This CL is to take the situation into account. Bug: 1000076 Change-Id: I94151a8843b61dad82f145dc97905dd24a697c71 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781910 Auto-Submit: Makoto Shimazu <shimazu@chromium.org> Reviewed-by:
Matt Falkenhagen <falken@chromium.org> Commit-Queue: Makoto Shimazu <shimazu@chromium.org> Cr-Commit-Position: refs/heads/master@{#692607}
-
Marc Treib authored
This adds an "is_account_store" flag to LoginDatabase, which specifies whether this DB stores profile-scoped or Gaia-account-scoped data. Sync uses this flag to clear the account-scoped data on signout. In the future, the flag will also be used by the DB itself to "tag" credentials it returns as coming from the account or from the profile. Bug: 998455 Change-Id: Ibcdc1082fab5085ef354be7c4055958165135f39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1748755 Commit-Queue: Marc Treib <treib@chromium.org> Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Cr-Commit-Position: refs/heads/master@{#692606}
-
Kouhei Ueno authored
Bug: 995157 Change-Id: Ic03a2da79f254510bd20379a93fd689e7aa16c3f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1758001 Commit-Queue: Kouhei Ueno <kouhei@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Alexander Timin <altimin@chromium.org> Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#692605}
-
Richard Knoll authored
This is a preparation to introduce a new type that should not be added to the mojom type. TBR=sky@chromium.org Bug: none Change-Id: Idfb7ba4172fc96755d0ab572869ff1d62df66f5e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781155 Commit-Queue: Richard Knoll <knollr@chromium.org> Reviewed-by:
Maggie Cai <mxcai@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#692604}
-
Yannic Bonenberger authored
*** Note: There is no behavior change from this patch. *** This CL replaces calls to base::{Bind,BindRepeating} with calls to base::BindOnce, and removes calls to base::AdaptCallbackForRepeating when the returned base::RepeatingCallback is immediately converted to a base::OnceCallback. This CL was uploaded by git cl split. R=ricea@chromium.org Bug: 714018 Change-Id: Ibd3e309b05a99fb6d45b500486f5407369f4711b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1778771Reviewed-by:Adam Rice <ricea@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Auto-Submit: Yannic Bonenberger <contact@yannic-bonenberger.com> Cr-Commit-Position: refs/heads/master@{#692603}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/ce202a0f987c..082696efd9c7 git log ce202a0f987c..082696efd9c7 --date=short --no-merges --format='%ad %ae %s' 2019-09-03 ilnik@webrtc.org Revert "Refactor FEC code to use COW buffers" Created with: gclient setdep -r src/third_party/webrtc@082696efd9c7 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 TBR=webrtc-chromium-sheriffs-robots@google.com Bug: None Change-Id: I961a3d47ca4e4bc5434ec2fbb3d7c132e3e675e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781511Reviewed-by:
-
Jérôme Lebel authored
ChromeSigninViewControllerTest.TestConsentWithSettings uses the following method with pre-unified consent and with unified consent. -[<SigninConfirmationViewControllerDelegate> signinConfirmationControllerDidTapSettingsLink:] This method is available only with pre-unified consent and will disappear with pre-unified consent code will disappear. This patch updates this unittest with unified consent by tapping the on the settings link. Bug: 1000178 Change-Id: If1cd2f3abe13d71f4e8967c5822864aeffa4d379 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781677 Commit-Queue: Jérôme Lebel <jlebel@chromium.org> Reviewed-by:Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#692601}
-
Gyuyoung Kim authored
The previous CL(https://crrev.com/c/1768840) missed to apply pending_remote to SetListeningForActivate in vr_service.mojom. This CL applies it. Additionally, this CL replaces mojo::Binding with mojo::Receiver in vr_display.h and vr_service_impl.h Bug: 955171 Change-Id: Iba911f52c5fa52ce38d904e4fc147158d2e1e539 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1775879 Commit-Queue: Gyuyoung Kim <gyuyoung@igalia.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Oksana Zhuravlova <oksamyt@chromium.org> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#692600}
-
Juan Antonio Navarro Perez authored
Repeating --output-format histograms --output-format histograms should not attempt to write histograms twice! TBR=crouleau@chromium.org Bug: 1000010 Change-Id: Ie9e97bfe3d68e093a6a59497fbc002182a4d80fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781453Reviewed-by:
Juan Antonio Navarro Pérez <perezju@chromium.org> Commit-Queue: Juan Antonio Navarro Pérez <perezju@chromium.org> Cr-Commit-Position: refs/heads/master@{#692599}
-
Jinho Bang authored
If we use "use_jumbo_build = true" flag on Android, currently build error occurs as follows: In file included from gen/content/browser/browser_jumbo_8.cc:45: In file included from ./../../content/browser/media/android/media_player_renderer.cc:13: In file included from ../../content/browser/android/scoped_surface_request_manager.h:14: In file included from ../../gpu/ipc/common/android/scoped_surface_request_conduit.h:9: In file included from ../../gpu/ipc/common/android/texture_owner.h:15: In file included from ../../ui/gl/gl_bindings.h:31: ../../third_party/mesa_headers/GL/gl.h:173:9: error: 'GL_FALSE' macro redefined [-Werror,-Wmacro-redefined] ^ ../../third_party/khronos/GLES2/gl2.h:88:9: note: previous definition is here ^ This patch just fixes the build error using forward declaration of TextureOwner in scoped_surface_request_conduit.h. TBR=bratell@opera.com,nasko@chromium.org Bug: none Change-Id: I9bd0eec218ebc5d418278b48722f90f920dfc946 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782202 Commit-Queue: Jinho Bang <jinho.bang@samsung.com> Reviewed-by:Jinho Bang <jinho.bang@samsung.com> Cr-Commit-Position: refs/heads/master@{#692598}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/0dce762b40b7..d597c831131e Created with: gclient setdep -r src-internal@d597c831131e 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 jbudorick@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.chrome.try:linux-chromeos-chrome TBR=jbudorick@google.com Bug: chromium:None Change-Id: Ia0506d21d816b9c7cf534cdd4618855afe361405 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782123Reviewed-by:
-
Himanshu Jaju authored
This could happen when we receive the phone unlocked event and Chrome is not yet initialised. Bug: 999779 Change-Id: Ia30ffd424b84ca0d47861cd20601b7172fce40ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781433Reviewed-by:
Boris Sazonov <bsazonov@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> Cr-Commit-Position: refs/heads/master@{#692596}
-
Maksim Moskvitin authored
It was possible, that SyncEngineBackend was destroyed inside UI sequence, following implementation of SyncEngineImpl::Shutdown(): sync_task_runner_->PostTask( FROM_HERE, base::BindOnce(&SyncEngineBackend::DoShutdown, backend_, reason)); backend_ = nullptr; This could happen in two cases: 1. |sync_task_runner_| become inactive before posting DoShutdown task. 2. DoShutdown() task completes before "backend_ = nullptr". Now we explicitly release |backend_| ownership from SyncEngineImpl with ReleaseSoon(), so its destructor can be called only inside Sync sequence. If first case described above is a correct hypothesis, we may have a problem with leaking significant amount of memory, but hopefully it can happen only during browser shutdown (and we have no better solution). Bug: 999964 Change-Id: I00261ba2e3f2b71245f559c09ff7d7cd7a91c849 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781456 Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Reviewed-by: -
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/SPIRV-Tools.git/+log/65e362b7ae2a..2c5ed16ba97d git log 65e362b7ae2a..2c5ed16ba97d --date=short --no-merges --format='%ad %ae %s' 2019-09-02 afdx@google.com Fix end comments in header files (#2829) Created with: gclient setdep -r src/third_party/SPIRV-Tools/src@2c5ed16ba97d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/spirv-tools-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,jmadill@chromium.org,jmadill@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_angle_vk32_deqp_rel_ng;luci.chromium.try:android_angle_vk32_rel_ng;luci.chromium.try:android_angle_vk64_deqp_rel_ng;luci.chromium.try:android_angle_vk64_rel_ng;luci.chromium.try:linux_angle_deqp_rel_ng;luci.chromium.try:linux-angle-rel;luci.chromium.try:win-angle-rel-32;luci.chromium.try:win-angle-rel-64;luci.chromium.try:win-angle-deqp-rel-32;luci.chromium.try:win-angle-deqp-rel-64 TBR=radial-bots+chrome-roll@google.com,jmadill@chromium.org,jmadill@google.com Bug: None Change-Id: I9218b2fcdd0b320767ebecd1d3071ede48f3685d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782122Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/d57839b3315d..24a3df72b959 git log d57839b3315d..24a3df72b959 --date=short --no-merges --format='%ad %ae %s' 2019-09-03 tcwang@google.com afdo: Implement kernel afdo verification builders. Created with: gclient setdep -r src/third_party/chromite@24a3df72b959 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@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:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I26ba9390808dbd23c205e76c180055c122723ebd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782121Reviewed-by:
-
Mugdha Lakhani authored
to test that periodicsync events are fired at an expected frequency, and that we update registrations as expected. Bug: 925297 Change-Id: I8b26337c8ef6b8d38d3466c2fe15e3252bdd266c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1713642 Commit-Queue: Mugdha Lakhani <nator@chromium.org> Reviewed-by:
-
Lowell Manners authored
This enum forces tests to specify why they are disabling the BackForwardCache, to make future triaging of tests impacted by the BackForwardCache being enabled easier. Change-Id: I72a9b81e491b7e659f33792e087df6bc8b697efc Bug: 990354 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1780740Reviewed-by:
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/179d7b28a36a..c7910d19fe50 git log 179d7b28a36a..c7910d19fe50 --date=short --no-merges --format='%ad %ae %s' 2019-09-03 cwallez@chromium.org Fix missing virtual on destructor Created with: gclient setdep -r src/third_party/dawn@c7910d19fe50 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@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:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel TBR=cwallez@google.com Bug: None Change-Id: I9a38dc1391fd0297b994301db4061c3908538d92 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782120Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/31b524cf60b7..c26869d540f3 git log 31b524cf60b7..c26869d540f3 --date=short --no-merges --format='%ad %ae %s' 2019-09-03 angle-autoroll@skia-public.iam.gserviceaccount.com Roll ./third_party/spirv-tools/src 65e362b7ae2a..2c5ed16ba97d (1 commits) Created with: gclient setdep -r src/third_party/angle@c26869d540f3 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 jmadill@chromium.org,jmadill@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=jmadill@chromium.org,jmadill@google.com Bug: chromium:None Change-Id: Ida878ce7824910e99db95ea2d2cba12c2f20674c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1782119Reviewed-by:
-
Oleh Lamzin authored
Wrap wilco related policy descriptions into <ph> tag. BUG=b:140108193 TEST=none Change-Id: I2d2b32a5c9227a2fd7203b74199b650aa726037b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781454 Commit-Queue: Oleh Lamzin <lamzin@google.com> Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Cr-Commit-Position: refs/heads/master@{#692588}
-
Luciano Pacheco authored
Remove BackgroundWindow.prototype.launcher.launchFileManager because Closure wasn't checking the type of its argument. Bug: 778674 Change-Id: I2e052d9a43e1ca206ffaf56f946fdb6d25ed21b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1775880 Commit-Queue: Luciano Pacheco <lucmult@chromium.org> Auto-Submit: Luciano Pacheco <lucmult@chromium.org> Reviewed-by:
Alex Danilo <adanilo@chromium.org> Cr-Commit-Position: refs/heads/master@{#692587}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/3dd9de12f761..0241d1092506 git log 3dd9de12f761..0241d1092506 --date=short --no-merges --format='%ad %ae %s' 2019-09-03 primiano@google.com Merge "Add missing sqlite initialization to trace processor unittests" 2019-09-02 treehugger-gerrit@google.com Merge "Increase timeout in HeapprofdCtsTest." 2019-09-02 treehugger-gerrit@google.com Merge "perfetto-ui: Link to bug for thread state" 2019-09-02 fmayer@google.com Merge "Fix OSS-Fuzz build." 2019-09-02 lalitm@google.com Merge "trace_processor: add support for strings in db tables" 2019-09-02 treehugger-gerrit@google.com Merge "Move perfetto's recording controllers at the top" 2019-09-02 lalitm@google.com Merge "test: fix unauthorized error when uploading metrics" 2019-09-02 hjd@google.com Merge "Fix CPU numbering" 2019-09-02 hjd@google.com Merge "Remove rtl character" 2019-09-02 eseckler@google.com Merge "ui: Ignore custom_utils symlink" 2019-09-02 lalitm@google.com Merge "trace_processor: add support for JSON metric output" 2019-08-31 primiano@google.com Merge "test: fix perf metrics uploader crash" 2019-08-30 lalitm@google.com trace_processor: fix debug build 2019-08-30 lalitm@google.com Merge "trace_processor: make StringPool::Id a POD" 2019-08-30 treehugger-gerrit@google.com Merge "Add line number to TrackEvent" 2019-08-30 treehugger-gerrit@google.com Merge "Add ui for choosing chrome categories" 2019-08-30 nicomazz@google.com Record android traces from the UI 2019-08-30 primiano@google.com Fix StringPool on 32-bit Android 2019-08-29 primiano@google.com Merge "Remove Travis and update docs" 2019-08-29 primiano@google.com Merge "Major clean up build files, use flags-per-feature." Created with: gclient setdep -r src/third_party/perfetto@0241d1092506 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 TBR=perfetto-bugs@google.com Bug: chromium:139536756 Change-Id: Iebe41fdae16f0916cab4441dc2cd0746ab5f4370 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1780333Reviewed-by:
-
Oleh Lamzin authored
Wrap internet connection types into <ph> tag. BUG=b:140236926 TEST=none Change-Id: I76e8d8893f90ca06963c525c586a978944ed8b20 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1781579Reviewed-by:
-
Mike West authored
We don't implement the underlying feature for [1] yet. This patch ensures that it has consistent error state so that we can land expectation files instead of skipping it. [1]: external/wpt/html/cross-origin-opener-policy/coop-navigated-popup.https.html Bug: 994214 Change-Id: Icfe42f553d35265d83f19f244f0f8bcc2ce3743d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1778615 Commit-Queue: Mike West <mkwst@chromium.org> Reviewed-by:
Kamila Hasanbega <hkamila@chromium.org> Cr-Commit-Position: refs/heads/master@{#692584}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/a77a1f910ba3..ce202a0f987c git log a77a1f910ba3..ce202a0f987c --date=short --no-merges --format='%ad %ae %s' 2019-09-03 peah@webrtc.org Reland "Reland "Add core multi-channel pipeline in AEC3 This CL adds basic the basic pipeline to support multi-channel processing in AEC3."" Created with: gclient setdep -r src/third_party/webrtc@ce202a0f987c 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 TBR=webrtc-chromium-sheriffs-robots@google.com Bug: None Change-Id: I862d93af872874c8bea75ad8bdd7e90e829b1948 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1778682Reviewed-by:
-
