- 15 Jan, 2021 40 commits
-
-
Stepan Khapugin authored
Puts dispatcher to a special mode where it pretends to recognize all selectors and silently fail on shutdown. Bug: 1137686, 1163129 Change-Id: Ib065d7f564f22c5be2285201d5dcd9dea39f60d1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2472039 Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org> Cr-Commit-Position: refs/heads/master@{#844126}
-
Bence Béky authored
https://quiche.googlesource.com/quiche.git/+log/e84d83393be4..9aef115356ce $ git log e84d83393..9aef11535 --date=short --no-merges --format='%ad %ae %s' 2021-01-14 quiche-dev Fixes test flakiness by forcing the test client to reconnect after fuzzed requests. 2021-01-14 renjietang In QuicConnection, cancel the previous path validation request before starting a new one. 2021-01-14 mattm Send correct QUIC CRYPTO_ERROR connection error for TLS errors 2021-01-14 renjietang In http/end_to_end_test, use live client address to send STATELESS_RESET. 2021-01-14 wub Minor tweaks to TlsServerHandshaker: - Change TlsServerHandshaker::SelectCertStatus() to TlsServerHandshaker::select_cert_status(). - Set expected_ssl_error to SSL_ERROR_WANT_READ in OnSelectCertificateDone(). - Add a test for async select cert and async signature. 2021-01-14 wub In crypto_test_utils, move connection close frame between two test connections. This allows tests to check connection close errors on both ends. 2021-01-14 wub Add a flag count for --gfe2_restart_flag_quic_tls_prefer_server_cipher_and_curve_list. Created with: roll-dep src/net/third_party/quiche/src src/third_party/quic_trace/src Change-Id: I3f634a094103c70bf9db30bae3646a740f6202ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633321 Auto-Submit: Bence Béky <bnc@chromium.org> Commit-Queue: Renjie Tang <renjietang@chromium.org> Reviewed-by:
Renjie Tang <renjietang@chromium.org> Cr-Commit-Position: refs/heads/master@{#844125}
-
Hongchan Choi authored
The Finch setting might not be activated for some cases, and we want to provide developers with thread priority information via chrome://tracing. Bug: 1165842 Change-Id: I50cf618587acb8ce01237c894a21ad4965e22a62 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631288Reviewed-by:
Raymond Toy <rtoy@chromium.org> Auto-Submit: Hongchan Choi <hongchan@chromium.org> Commit-Queue: Hongchan Choi <hongchan@chromium.org> Cr-Commit-Position: refs/heads/master@{#844124}
-
Junbo Ke authored
Previously no cookie settings were provided when NetworkContext was created, and the default in-memory cookie store was used. Provide a cookie path so that the on-disk cookie store is used. Bug: internal b/177479549 Test: Launch YT on device and verified cookies survived reboot. Change-Id: Icf6ac063ffc0fc13de36bb6dd6b62edc8e4496a5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631358Reviewed-by:
Luke Halliwell (slow) <halliwell@chromium.org> Commit-Queue: Junbo Ke <juke@chromium.org> Cr-Commit-Position: refs/heads/master@{#844123}
-
Caitlin Fischer authored
The experiment launched. Bug: 1126640 Change-Id: I674ef2336f3f22cf3859775805ec7997a4308281 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631929Reviewed-by:
Yann Dago <ydago@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#844122}
-
Dave Tapuska authored
Convert FrameHostMsg_DidCreateOutOfProcessPepperInstance and FrameHostMsg_DidDeleteOutOfProcessPepperInstance to mojo messages. These messages can use the PepperBrowserConnection The implementation for RenderFrameMessageFilter can move into the pepper subclasses themselves. BUG=1157519 Change-Id: Ic051729ed0edf99d5bd8165fe5d4d5e21b3cf42c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626413 Commit-Queue: Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Arthur Sonzogni <arthursonzogni@chromium.org> Reviewed-by:
Bill Budge <bbudge@chromium.org> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/master@{#844121}
-
Michael Ershov authored
* Delete default constructors in mock callback observers because writing them explicitly doesn’t change anything. * Make `MockDeviceManagementService service_` a strict mock so we don’t need to have EXPECT_CALL().Times(0) in many test. * Change some `EXPECT_CALL(..., Func(_))` into `EXPECT_CALL(..., Func)` where checking arguments is not useful. * Remove some arguments from Expect* functions where they were unused. * Extract creation of policy_response into a standalone function to create it only when necessary and decrease implicit dependencies. * Reformat the file. Bug: 1150887 Test: CloudPolicyClientTest* Change-Id: I3c150a59161a6272d37f19234520a8ac9cb850ea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2550032 Commit-Queue: Michael Ershov <miersh@google.com> Reviewed-by:
Pavol Marko <pmarko@chromium.org> Cr-Commit-Position: refs/heads/master@{#844120}
-
Eric Orth authored
Updating everything to match the latest style guide preferences, mostly using references much more liberally and converting output params to returns wherever reasonable. Also switching from copies to moves in a couple places that I happened to notice, and a couple more random cleanups to make Tricium happy. Change-Id: I999f511835e70e61ee8c0e7c5dd7e6b7f2396aea Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626786Reviewed-by:
Matt Menke <mmenke@chromium.org> Commit-Queue: Eric Orth <ericorth@chromium.org> Cr-Commit-Position: refs/heads/master@{#844119}
-
chinsenj authored
Currently, the ChromeVox behavior is broken. It doesn't echo typed text, nor does it read out typed text. This CL fixes ChromeVox behavior by calling Textfield::GetAccessibleNodeData() in DeskNameView::GetAccessibleNodeData(). Test: manual Bug: 1166732, 1166693 Change-Id: I54306c8b3ea02000aef7663ace32ffd314d5c235 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632045Reviewed-by:
Ahmed Fakhry <afakhry@chromium.org> Commit-Queue: Jeremy Chinsen <chinsenj@chromium.org> Cr-Commit-Position: refs/heads/master@{#844118}
-
Joshua Pawlicki authored
Inflated distributions are useful for running A/B tests to understand the impact of shipping larger binaries. Bug: 1154844 Change-Id: Ifdfeeb200b58174e5c3e7f346ecf013780111d25 Fixed: 1154844 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625888 Commit-Queue: Joshua Pawlicki <waffles@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Cr-Commit-Position: refs/heads/master@{#844117}
-
Scott Violet authored
This generally should only happen if the renderer is compromised. BUG=none TEST=none Change-Id: I88d522e1e5f3f557c7f976541b6dc50fb0cfed81 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631296Reviewed-by:
Shimi Zhang <ctzsm@chromium.org> Commit-Queue: Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#844116}
-
Caitlin Fischer authored
The server-side configs show that these studies have launched. Bug: 1126640 Change-Id: I29f802ad203fecc0eab77f68df169e11d02099c0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631433Reviewed-by:
Becca Hughes <beccahughes@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#844115}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1610690109-0f7956766f9641d6835b78b89edaf84f3a491ef2.profdata to chrome-win32-master-1610711423-66d1757656af1c1220147c4ed72bfc529787f050.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win32-chromium Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I385df950dcf035cdf4d92d0aee7e6726f79f47e4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632836Reviewed-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@{#844114}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/5678b56f5e21..d2e76b73efc2 2021-01-15 angle-autoroll@skia-public.iam.gserviceaccount.com Roll SwiftShader from 5255c465bbba to aedd133cd85f (1 revision) 2021-01-15 angle-autoroll@skia-public.iam.gserviceaccount.com Roll vulkan-deps from 5869a809d551 to 7b69f3d087b8 (5 revisions) 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/+doc/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: I68ed451d3ee283335eeccf2a0ad54769072448cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632837Reviewed-by:
-
David Maunder authored
Speedup: 2783ms -> 36ms (99% speedup) Bug: 1166919 Change-Id: If7b9e406fb5c1ce46e4a224542fe0ab60ee34c32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631227 Commit-Queue: David Maunder <davidjm@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Cr-Commit-Position: refs/heads/master@{#844112}
-
Monica Basta authored
Before this CL only the icon with the '+' was clickable. The full card should be clickable. Fixed: 1167120 Change-Id: I4c326ad8c17fc34425ed3cb9934304eac801777a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632668 Commit-Queue: Monica Basta <msalama@chromium.org> Reviewed-by:
David Roger <droger@chromium.org> Cr-Commit-Position: refs/heads/master@{#844111}
-
Yusuke Sato authored
BUG=None TEST=try Change-Id: Ic3983403036f8e11749c7969dddd027e8e46d820 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632391Reviewed-by:
-
Etienne Pierre-doray authored
We're seeing jank in LookalikeUrlService::OnFetchEngagedSites from uma sampling profiler. There's a few possible culprits: - First call to GetDomainInfo causes icu loading - url_formatter::GetSkeletons is expensive and called on many urls - IsEngagementAtLeast is expensive and called on many urls To better understand the problem, this CL adds relevant trace events and records count of engaged sites as UMA histogram. Bug: 1135279 Change-Id: Ie6ee4ed2dbeeed26e4bbdd72726a0ad48e9bc4bf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2615322Reviewed-by:
Etienne Bergeron <etienneb@chromium.org> Reviewed-by:
Weilun Shi <sweilun@chromium.org> Reviewed-by:
Joe DeBlasio <jdeblasio@chromium.org> Commit-Queue: Etienne Pierre-Doray <etiennep@chromium.org> Cr-Commit-Position: refs/heads/master@{#844109}
-
Yi Gu authored
Seems due to crrev.com/c/2500441. See linked bug for details. Bug: 1167158 Change-Id: I266c816d846fe6b90c65b5d77c9a4f65714c01b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633362Reviewed-by:
Anatoliy Potapchuk <apotapchuk@chromium.org> Reviewed-by:
David Bertoni <dbertoni@chromium.org> Commit-Queue: Yi Gu <yigu@chromium.org> Cr-Commit-Position: refs/heads/master@{#844108}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/6d70b13800e9..3100aca993ac 2021-01-15 andoli@chromium.org [module.json extensions] inspector_main views 2021-01-15 andoli@chromium.org [module.json extensions] Add unit tests for new setting extensions registration infrastructure 2021-01-15 andoli@chromium.org [module.json extensions] input views 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/+doc/master/autoroll/README.md Bug: chromium:1134103,chromium:1153091 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: Iae558ac5090f680299e965c86f09daea6ee43f12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633523Reviewed-by:
-
Yusuke Sato authored
BUG=None TEST=try Change-Id: Iaa6fcf9e406da1f88470cd78843960880c9abfab Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631629Reviewed-by:
-
Kuo-Hsin Yang authored
Checking path existence in procfs is fast, it's not necessary to use ScopedAllowIO. Bug: 1166221 Change-Id: I60ec3f5865239ba426f3064ce5a05d6688320de8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631807 Commit-Queue: Brian Geffon <bgeffon@chromium.org> Reviewed-by:
Brian Geffon <bgeffon@chromium.org> Cr-Commit-Position: refs/heads/master@{#844105}
-
ssid authored
ASYNC* version is deprecated. No functional change should be visible in trace. Perf sheriffs: This might affect input latency metrics in telemetry. Change-Id: I2fdadeb4ae8c72af28e39a35927cb995408ee995 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625968 Auto-Submit: ssid <ssid@chromium.org> Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#844104}
-
ckitagawa authored
After landing flake fixes for Win/Linux I suspect this is also no longer an issue on Mac. Bug: 1160608 Change-Id: I22313baee7d82ac159ba62417fac0ca4a3cd704d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628107 Auto-Submit: Calder Kitagawa <ckitagawa@chromium.org> Commit-Queue: Mehran Mahmoudi <mahmoudi@chromium.org> Reviewed-by:
Mehran Mahmoudi <mahmoudi@chromium.org> Cr-Commit-Position: refs/heads/master@{#844103}
-
Guillaume Jenkins authored
The Spellcheck.MisspellRatio and Spellcheck.ReplaceRatio histograms haven't been in use for some time. The code path to send samples is not being called. This CL marks them as obsolete and removes the corresponding UMA macros. Bug: 1165190 Change-Id: I7528d308506dc5011ba3f5958546112dd765ec69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628932Reviewed-by:
Caitlin Fischer <caitlinfischer@google.com> Commit-Queue: Guillaume Jenkins <gujen@google.com> Cr-Commit-Position: refs/heads/master@{#844102}
-
Yaron Friedman authored
BUG=783819 Change-Id: Ie7686169b0fb30050c83bbce42c42accc810e982 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618181Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#844101}
-
Ramya Nagarajan authored
BUG=1072583,1138380,1138379,1138378,1138377,1138376,1138375,1138315,1158019 Change-Id: I77e6b1879ac8e2bef70975ee7f23c58cf8cc1487 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2626147Reviewed-by:
Jeffrey Cohen <jeffreycohen@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Ramya Nagarajan <ramyan@chromium.org> Cr-Commit-Position: refs/heads/master@{#844100}
-
Jarryd authored
This makes debugging a test and writing tests a little easier by allowing developers to run a single test at a time. * Add new chrome switch, kWebAppIntegrationTestCase * Add new method, GetCommandLineTestOverride() Bug: 1165832 Change-Id: I739c1fc85b115e77b881fcdab87db06ab01cf074 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2624033 Commit-Queue: Jarryd Goodman <jarrydg@chromium.org> Reviewed-by:
Daniel Murphy <dmurph@chromium.org> Cr-Commit-Position: refs/heads/master@{#844099}
-
Jon Mann authored
Chrome doesn't yet track the "Automatic" state for the metered property of networks. To avoid setting networks permanently to the current automatic state, this change temporarily marks all networks as auto until we can get the information from Shill. Bug: 1128692 Change-Id: I2a7295ed9cdfb106b5c3b894d0963b006046bfbc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631469 Commit-Queue: Steven Bennetts <stevenjb@chromium.org> Reviewed-by:
Steven Bennetts <stevenjb@chromium.org> Auto-Submit: Jon Mann <jonmann@chromium.org> Cr-Commit-Position: refs/heads/master@{#844098}
-
Alison Maher authored
Set the ForcedColors flag to 'stable' and update test expectations. This includes the launch of the 'forced-colors' media query and the 'forced-color-adjust' CSS property. Intent-to-ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/hkjRPJ1-Ruk Note: There is an open blocking bug for this feature. It is blocked on a spec issue, but this should be resolved next week, and I will make sure the resulting fix gets backported to the correct release. https://bugs.chromium.org/p/chromium/issues/detail?id=1166392 Bug: 970285,1148418 Change-Id: I7eeedf57f1dc66a6935ab153d166ea9718b27e8c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630827Reviewed-by:
Chris Harrelson <chrishtr@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Commit-Queue: Alison Maher <almaher@microsoft.com> Cr-Commit-Position: refs/heads/master@{#844097}
-
Josh Karlin authored
FCP can be delayed due to x-site frames being render throttled. Bug: 1166207 Change-Id: I0f0eef93f4f8decb556eb079df453ae1ad21fe60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627707 Commit-Queue: Josh Karlin <jkarlin@chromium.org> Reviewed-by:
John Delaney <johnidel@chromium.org> Cr-Commit-Position: refs/heads/master@{#844096}
-
Raphael Kubo da Costa authored
Screen Wake Locks were marked as a stable feature in r763697 ("[wakelock] Mark ScreenWakeLock feature as stable"), so it is no longer necessary to manually enable it support for them here. Change-Id: I69b0578349918bd9701788cc3c792c457f506f55 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633052 Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Commit-Queue: Alexander Timin <altimin@chromium.org> Auto-Submit: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com> Reviewed-by:Alexander Timin <altimin@chromium.org> Cr-Commit-Position: refs/heads/master@{#844095}
-
chromium-internal-autoroll authored
Release_Notes: http://go/help_app-x20/relnotes/Main/help_app_nightly_202101150600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/help_app/app/+/BhbSyh4bjbYmwfA5WJTXzE9uMvDFyyviZuft_yjZ8ZgC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/help-app-chromium-autoroll Please CC help-app@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: b/174321021 Tbr: help-app@grotations.appspotmail.com Change-Id: I152d627b49e367683919a87128bf544689b175b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633381Reviewed-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@{#844094}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/628b7f61f813..5fcf0fa9382e 2021-01-14 pmoy@chromium.org chromite: expect hotlog user in hotline group on cfm devices 2021-01-14 chrome-bot@chromium.org Update config settings by config-updater. 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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:chromeos-betty-pi-arc-chrome;luci.chromium.try:chromeos-kevin-rel Tbr: chrome-os-gardeners@google.com Change-Id: Ib99f592b202ac50ed6bf63242a1d27ddfb9e9422 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633384Reviewed-by:
-
Adithya Srinivasan authored
Bug: 1146627 Change-Id: Idb2ca2ba5a1053fd0439dbb473c797b53fb2ac18 Tbr: jdonnelly@chromium.org Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2630366Reviewed-by:
David Van Cleve <davidvc@chromium.org> Reviewed-by:
Justin Donnelly <jdonnelly@chromium.org> Commit-Queue: Adithya Srinivasan <adithyas@chromium.org> Cr-Commit-Position: refs/heads/master@{#844092}
-
Yi Gu authored
See linked bug for details. TBR=tvanderlippe@chromium.org Bug: 1167158 Change-Id: Ief155b70c1a8c0ecbc306b71665918416e347315 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633342Reviewed-by:
-
Aaron Leventhal authored
Also add TODOs for Nektarios on next round of fixes to this code. Bug: None Change-Id: I1ce3184ab3caed82746c6e06e0dc81c249f9f600 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633341 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Auto-Submit: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by:
Nektarios Paisios <nektar@chromium.org> Cr-Commit-Position: refs/heads/master@{#844090}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202101150600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/xO6b6gm3QxUDRY3PGCD_ON0uPe2bjwP9ftauSv0ar3cC If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/media-app-chromium-autoroll Please CC media-app@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: b/138543581,b/157694064,b/173979544,b/175515520,b/175517195,b/177375485,b/177381582,b/177382762,b/177388943,b/177620087 Tbr: media-app@grotations.appspotmail.com Change-Id: Iabc1617da20640879cbc7b957589075b34345376 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633132Reviewed-by:
-
Regan Hsu authored
The EOL dates listed at https://support.google.com/chrome/a/answer/6220366?hl=en do not provide a timezone. However, they refer to UTC instead of a local time zone. (End of life occurs at a single point in time). Since users are NOT told that the time zone is in UTC, they will likely confuse the end of life date to be in their local timezone. If the end of life is on the first day of the month, the end of life will show as one month sooner than the actual end of life. This CL adds an extra parameter to base::TimeFormatMonthAndYear() to allow for time formatting in UTC instead of the local time. Fixed: 1126296 Change-Id: Iede26508a9a30e776225095bd6267bd2c2fe64eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2399826 Commit-Queue: Regan Hsu <hsuregan@chromium.org> Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Cr-Commit-Position: refs/heads/master@{#844088}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1610700976-d7ed4801f0bf655f1a5ed007c5aa96678f4cba28.profdata to chrome-win64-master-1610711423-bdaee35d021c9a50df10abe9e0067f035c4386a3.profdata If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pgo-win64-chromium Please CC pgo-profile-sheriffs@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/+doc/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:win64-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: Ie5929fa024e688cfba5623b55d1b6986a9526ce7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632833Reviewed-by:
-
