- 18 Feb, 2020 40 commits
-
-
Chromium WPT Sync authored
Using wpt-import in Chromium ecbb7fc5. With Chromium commits locally applied on WPT: acd8a467 "SharedWorker: Use CSP headers to outside settings" ec83d167 "Update performance.measureMemory to the latest proposal" d5cd6b98 "SharedWorker: Assign unique names to SharedWorkers to avoid unintentional matching" 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 NOAUTOREVERT=true TBR=lpz No-Export: true Change-Id: Idbaa749371e12b11f49335a3b9c01f4c23becea3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062092Reviewed-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@{#742186}
-
Evan Stade authored
This activity has no visible UI, and is to be used for perf tests so that performance measurements won't be affected by changes to WebLayerShellActivity. If we don't do this, we're forced to keep the shell's top chrome the exact same size forever. See linked bug. Android WebView also has a TelemetryActivity. Bug: 1045609 Change-Id: I7aa0443ef93a225ed6b594aba09d4c64158408ed Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2052805Reviewed-by:
Clark DuVall <cduvall@chromium.org> Commit-Queue: Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#742185}
-
Gauthier Ambard authored
The context wasn't check for nil before being used, leading to a series of crashes. Fixed: 1050771 Change-Id: I5e6d08df1058f75fbf22240aefd3d60951be3ac5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059990Reviewed-by:
Ali Juma <ajuma@chromium.org> Reviewed-by:
David Jean <djean@chromium.org> Commit-Queue: Gauthier Ambard <gambard@chromium.org> Cr-Commit-Position: refs/heads/master@{#742184}
-
Xianzhu Wang authored
We need to keep them at least until launch of CompositeAfterPaint Bug: 1043697 Change-Id: I1126a10c751c130bda175891537f51a75bb2fafc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2060655Reviewed-by:
Stephen Chenney <schenney@chromium.org> Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org> Cr-Commit-Position: refs/heads/master@{#742183}
-
Nicolas Ouellet-payeur authored
BrowserSwitcherPolicyMigrator checks if BrowserSwitcherEnabled is true before doing anything. This avoids doing unnecessary work. However, the migrator used to run from ConfigurationPolicyProvider, which only sees the PolicyBundle from a single provider (rather than the merged policies). The issue: if BrowserSwitcherEnabled is set through e.g. platform policies, then only platform policies will migrate. If it's set through user cloud, then only user cloud policies will migrate, etc. Now, the migrators will run from PolicyServiceImpl, after merging the policies from the different providers. This way, BrowserSwitcherEnabled is in the same PolicyBundle as the LBS extension's policies, even if they're configured through a different provider. Bug: 1030607 Change-Id: Ic681fb02eab391664de7135d8f171a0bca812d3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050806Reviewed-by:
Julian Pastarmov <pastarmovj@chromium.org> Commit-Queue: Nicolas Ouellet-Payeur <nicolaso@chromium.org> Cr-Commit-Position: refs/heads/master@{#742182}
-
Mike Wittman authored
Provides a global public metadata interface for setting metadata on already-recorded samples in active profiles. Routes the metadata setting via global functions in sample_metadata.h to provide consistency with the existing interface for setting metadata. Bug: 1034758 Change-Id: Ie7677efb976a8a035e9bbcf689abe98ad64cf225 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036561 Commit-Queue: Mike Wittman <wittman@chromium.org> Reviewed-by:
Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/master@{#742181}
-
Bret Sepulveda authored
TBR=rdevlin.cronin@chromium.org Bug: 1003661 Change-Id: I1d921dcf979ba9956bce1553c8f3a3bd2235dbf9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062353Reviewed-by:
Bret Sepulveda <bsep@chromium.org> Commit-Queue: Bret Sepulveda <bsep@chromium.org> Cr-Commit-Position: refs/heads/master@{#742180}
-
Nazih Almalki authored
The following histograms expire after M81 Bug: 1037241 Change-Id: I97de132f696e802304e171924aec34b8e91f6603 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2054272 Commit-Queue: Nazih Almalki <nalmalki@google.com> Reviewed-by:
Behdad Bakhshinategh <behdadb@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#742179}
-
Mirko Bonadei authored
This CL adds -nostdinc++ and -isystem flags that point to the Chromium libc++ to cflags_objcc. Before this CL, .mm files would use libc++ headers shipped with clang, while .cc files would use libc++ headers in buildtools. Since libc++ is (usually) abi-compat to itself, this (usually) works. We we have detected this problem because it looks like [1] has introduced an ABI breaking change [2]. [1] - https://reviews.llvm.org/rGf97936fabd263e3b311e3b8e9ffca4920e4fcff0 [2] - http://lists.llvm.org/pipermail/libcxx-commits/2020-February/007865.html Bug: 1051010, 400091 Change-Id: Icb49aba558a911369962f085f798a112f80d4273 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062355 Commit-Queue: Mirko Bonadei <mbonadei@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#742178}
-
Olivier Robin authored
The reporting of metrics has been broken by https://chromium-review.googlesource.com/c/chromium/src/+/1405508 The SHUTDOWN_IN_FOREGROUND_WITH_MAIN_THREAD_FROZEN will now be reported only if there is no normal crash report (main thread freeze report should only be seen as an explanation of crashes without real report). Bug: 1052377 Change-Id: I1aa17d5061735732324448128a005cea4f9d9ba6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2060499Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Sylvain Defresne <sdefresne@chromium.org> Commit-Queue: Olivier Robin <olivierrobin@chromium.org> Cr-Commit-Position: refs/heads/master@{#742177}
-
Yusuf Sengul authored
Bug: 1052634 Change-Id: Ibcc0f04b6105a7651309e08cf8433828bf80a715 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058695 Commit-Queue: Yusuf Sengul <yusufsn@google.com> Reviewed-by:
Tien Mai <tienmai@chromium.org> Cr-Commit-Position: refs/heads/master@{#742176}
-
arthursonzogni authored
The file: services/network/public/mojom/content_security_policy-shared.h doesn't exist, this was a typo. The correct one is: services/network/public/mojom/content_security_policy.mojom-shared.h Bug: None Change-Id: I37c611c94f05806bf53293972a9371dfe17a561d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062431 Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#742175}
-
Elly Fong-Jones authored
This test was accessing browser()->window() after it had already been destroyed. Instead, have the test expect that there are no remaining windows. Bug: 1049284 Change-Id: I14c445e528c267ee48ad769289c17ac7270f0e24 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057447 Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org> Reviewed-by:
Peter Boström <pbos@chromium.org> Cr-Commit-Position: refs/heads/master@{#742174}
-
Andrew Grieve authored
This reverts commit 3051c63a. Reason for revert: No longer required by goma Original change's description: > Android: Split out a "javac" wrapper from compile_java.py for GOMA > > Bug: 726475 > Change-Id: Ia9068d24655c3cff62faeaf6eec7815fec4fdba5 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967792 > Reviewed-by: Peter Wen <wnwen@chromium.org> > Commit-Queue: Andrew Grieve <agrieve@chromium.org> > Cr-Commit-Position: refs/heads/master@{#735504} TBR=wnwen@chromium.org,agrieve@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 726475 Change-Id: I768451be2e5e2609fd9d1623f72e3ec71eb106b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2061396 Commit-Queue: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#742173}
-
Mark Cogan authored
This CL creates AllWebStateListObservationRegistrar, which can be used in any case when an object needs to observe all web state lists for a given BrowserState. This is a generalized version of the snapshot cache tab model observer, which this replaces. For cases where only regular or OTR browsers' WebStateLists should be observed, AllWebStateListObservationRegistrar has an optional param that can be set at creation time. To avoid circular dependencies, one target in web_state_list/ had to be split from the main target (hence the scattershot BUILD.gn updates). Change-Id: Ic3977b709d5b089ebf31afd0fa868067833f2249 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1997306 Commit-Queue: Mark Cogan <marq@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Justin Cohen <justincohen@chromium.org> Cr-Commit-Position: refs/heads/master@{#742172}
-
Marc-Antoine Ruel authored
I moved team. No code change. Change-Id: I84dd0f3f40f44c7e1cbf9d4516e78d3490f81f0d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062291 Auto-Submit: Marc-Antoine Ruel <maruel@chromium.org> Reviewed-by:
Takuto Ikuta <tikuta@chromium.org> Reviewed-by:
John Budorick <jbudorick@chromium.org> Commit-Queue: John Budorick <jbudorick@chromium.org> Cr-Commit-Position: refs/heads/master@{#742171}
-
Clemens Arbesser authored
Bug: b/144075373 Change-Id: I559fb7bd9ad4273e3360604c24c230ce5edc0ef9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2043799 Commit-Queue: Clemens Arbesser <arbesser@google.com> Reviewed-by:
Sandro Maggi <sandromaggi@google.com> Cr-Commit-Position: refs/heads/master@{#742170}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/78b471760dd9..c1bb9cba16be git log 78b471760dd9..c1bb9cba16be --date=short --first-parent --format='%ad %ae %s' 2020-02-18 robertphillips@google.com Revert "Manage renderCmdEncoder over lifetime of GrMtlOpsRenderPass." Created with: gclient setdep -r src/third_party/skia@c1bb9cba16be 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 lovisolo@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: lovisolo@google.com Change-Id: Iecc8baf602bbe90f162ec784b843ad91de4dde16 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062309Reviewed-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@{#742169}
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/0bbf7ba9f909..2883de942283 git log 0bbf7ba9f909..2883de942283 --date=short --first-parent --format='%ad %ae %s' 2020-02-18 capn@google.com Fix sRGB conversion precision issues Created with: gclient setdep -r src/third_party/swiftshader@2883de942283 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 Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: Icf119c6bfe89903416c90e08c8ff473afac2febe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062308Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/389d9af998f3..1c25d4b5c206 git log 389d9af998f3..1c25d4b5c206 --date=short --first-parent --format='%ad %ae %s' 2020-02-18 ahassani@chromium.org xbuddy: Fix delta_payload artifact 2020-02-18 ahassani@chromium.org nebraska_wrapper: Fix health_check request to nebraska 2020-02-17 achuith@chromium.org vm: Add mocks for system attributes. Created with: gclient setdep -r src/third_party/chromite@1c25d4b5c206 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 Bug: None Tbr: chrome-os-gardeners@google.com Change-Id: I05987c5ca5d9d9918860cd642f8300ba87c2ddae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062310Reviewed-by:
-
Marc Treib authored
Also hand over ownership from treib@ to vasilii@ Bug: 1053095 Change-Id: I5511d845c7ac18c400b7f7791e43889777adb7b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2061811Reviewed-by:
Vasilii Sukhanov <vasilii@chromium.org> Reviewed-by:
Alex Ilin <alexilin@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#742166}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/KhronosGroup/glslang/+log/113d07a6ebda..ed0da37dd994 git log 113d07a6ebda..ed0da37dd994 --date=short --first-parent --format='%ad %ae %s' 2020-02-18 johnkslang@users.noreply.github.com Merge pull request #2087 from KhronosGroup/fix-2070-implicit-conv-single-arg Created with: gclient setdep -r src/third_party/glslang/src@ed0da37dd994 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/glslang-chromium-autoroll Please CC radial-bots+chrome-roll@google.com,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 Bug: None Tbr: radial-bots+chrome-roll@google.com,cwallez@google.com Change-Id: Ic77bbdd6cb0e6e3b973a206bd74a0a869da5ec01 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2061204Reviewed-by:
-
Tien Mai authored
This script will query extensions in the domain and generate a list of machines that have them installed. Change-Id: Ie70b982ca855b6364b4100f0b42adeee73f0b60a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2044331 Commit-Queue: Tien Mai <tienmai@chromium.org> Reviewed-by:
-
Mirko Bonadei authored
According to [1], -stdlib=libc++ should not be used in Chromium builds. [1] - https://bugs.chromium.org/p/chromium/issues/detail?id=1051010#c32 Bug: 1051010 Change-Id: Ied94f9b548994b8a21216f9e8cd0761704f6f85a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062331Reviewed-by:
-
Sergey Poromov authored
|enterprise.owned| == true is the same as |enterprise.mode| == "enterprise" || |enterprise.mode| == "enterprise_ad" || |enterprise.mode| == "demo_mode" from M19: https://crrev.com/9403010 All such old devices (pre-2012) are EOL: mario(56), alex(58), zgb(58), lumpy(65), stumpy(65), snow(75), parrot(69), stout(69). So we effectively can deprecate the field. See https://crrev.com/c/2043892 for Chrome OS change. TBR=antrim@chromium.org Bug: 725918 Test: Unit tests updated. Change-Id: I9c07991d09d1016b819015e5b8a3157de5d24e12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2043836 Commit-Queue: Sergey Poromov <poromov@chromium.org> Reviewed-by:
Maksim Ivanov <emaxx@chromium.org> Reviewed-by:
Igor <igorcov@chromium.org> Cr-Commit-Position: refs/heads/master@{#742162}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/5efe7f09dc4d..a8103c827183 Created with: gclient setdep -r src-internal@a8103c827183 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 Bug: None Tbr: jbudorick@google.com Change-Id: I016f95c9a57584ef96ff7606eaa6cc2ad3b412b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062155Reviewed-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@{#742161}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/27e0b30d80dd..526921b3db19 git log 27e0b30d80dd..526921b3db19 --date=short --first-parent --format='%ad %ae %s' 2020-02-18 eseckler@google.com producer ipc: Support startup tracing via producer SMB behind IPC Created with: gclient setdep -r src/third_party/perfetto@526921b3db19 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:147742905 Tbr: perfetto-bugs@google.com Change-Id: Iacbbedda03a9a31c5bc08d0c5e8b5f588be96f6b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062153Reviewed-by:
-
Miguel Casas-Sanchez authored
crrev.com/c/1828078 added and wired the video encode acceleration minimum resolution; this info is used from peerconnection's rtc_video_encoder.cc and video_codec_factory.cc to avoid using a hw accelerator for resolutions below the given one, if the appropriate flag is enabled. This CL enables the use of such mode by default on ChromeOS. TEST=https://codepen.io/miguelao/full/jONQBYb on kohaku, then inspecting chrome:webrtc-internals, verifying that resolutions below 321x241 are encoded using libvpx while larger ones are encoded using "VaapiVidoeEncodeAccelerator", i.e. the video encode accelerator in Chrome, in this case VA-API. Joining a Meet conference with a few bots and all working as expected, see https://imgur.com/a/B1713ID Bug: 1052352 Change-Id: I7def6906955bdce182a594f6092d462a25bd37a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057244Reviewed-by:
Florent Castelli <orphis@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Kentaro Hara <haraken@chromium.org> Auto-Submit: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#742159}
-
Fredrik Söderquist authored
Update the expectation for virtual/scalefactor200/css3/filters/effect-reference-image-hw.html since it appears to always be failing for the same reason as the other virtual/scalefactor200/css3/filters/effect-reference-image* tests (minor interpolation differences with the reference). Bug: 658305, 1051044 Change-Id: Idf9fe701f10b141a007d97681c5f88d1b6bca448 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2060959 Commit-Queue: Stephen Chenney <schenney@chromium.org> Auto-Submit: Fredrik Söderquist <fs@opera.com> Reviewed-by:
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/7f0638a9..ab52f9fd 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: I11d1c4954a3587509bdd5c12a9aff1bfebf1159f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2062090Reviewed-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@{#742157}
-
Bret Sepulveda authored
I investigated the tests that failed in this build: https://ci.chromium.org/p/chromium/builders/try/fuchsia_x64/496805 and noticed basically all of them are timeout-flaky on Fuchsia, filed under different bugs. So this patch marks all of them. Also marks some previously-marked tests as also crashing. TBR=wez@chromium.org Bug: 1050893, 1051014, 1051370, 1051015, 1050995, 1051774, 1051133, 1051131, 1053512 Change-Id: Ib7e72afeb426612b32a60702c1b4505be29d6520 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2061758 Commit-Queue: Bret Sepulveda <bsep@chromium.org> Reviewed-by:
-
Nohemi Fernandez authored
This CL is part of a series of refactors to move the existing sign-in architecture to the Coordinator-Mediator design paradigm. Fore more information, see go/chrome-ios-signin-migration. Bug: 971989 Change-Id: I3131d6f20fa230b1c55cf9f979d3ed34aa38ccc4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2047249 Commit-Queue: Nohemi Fernandez <fernandex@chromium.org> Reviewed-by:
Jérôme Lebel <jlebel@chromium.org> Cr-Commit-Position: refs/heads/master@{#742155}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/f0e349172618..fced1b9a3942 git log f0e349172618..fced1b9a3942 --date=short --first-parent --format='%ad %ae %s' 2020-02-18 tvanderlippe@chromium.org Remove typedefs from timeline{_model}-legacy.js 2020-02-18 tvanderlippe@chromium.org Remove typedefs from web_audio-legacy.js 2020-02-18 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. Created with: gclient setdep -r src/third_party/devtools-frontend/src@fced1b9a3942 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:1006759 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Id1c31fc2799d40e72112174ebf0e2d4c63032c87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2061662Reviewed-by:
-
Wez authored
Migrate dependencies on SDK-provided prebuilt & C++ libraries to refer directly to the SDK-provided GN targets, rather than the old Chromium- generated rules. TBR=jochen Bug: 1050703 Change-Id: Ifc200463791e71763d04de3e3cdd394404bdfedb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059008Reviewed-by:
Wez <wez@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Commit-Queue: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#742153}
-
David Bienvenu authored
Change-Id: I1ddb17a4a89ddc44556d65ed8468c572f6f05bba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059534Reviewed-by:
-
Rune Lillesveen authored
The shape, forced-colors, and navigation-controls media features were accepted without a value, even if their runtime flags were disabled. Bug: 1051617 Change-Id: Ifc3c3976ac5bccc406ff327a120dd364ea674bb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2061253 Commit-Queue: Rune Lillesveen <futhark@chromium.org> Reviewed-by:
Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#742151}
-
Ilya Nikolaevskiy authored
Bug: 1027108 Change-Id: Idb394958879058c2e05da571ca4ba5f684ddd1aa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2060976 Commit-Queue: Ilya Nikolaevskiy <ilnik@chromium.org> Commit-Queue: Robert Kaplow <rkaplow@chromium.org> Auto-Submit: Ilya Nikolaevskiy <ilnik@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#742150}
-
Fredrik Söderquist authored
Bug: 658305 Change-Id: Ie12b6cd1c0e1c7b9fa5625454e25586c1d723311 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2061250 Auto-Submit: Fredrik Söderquist <fs@opera.com> Reviewed-by:
-
Antonio Gomes authored
This mojo message is sent to both blink::LocalFrame and blink::RemoteFrame. As a follow up, all calls to blink::FramePolicy will be converted to blink::mojom::FramePolicy. It will allow t_p/blink/common/frame/frame_policy.typemap and the respective traits files to be removed. Bug: 1047272 R=dtapuska@chromium.org, haraken@chromium.org, kinuko@chromium.org Change-Id: I9256ebd346ccb0238579152bb3d0648326528a41 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057012Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
-
Clemens Arbesser authored
This CL allows the CollectUserData action to surface generic UI which contains mandatory sections. Since currently chips can't be directly controlled by the generic UI framework, this is done with change in the action itself. In the future, this workaround will be removed. This CL also adds logical operations to the set of supported interactions. Bug: b/145043394 Change-Id: I269d44620a2b194dc3218feebfd16f38d592ecdd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2036100 Commit-Queue: Clemens Arbesser <arbesser@google.com> Reviewed-by:
-
