- 21 Jan, 2020 2 commits
-
-
Patrick Monette authored
This change is necessary to add dedicated workers to the performance manager graph. An invariant of the WorkerNode is that its ProcessNode is always valid. This can only be accomplished by making sure that the WorkerNode is destroyed before its ProcessNode. Because the performance_manager::RenderProcessUserData class also subscribes to the RenderProcessHostObserver interface and deletes the ProcessNode when its RenderProcessHost is destroyed, we can't use RenderProcessHostDestroyed in DedicatedWorkerHost because there are no guaranteed ordering on the notification. In fact, since the DedicatedWorkerHost always subscribe to the RenderProcessHost after the performance_manager::RenderProcessUserData class, we always get the wrong ordering in practice. This can be easily fixed by replacing the usage of RenderProcessHostDestroyed by RenderProcessExited in the DedicatedWorkerHost class, which is always invoked first. It also happens that it is a correct change to make because it is when the process exits that the mojo connections with the renderer are closed, not when the RenderProcessHost is destroyed. For consistency, the same change is done with the SharedWorkerHost. Bug: 993029, 1035555 Change-Id: Ib7d71e810cbb8d41f7a7475818d16428eff4e74f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006069 Commit-Queue: Patrick Monette <pmonette@chromium.org> Reviewed-by:
Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#733481}
-
Koji Ishii authored
The logic copied from the version for |NGPaintFragment|. Fixes ~36 tests. Bug: 982194 Change-Id: Ib2b8c55c66429097a38b6f818ab4dd2480f9ba06 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010465Reviewed-by:
Kent Tamura <tkent@chromium.org> Commit-Queue: Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#733480}
-
- 20 Jan, 2020 38 commits
-
-
nancy authored
This CL is used to integrate Web apps's context menus for app list to AppService: https://cs.chromium.org/chromium/src/chrome/browser/ui/app_list/web_app_context_menu.cc?l=69 https://cs.chromium.org/chromium/src/chrome/browser/ui/app_list/web_app_context_menu.cc?l=118 BUG=1038487 Change-Id: I4c28c44e8f31348f5d6af0247285eaa712bc9f9a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007793 Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Cr-Commit-Position: refs/heads/master@{#733479}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/e5aad3baed2b..42a5f6fa3728 git log e5aad3baed2b..42a5f6fa3728 --date=short --first-parent --format='%ad %ae %s' 2020-01-20 primiano@google.com Merge "amalgamator: normalize paths, make output stable" Created with: gclient setdep -r src/third_party/perfetto@42a5f6fa3728 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: perfetto-bugs@google.com Change-Id: I6de098b905a9ab30aaf6fc6fa85dd9f7608c8bd1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010332Reviewed-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@{#733478}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/0c10c9522a3b..62475e95da5b git log 0c10c9522a3b..62475e95da5b --date=short --first-parent --format='%ad %ae %s' 2020-01-20 jmadill@chromium.org Allow tests to pick ANGLE features. Created with: gclient setdep -r src/third_party/angle@62475e95da5b 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/+/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: timvp@google.com Change-Id: Ic5df6598ba6636ff996acb8ae1961cfcab5bdd31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010326Reviewed-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@{#733477}
-
Austin Tankiang authored
Sometimes, the feedback panel tries to call generateSourceMessage for a feedback panel with a cancelled state. This will fail, creating an empty panel. Handle this case to prevent that from happening. It doesn't really matter what gets returned in this case because the panel will not be shown anyway. Bug: 1015415 Change-Id: I599ec0e348c756d93b1a739dba6a239174eec3b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2009603 Commit-Queue: Alex Danilo <adanilo@chromium.org> Reviewed-by:
Alex Danilo <adanilo@chromium.org> Cr-Commit-Position: refs/heads/master@{#733476}
-
Kent Tamura authored
This CL covers the following input types: - <input type=date> - <input type=datetime-local> - <input type=month> - <input type=time> - <input type=week> This CL changes rendering result a little bit in fractional zoom levels. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_layout_tests_layout_ng_disabled Bug: 1040826 Change-Id: I3d3ee1d2b2190721b1b035c7c5ec95f2bc7e7ba1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003152 Commit-Queue: Kent Tamura <tkent@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Reviewed-by:
Yoshifumi Inoue <yosin@chromium.org> Cr-Commit-Position: refs/heads/master@{#733475}
-
Shawn Gallea authored
Webviews are now controlled/created by PlatformViewsService Bug: Internal b/144275588 Test: NONE Change-Id: Id6cb20066a4262f53d6c94d2db3820d06879da96 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011296Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Shawn Gallea <sagallea@google.com> Cr-Commit-Position: refs/heads/master@{#733474}
-
Robbie Gibson authored
Bug: 1043625 Change-Id: Id2e8a226d5df4afdf457dd2443327483f4e08a4e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010791 Auto-Submit: Robbie Gibson <rkgibson@google.com> Commit-Queue: Rohit Rao <rohitrao@chromium.org> Reviewed-by:
Rohit Rao <rohitrao@chromium.org> Cr-Commit-Position: refs/heads/master@{#733473}
-
chromium-autoroll authored
https://chromium.googlesource.com/external/github.com/google/shaderc/+log/c6a2ef12dffc..a32acc1be500 git log c6a2ef12dffc..a32acc1be500 --date=short --first-parent --format='%ad %ae %s' 2020-01-20 rharrison@google.com Rolling 3 dependencies and updating expectations (#966) Created with: gclient setdep -r src/third_party/shaderc/src@a32acc1be500 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/shaderc-chromium-autoroll Please CC radial-bots+chrome-roll@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: radial-bots+chrome-roll@google.com Change-Id: I1e4808954cc9306f6ed768e7251667b35a6828be Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010328Reviewed-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@{#733472}
-
Patrick Monette authored
This CL makes it so that the behavior of the mock class is closer to real implementation of RenderProcessHost. This change will be used in a follow up CL where the lifetime of a class is tied to the existence of the renderer process. Bug: 993029, 1035555 Change-Id: I0c933c7c0b3890bc561015be847e145fdd96410a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006450 Commit-Queue: Patrick Monette <pmonette@chromium.org> Reviewed-by:
Scott Violet <sky@chromium.org> Cr-Commit-Position: refs/heads/master@{#733471}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/5ddbe062..761790f8 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: Ief96e8394ca6dda3beaa257d03c323c868ef0c5a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010930Reviewed-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@{#733470}
-
Nina Satragno authored
Failing on several builders (e.g. https://ci.chromium.org/p/chromium/builders/ci/Win7%20Tests%20%28dbg%29%281%29/81310) Looks like I missed this failure before. TBR=dbeam@chromium.org No-try: true Bug: 1043665 Change-Id: Ic93870517911b2e404e724d0b9c06586bfa45c31 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011292Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Commit-Queue: Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#733469}
-
Shawn Gallea authored
This instead calls OnError to allow for proper cleanup when web contents destruction occurs. Bug: Internal b/146500172 Test: Build cast_shell Change-Id: I4c83313c8324e361cdb0a0275bfa76ea1a5ae72b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1985810 Commit-Queue: Shawn Gallea <sagallea@google.com> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/master@{#733468}
-
Jiewei Qian authored
Change-Id: I5812b9c270706086cc14b5cdc0406188eff31170 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2009592 Auto-Submit: Jiewei Qian <qjw@chromium.org> Commit-Queue: Jay Harris <harrisjay@chromium.org> Reviewed-by:
Jay Harris <harrisjay@chromium.org> Cr-Commit-Position: refs/heads/master@{#733467}
-
chromium-autoroll authored
Roll broadwell AFDO profile from 81-3987.18-1578913441-benchmark-81.0.4019.0-r1 to 81-3987.39-1579516543-benchmark-81.0.4019.0-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-broadwell-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/+/master/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I59d003d2a1ae76b77433b579ef41407441b9ffe5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010330Reviewed-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@{#733466}
-
Aaron Krajeski authored
With the new asynchronous restoring of contexts, things can break (ContextLostRestoredEventsEnabled) Bug: 1042738 Change-Id: Ib8cbe8c5575527e02f2e7245246615ba9c902d1b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003337 Commit-Queue: Aaron Krajeski <aaronhk@chromium.org> Reviewed-by:
Aaron Krajeski <aaronhk@chromium.org> Reviewed-by:
Fernando Serboncini <fserb@chromium.org> Reviewed-by:
Juanmi Huertas <juanmihd@chromium.org> Cr-Commit-Position: refs/heads/master@{#733465}
-
chromium-autoroll authored
Roll airmont AFDO profile from 81-3987.39-1578914089-benchmark-81.0.4019.0-r1 to 81-4025.0-1579516880-benchmark-81.0.4019.0-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-airmont-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/+/master/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: Iafb90e3603f8b1b40ba549afcff986398a11f1f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010329Reviewed-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@{#733464}
-
Nina Satragno authored
Disable CrSettingsPrivacyPageTest.PrivacyPageSoundTests and CrSettingsPrivacyPageTest.UMALoggingTests as they are crashing on Linux Tests (dbg) Looks like the previous revert did not solve the issue :'( TBR=dbeam@chromium.org No-try: true Bug: 1043665 Change-Id: I7711e99fdeeb24c6ba1d6c47e205b16c2dd34431 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011289 Commit-Queue: Nina Satragno <nsatragno@chromium.org> Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#733463}
-
Nick Burris authored
This reverts commit ae629163. Reason for revert: Verifying on Canary that this caused an artificial regression in scroll metrics, will reland. Original change's description: > viz: Fix FindLatestSurfaceUpTo when there is conflict > > The condition used in the binary search was wrong. Fixed it and added > a unit test. > > Bug: 1000868 > Change-Id: Iaf4af1bdfdb88db1082bfae89a3783faed860934 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1800743 > Auto-Submit: Saman Sami <samans@chromium.org> > Commit-Queue: Jonathan Ross <jonross@chromium.org> > Reviewed-by: Jonathan Ross <jonross@chromium.org> > Cr-Commit-Position: refs/heads/master@{#696170} TBR=jonross@chromium.org,samans@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 1000868, 1015120 Change-Id: Ia91e27f3acb11772980c5b5ff872827af53e548f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940998Reviewed-by:
Nick Burris <nburris@chromium.org> Commit-Queue: Nick Burris <nburris@chromium.org> Cr-Commit-Position: refs/heads/master@{#733462}
-
chromium-autoroll authored
Roll silvermont AFDO profile from 81-3987.39-1578912426-benchmark-81.0.4019.0-r1 to 81-4025.0-1579517934-benchmark-81.0.4019.0-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-silvermont-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/+/master/autoroll/README.md Tbr: c-compiler-chrome@google.com Change-Id: I879108952a722cfa0ba7f14b1f9da02d97e0d4eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010327Reviewed-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@{#733461}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/bb76282b5443..abf20c44084a Created with: gclient setdep -r src-internal@abf20c44084a 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: I0153029c5f73b5c834bd52a8a57666f676ef3a53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2009836Reviewed-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@{#733460}
-
Andrew Grieve authored
Causes "git cl format" and "git cl upload" presubmit checks to format changed lines in a review to adhere to our style guide (PEP-8). Bug: 846432 Change-Id: I0a91f85df9f69fff7a87868c40479cad671dc892 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1989512 Auto-Submit: Andrew Grieve <agrieve@chromium.org> Reviewed-by:
Alexander Hendrich <hendrich@chromium.org> Commit-Queue: Alexander Hendrich <hendrich@chromium.org> Cr-Commit-Position: refs/heads/master@{#733459}
-
Navid Zolghadr authored
Feel free to revert if it causes any regressions. Bug: 1000682 Change-Id: Ia65f85a763d20f906e5bcba1f4c3e565dcb64b15 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011135Reviewed-by:
David Bokan <bokan@chromium.org> Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org> Cr-Commit-Position: refs/heads/master@{#733458}
-
Sahel Sharify authored
Change-Id: I2efdc8098f3dd95eefe645701d833dcfd46279ec Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2005375Reviewed-by:
Danyao Wang <danyao@chromium.org> Commit-Queue: Sahel Sharify <sahel@chromium.org> Cr-Commit-Position: refs/heads/master@{#733457}
-
Maksim Ivanov authored
Don't allow the user to submit the dialog (e.g., click "Next") before entering anything into the input field. Before the CL, the user could submit an empty field, which would lead to unexpected effect for the user, since an empty input is treated internally like a cancellation. This CL changes this to only allow cancelling the dialog in case there's no input yet. In the (rare) case the user's smart card is not protected by a PIN, it's the responsibility of the smart card middleware to not request the PIN input at all. Bug: 1024251 Test: start SAML login using a smart card, reach the PIN dialog, check that the "Next" button is disabled and pressing "Enter" has no effect, enter any digit, check that the "Next" button is enabled Change-Id: I07bc8e48ffe802aa0fcfeda45f0db489a95fad5f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2002510Reviewed-by:
Denis Kuznetsov [CET] <antrim@chromium.org> Commit-Queue: Maksim Ivanov <emaxx@chromium.org> Cr-Commit-Position: refs/heads/master@{#733456}
-
Ben Mason authored
TBR=govind@chromium.org Change-Id: If1f3a513057aca9d727ae280a6feffea1f82bf53 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011172Reviewed-by:
Ben Mason <benmason@chromium.org> Reviewed-by:
Krishna Govind <govind@chromium.org> Commit-Queue: Ben Mason <benmason@chromium.org> Cr-Commit-Position: refs/heads/master@{#733455}
-
Nina Satragno authored
Disable virtual/web-components-v0-disabled/external/wpt/html/dom/reflection-grouping.html for linux -- it's flaking on "WebKit Linux Leak" See https://ci.chromium.org/p/chromium/builders/ci/WebKit%20Linux%20Leak/9703 TBR=masonfreed@chromium.org No-try: true Bug: 1043774 Change-Id: I729f72639d69fee4288edc29ea1abd0cb73e3fbb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011283Reviewed-by:
Nina Satragno <nsatragno@chromium.org> Commit-Queue: Nina Satragno <nsatragno@chromium.org> Cr-Commit-Position: refs/heads/master@{#733454}
-
Michael Thiessen authored
This makes tests defined by CalledByNativeJavaTest easier to disable by using the DisabledCalledByNativeJavaTest annotation. Bug: 1042808 Change-Id: I8e30d5a092e765c786927d753b0a3a22be4a605d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008311 Commit-Queue: Michael Thiessen <mthiesse@chromium.org> Reviewed-by:
Yaron Friedman <yfriedman@chromium.org> Cr-Commit-Position: refs/heads/master@{#733453}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/d8f8c29bb25a..0fee6ccc2e6e git log d8f8c29bb25a..0fee6ccc2e6e --date=short --first-parent --format='%ad %ae %s' 2020-01-20 rharrison@chromium.org Rolling 2 dependencies Created with: gclient setdep -r src/third_party/dawn@0fee6ccc2e6e If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/dawn-chromium-autoroll Please CC cwallez@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel Bug: None Tbr: cwallez@google.com Change-Id: I02bb77481c5e97c18d638d178e215d0575bd6fb6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2009835Reviewed-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@{#733452}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/ebf1fafe..5ddbe062 Please follow these instructions for assigning/CC'ing issues: https://v8.dev/docs/triage-issues Please close rolling in case of a roll revert: https://v8-roll.appspot.com/ This only works with a Google account. CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux-blink-rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:linux_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:mac_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:win_optional_gpu_tests_rel CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com Change-Id: I675e740e0895a9ad64ee073ba1d2674b0061a3f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010928Reviewed-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@{#733451}
-
Peng Huang authored
Bug: none Change-Id: I09d906ed6d642e7a819b75d5b36715c5677387e9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010181Reviewed-by:
Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by:
Ken Buchanan <kenrb@chromium.org> Commit-Queue: Peng Huang <penghuang@chromium.org> Cr-Commit-Position: refs/heads/master@{#733450}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/61380c09e241..1a68679e65af git log 61380c09e241..1a68679e65af --date=short --first-parent --format='%ad %ae %s' 2020-01-20 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision f777073e..2a6702f0 (733282:733412) 2020-01-20 ilnik@webrtc.org Propagate is_bw_limited flag with bw allocation everywhere it's copied 2020-01-20 danilchap@webrtc.org Publish DependencyDescriptor structures in the api Created with: gclient setdep -r src/third_party/webrtc@1a68679e65af 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/+/master/autoroll/README.md Bug: None Tbr: webrtc-chromium-sheriffs-robots@google.com Change-Id: I9cf386f91647b8ea75e6bdc0376635abf61e5440 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011213Reviewed-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@{#733449}
-
Chromium WPT Sync authored
Using wpt-import in Chromium 0f9c87a6. With Chromium commits locally applied on WPT: 0f8fd66b "[WPT/common/security-features] Support sub projects and split referrer-policy 4K tests" Note to sheriffs: This CL imports external tests and adds expectations for those tests; if this CL is large and causes a few new failures, please fix the failures by adding new lines to TestExpectations rather than reverting. See: https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md NOAUTOREVERT=true TBR=robertma No-Export: true Change-Id: I36f6d309b6e8c687b740bb5ede428fcaa680d456 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2010927Reviewed-by:
WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/master@{#733448}
-
Randy Rossi authored
This API is requested by the chromevox extension manifest but not used in chromecast. This causes a DCHECK failure in the manifest permissions parser. Adding the feature/permission here so DCHECK doesn't cause failure to install the extension in eng builds. Test: Local build with x86 chromecast simulator (eng) Bug: None Change-Id: I9ceb769b768f15ab523653afe3defc7f1627d9a8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2007477Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Commit-Queue: Randy Rossi <rmrossi@chromium.org> Cr-Commit-Position: refs/heads/master@{#733447}
-
Albert Chaulk authored
This allows querying the CanGoBack status of the underlying app Bug: b/145762033 Test: None Change-Id: I330d7124dd7817db69f5ff41bfa58f6059971113 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008066Reviewed-by:
Luke Halliwell (slow) <halliwell@chromium.org> Commit-Queue: Albert Chaulk <achaulk@chromium.org> Cr-Commit-Position: refs/heads/master@{#733446}
-
Albert Chaulk authored
GRPC appears to barf if Finish() is called on a stream that is still active on the read side. The intent was to allow shutting down by cast_shell at any time, however we have to wait until both read and write are inactive Call OnError() at any time from any thread, sets errored_ The flows now are If this happens between a read completion and the start of the next read - If send_pending_ is false, ReadComplete calls Finish - Else, read_pending_ becomes false - Later, WriteComplete will call Finish If the read has started and a write is pending - If the write finishes first, sets send_pending_ false -- Then, the read completion will call Finish - If the read finishes first, sets read_pending_ false -- Then, the write completion will call Finish A consequence of this is that we can now only shut down most of the time after the next message from the client is received Bug: b/146500172 Test: with patch 1985810 Change-Id: I51df0503b412f86e888143eecae76b6610762552 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2008367 Commit-Queue: Albert Chaulk <achaulk@chromium.org> Reviewed-by:
Daniel Nicoara <dnicoara@chromium.org> Cr-Commit-Position: refs/heads/master@{#733445}
-
chromium-internal-autoroll authored
https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/900f1f215dee..bb76282b5443 Created with: gclient setdep -r src-internal@bb76282b5443 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: chromium:989667 Tbr: jbudorick@google.com Change-Id: Id66a72545bf5b1bf81e5090f1512532736c81a25 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011211Reviewed-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@{#733444}
-
chromium-autoroll authored
https://chromium.googlesource.com/devtools/devtools-frontend.git/+log/fa9410e8e8a6..cbab43ca0aa3 git log fa9410e8e8a6..cbab43ca0aa3 --date=short --first-parent --format='%ad %ae %s' 2020-01-20 tvanderlippe@chromium.org Typecheck Trie.js with TypeScript Created with: gclient setdep -r src/third_party/devtools-frontend/src@cbab43ca0aa3 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/devtools-frontend-chromium Please CC devtools-waterfall-sheriff-onduty@grotations.appspotmail.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: chromium:1011811 Tbr: devtools-waterfall-sheriff-onduty@grotations.appspotmail.com Change-Id: I918401305b15c2805c448f43577b693c9b65818a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011210Reviewed-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@{#733443}
-
chromium-autoroll authored
https://android.googlesource.com/platform/external/perfetto.git/+log/c5af6931c0ed..e5aad3baed2b git log c5af6931c0ed..e5aad3baed2b --date=short --first-parent --format='%ad %ae %s' 2020-01-20 lalitm@google.com bazel: add indirection layer for public visibility 2020-01-20 lalitm@google.com Merge "perfetto: don't enable perfetto before running tests" 2020-01-20 lalitm@google.com Merge "trace_processor: make slice stack ids safe for JS" 2020-01-20 lalitm@google.com Merge "trace_processor: add flamegraph virtual table" Created with: gclient setdep -r src/third_party/perfetto@e5aad3baed2b If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/perfetto-chromium-autoroll Please CC perfetto-bugs@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md Bug: None Tbr: perfetto-bugs@google.com Change-Id: I19c839771a8b37a8d84fa56bc98c1a05e08aea76 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2011145Reviewed-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@{#733442}
-