- 07 Nov, 2019 40 commits
-
-
chromium-autoroll authored
Roll airmont AFDO profile from 80-3945.13-1572864139-benchmark-80.0.3954.0-r1 to 80-3945.13-1572864139-benchmark-80.0.3960.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 CQ_EXTRA_TRYBOTS= TBR=c-compiler-chrome@google.com Change-Id: I5819503f1f56f89b8165cd9d22b3593302e8f61a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903667Reviewed-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@{#713384}
-
Himanshu Jaju authored
Peer connection sharing capability is added to SharingSpecifics which determines if a remote peer is capable of receiving an incoming request to start a webrtc connection. This helps us to filter out M80+ devices from older devices and reduce failure rates. Bug: 1022288 Change-Id: If23506d07be0532a3e04a30fbd97d28fddd4d9c8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903348Reviewed-by:
Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Richard Knoll <knollr@chromium.org> Commit-Queue: Himanshu Jaju <himanshujaju@chromium.org> Cr-Commit-Position: refs/heads/master@{#713383}
-
chromium-autoroll authored
Roll broadwell AFDO profile from 80-3943.1-1572873357-benchmark-80.0.3954.0-r1 to 80-3943.1-1572873357-benchmark-80.0.3960.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 CQ_EXTRA_TRYBOTS= TBR=c-compiler-chrome@google.com Change-Id: Icd6d5dc40a8c8f3ae79580cc401daafaaa709e63 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903666Reviewed-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@{#713382}
-
Friedrich Horschig authored
If the state changes while or briefly after the bottom sheet is hidden, the BottomSheet#sendOffsetChangeEvents triggers without sheet content which sets the maximum full ratio to 0. Since the hidden full ration is divided by that maximum full ration, the result is NaN which is then propagated to Observers [1]. [1] Sample stack trace of an Observer receiving NaN after onLayout: BottomContainer${EmptyBottomSheetObserver}#onSheetOffsetChanged(NaN, 0); at Rz1.a(PG:2) at org.chromium.chrome.browser.widget.bottomsheet.BottomSheet.a(PG:102) at org.chromium.chrome.browser.widget.bottomsheet.BottomSheet.a(PG:127) at TV1.onLayoutChange(PG:40) at android.view.View.layout(View.java:19677) at android.view.ViewGroup.layout(ViewGroup.java:6075) at android.widget.FrameLayout.layoutChildren(FrameLayout.java:323) at android.widget.FrameLayout.onLayout(FrameLayout.java:261) Bug: 1021885 Change-Id: I21573d91b92f1c017ec2267381c196ae79903545 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1901566Reviewed-by:
Matthew Jones <mdjones@chromium.org> Commit-Queue: Friedrich [CET] <fhorschig@chromium.org> Cr-Commit-Position: refs/heads/master@{#713381}
-
chromium-autoroll authored
https://chromium.googlesource.com/angle/angle.git/+log/cc0919dcb64b..8542baee0645 git log cc0919dcb64b..8542baee0645 --date=short --no-merges --format='%ad %ae %s' 2019-11-07 angle-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/glslang/src 5d0e01d9e7f9..e471df3c9154 (2 commits) Created with: gclient setdep -r src/third_party/angle@8542baee0645 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 jonahr@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_optional_gpu_tests_rel TBR=jonahr@google.com Bug: chromium:None Change-Id: I16da7d893f90abb6c7c8b6c7d121be17b73e9539 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903414Reviewed-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@{#713380}
-
Dominick Ng authored
Bug: None Change-Id: I4d797045609142e466d030b6bb7911ca57cdcc86 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1900788 Auto-Submit: Dominick Ng <dominickn@chromium.org> Commit-Queue: Nancy Wang <nancylingwang@chromium.org> Reviewed-by:
Nancy Wang <nancylingwang@chromium.org> Cr-Commit-Position: refs/heads/master@{#713379}
-
Yuki Shiino authored
__all__ has been misunderstood and unnecessarily defined. Removes __all__ definitions. We don't use |import *|. Bug: 839389 Change-Id: I571600ad50c0d3ef20028efe7fe576cd1ef60762 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903183 Commit-Queue: Hitoshi Yoshida <peria@chromium.org> Reviewed-by:
Hitoshi Yoshida <peria@chromium.org> Cr-Commit-Position: refs/heads/master@{#713378}
-
Maya Lekova authored
Bug: chromium:988677 Change-Id: I8ed3228b225cb98f102f4493a47e9f2a231319ce Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1886412 Commit-Queue: Maya Lekova <mslekova@chromium.org> Auto-Submit: Maya Lekova <mslekova@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#713377}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/81bef5295824..c2ef0f867b79 git log 81bef5295824..c2ef0f867b79 --date=short --no-merges --format='%ad %ae %s' 2019-11-07 achuith@chromium.org xbuddy: Fix for unittest in python3. 2019-11-07 vapier@chromium.org pylintrc: enable overlapping-except check 2019-11-07 vapier@chromium.org pylintrc: enable redefined-variable-type check Created with: gclient setdep -r src/third_party/chromite@c2ef0f867b79 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: Iaf7f20e4cd9a16887b5cd0522fd7c138e8d9d3cd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903413Reviewed-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@{#713376}
-
Vasilii Sukhanov authored
Bug: 998496 Change-Id: I47c837120811b27de1f22fccb35893ccb7c2ebcc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1901471Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org> Cr-Commit-Position: refs/heads/master@{#713375}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/345a2735e2c8..c4420ef3dc6c git log 345a2735e2c8..c4420ef3dc6c --date=short --no-merges --format='%ad %ae %s' 2019-11-07 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/angle2 1d09b983031b..cc0919dcb64b (8 commits) Created with: gclient setdep -r src/third_party/skia@c4420ef3dc6c 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/+/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 TBR=ethannicholas@google.com Bug: chromium:None Change-Id: If7d89f32291844c1dbf0324f5a0bdc72e1760941 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903308Reviewed-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@{#713374}
-
Mihai Sardarescu authored
Desktop Identity Consistency has now launched and we are using a different flag to force the Dice Identity Consistency migration. Note that this feature flag was used in the past by some users to disable browser sign-in, but that no longer works and the users can disable browser sign-in from the chrome://settings/privacy Note that this CL does not remove the corresponding finch feature as that is still required for unit and integration tests until ForceDiceMigration feature is rolled out. Bug: 1021535 Change-Id: Id671b3302af3cc854f2c2decd7511f5401cd0569 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1893273Reviewed-by:
Jochen Eisinger <jochen@chromium.org> Commit-Queue: Mihai Sardarescu <msarda@chromium.org> Cr-Commit-Position: refs/heads/master@{#713373}
-
Marc Treib authored
Bug: 1016712 Change-Id: Iaf86d87d3f53c6446199897f4a2482c49ef5ff2d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1900996Reviewed-by:
Vadym Doroshenko <dvadym@chromium.org> Commit-Queue: Marc Treib <treib@chromium.org> Cr-Commit-Position: refs/heads/master@{#713372}
-
Yang Guo authored
Previous names do not indicate what they actually do. Change-Id: I4ed60f0af77b017b88f95dab90a49a1ba940c57f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1883575 Commit-Queue: Yang Guo <yangguo@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Auto-Submit: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#713371}
-
Fredrik Söderquist authored
With some unlucky combinations of parameters (timing and current time), we could end up spinning in the resolve loop, (re)resolving the same interval over and over, not making forward progress. Guard against this by bumping the next "begin after" value by epsilon if the resolved end is the same as the current "begin after". Bug: 1021630 Change-Id: I71ba25cd423c24428f5d3f41f05fc83a2a1693cb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1901043Reviewed-by:
Philip Rogers <pdr@chromium.org> Commit-Queue: Fredrik Söderquist <fs@opera.com> Cr-Commit-Position: refs/heads/master@{#713370}
-
Michael Lippautz authored
The Visitor parameter was not needed for custom weak callbacks because such callbacks are anyways not allowed to revive an object. Replace the parameter with WeakCallbackInfo which can be used to query liveness information. This allows us to move ObjectAliveTraits and its callers into a heap-private section in future as WeakCallbackInfo is only exposed when such queries are allowed. Renamed RegisterWeakMembers to RegisterWeakCallbackMethod as it is just delegating to RegisterWeakCallback appropriately. The GC plugin bailed out on checking for whether all fields are traced as soon as RegisterWeakMembers was present. The rename now requires changing WeakMember<> to UntracedMember<> because the method name is different. This matches semantics though as WeakMember<> should be automatically cleared by the GC whereas UntracedMember<> is manually cleared by the callback. A followup removes the GC plugin logic. Bug: 982754 Change-Id: I8387c12c06a9c35a6732060dd212290f058a7199 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1899377 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by:
Omer Katz <omerkatz@chromium.org> Reviewed-by:
Kentaro Hara <haraken@chromium.org> Cr-Commit-Position: refs/heads/master@{#713369}
-
chromium-autoroll authored
https://dawn.googlesource.com/dawn.git/+log/f8045a095cc1..64cfaeac4c5d git log f8045a095cc1..64cfaeac4c5d --date=short --no-merges --format='%ad %ae %s' 2019-11-07 yunchao.he@intel.com Reland "Implement readonly storage buffer - validation at API side" Created with: gclient setdep -r src/third_party/dawn@64cfaeac4c5d 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 TBR=cwallez@google.com Bug: None Change-Id: I61963fb40a584f189e43394baa5b6c15c0981336 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903411Reviewed-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@{#713368}
-
chrome://help-appRachel Carpenter authored
This is shown in the launcher with --enable-features=HelpAppV2, otherwise existing Get Help app is shown. Bug: 1012578, b/140960611 Change-Id: I18a56bce24733fa2efa847ad4d2b8db5a7eccc6e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902174 Commit-Queue: Rachel Carpenter <carpenterr@google.com> Reviewed-by:
Trent Apted <tapted@chromium.org> Cr-Commit-Position: refs/heads/master@{#713367}
-
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: I259fa814159f5f85b11515fbfddf3aff0356ffbf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903407Reviewed-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@{#713366}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/b70bebf7..dfb12d9e 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: I0f933d9011be92e00d46ebe1f8dfe1ee547a73e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902429Reviewed-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@{#713365}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/e09342dccb0d..81bef5295824 git log e09342dccb0d..81bef5295824 --date=short --no-merges --format='%ad %ae %s' 2019-11-07 vapier@chromium.org pylintrc: list more 3rd party libs Created with: gclient setdep -r src/third_party/chromite@81bef5295824 If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I2eb62ef34984c46fb7774d2c11656d953a3dd26a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903406Reviewed-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@{#713364}
-
Jochen Eisinger authored
Bug: 1018108 Change-Id: Ia29e269f2335ee91432f3c4eb308d7ae3b8ac72b Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1890431Reviewed-by:
Andrey Kosyakov <caseq@chromium.org> Reviewed-by:
Philip Jägenstedt <foolip@chromium.org> Reviewed-by:
Luke Z <lpz@chromium.org> Reviewed-by:
Robert Sesek <rsesek@chromium.org> Reviewed-by:
Dirk Pranke <dpranke@chromium.org> Reviewed-by:
John Rummell <jrummell@chromium.org> Commit-Queue: Jochen Eisinger <jochen@chromium.org> Cr-Commit-Position: refs/heads/master@{#713363}
-
Adam Rice authored
Coverage indicated that the case where there is an exception looking up a pipeTo or pipeThrough option was not actually tested. Add a web platform test to verify that exceptions are thrown and that options are accessed in the correct order. Change-Id: I88d889a42853ee0625cc51fe30cd119b118289b8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903169Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#713362}
-
Yang Guo authored
https://chromium.googlesource.com/devtools/devtools-frontend/+log/ab8035da9c..e66080e9a1 TBR=aerotwist@chromium.org Change-Id: Icb5a5e75a17f490a436743f042126438b68947e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903346Reviewed-by:
Yang Guo <yangguo@chromium.org> Commit-Queue: Yang Guo <yangguo@chromium.org> Cr-Commit-Position: refs/heads/master@{#713361}
-
Varun Khaneja authored
R=xinghuilu Bug: 963165 Change-Id: I3d78316f61aade1f4f6803e7646c149c12e9661e Fixed: 1021302 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1897002 Commit-Queue: Varun Khaneja <vakh@chromium.org> Auto-Submit: Varun Khaneja <vakh@chromium.org> Reviewed-by:
Mark Pearson <mpearson@chromium.org> Cr-Commit-Position: refs/heads/master@{#713360}
-
chromium-autoroll authored
Roll ChromeOS orderfile from 80-3940.0-1572255699-benchmark-80.0.3951.3-r1 to 80-3943.1-1572866479-benchmark-80.0.3954.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-orderfile-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 CQ_EXTRA_TRYBOTS= TBR=c-compiler-chrome@google.com Change-Id: Ifcd186c5349354dc68447e13f99303988d44c0f6 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1903410Reviewed-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@{#713359}
-
Hiroki Nakagawa authored
Bug: 911415 Change-Id: I6a04f632ba9f5eb5338cb86060cc93e8d20ef852 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1898163 Auto-Submit: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by:
Kenichi Ishibashi <bashi@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/heads/master@{#713358}
-
Trent Apted authored
This is needed to allow JS tests themselves to be compiled to ease future maintenance. js2gtest.js also needs to be compiled for that, which will be done in a follow-up. Hand-crafted externs are added for mock4js since it is not able to be consumed by the compiler directly. axs_testing.js is precompiled and also not easily consumed by the compiler, so appropriate suppressions are added to the a11y methods of test_api.js that deal with it. Bug: 1000989 Change-Id: Ife6b7595674ffc79c2eadc5484d0804830a648ee Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1787477 Commit-Queue: Trent Apted <tapted@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Reviewed-by:
Andrew Grieve <agrieve@chromium.org> Cr-Commit-Position: refs/heads/master@{#713357}
-
Alexey Baskakov authored
This code is disabled by default behind kDesktopPWAsWithoutExtensions and kDesktopPWAsUSS base features. A browser end-to-end tests will be added later in a follow up CL. An MVP implementation of the bridge+sync needed first. Bug: 860583 Change-Id: Ibde266ad7cb74af380b6d5949f4636c2333457e5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1893488Reviewed-by:
Mark Pearson <mpearson@chromium.org> Reviewed-by:
Alan Cutter <alancutter@chromium.org> Commit-Queue: Alexey Baskakov <loyso@chromium.org> Cr-Commit-Position: refs/heads/master@{#713356}
-
chromium-autoroll authored
https://chromium.googlesource.com/chromiumos/chromite.git/+log/62303e032c7c..e09342dccb0d git log 62303e032c7c..e09342dccb0d --date=short --no-merges --format='%ad %ae %s' 2019-11-07 chrome-bot@chromium.org Update config settings by config-updater. Created with: gclient setdep -r src/third_party/chromite@e09342dccb0d If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/chromite-chromium-autoroll Please CC chrome-os-gardeners@google.com on the revert to ensure that a human is aware of the problem. To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+/master/autoroll/README.md CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel TBR=chrome-os-gardeners@google.com Bug: None Change-Id: I409fed5bfffaf9d8e929b6d1f4de0c82a59da91f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902261Reviewed-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@{#713355}
-
Kamila authored
If a media (camera/mic/camera+mic) permission was recently accepted on a site level, but it was blocked on a system level, auto open bubble that leads users to system permissions. Situation this will be triggered: 1) Site asks for media permission. 2) Permission prompt shows on the left side of the omnibox. 3) User accepts the permission prompt. 4) Blocked icon appears on the right side of the omnibox & the bubble which gives the user the option to "Open system preferences" auto-opens. Note that if mic and camera are requested individually, the bubble will auto-open for each of them once. Change-Id: I611b4f256ca4f0793d2e97bb8bc8bc4cd12babe1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1897659 Commit-Queue: Kamila Hasanbega <hkamila@google.com> Reviewed-by:
Balazs Engedy <engedy@chromium.org> Reviewed-by:
Tommy Li <tommycli@chromium.org> Cr-Commit-Position: refs/heads/master@{#713354}
-
chromium-autoroll authored
https://skia.googlesource.com/skia.git/+log/67d43fe58187..345a2735e2c8 git log 67d43fe58187..345a2735e2c8 --date=short --no-merges --format='%ad %ae %s' 2019-11-07 skia-autoroll@skia-public.iam.gserviceaccount.com Roll third_party/externals/swiftshader 215bc7949b35..27a3d31d7a9d (2 commits) 2019-11-07 rosasco@google.com No GL support on Fuchsia. Created with: gclient setdep -r src/third_party/skia@345a2735e2c8 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/+/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 TBR=ethannicholas@google.com Bug: chromium:None Change-Id: Ic8ee40a2ab9dd34e6e950306624808a4f6f55b5d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902262Reviewed-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@{#713353}
-
chromium-autoroll authored
https://webrtc.googlesource.com/src.git/+log/0d65febb94a9..70ec48ca281c git log 0d65febb94a9..70ec48ca281c --date=short --no-merges --format='%ad %ae %s' 2019-11-07 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 47e9a612..59fc3bb1 (713182:713284) Created with: gclient setdep -r src/third_party/webrtc@70ec48ca281c 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 TBR=webrtc-chromium-sheriffs-robots@google.com Bug: chromium:None Change-Id: I213d29f2a7f42023068817215633e724eaa7822d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902479Reviewed-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@{#713352}
-
Ramin Halavati authored
Persistent filesystem is enabled by default in incognito mode. Storage is still done in memory and is deleted when browsing session ends. Tested: third_party/blink/tools/run_blink_wptserve.py out/Default/chrome --incognito \ http://localhost:8001/wpt_internal/file-system-api\ /temporary_vs_persistent.window.html Bug: 990592 Change-Id: I2294dc65c79553917c28541897d5018afaa7b678 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1901079 Commit-Queue: Ramin Halavati <rhalavati@chromium.org> Reviewed-by:
Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#713351}
-
Koji Ishii authored
Following bot results are included. 204 206 207 208 209 TBR=yosin@chromium.org NOTRY=true Bug: 982194 Change-Id: Ia03b3f364433c288ab2427b5c8f46e9f03b501eb Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1901148 Commit-Queue: Koji Ishii <kojii@chromium.org> Reviewed-by:
Koji Ishii <kojii@chromium.org> Cr-Commit-Position: refs/heads/master@{#713350}
-
v8-ci-autoroll-builder authored
Summary of changes available at: https://chromium.googlesource.com/v8/v8/+log/80def79b..b70bebf7 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: I9d07e85bae01c408824a63df36e286232d6628b5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1902588Reviewed-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@{#713349}
-
Adam Rice authored
Remove ReadableStreamNative::PipeToEngine::Promise() getter, which is unused. Change-Id: I2bab42adc6eebdf697f38ecb4fcb96885aefcf1f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1900521Reviewed-by:
Yutaka Hirano <yhirano@chromium.org> Commit-Queue: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/master@{#713348}
-
Meredith Lane authored
Adds in extra test cases relating to moving elements in and out of scope. This behaviour is still under discussion, so is likely to change in future as the API is finalized. Bug=981423 Change-Id: I5863b1f8d7ab1b6287af1d95e859945af38fea60 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1816496 Commit-Queue: Meredith Lane <meredithl@chromium.org> Reviewed-by:
Kent Tamura <tkent@chromium.org> Reviewed-by:
Alice Boxhall <aboxhall@chromium.org> Cr-Commit-Position: refs/heads/master@{#713347}
-
Christopher Lam authored
This CL adds a semantic color file which will be used across all ChromeOS WebUIs such as System Web Apps and System Dialogs. As a strawman, some top-level OS Settings styles have been replaced. Bug: 1018654 Change-Id: Id06fe0a1ae6366e6e990c10f4ee004b330829b7e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1880358Reviewed-by:
Kyle Horimoto <khorimoto@chromium.org> Reviewed-by:
Dan Beam <dbeam@chromium.org> Commit-Queue: calamity <calamity@chromium.org> Cr-Commit-Position: refs/heads/master@{#713346}
-
Will Cassella authored
This enables WebXR sessions to record which features they requested, which features were granted, as well as which features were used or attempted to be used. This also fixes a small bug where the stop time was not being recorded for inline sessions. Bug: 995849 Change-Id: If025e5485dd9a99cd4bf0da63860dcd4f96413f4 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1867199 Commit-Queue: Will Cassella <cassew@google.com> Reviewed-by:
Daniel Cheng <dcheng@chromium.org> Reviewed-by:
Robert Kaplow <rkaplow@chromium.org> Reviewed-by:
Alexander Cooper <alcooper@chromium.org> Reviewed-by:
Klaus Weidner <klausw@chromium.org> Cr-Commit-Position: refs/heads/master@{#713345}
-