- 17 Jan, 2021 40 commits
-
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1610856595-946a6d2a878841b9e52df2b213b33290b223745d.profdata to chrome-win32-master-1610892928-c40464b32706b928d660bda5529a00a25adfa05a.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: Ic061872888d7b64e3549998f189741d878317879 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634991Reviewed-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@{#844403}
-
Mirko Bonadei authored
This target has been merged into //rtc_base:threading and //rtc_base:async_resolver will be removed soon. Bug: webrtc:9987 Change-Id: I303a212bc164bf95fb8a42eba03c532ed85b0bd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2623549Reviewed-by:
Harald Alvestrand <hta@chromium.org> Commit-Queue: Mirko Bonadei <mbonadei@chromium.org> Cr-Commit-Position: refs/heads/master@{#844402}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/9f09435bc192..60015ff672d9 2021-01-16 syoussefi@chromium.org Vulkan: Redo RewriteStructSamplers 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: I314bbf4ae4987723988c5901a327caf8c18a5e0b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633762Reviewed-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@{#844401}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1610775681-fd751d9e49ed1bc37f4f2d81eeaeebce2c47ec09.profdata to chrome-win64-master-1610892928-42ffc5cfac02c8db6ece144a03a76e06762bb041.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: Id165b8f3f00384c5b4c302ca1d64322dc7dd9edd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633435Reviewed-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@{#844400}
-
Eugene But authored
Bug: None Change-Id: I5a827a19b9fbc3f8f6cf533f8d8b885309b8c768 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634342 Commit-Queue: edchin <edchin@chromium.org> Reviewed-by:
edchin <edchin@chromium.org> Cr-Commit-Position: refs/heads/master@{#844399}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1610755196-5c734541ab8c568bfbdad6f3ede65cc794b2d6ff.profdata to chrome-win32-master-1610856595-946a6d2a878841b9e52df2b213b33290b223745d.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: I415148135a9230b2f26b798aa729345a0e7f79d4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634977Reviewed-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@{#844398}
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/afdo-chromium-autoroll Please CC gbiv@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/+doc/master/autoroll/README.md Tbr: gbiv@chromium.org Change-Id: If011ff733e8159ea00f7f1cb140837f6bbcb98b9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634980Reviewed-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@{#844397}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1610765751-8857ea043bec313dded979c8fdfc3dd025b4df44.profdata to chrome-win64-master-1610775681-fd751d9e49ed1bc37f4f2d81eeaeebce2c47ec09.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: I5317721395224701e376437468e3380eb623d290 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634979Reviewed-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@{#844396}
-
Mike Reed authored
Test images rebaselined to account for the new behavior in skia's picture-shader when a post-raster sampling is required. Note on change to cc_unittest: Several of these tests try to compare output between a direct draw (RasterExpectedBitmap) and an OOPR draw (Raster), expecting the two results to be identical. However, OOP doesn't *always* produce the same Skia calls as direct; if it sees a picture-shader (PaintShader::MakePaintRecord) it will convert this to a pre-scaled picture-image-shader, and then draw with that. This makes it invalid to always require *exact* pixel comparisons, since it may have sent (slightly) different commands/floats to the GPU. This CL (with a change to picture-shader's handling of post-raster sampling) stumbled over such a different (perhaps only on Nexus5-lollipop). To make the test more robust, those tests now call set_has_animated_images(true) to force converting kRasterAtScale to kFixedScale for both direct and oop. Change-Id: Ic0ce9128c75ea598f593187f3a1b54e2c0c4cd8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2619838Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by:
Khushal <khushalsagar@chromium.org> Reviewed-by:
Florin Malita <fmalita@chromium.org> Commit-Queue: Mike Reed <reed@google.com> Cr-Commit-Position: refs/heads/master@{#844395}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202101170600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/alcm_LiO62roi1ezYRwFxRVtvZggBQWdZ5rfXIxetisC 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: None Tbr: media-app@grotations.appspotmail.com Change-Id: I99cd04a4a76bd852c0103e97f7bd7c10fa5aa460 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634976Reviewed-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@{#844394}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/9c8dd8763605..09729d2ecf49 2021-01-17 webrtc-version-updater@webrtc-ci.iam.gserviceaccount.com Update WebRTC code version (2021-01-17T04:01:53). 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/+doc/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I7163d083e2ab65dfdb15bd9156d5e3eccd5e03b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634973Reviewed-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@{#844393}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1610775681-09dada7bad4e7c2ffe1854f240d996243cad5870.profdata to chrome-mac-master-1610856595-a70e6e2e0e2afc7578d7a1985e7c97870006ff00.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: Iee3d4801e64d85eb711455d52f9a8f47055dc1d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634978Reviewed-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@{#844392}
-
chromium-autoroll authored
Roll ChromeOS Bigcore AFDO profile from 89-4374.0-1610361443-benchmark-89.0.4389.2-r1 to 89-4374.0-1610361443-benchmark-89.0.4389.4-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: I521e0acbfd7f68bc4762704e38c35a848f6f848b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634975Reviewed-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@{#844391}
-
chromium-autoroll authored
Roll ChromeOS Atom AFDO profile from 89-4380.0-1610362181-benchmark-89.0.4389.2-r1 to 89-4380.0-1610362181-benchmark-89.0.4389.4-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: Idb117ff477c5998f7a43396c21e4378c2f9c4e32 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634974Reviewed-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@{#844390}
-
Caitlin Fischer authored
The server-side config indicates that the study has ended. Bug: 1126640 Change-Id: Ic9fac9383c5120ecc1b9a8e91825bcb45ffb4539 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631432Reviewed-by:
Weilun Shi <sweilun@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#844389}
-
Miguel Casas authored
VP8 Hw decoding on Intel Broadwell ChromeOS is disabled at several levels due to instabilities with old kernels. The kernel was migrated a while ago (to 4.14) so it should work fine. This CL removes the GPU driver workaround for this. A catch is that some BDW Chromeboxes have an external companion video acceleration chip that provides VP8 Hw decoding. In those systems we want to keep using that chip, which is accessed via the V4L2 interface. This CL also changes the way accelerated decoders are created to prefer the V4L2 ones. Bug: b:172338625 Change-Id: Ie3f377d2c0fc6708949fcb95bf3cc5babfdce43a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2614849Reviewed-by:
Andres Calderon Jaramillo <andrescj@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Miguel Casas <mcasas@chromium.org> Cr-Commit-Position: refs/heads/master@{#844388}
-
James Cook authored
* Consolidate an extra block of browser tests with the main block * Remove some unnecessary is_chromeos_ash checks that were already inside an is_chromeos_ash block. Bug: none Change-Id: I02cfc8bf3547a4b54035a62b68c8c1b95d54e6f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634133 Commit-Queue: Jenny Zhang <jennyz@chromium.org> Auto-Submit: James Cook <jamescook@chromium.org> Reviewed-by:
Jenny Zhang <jennyz@chromium.org> Cr-Commit-Position: refs/heads/master@{#844387}
-
chromium-autoroll authored
This CL may cause a small binary size increase, roughly proportional to how long it's been since our last AFDO profile roll. For larger increases (around or exceeding 100KB), please file a bug against gbiv@chromium.org. Additional context: https://crbug.com/805539 Please note that, despite rolling to chrome/android, this profile is used for both Linux and Android. If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/afdo-chromium-autoroll Please CC gbiv@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/+doc/master/autoroll/README.md Tbr: gbiv@chromium.org Change-Id: I42bbfaf4d7748c3f335d5470b0612a7e7011f551 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634462Reviewed-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@{#844386}
-
chromium-autoroll authored
Roll Chrome Linux PGO profile from chrome-linux-master-1610755196-61d932c6744ad62f0472d9ac776510bd42cd0a54.profdata to chrome-linux-master-1610775681-262289403e7fd8444a73878a73a9f9f97304c245.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-linux-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:linux-chrome Tbr: pgo-profile-sheriffs@google.com Change-Id: I0a5dfb8fca3105b2b4b3cf271146b1d94cbd596b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633657Reviewed-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@{#844385}
-
Javier Fernández García-Boente authored
The RunPartInfo may have an offset, if the NGInlineItem has been created from a different segment. This value is stored in the part's offset_ attribute. We use the offset_ to calculate the ShapeResultView character position, but it seems we were not considering when evaluating safe to break points in the part. Bug: 1160214, 1163545 Change-Id: I40ece9ac6f0bd07e602d9693efc63a08ca959e8d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2625873Reviewed-by:
Koji Ishii <kojii@chromium.org> Commit-Queue: Javier Fernandez <jfernandez@igalia.com> Cr-Commit-Position: refs/heads/master@{#844384}
-
Cliff Smolinsky authored
This change adds GetConnectionCost() to the NetworkChangeNotifier class. The structure is modeled after the existing functions of the class. The base class implements a basic best-effort guess that works on platforms that can detect cellular versus non-cellular types, which is essentially the same as how "metered" network checks exist today. This change updates the NetworkChangeNotifierWin class to retrieve the metered network status and register for updates from the OS. It also creates an Observer class similar to the other existing ones to notify other components when it changes. It's important to note that NetworkChangeNotifierWin will only register for updates from the OS once an Observer is connected. If there is no observer connected and someone asks for the current connection cost it will be retrieved from the OS at that time rather than using the cached value. Bug: 1143428 Change-Id: I6f03ae91869087c6ad72a7f5891df158815137d7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2542047Reviewed-by:
Paul Jensen <pauljensen@chromium.org> Reviewed-by:
Kinuko Yasuda <kinuko@chromium.org> Reviewed-by:
Tarun Bansal <tbansal@chromium.org> Commit-Queue: Cliff Smolinsky <cliffsmo@microsoft.com> Cr-Commit-Position: refs/heads/master@{#844383}
-
Victor Costan authored
Bug: 1163048 Change-Id: Idfe99915951d025e7b47f952cc553b20c0fefd87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628387 Commit-Queue: Victor Costan <pwnall@chromium.org> Reviewed-by:
enne <enne@chromium.org> Cr-Commit-Position: refs/heads/master@{#844382}
-
chromium-autoroll authored
Roll Chrome Mac PGO profile from chrome-mac-master-1610755196-59a4a0c119004651094c88c9b6ab2bda6a695e2e.profdata to chrome-mac-master-1610775681-09dada7bad4e7c2ffe1854f240d996243cad5870.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: I0a7614b161cdbe9c471475b4be993f8c5b3b51b3 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633658Reviewed-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@{#844381}
-
chromium-autoroll authored
Roll Chrome Win64 PGO profile from chrome-win64-master-1610755196-7abba2cfdf73565a08dbdbba7efd11f1e8902293.profdata to chrome-win64-master-1610765751-8857ea043bec313dded979c8fdfc3dd025b4df44.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: I150f1d16ca4b536b1c615590e91455c38ea6ed9c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633290Reviewed-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@{#844380}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/ff170c6f508d..9f09435bc192 2021-01-16 m.maiya@samsung.com Vulkan: Rename ReplaceClipDistanceVariable files 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: I49fe351ac3f3d9cc7827296e226523c071f846af Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634343Reviewed-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@{#844379}
-
Dmitry Gozman authored
This allows us to CommitPendingWrite() in PostMainMessageLoopRun(), while it is still safe to do so, and avoid crashes on shutdown. Previously, PrefService was doing non-trivial work during HeadlessContentMainDelegate::~HeadlessContentMainDelegate() that ended up with SIGABRT on MacOS. Drive-by: also SetEncryptionKey() in network service on Mac, similar to Windows. Bug: 1050905 TBR: gab@chromium.org Change-Id: I70e632d5f3a03a68b9ef90458315e2c2a516e1f1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634681 Commit-Queue: Dmitry Gozman <dgozman@chromium.org> Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Cr-Commit-Position: refs/heads/master@{#844378}
-
chromium-autoroll authored
Roll Chrome Win32 PGO profile from chrome-win32-master-1610744388-5f878bc1b38d4c2e869a6a4ceb1a959431b1ffe7.profdata to chrome-win32-master-1610755196-5c734541ab8c568bfbdad6f3ede65cc794b2d6ff.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: Id0d6692c03caf5994b036738be53c46f7c1c014e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634310Reviewed-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@{#844377}
-
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 chrome-fuchsia-gardener@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.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-deterministic-dbg;luci.chromium.try:fuchsia-x64-cast Tbr: chrome-fuchsia-gardener@grotations.appspotmail.com Change-Id: I26cc09e14feba87ab75873ddc0dcaa50fc7fc876 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634312Reviewed-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@{#844376}
-
WangHui authored
Fix Security DCHECK failure triggered by the conversion of RemoteFrame to LocalFrame. In OOPIFs mode, the text finder corresponding to the remote frame also needs to be notified, the match rects are invalid and need to be recalculated. Add a TODO first, will fix it in another CL. Bug: 1167505,1147796 Change-Id: I7056ea45ef559988abc56fcbd1e4b02964ba29ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631560Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Commit-Queue: HuiWang <wanghui210@huawei.com> Cr-Commit-Position: refs/heads/master@{#844375}
-
Min Qin authored
finch change:cl/352069245 Change-Id: I044ad0cf635e796bf35cb55f7fa08d354aa93655 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633187 Commit-Queue: Min Qin <qinmin@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#844374}
-
Ching-Kang Yen authored
Add the metrics to record the command code and system uptime when the TPM writing or reading commands timeout. The corresponding changes on the Chrome OS side is in crrev.com/c/2619447 BUG=b:176421411 Change-Id: I1803d90e74ab3b82358df30cf108085af50b5f34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2627652 Commit-Queue: Ching-Kang Yen <chingkang@chromium.org> Reviewed-by:
Steven Holte <holte@chromium.org> Cr-Commit-Position: refs/heads/master@{#844373}
-
chromium-internal-autoroll authored
Release_Notes: http://go/media_app-x20/relnotes/Main/media_app_202101160600_RC00.html https://chrome-infra-packages.appspot.com/p/chromeos_internal/apps/media_app/app/+/YNL0Lo1NPjtln2cK6MXj9Xw_pNW1UocLERdeu0clwWMC 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: None Tbr: media-app@grotations.appspotmail.com Change-Id: I2276bc4882c60bdde241c1179a06f138d880ecba Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634318Reviewed-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@{#844372}
-
David Reveman authored
This makes Fuchsia behave more like Android memory pressure signals. MODERATE and CRITICAL pressure notifications are now sent periodically and not only when the level changes. This is important as components expect to be able to just respond to discrete events, which means we need periodic "refreshes" of MODERATE and CRITICAL pressure. Bug: 1166976 Change-Id: I829a3f3c6cd40e7753119ade19f2aac0d58a97ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633682 Commit-Queue: David Reveman <reveman@chromium.org> Reviewed-by:
Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#844371}
-
chromium-autoroll authored
Roll ChromeOS Bigcore AFDO profile from 89-4374.0-1610361443-benchmark-89.0.4387.0-r1 to 89-4374.0-1610361443-benchmark-89.0.4389.2-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: I2573466ebd8f145ea824618590e6a5d44bbbfc39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633292Reviewed-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@{#844370}
-
Internal Frameworks Autoroller authored
TBR=bling-team@google.com Change-Id: Ie44d062c7e9c6aa0981e27242fbad496046b0636 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634921Reviewed-by:
Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: Internal Frameworks Autoroller <bling-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#844369}
-
chromium-autoroll authored
Roll ChromeOS Atom AFDO profile from 89-4380.0-1610362181-benchmark-89.0.4387.0-r1 to 89-4380.0-1610362181-benchmark-89.0.4389.2-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: I7a89e1e33bd003d307add7436d39dba45f5cf579 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2633291Reviewed-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@{#844368}
-
Keishi Hattori authored
In the commit below, we started to adjust a zero-sized allocation to a size of 1. https://chromium.googlesource.com/chromium/src/+/d5c951e819784cf240b0b85cbfd317563969bbc1 This caused the PartitionAllocTest.PartialPageFreelists test to fail. Change-Id: I42df204a083ad18bcc055aaf24e2946e1a67c2ff Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2624174Reviewed-by:
Benoit L <lizeb@chromium.org> Commit-Queue: Keishi Hattori <keishi@chromium.org> Cr-Commit-Position: refs/heads/master@{#844367}
-
Caitlin Fischer authored
The experiment launched. The feature was default enabled on the appropriate platforms in crrev.com/c/2340110. Bug: 1126640, 976583 Change-Id: I6142f21d207ab56cd127d3203aea1213f01104a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631930Reviewed-by:
Mark Pearson <mpearson@chromium.org> Commit-Queue: Caitlin Fischer <caitlinfischer@google.com> Cr-Commit-Position: refs/heads/master@{#844366}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/7acc2d9fe3a6..9c8dd8763605 2021-01-16 mbonadei@webrtc.org Fixing WebRTC/Chromium FYI build. 2021-01-16 mbonadei@webrtc.org Move iOS bundle data for tests inside rtc_include_test (take 2). 2021-01-16 asapersson@webrtc.org SimulcastEncoderAdapter: Add field trial for EncoderInfo settings. 2021-01-16 danilchap@webrtc.org In criket::BaseChannel replace AsyncInvoker with task queue functions 2021-01-16 mbonadei@webrtc.org Move iOS bundle data for tests inside rtc_include_test. 2021-01-16 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 3c2d1e3b..da248227 (844134:844357) 2021-01-16 webrtc-version-updater@webrtc-ci.iam.gserviceaccount.com Update WebRTC code version (2021-01-16T04:03:13). 2021-01-15 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 72fe6d7a..3c2d1e3b (844008:844134) 2021-01-15 jakobi@webrtc.org Reland "Default enable delay adaptation during DTX." 2021-01-15 danilchap@webrtc.org Reland "Replace RTC_WARN_UNUSED_RESULT with ABSL_MUST_USE_RESULT in c++ code" 2021-01-15 danilchap@webrtc.org In SVC controllers add support for frames dropped by encoder 2021-01-15 mbonadei@webrtc.org Reland "Refactor rtc_base build targets." 2021-01-15 jakobi@webrtc.org Revert "Default enable delay adaptation during DTX." 2021-01-15 jakobi@webrtc.org Default enable delay adaptation during DTX. 2021-01-15 sprang@webrtc.org Refactors SimulcastEncoder Adapter. 2021-01-15 sergio.garcia.murillo@gmail.com Set AV1E_SET_ERROR_RESILIENT_MODE on T1 and T2 enhanced layers 2021-01-15 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 42ab9dc8..72fe6d7a (843550:844008) 2021-01-15 danilchap@webrtc.org Replace RTC_WARN_UNUSED_RESULT with ABSL_MUST_USE_RESULT in audio_coding 2021-01-15 nisse@webrtc.org Update p2p/ to use C++ lambdas instead of rtc::Bind 2021-01-15 aleloi@webrtc.org Revert "Improve structuring of test for audio glitches." 2021-01-15 aleloi@google.com Revert "Add ability to load CreateDirect3DDeviceFromDXGIDevice from d3d11.dll" 2021-01-15 nisse@webrtc.org Update android jni code to use C++ lambdas instead of rtc::Bind 2021-01-15 nisse@webrtc.org Simplify FakeRtcEventLog, delete rtc::Bind usage 2021-01-15 landrey@webrtc.org Add cross trafic emulation api 2021-01-15 webrtc-version-updater@webrtc-ci.iam.gserviceaccount.com Update WebRTC code version (2021-01-15T04:04:08). 2021-01-14 mbonadei@webrtc.org mb: Fully remove references to 'masters' in favor of 'builder_groups'. 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/+doc/master/autoroll/README.md Bug: chromium:1117773 Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I9674b3bf834e3b1b8e7d50e226f7f13bae91ed10 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2632812Reviewed-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@{#844365}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/05e5446145a6..a799f6c37d4d 2021-01-17 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update SKP version 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 ethannicholas@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: ethannicholas@google.com Change-Id: Ib0abdee4255fc628367ad89792dbae8a96acea89 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2634801Reviewed-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@{#844364}
-