- 16 Feb, 2020 21 commits
-
-
Mia Glaese authored
Screen capture: https://drive.google.com/drive/folders/1VSZGz0yMwmYBV0uG0Zv5jgtLzKQt8DVM?usp=sharing Bug: 1025296 Change-Id: I6d3671252578fa9f37e5f1173b8d55b364a898c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1981853 Commit-Queue: Mia Glaese <glamia@chromium.org> Reviewed-by:
Yusuf Ozuysal <yusufo@chromium.org> Reviewed-by:
Patrick Noland <pnoland@chromium.org> Reviewed-by:
Ganggui Tang <gogerald@chromium.org> Cr-Commit-Position: refs/heads/master@{#741772}
-
Yuki Shiino authored
Bug: 839389 Change-Id: I158f60540bc3187264822e637e09216d9d524815 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055911 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#741771}
-
Yuki Shiino authored
Bug: 839389 Change-Id: I9b6249cc25cf1e2895f4064d0c17e95fa196760f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057163 Commit-Queue: Yuki Shiino <yukishiino@chromium.org> Reviewed-by:
-
Keishi Hattori authored
Use the LifecycleObserverList that was added in crrev.com/c/2054687 for SynchronousMutationObserver. Bug: 1052319 Change-Id: Icff64c80e3559f12c3d8d191ee9b7e8808c81db8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056763 Commit-Queue: Keishi Hattori <keishi@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#741769}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/710aa2fccc78..1892c38db5c8 Created with: gclient setdep -r src-internal@1892c38db5c8 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: Ida0e80b703bc37f11bc8c39a3377d349ef75ac18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059208Reviewed-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@{#741768}
-
chromium-autoroll authored
If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/fuchsia-sdk-chromium-autoroll Please CC cr-fuchsia+bot@chromium.org on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast Tbr: cr-fuchsia+bot@chromium.org Change-Id: I48ee584eee7379094d8906baad477f81e8806e28 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058916Reviewed-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@{#741767}
-
Keishi Hattori authored
Use the LifecycleObserverList that was added in crrev.com/c/2054687 for DocumentShutdownObserver. Bug: 1052319 Change-Id: Idf095cfb8fb7b895f42abc3873c74b915bcbaa34 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056195Reviewed-by:
-
Keishi Hattori authored
LifecycleObserver quickly becomes confusing when adding multiple to one class and the method name starts conflicting. This CL adds HeapObserverList which is like base::ObserverList for GCed objects. HeapObserverList copies the behavior of LifecycleNotifier. This CL also uses it for PageVisibilityObserver. Bug: 1052319 Change-Id: I4a3ffaeddf7311249db56954d24897de24d68c12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2054687 Commit-Queue: Keishi Hattori <keishi@chromium.org> Reviewed-by:
-
Christopher Cameron authored
This has no callers. TBR=khushalsagar Bug: 1049334 Change-Id: I1f1b17dc3481921bfbeb93efa07fc49d7763bea1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058793 Commit-Queue: ccameron <ccameron@chromium.org> Reviewed-by:
ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#741764}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/ee1be8484c84..710aa2fccc78 Created with: gclient setdep -r src-internal@710aa2fccc78 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I8e0cf221daa422915ba0fce0e9d920b991d71559 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058772Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/2c5ee187245a..a27ca5566533 git log 2c5ee187245a..a27ca5566533 --date=short --first-parent --format='%ad %ae %s' 2020-02-16 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update Go Deps Created with: gclient setdep -r src/third_party/skia@a27ca5566533 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/skia-autoroll Please CC lovisolo@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: lovisolo@google.com Change-Id: I41a3baeac5e69b8b17d965c343fecb79d139094f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058669Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/55e300fa1098..ce86587402d2 git log 55e300fa1098..ce86587402d2 --date=short --first-parent --format='%ad %ae %s' 2020-02-16 devtools-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com Update DevTools Chromium DEPS. Created with: gclient setdep -r src/third_party/devtools-frontend/src@ce86587402d2 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I29a68c63fb0ca069059bd63d5da03bfcfa2c41fb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058913Reviewed-by:
-
Asanka Herath authored
When generating the high entropy API list, instead of only showing the high entropy ones, include all of them with proper annotations so we know which ones are already marked as high entropy. The output is also explicitly a CSV file that is now located at the root of the build tree where it is easily accessible. To generate the list of Blink JS APIs, use the following ninja incantation: ninja -C out/Debug generate_high_entropy_list Now look for the file named high_entropy_list.csv in the build directory. R=yukishiino@chromium.org Bug: 973801 Change-Id: I1bf7ee7a48d0b8db0cf2dd284e3557a4fa73a7e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055685 Commit-Queue: Asanka Herath <asanka@chromium.org> Reviewed-by:Yuki Shiino <yukishiino@chromium.org> Cr-Commit-Position: refs/heads/master@{#741760}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9abfd296d261..ee1be8484c84 Created with: gclient setdep -r src-internal@ee1be8484c84 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I442e31ba5df1275e13b462500c9f546bbf8eb93a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2059113Reviewed-by:
-
jongdeok.kim authored
Bug: 1007711 Change-Id: I5d8a956adbf53993aab8eecb08f00131d41a755d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2037176Reviewed-by:
Tommy Li <tommycli@chromium.org> Commit-Queue: Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#741758}
-
Anastasia Helfinstein authored
There is a significant amount of behavior that is specific to editable text nodes. This change creates a new EditableTextNode type to handle that behavior, and takes the first step towards migrating the behavior. Bug: None Change-Id: Ib6e5d2e7530d36bb33232fa28c3e29b403b08335 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2051366 Commit-Queue: Anastasia Helfinstein <anastasi@google.com> Reviewed-by:
Akihiro Ota <akihiroota@chromium.org> Cr-Commit-Position: refs/heads/master@{#741757}
-
Sadrul Habib Chowdhury authored
The throughput metrics were renamed from Graphics.Smoothness.Throughput to Graphics.Smoothness.PercentDroppedFrames in crrev.com/741484. Update the rendering benchmark to report these renamed metrics. BUG=1048780 TBR=xidachen@ Change-Id: I1fe717a69c106de930879b3344cac85bfdee9273 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058792Reviewed-by:
Sadrul Chowdhury <sadrul@chromium.org> Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Auto-Submit: Sadrul Chowdhury <sadrul@chromium.org> Cr-Commit-Position: refs/heads/master@{#741756}
-
Peter Kasting authored
This reverts commit f7c0a756. Reason for revert: Causes several build warnings of the form: "chrome_user_metrics_extension.proto:15:1: warning: Import cast_assistant_logs.proto but not used." Original change's description: > Export UMA protos with proto_export.py. > > Bug: 32486634 > Test: CQ > Change-Id: I1418d910625d32ac67d33624c002ca630b1de37d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2048407 > Commit-Queue: Yilong Yao <yilongyao@google.com> > Reviewed-by: Brian White <bcwhite@chromium.org> > Cr-Commit-Position: refs/heads/master@{#740815} TBR=bcwhite@chromium.org,halliwell@chromium.org,yilongyao@google.com # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 32486634 Change-Id: I92db46cf837eac247d99224f3cc173ca09c98468 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058696Reviewed-by:
Peter Kasting <pkasting@chromium.org> Commit-Queue: Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#741755}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/73718a05a58b..9abfd296d261 Created with: gclient setdep -r src-internal@9abfd296d261 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I267c3361763e87d11b72175891912c1d0513fa3d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058849Reviewed-by:
-
Christoph Schwering authored
The experiment is extended by also testing for blacklisting social titles from being filled into company fields. The study experiments with restricting Autofill from filling company fields in different ways. Additionally to experimenting with not filling company fields altogether as well as not filling potential birthyears into company names, the extended study experiments with not filling (some) social titles. Bug: 961675 Change-Id: I5e77bcfa08eb6b3306fe809136817e5544034248 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050313Reviewed-by:
Jesse Doherty <jwd@chromium.org> Reviewed-by:
Ioana Pandele <ioanap@chromium.org> Commit-Queue: Christoph Schwering <schwering@google.com> Cr-Commit-Position: refs/heads/master@{#741753}
-
Christoph Schwering authored
Bug: 1051504 Change-Id: I614f91e530c25284d90e92763d6f2a6af79bb28b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2056825 Commit-Queue: Mike Dougherty <michaeldo@chromium.org> Reviewed-by:
Mike Dougherty <michaeldo@chromium.org> Cr-Commit-Position: refs/heads/master@{#741752}
-
- 15 Feb, 2020 19 commits
-
-
Caleb Rouleau authored
This reverts commit 2131f972. Reason for revert: broke official mac builds https://ci.chromium.org/p/chrome/builders/ci/mac-builder-perf?limit=200 https://ci.chromium.org/p/chrome/builders/ci/mac-builder-perf/155871 Original change's description: > [mb.py] Check multiple locations for the real python. > > Sometimes the value of sys.prefix (or sys.real_prefix in vpython) > includes the bin/ directory within the python installation, and > sometimes it does not. To accommodate this, check both prefix/bin and > prefix itself for the python executable. > > Bug: 1049421 > Change-Id: Ia7c072dc0b4b8232ec8fdce20f9211e3c978a3ad > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055976 > Commit-Queue: Sajjad Mirza <sajjadm@chromium.org> > Reviewed-by: Nico Weber <thakis@chromium.org> > Reviewed-by: Robbie Iannucci <iannucci@chromium.org> > Cr-Commit-Position: refs/heads/master@{#741574} TBR=thakis@chromium.org,iannucci@chromium.org,sajjadm@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1049421 Change-Id: I957fecc3b0fe209139317dc9c21efa1e89bba36d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058789Reviewed-by:
Caleb Rouleau <crouleau@chromium.org> Commit-Queue: Caleb Rouleau <crouleau@chromium.org> Cr-Commit-Position: refs/heads/master@{#741751}
-
Caleb Rouleau authored
This will cause some benchmarks to start running on different devices on the waterfall than they used to run on, which may cause discontinuities in the data on the chromeperf dashboard. DO NOT REVERT this change for any perf regression. TBR=johnchen@chromium.org Bug: 1030840 Change-Id: I54709dba2f0ca108a90ad4f70b7c952a2cb19047 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058791Reviewed-by:
-
Sadrul Habib Chowdhury authored
Some of the parameters for the ui::Compositor that were added for mus are no longer needed. Remove these. BUG=none TBR=oshima@ for trivial chromecast/ mechanical change Change-Id: Ida403cca9391f3e3c5626b5dda5ef2e4c78b914c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058035 Commit-Queue: Sadrul Chowdhury <sadrul@chromium.org> Auto-Submit: Sadrul Chowdhury <sadrul@chromium.org> Reviewed-by:
Mitsuru Oshima <oshima@chromium.org> Cr-Commit-Position: refs/heads/master@{#741749}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/e85da7c77b6f..73718a05a58b Created with: gclient setdep -r src-internal@73718a05a58b If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I4680c3b4fced027c1e069714eac9b1d5857db8f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058688Reviewed-by:
-
Christopher Cameron authored
We are getting reports of the browser process rejecting connections from app shims from the field. The failures happen after Chrome has been open for a while (so reproducing from the console to get logs is not an option). Address this in two ways. 1. Add more LOG(INFO) calls in the app shim process itself. This is needed (and is here to stay) because, if something goes wrong connecting to Chrome or loading the Chrome framework, there is no other mechanism for getting feedback (no crash reports, etc). 2. Add four NSLog calls in the browser, for - Mach connection received - Mojo connection received first message - Mojo connection disposition (use or discard), so 2 calls here - Mojo connection closed (regardless of disposition) These calls are NOT here to stay -- they are for debugging problems we are seeing in Chrome 80. They are likely to be moved to an internal URL. Disabling presubmit because this is intentionally adding LOG(INFO)s. NOPRESUBMIT=True Bug: 1052131 Change-Id: Ia6fd1cb21802c97d8b9fed6146db48fdc3463e93 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055994Reviewed-by:
Robert Sesek <rsesek@chromium.org> Commit-Queue: ccameron <ccameron@chromium.org> Cr-Commit-Position: refs/heads/master@{#741747}
-
George Burgess IV authored
The NOLINT here was to make tidy stop complaining about the lack of an `explicit` constructor for this ScopedTraceEvent. Unfortunately, adding that makes it difficult to init ScopedTraceEvents as we're doing right now. It's arguable either way that tidy should/shouldn't diagnose this, since template trickery/decltype/etc can easily allow you to construct `ScopedTraceEvent`s on your own. Because the argument is useless anyway, using `...` makes tidy quiet down, and appears just as optimization-friendly. Bug: 1044592 Change-Id: Ib6203b40df504aa82816555e9c915f06ea60246f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055889Reviewed-by:
Eric Seckler <eseckler@chromium.org> Commit-Queue: George Burgess <gbiv@chromium.org> Cr-Commit-Position: refs/heads/master@{#741746}
-
ziyangch authored
Bug: Internal b/147703983 Test: test with eureka-internal/355651. Change-Id: I86a86df4844f3d6e6103f896061ba6d9c2b7599c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055425Reviewed-by:
Yuchen Liu <yucliu@chromium.org> Reviewed-by:
Simeon Anfinrud <sanfin@chromium.org> Commit-Queue: Ziyang Cheng <ziyangch@chromium.org> Cr-Commit-Position: refs/heads/master@{#741745}
-
Ian Kilpatrick authored
This adds a separate codepath for building up the inline containing block information from fragment items, instead of the line-box tree. I kept a separate codepath for ease of removal later. Fixes ~15 tests. Bug: 982194 Change-Id: Ibdaf708d4ca264071ab4b8b6b7099ad8a998e867 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2048707 Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#741744}
-
Koji Ishii authored
This patch adds integrity checks for the flags of |NGPhysicalBoxFragment| and its actual children. Bug: 982194 Change-Id: Ic18f088c1263d4f76f03dc1f22a88d3700254b68 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2050151Reviewed-by:
Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by:
Morten Stenshorne <mstensho@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#741743}
-
Rakesh Soma authored
Change-Id: Ic11c66281f2144d0e757eda3e5a5122b4322c222 Bug: 1052570 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057291 Auto-Submit: Rakesh Soma <rakeshsoma@google.com> Reviewed-by:
Yusuf Sengul <yusufsn@google.com> Reviewed-by:
Tien Mai <tienmai@chromium.org> Commit-Queue: Rakesh Soma <rakeshsoma@google.com> Cr-Commit-Position: refs/heads/master@{#741742}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/238d16ed563f..e85da7c77b6f Created with: gclient setdep -r src-internal@e85da7c77b6f If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I5bb671cd6ec339d33b33e4e7442e6fb01ec5aca0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058354Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/3eaed8d0093f..2c5ee187245a git log 3eaed8d0093f..2c5ee187245a --date=short --first-parent --format='%ad %ae %s' 2020-02-15 reed@google.com remove legacy factory for overdrawcolorfilter 2020-02-15 herb@google.com Make SkStrikeCache::Node be SkStrike. Created with: gclient setdep -r src/third_party/skia@2c5ee187245a 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 stani@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: stani@google.com Change-Id: I2f5638f67a2e44fdfd9483004485b20feab9f5d9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058356Reviewed-by:
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/b7ceaa8efd2b..3eaed8d0093f git log b7ceaa8efd2b..3eaed8d0093f --date=short --first-parent --format='%ad %ae %s' 2020-02-15 reed@google.com fix clang-tidy warnings Created with: gclient setdep -r src/third_party/skia@3eaed8d0093f 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 stani@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: stani@google.com Change-Id: Ibcd4ff017d4049f52684d72f41054b1bdbb05525 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058352Reviewed-by:
-
chromium-autoroll authored
https://swiftshader.googlesource.com/SwiftShader.git/+log/348f07b40c2b..481daed34f15 git log 348f07b40c2b..481daed34f15 --date=short --first-parent --format='%ad %ae %s' 2020-02-15 swiftshader.regress@gmail.com Regres: Update test lists @ 348f07b4 Created with: gclient setdep -r src/third_party/swiftshader@481daed34f15 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll Please CC swiftshader-team+autoroll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_chromium_msan_rel_ng;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: swiftshader-team+autoroll@google.com Change-Id: I368e8f02729d174903ca4c5640815cfe2694342b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058351Reviewed-by:
-
Tarun Bansal authored
Bug: 1038703 Change-Id: I69653b606f593f2ecff4b6542d898885014efd90 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057588 Commit-Queue: Robert Ogden <robertogden@chromium.org> Reviewed-by:
Robert Ogden <robertogden@chromium.org> Cr-Commit-Position: refs/heads/master@{#741737}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/a67744d2cebb..238d16ed563f Created with: gclient setdep -r src-internal@238d16ed563f If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: I027c6c43187ef19e46bfcb944a41d6c60d591b39 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058457Reviewed-by:
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/798a83759956..2dd40d7fa75c git log 798a83759956..2dd40d7fa75c --date=short --first-parent --format='%ad %ae %s' 2020-02-15 jmadill@chromium.org Vulkan: Free pool allocation leak with graph disabled. Created with: gclient setdep -r src/third_party/angle@2dd40d7fa75c 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 courtneygo@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win-asan;luci.chromium.try:win_optional_gpu_tests_rel Bug: None Tbr: courtneygo@google.com Change-Id: I9707f84dca5197822a514f54f2cdd7c4b2230368 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058456Reviewed-by:
-
Peng Huang authored
The driver fix [1] has been merged to 19.3 and 20.0 staging branches, it will be released with 19.3.5 and 20.0.0-rc4. So enabled vulkan and gl interop for mesa 19.3.5 and later version. [1] https://gitlab.freedesktop.org/mesa/mesa/commit/b81f4a4092b0e4091e728ec50606dc6561963fba Bug: 1046462 Change-Id: I781bc82734a4fc9a8443f9cf160caf4b7a5e20ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2057054 Auto-Submit: Peng Huang <penghuang@chromium.org> Reviewed-by:
Zhenyao Mo <zmo@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#741734}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/1d3482867b00..a67744d2cebb Created with: gclient setdep -r src-internal@a67744d2cebb If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll Please CC jbudorick@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome Bug: None Tbr: jbudorick@google.com Change-Id: Ic89acee2106efa026bfd3db72b9fcf55ea751768 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2058453Reviewed-by:
-
