- 21 Jan, 2021 40 commits
-
-
Kushagra Sinha authored
Simplify version checks in AccountManagerFacadeImpl by using the synchronous version accessor in LacrosChromeServiceImpl Change-Id: I7a83a352f10977e0d3ce1d84528d76726688016c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640436 Commit-Queue: Kush Sinha <sinhak@chromium.org> Reviewed-by:
James Cook <jamescook@chromium.org> Cr-Commit-Position: refs/heads/master@{#845656}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/d5c88e60cff4..e41b3bb941a6 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 anastasiian@google.com,lgrey@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:linux-chromeos-chrome Bug: chromium:1151505,chromium:1168777 Tbr: anastasiian@google.com,lgrey@google.com Change-Id: Ie2a7475cdd16ee3408efc18cbf58cb924e940be7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642808Reviewed-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@{#845655}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202101210600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/VfjLSnBpe5wh7h4SqNeUqE6zmybZ1Sebm0S0ltU1uCoC 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/172415656,b/173070498,b/174442020,b/174603791,b/177856222 Tbr: media-app@grotations.appspotmail.com Change-Id: Ia85aa41caab1be804448ac4645a16aabc7a71c2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642806Reviewed-by:
-
stkhapugin authored
Track the session as open while there is at least one foreground window. Log this in a dedicated app agent to avoid polluting AppState. The same is done to IOSProfileSessionDurationsService's session start/end events. Bug: 1156586 Change-Id: I37586f989039206fbaa90f7ec4046fbf9582e70a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2599870 Commit-Queue: Stepan Khapugin <stkhapugin@chromium.org> Auto-Submit: Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Mihai Sardarescu <msarda@chromium.org> Reviewed-by:
Mark Cogan <marq@chromium.org> Cr-Commit-Position: refs/heads/master@{#845653}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/87a055b02027..e0d023562bd9 2021-01-21 johnstiles@google.com Remove obsolete reference to Flex lexer. 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 scroggo@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-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 Cq-Do-Not-Cancel-Tryjobs: true Bug: None Tbr: scroggo@google.com Change-Id: I4e2ccf610c033e37b20c81e03711b7215b8afc9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642819Reviewed-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@{#845652}
-
Leonard Grey authored
This reverts commit cfd230fd. Reason for revert: Speculative due to https://crbug.com/1169160 Original change's description: > Files app: Enable JS modules by default > > Bug: 1133186 > Change-Id: I4a92f4f60ce7b98ef3bc8f35e115eab428dda298 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639351 > Commit-Queue: Luciano Pacheco <lucmult@chromium.org> > Reviewed-by: Jeremie Boulic <jboulic@chromium.org> > Cr-Commit-Position: refs/heads/master@{#845564} TBR=lucmult@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com,jboulic@chromium.org Change-Id: I62ac3ac7851d7e7e5fa52f944c2d8e6ab3b2705a No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 1133186 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2643021Reviewed-by:
Leonard Grey <lgrey@chromium.org> Commit-Queue: Leonard Grey <lgrey@chromium.org> Cr-Commit-Position: refs/heads/master@{#845651}
-
Robert Flack authored
The reporting code no longer exists, and we haven't noticed missing this histogram so it should be safe to expire. Bug: 1089338 Change-Id: Iab50286cbdb4ddb3d403df83b6bfddafc50dd236 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640750Reviewed-by:
Glenn Hartmann <hartmanng@chromium.org> Reviewed-by:
Ilya Sherman <isherman@chromium.org> Commit-Queue: Robert Flack <flackr@chromium.org> Cr-Commit-Position: refs/heads/master@{#845650}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/f9033fa039cd..30152edff696 2021-01-21 szuend@chromium.org Add Trust Token pane in the Application Panel 2021-01-21 tvanderlippe@chromium.org Add network as dependency of security 2021-01-21 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools DEPS. 2021-01-21 petermarshall@chromium.org Typo fix in DataGrid 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:1126824 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I97115767363db6b75a0576d4e8b996b0579dfa3a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642740Reviewed-by:
-
Robert Flack authored
We have been actively using these metrics to identify areas to invest scrolling improvements in and to gauge the success of improvements to scrolling. Bug: 1089343 Change-Id: I7fe4a4e76349259ca7b245c0653497a712434aa0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640643 Commit-Queue: Robert Flack <flackr@chromium.org> Reviewed-by:
-
Jan Wilken Dörrie authored
This change prepares //net/proxy_resolution/win for the switch of base::string16 to std::u16string. Bug: 911896 Change-Id: If58c61761969fa355bea533d87b70e393951c7c9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642146 Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org> Reviewed-by:
Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/master@{#845647}
-
Dominik Röttsches authored
According to b/177801059 and b/178006074 issues are resolved that had the the mirror repository flip-flopping between syncing the old and the new upstream source of truth, compare https://crbug.com/1168536. Relanding the forward roll. https://chromium.googlesource.com/chromium/src/third_party/freetype2.git/+log/03ceda9701cd..b594cd90bd05 $ git log 03ceda970..b594cd90b --date=short --no-merges --format='%ad %ae %s' 2021-01-19 apodtele * srd/base/ftlcdfil.c (FT_Library_SetLcdGeometry): Fix return value. 2021-01-15 madigens [afshaper] Fix hb_ot_tags_from_script deprecation warning. 2021-01-17 wl * src/tools/update-copyright-year: Fix single-year entry handling. 2021-01-17 wl Update all copyright notices. 2021-01-17 wl no-copyright: Updated. 2021-01-16 apodtele * builds/unix/unixddef.mk: Remove the second DEVEL_DIR definition. 2021-01-16 wl Documentation update for repository move to 'freedesktop.org'. 2021-01-16 wl .gitattributes: New file. 2021-01-16 wl README, README.git: First updates due to freedesktop.org migration. 2021-01-15 drott CHANGES: Mention 'COLR' v1 support. 2021-01-15 wl [sfnt] Additional checks for 'colr' table presence. 2021-01-14 drott Add config option to test for 'COLR' v1 support in headers. 2020-12-16 drott [base] Fill 'COLR' v1 API templates to make them work (#59703). 2020-12-16 drott [sfnt] Register 'COLR' v1 API in driver (#59703). 2020-12-16 drott [sfnt] Add 'COLR' v1 API to retrieve color layers (#59703). 2020-12-16 drott [sfnt] Add 'COLR' v1 API to iterate color stops (#59703). 2020-12-16 drott [sfnt] Add API to get actual paint from `FT_OpaquePaint` (#59703). 2020-12-16 drott [sfnt] Add API to retrieve 'COLR' v1 root paint (#59703). 2020-12-16 drott Add new methods required for 'COLR' v1 to public API (#59703). 2020-12-16 drott Add types required for 'COLR' v1 to public API (#59703). Created with: roll-dep src/third_party/freetype/src R=bungeman@chromium.org,drott@chromium.org Cq-Include-Trybots: luci.chromium.try:linux_chromium_msan_rel_ng Bug: 1167653 Change-Id: I29c46d893fff921fe8bb029466906d97b1c4a371 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642345 Commit-Queue: Ben Wagner <bungeman@chromium.org> Reviewed-by:
Ben Wagner <bungeman@chromium.org> Cr-Commit-Position: refs/heads/master@{#845646}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/099b043d..ee9fbcba 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: I9160dcc900ab1efc1ba3dc323074cd6556ca2845 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642739Reviewed-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@{#845645}
-
Michael Lippautz authored
A past refactoring translated `unique_ptr<TaskRunnerTimer>` to `Member<DisallowNewWrapper<HeapTaskRunnerTimer>>` to preserve semantics. Inline HeapTaskRunnerTimer which avoids a dynamic allocation. Change-Id: I8a859c068c9889b5e2bafb01619138ad2f1e0e59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642326Reviewed-by:
Kentaro Hara <haraken@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#845644}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1611219467-221ce2b3efda04c3b102ac62c26b5f5a8e2aaa76.profdata to chrome-win64-master-1611230296-6b85df13abed72480b96a917e46b214e59288b63.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: If8a4925fe78ed1255a1d4c902e309091ed763ae9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642916Reviewed-by:
-
Wojciech Dzierżanowski authored
MediaPlayerId objects are supposed to be unique browser-wide. A well-behaved renederer process will not try to reuse them. Bug: 1168737 Change-Id: Iaa1d54face4bd475d6df8a00d282a5b88242b735 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640381Reviewed-by:
Chrome Cunningham <chcunningham@chromium.org> Commit-Queue: Wojciech Dzierżanowski <wdzierzanowski@opera.com> Cr-Commit-Position: refs/heads/master@{#845642}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1611219467-390b4abe6a87e7c94cab88849ad56f5359438186.profdata to chrome-win32-master-1611230296-c6265b318ac69ceb3057c4103fbc67710d80a9da.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: I1f7848ef05366ca74c969e7ba1b4df16b2b0a0f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642817Reviewed-by:
-
Danila Kuzmin authored
Bug: 1159859 Change-Id: I86c4e4f96c3d2fba164983f4017370e6c3e1f006 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627423Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Reviewed-by:
Roman Aleksandrov <raleksandrov@google.com> Commit-Queue: Danila Kuzmin <dkuzmin@google.com> Cr-Commit-Position: refs/heads/master@{#845640}
-
danakj authored
We do this in unit tests already, which found some expensive waste. We have many browser tests which fail with timeouts during shutdown flakily. In order to diagnose and fix these, we need to know what task is running that is blocking shutdown. We can do that by using the TestTaskTracker in the ThreadPoolInstance. In order to use TestTaskTracker, we must have the browser test launcher able to override the creation of the ThreadPoolInstance. So we change the ContentBrowserClient API to be responsible for that creation, instead of just a query about whether it should be created or not. And we inject a test-only ContentBrowserClient that creates a ThreadPoolInstance through the base::Test::TaskEnvironment. We add tracking of the posted_from location of all running tasks in the TestTaskTracker, and introduce a timeout during shutdown. If the timeout is hit, we log all of the running tasks. Bug: 811470 Change-Id: I9f33a8224ab73f436656915f4a26067b1b7b5b9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2505733Reviewed-by:
Avi Drissman <avi@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Reviewed-by:
Ted Choc <tedchoc@chromium.org> Reviewed-by:
Gabriel Charette <gab@chromium.org> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: danakj <danakj@chromium.org> Cr-Commit-Position: refs/heads/master@{#845639}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/9f4b159b7aa0..f28a06ba7281 2021-01-21 angle-autoroll@skia-public.iam.gserviceaccount.com Roll vulkan-deps from 3180f85f9bcd to f646afdb8929 (2 revisions) 2021-01-21 angle-autoroll@skia-public.iam.gserviceaccount.com Roll Chromium from 13257563 to 67fb6a84 (480 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 cnorthrop@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: cnorthrop@google.com Change-Id: Iabf5e01bc6fc9917ffb6028695cb1f28a0397740 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642797Reviewed-by:
-
Oleg Davydov authored
This commit moves expire date of the following histograms: * Extensions.ForceInstalledManifestFetchFailedHttpErrorCode2 * Extensions.ForceInstalledReadyTime * Extensions.ForceInstalledStage2 The expire date is now in sync with other histograms owned by our team (Extensions.Force*). Bug: 1165254, 1165255 Change-Id: Ie7d7ce0e96fe813321f7dbab53b1667bdf82bc4c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642366 Auto-Submit: Oleg Davydov <burunduk@chromium.org> Commit-Queue: Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Cr-Commit-Position: refs/heads/master@{#845637}
-
Julie Jeongeun Kim authored
On the current code, even though |preview_ui_| is checked before calling CheckForCancel(), the renderer could not get the reply as the print WebUI dialog is already closed on the browser. If then, the renderer gets blocked. Since CheckForCancel() is called multiple times while handling the print preview request and |preview_ui_| could be disconnected once the print WebUI is closed, this change moves CheckForCancel() to mojom::PrintManagerHost as PrintViewManager which implements it is alive while WebContents is available. Bug: 1166492, 1167170, 1008939 Change-Id: Iffc5d5354be3778ec7f33cff11051858432b5bf0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632023Reviewed-by:
Eric Seckler <eseckler@chromium.org> Reviewed-by:
Sam McNally <sammc@chromium.org> Reviewed-by:
Dave Tapuska <dtapuska@chromium.org> Reviewed-by:
Rebekah Potter <rbpotter@chromium.org> Commit-Queue: Julie Kim <jkim@igalia.com> Cr-Commit-Position: refs/heads/master@{#845636}
-
David Jean authored
BVC would start an activity overlay when shutting down, creating a never ending animation. Bug: 1143708 Change-Id: I7654a7430325601fd71f7ba4b789b3c663b40353 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2637701Reviewed-by:
Stepan Khapugin <stkhapugin@chromium.org> Reviewed-by:
Zhaoyang Li <zhaoyangli@chromium.org> Commit-Queue: David Jean <djean@chromium.org> Cr-Commit-Position: refs/heads/master@{#845635}
-
Hans Wennborg authored
New Clang warns on calling free() on stack objects by default. Bug: 1169073 Change-Id: I9f89e389308060b424832cfc400b2fef5c104120 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642145 Auto-Submit: Hans Wennborg <hans@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Reviewed-by:
Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#845634}
-
Ben Mason authored
Change-Id: I3c8d8d7c7db20be57c28f8ff0f04c13bf3cde9df Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642856 Auto-Submit: Ben Mason <benmason@chromium.org> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#845633}
-
Bret Sepulveda authored
This patch creates a vector_icons target for components/permissions so that we can move there any icons not used anywhere else. The two existing icons for which this is true are accessibility.icon and usb_security_key.icon. Bug: 1110905 Change-Id: I13f6d2c9c54aabcae8beeb5d14ee40263c8ff62d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2637598 Commit-Queue: Bret Sepulveda <bsep@chromium.org> Reviewed-by:
Illia Klimov <elklm@chromium.org> Reviewed-by:
Andy Paicu <andypaicu@chromium.org> Reviewed-by:
Evan Stade <estade@chromium.org> Cr-Commit-Position: refs/heads/master@{#845632}
-
Danil Chapovalov authored
Change Log: https://chromium.googlesource.com/external/github.com/abseil/abseil-cpp/+log/322ae2420d..b2dcbba183 Full diff: https://chromium.googlesource.com/external/github.com/abseil/abseil-cpp/+/322ae2420d..b2dcbba183 Bug: None Change-Id: I7f4a4235d5eb8b57bfbdb0e07039f975c76b7e6c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640441Reviewed-by:
Mirko Bonadei <mbonadei@chromium.org> Commit-Queue: Danil Chapovalov <danilchap@chromium.org> Cr-Commit-Position: refs/heads/master@{#845631}
-
Michael Lippautz authored
This adds write barriers for - TraceWrapperV8Reference (C++->JS) - Embedder fields (JS->C++) Depends on https://crrev.com/c/2640419 Bug: chromium:1056170 Change-Id: I79c5e7242d0ff8b83579a5258970436df6026ee8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640618Reviewed-by:
Omer Katz <omerkatz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#845630}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1611208290-983521cb9aa454798e29d76ad68922e8cdd2db84.profdata to chrome-mac-master-1611230296-dcf016b3b57961245ab4f6b250bc80f143758478.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-mac-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:mac-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: If0e7d15bdb731dd2626420883771495428cfce7e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642799Reviewed-by:
-
Anastasiia N authored
TBR=sky@chromium.org Bug: 1169082 Change-Id: I4a70d82ee1e6754d2b16a747f7288d4652abf83a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642678Reviewed-by:
Anastasiia N <anastasiian@chromium.org> Commit-Queue: Anastasiia N <anastasiian@chromium.org> Cr-Commit-Position: refs/heads/master@{#845628}
-
Alice Wang authored
This CL cleans up SigninPromoUtilTest by removing the unused method and annotation. Bug: 1166173 Change-Id: Idb9bceb7dac0c371af3c2e9b2b15eefddbf2722a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640034Reviewed-by:
Tanmoy Mollik <triploblastic@chromium.org> Commit-Queue: Alice Wang <aliceywang@chromium.org> Cr-Commit-Position: refs/heads/master@{#845627}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/477bd92472cc..3b349f3ea9c0 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-trace-processor-linux-chromium 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/+doc/master/autoroll/README.md Tbr: perfetto-bugs@google.com Change-Id: I5fab1d1ef557e00f7739fa05e9cf0f6454c50ccd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642738Reviewed-by:
-
chromium-autoroll authored
Roll ChromeOS Atom AFDO profile from 89-4384.0-1610969724-benchmark-89.0.4389.9-r1 to 89-4384.0-1610969724-benchmark-89.0.4389.10-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-atom-chromium Please CC c-compiler-chrome@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 Tbr: c-compiler-chrome@google.com Change-Id: Iaa4526a6659275b1fb790848bac52e4278c03032 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642802Reviewed-by:
-
Alice Wang authored
This CL adds a render test for SigninFirstRunFragment when no accounts are on device. Bug: 1045473 Change-Id: I058212677f7f4cb0d29888632f12d2fabd75ded0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2639895Reviewed-by:
-
chromium-autoroll authored
Roll ChromeOS Bigcore AFDO profile from 89-4384.0-1610966529-benchmark-89.0.4389.9-r1 to 89-4384.0-1610966529-benchmark-89.0.4389.10-r1 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/cros-afdo-bigcore-chromium Please CC c-compiler-chrome@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 Tbr: c-compiler-chrome@google.com Change-Id: I55e58cc45b74c50db2a08a290e6ef6477378210c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642800Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/309863f0a8f1..f9033fa039cd 2021-01-21 chrche@microsoft.com [Loc] Migrate perf_ui to localization V2 2021-01-21 tvanderlippe@chromium.org Migrate MultiMap to map-utilities 2021-01-21 mathias@chromium.org Enable focus styles for network request blocking checkboxes 2021-01-21 szuend@chromium.org Roll deps from Chromium into DevTools 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:1050549,chromium:1136655 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I811a2ab39894bdd07a300b72cfd2ad493541776d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642516Reviewed-by:
-
Richard Knoll authored
The UNNotification API expects us to provide a unique identifier for each notification we show. The previous implementation simply used the notification id as-is which breaks with multiple profiles as their ids may overlap. This CL changes the used id to be "ProfileID|NotificationId" instead to avoid this issue. Also fixes support for the renotify flag. Bug: 1127306 Change-Id: I9f302c3e045d2f6f3358f5d528e80f9a626fca59 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2637519 Commit-Queue: Richard Knoll <knollr@chromium.org> Reviewed-by:
Rayan Kanso <rayankans@chromium.org> Cr-Commit-Position: refs/heads/master@{#845621}
-
Ossama Mahmoud authored
This is a reland of ddd08c52 Original change's description: > OOBE: Arc-ToS Improvements > > Migrate ArcToSScreen to multistep behavior. > Get rid of display: none; and display: block; > > Bug: 1156667 > Change-Id: I4c2fc425edd4883c5edfceb0a5a9f67a6227de7b > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2603744 > Commit-Queue: Ossama Mahmoud <osamafathy@google.com> > Reviewed-by: Denis Kuznetsov [CET] <antrim@chromium.org> > Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org> > Cr-Commit-Position: refs/heads/master@{#844554} Bug: 1156667 Change-Id: I53e9d533c9e3b7d5b5ba44dcf55997a3d9f6fab6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2637560Reviewed-by:
Roman Sorokin [CET] <rsorokin@chromium.org> Commit-Queue: Ossama Mahmoud <osamafathy@google.com> Cr-Commit-Position: refs/heads/master@{#845620}
-
Jan Wilken Dörrie authored
This change prepapres sys_info_win for the string of base::string16 to std::u16string. Bug: 911896 Change-Id: I53c2cb2127aa576d8c4f83382893c5ffdd095070 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2642267 Commit-Queue: Peter Kasting <pkasting@chromium.org> Reviewed-by:
Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#845619}
-
Hans Wennborg authored
Link-time optimization enables greater performance, but leads to significantly longer link times. This change turns off optimization in the link step except for select targets such as the actual browser executable/shared lib. Source files are still compiled with the usual optimization flags, and the ThinLTO mechanism is still used for all links; this only affects whether optimizations are also performed in the link step or not. The motivation is to speed up builds with thin_lto_enable_optimizations so that this can be enabled in official builds on all targets. Currently only ChromeOS and Android use thin_lto_enable_optimizations, and in terms of production builds this is a no-op since the optimization is applied to the shipping binaries as before. However it means that tests and auxiliary binaries won't be optimized during the link step. In terms of build speed, this reduces the link time of v8_context_snapshot_generator in a Linux build with thin_lto_enable_optimizations from 173 to 39 CPU minutes. On Windows, the link time of the same target goes from 2m50 to 1m40 (wall-clock time). Linking unit_tests goes from 8m50 to 5m40. Build timings (best of two) of official "all" builds on my Win workstation: - Without ThinLTO: 25m - With ThinLTO opts: 4h36m - With ThinLTO opts+this patch: 2h39m With the ThinLTO cache enabled (requires fixing crbug.com/871962): - With ThinLTO opts+this patch: 1h52m Hopefully this patch (esp. if we can also fix the thinlto cache bug) would make win-official survive enabling thin_lto_enable_optimizations in official builds. Build timings of official "all" builds on my Linux workstation: (ThinLTO without opts is already enabled in official builds due to CFI, so I didn't measure with it disabled.) - With ThinLTO opts: 4h00m - With ThinLTO + this patch: 1h12m Note that this means test binaries and the shipping browser see different levels of optimization. We think that is the right trade-off: the difference should only matter in case of compiler/linker bugs, and we believe the browser binary gets enough testing (e.g. by perf bots) that such bugs will still be caught. Also to some extent this is already the case: most testing is done on non-official builds, and official builds use different optimizations (notably PGO). We have more ideas for speeding up linking of the non-link-time-optimized targets, but we hope this is enough to enable ThinLTO in official Windows and Linux builds. Bug: 110124, 1057737 Change-Id: I4130c02d0b7fe7012e52c92e51a0b255b576ad2b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628955 Commit-Queue: Hans Wennborg <hans@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#845618}
-
Christian Dullweber authored
Bug: 1146211 Change-Id: Ib9667340b5148cfe56adea91cf1e2089c1f8b3d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2635152 Auto-Submit: Christian Dullweber <dullweber@chromium.org> Reviewed-by:
Michael Thiessen <mthiesse@chromium.org> Commit-Queue: Christian Dullweber <dullweber@chromium.org> Cr-Commit-Position: refs/heads/master@{#845617}
-
