GitLab

Use CallStackProfile.Sample.count field for that.

BUG=878604

Change-Id: Ie64d4b173a6b41c0a46d582429b32336fa3fe0cc
Reviewed-on: https://chromium-review.googlesource.com/1197429
Commit-Queue: Alexei Filippov <alph@chromium.org>
Reviewed-by: Mike Wittman <wittman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589755}

Bug: None
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I51bd6d690e40e5c69245595f6b685e435b11b3fc
Reviewed-on: https://chromium-review.googlesource.com/1214424Reviewed-by: Danyao Wang <danyao@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589754}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/aca984cbf105..4d2b901804e0


git log aca984cbf105..4d2b901804e0 --date=short --no-merges --format='%ad %ae %s'
2018-09-08 nodir@google.com [bot_update] Stop using repository properties


Created with:
  gclient setdep -r src/third_party/depot_tools@4d2b901804e0

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:877161,chromium:694348
TBR=agable@chromium.org

Change-Id: Id654c6bb6ee3d471ebe214dd6762179069114c79
Reviewed-on: https://chromium-review.googlesource.com/1214582Reviewed-by: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#589753}

D3D11VideoDecoderClient is subclassed by the D3D11VideoDecoder to allow
accelerators to get and set picture buffers. Since this will be shared
by the H264Accelerator and VP9Accelerator, it should be moved into its
own file.

Bug: 881922
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
Change-Id: If48714459ad29c6f29d7b98c84f3f45cc878d448
Reviewed-on: https://chromium-review.googlesource.com/1214103
Commit-Queue: Ted Meyer <tmathmeyer@chromium.org>
Reviewed-by: Frank Liberato <liberato@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589752}

Original change was a11e3884 (Reviewed
on  https://chromium-review.googlesource.com/1211915).

The original change passed all CQ tests, but was reverted in [1] because
it broke a debug trybot [2]. The fix was just to add an import to
i18n_setup.html in multidevice_feature_behavior.html. Verified all tests
are now passing.

[1] https://chromium-review.googlesource.com/c/chromium/src/+/1212212
[2] https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8936081737798843840/+/steps/viz_browser_tests/0/logs/CrSettingsMultideviceFeatureToggleTest.All/0

Bug: 876796
Change-Id: Ia78bb41ea459f7c31c60a3b3d0fcc9f32bb5eeb2
Reviewed-on: https://chromium-review.googlesource.com/1214422Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Commit-Queue: Jeremy Klein <jlklein@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589751}

Requires crrev.com/c/1213882

Bug: 881910
Change-Id: I725b3c1776ab5f58f6c99624d5b90798b2f14da1
Reviewed-on: https://chromium-review.googlesource.com/1213723Reviewed-by: Ben Pastene <bpastene@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589750}

Bug: 878163
Change-Id: I3e01dacba1cd86753b996d0a55aeefe878dc37f6
Reviewed-on: https://chromium-review.googlesource.com/1213708
Commit-Queue: Kevin Strohbehn <ginko@google.com>
Reviewed-by: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589749}

This CL extracts PIN-setting element into cr_components so that it could be
integrated into another WebUI.

Bug: 852553
Change-Id: Ia7e08465fbaf5d457f1d804dbfc2dbba2e6a5071
Reviewed-on: https://chromium-review.googlesource.com/1212404
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589748}

Split the unique autofill rule into two cases: autofill previewed (fields
are filled when hovering over an autofill suggestion) and autofill selected
(fields are filled with a selected autofill suggestion). We stop styling
based on the old rule, and only keep it around for site compatibility. For now, we keep
the same (CSS) formatting for both rules. A future CL will differentiate
the styles, with options controlled by a flag.

Bug: 880258
Change-Id: I2d9148423442a9bfa51290776f4bf54cea0caf8a
Reviewed-on: https://chromium-review.googlesource.com/1206031
Commit-Queue: Fabio Tirelo <ftirelo@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Fabio Tirelo <ftirelo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589747}

TBR=dtrainor@chromium.org

Bug: 871389
Change-Id: I7bc668e547a2db5f2ece64e2b46bea91708e37fa
Reviewed-on: https://chromium-review.googlesource.com/1211909Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589746}

Bug: 646404
Change-Id: I9c2b313fb869a21190a95ed96542c2197759ce20
Reviewed-on: https://chromium-review.googlesource.com/1214462Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589745}

https://skia.googlesource.com/skia.git/+log/24e8f58cfa9c..2810c856dfa2


git log 24e8f58cfa9c..2810c856dfa2 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader 3655209d86f4..cf47cfdd7c44 (1 commits)


Created with:
  gclient setdep -r src/third_party/skia@2810c856dfa2

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;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=jvanverth@chromium.org

Change-Id: Idca46f57aebba901d1414ada199df702f56954be
Reviewed-on: https://chromium-review.googlesource.com/1213449Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#589744}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/6f64185a..cbaaa59c

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_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;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: I320a48ab373ca2dff46b57f4b042855a122cdd26
Reviewed-on: https://chromium-review.googlesource.com/1214331Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#589743}

1. Set 32ms AV sync threshold.
  - In my measurements the video decoder implementation on some
  platforms will occasionally make 1 frame corrections within itself,
  which AvSync sees as small jumps in the video pts for reasons I do not fully
  understand yet. The AV sync threshold should be greater than
  these jitters, otherwise it kicks in extraneously.

2. Perform In-Sync corrections only when the content is < 5ms in sync.
   This reduces how often AV sync kicks in, as the sync needs to drift
   (32-5)ms until AV sync kicks in again.

3. Reduce the AV sync multiplier from 1% playback rate of change to 0.2%.
   1% was too huge and caused overcorrections.

4. Increase the linear regression time to 1min. This allows us to filter
   out the small jumps mentioned in #1, and we get a much more accurate
   estimate of the video slope as a result.

5. Don't AV sync unless the video slope is calucalted with very low
   error, and with very small slope variance.

6. Don't AV sync content with very low frame rate. This is usually
   audio-only content with a dummy video stream, and AV sync is harmful
   in these cases.

7. Don't apply a linear regression the AV sync difference. This linear
   regression doesn't seem to help, and in some cases seems to obscure
   what's going on.

Bug: b/112240022
Test: cast_media_unittests, manual.

Change-Id: I10584580a98663bd35421e45125f8dc38e8b0647
Reviewed-on: https://chromium-review.googlesource.com/1187704
Commit-Queue: Mina Almasry <almasrymina@chromium.org>
Reviewed-by: Sergey Volk <servolk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589742}

https://chromium.googlesource.com/webm/libvpx.git/+log/753fd86e86ac..4ddfa331c4f5

$ git log 753fd86e8..4ddfa331c --date=short --no-merges --format='%ad %ae %s'
2018-09-05 huisu Initialize the best partition before partition RDO
2018-08-29 marpan vp9-svc: Allow for setting framerate per spatial layer.
2018-08-31 jingning Adaptive ARF factor decision
2018-08-29 jingning Recursive rate allocation for multi-layer ARF coding
2018-08-28 jingning Enable adaptive rate allocation for multi-layer ARFs
2018-09-04 huisu Move partition search ML models to a seperate file
2018-09-04 marpan vp9-svc: Fix to first_spatial_to_encode for pattern constraint.
2018-08-28 jingning Increase encoder buffer for multi-layer ARFs
2018-08-28 jingning Structure the multi-layer ARF locations
2018-09-03 paulwilkins Fix short first kf bug.
2018-08-27 jingning Assign target bits for multi-layer ARF system
2018-09-03 marpan vp9-svc: Add bypass flag to constrain inter_layer.
2018-09-03 paulwilkins Revert "Revert "Prevent double application of min rate in two pass.""
2018-09-02 marpan vp9-svc: Fix condition for pattern constraints
2018-08-27 jingning Properly update the raw_src_frame for psnr calculation
2018-08-25 jingning Build arf index stack
2018-08-31 marpan vp9-svc: Add first_spatial_layer_to_encode per superframe
2018-07-16 huisu ML based rectangular partition search pruning
2018-08-24 jingning Fix arf_src_offset calculation
2018-08-23 jingning Set minimum frame size to be 1 byte
(...)

Created with:
  roll-dep src/third_party/libvpx/source/libvpx
R=johannkoenig@google.com

Change-Id: Iabdcddd52bc1b080b87155333614cb0f07b34627
Reviewed-on: https://chromium-review.googlesource.com/1214362Reviewed-by: Tom Finegan <tomfinegan@chromium.org>
Commit-Queue: Jerome Jiang <jianj@google.com>
Cr-Commit-Position: refs/heads/master@{#589741}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/6dd7eccb9a96..0a162b0cd376


git log 6dd7eccb9a96..0a162b0cd376 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 chrome-bot@chromium.org Update config settings by config-updater.


Created with:
  gclient setdep -r src/third_party/chromite@0a162b0cd376

The AutoRoll server is located here: https://autoroll.skia.org/r/chromite-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.


TBR=chrome-os-gardeners@chromium.org

Change-Id: Ib1f09a89b05371b1d541973da97d0b369c92aa6e
Reviewed-on: https://chromium-review.googlesource.com/1213448Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#589740}

Per the PM's request, add UMA to record how many times the hosted app
menu button are clicked.

Bug: None
Change-Id: Ib52f936ce5029bf7c23ed15f14f724db665d81f9
Reviewed-on: https://chromium-review.googlesource.com/1214084
Commit-Queue: Xiaoqian Dai <xdai@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589739}

Bug: 851636
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Ib44edb874db58d7eeda6551b64bc7f77a88f227c
Reviewed-on: https://chromium-review.googlesource.com/1214074Reviewed-by: Eugene But <eugenebut@chromium.org>
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589738}

This CL records touch action rects for TablePainter. A layout
test is added to ensure its correctness.

Bug: 851674
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ic82e47898ed2b1bf97955dc7fffcf86d9eb7c7e3
Reviewed-on: https://chromium-review.googlesource.com/1213535Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589737}

Before this CL, the ranking order is:
1) visible main frame
2) visible subframe in viewport
3) visible subframe outside of viewport
4) invisible main frame
5) invisible subframe in viewport
6) invisible subframe outside of viewport

This CL moves 4) above 3).

This complicates the comparison algorithm quite a bit, since it's no
longer ok to compare fields independently.

Expand testRanking to cover all cases in the list above.
Also make failures in unit test easier to debug by using
assertArrayEquals.

Bug: 855037
Change-Id: I4aa1c785fcdb6978cfeca9bf8e6989dd6d3153ea
Reviewed-on: https://chromium-review.googlesource.com/1213924Reviewed-by: Siddhartha S <ssid@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589736}

Bug: 868213
Change-Id: Ic990e6dd681159e7c214bfbba54a460c56bb0588
Reviewed-on: https://chromium-review.googlesource.com/1214563Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
Commit-Queue: Ryan Tseng <hinoka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589735}

TBR=smut

Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I189b8ef718f2be0a9591c8914c39d87ee70ebaed
Reviewed-on: https://chromium-review.googlesource.com/1214382
Commit-Queue: iOS Autoroller <ios-autoroller@chromium.org>
Reviewed-by: iOS Autoroller <ios-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589734}

1 - Fixed empty view being chopped off
2 - Hooked up PrefetchStatusProvider to the value of feature

Bug: 882011
Change-Id: Ic4e89a4720b52da84b433092d1de7ace702b431a
Reviewed-on: https://chromium-review.googlesource.com/1213520Reviewed-by: David Trainor <dtrainor@chromium.org>
Commit-Queue: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589733}

In Polymer 2 the following syntax for registering event listeners
is no longer supported.

listeners: {
  'id.eventName': 'onEventName_',
},

Instead the listener must be added either programmatically, or
declaratively directly on the |id| element.

Bug:875470

Change-Id: I84f1d61b9b669dda1922f6c8d5f2bbc8de211c1c
Reviewed-on: https://chromium-review.googlesource.com/1213380Reviewed-by: Esmael El-Moslimany <aee@chromium.org>
Commit-Queue: Demetrios Papadopoulos <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589732}

Array.p.sort does not expect comparator result of BigInt.

BUG=881884

Change-Id: I3215e4dab8dcfc1e4e830cebf07d1dcf674d0d2e
Reviewed-on: https://chromium-review.googlesource.com/1213928Reviewed-by: Erik Luo <luoe@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589731}

It is the initial implementation of UMA heap profiles collection controller.
Profile collection is performed periodically at random moments in time
distributed according to Poisson stream with the intensity of one profile
per 24 hours.

By default the profile collection and reporting is turned off.
It can be enabled with the flag:
--sampling-heap-profiler[=<sampling interval in KB>]
If the interval is not specified the default value of 128KB is used.

Also it can be enabled by a Finch experiment named "SamplingHeapProfiler".
It has a single parameter "sampling-rate-kb" which defaults to 128KB.

Profiles are reported via the same pipeline and format we currently
report CPU profiles.
The only difference is the trigger event for heap profiles is
PERIODIC_HEAP_COLLECTION.

BUG=878604

Change-Id: I172de2c02f41c5d2a073d33d10267fcdc2fdf3a8
Reviewed-on: https://chromium-review.googlesource.com/1194978Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Mike Wittman <wittman@chromium.org>
Commit-Queue: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589730}

This CL modifies the media intent handler enabling logic to also enable
devices that are enterprise-managed.

This CL also moves MediaViewerUtils.updateMediaLauncherActivityEnabled
code into an AsyncTask to avoid the need for disk reads/writes on the
main thread.

Bug: 879647
Change-Id: I29794f2b0ac18e8ce65763c07c4a35b7c8607b8a
Reviewed-on: https://chromium-review.googlesource.com/1200405
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589729}

Previously, the BackgroundVideoTrackOptimization flag was used to
control both src= and MSE videos. MSE videos has been fully decoupled
from the flag now. This CL also uses max_keyframe_distance as a fixed
value, determined by the previous finch experiment on MSE videos.

The chrome://flags entry is also being removed in preparation for the
experiment and (most likely) subsequent enabling of the feature.

Bug: 709302
Change-Id: I3875fc700ceb569da7a7c4fa39b28d938235e6a8
Reviewed-on: https://chromium-review.googlesource.com/1194794
Commit-Queue: Ted Meyer <tmathmeyer@chromium.org>
Reviewed-by: Ken Buchanan <kenrb@chromium.org>
Reviewed-by: Nasko Oskov <nasko@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589728}

On the GmsCore side, EASY_UNLOCK_HOST is blacklisted from being
automatically disabled when BETTER_TOGETHER_HOST is disabled. This is
done to prevent CryptAuth from losing the enabled status of EasyUnlock
on host devices that have grandfathered-in EasyUnlock support. In order
to disable EasyUnlock, it must be done so explicitly. Therefore, when
the user chooses to manually disable all Better Together features via the
"Forget this device" button in Chrome OS or a comparable method on Android,
EASY_UNLOCK_HOST should be explicitly disabled in addition to
BETTER_TOGETHER_HOST.

  - before this change, EASY_UNLOCK_HOST was *not* disabled when "Forget
    this device" button was used, and
  - after this change, EASY_UNLOCK_HOST *was* disabled when "Forget this
    device" button was used.

Bug: 881612
Change-Id: If1f1898a8942f9c42a0f5cceb20095ad1ef087d5
Tested: Manually verified that when EASY_UNLOCK_HOST is blacklisted,
Reviewed-on: https://chromium-review.googlesource.com/1212742Reviewed-by: Jeremy Klein <jlklein@chromium.org>
Commit-Queue: Josh Nohle <nohle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589727}

- Remove separate screen handlers
- Share screen handler with the OOBE screen handler

Bug: b/114310423
Test: Manual Test
Change-Id: I43ce2c88ef53f03f846b7598a9a02b9c4d1511a2
Reviewed-on: https://chromium-review.googlesource.com/1212446
Commit-Queue: Yue Li <updowndota@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589726}

While Chrome checks both the 32- and 64-bit registries to discover
native messaging hosts, Firefox only checks the native registry. This
poses a challenge, as 32-bit installers generally aren't allowed to
install 64-bit components (such as registry keys). However, it turns out
that it is possible to suppress the resulting error, and this CL does
just that, allowing the required keys to be installed in the native
registry on 64-bit Windows.

Bug: 880542
Change-Id: I2552d24ec7dd2e7cce8febdc42b048a1e5caf568
Reviewed-on: https://chromium-review.googlesource.com/1213956
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Reviewed-by: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589725}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/1cefd62ebe68..aca984cbf105


git log 1cefd62ebe68..aca984cbf105 --date=short --no-merges --format='%ad %ae %s'
2018-09-07 cwallez@chromium.org Add test for a weirdness of gclient use_relative_paths and recurse_deps
2018-09-07 tandrii@chromium.org Make ehmaldonado top level OWNER.
2018-09-07 martiniss@google.com `git cl split`: Fix typos in cq_dry_run code
2018-09-07 cwallez@chromium.org gclient_test: use write() for hook tests
2018-09-07 nodir@google.com [bot_update] Pass git_repo param in test
2018-09-07 nodir@google.com Update tryserver to use buildbucket.build.input.gerrit_changes


Created with:
  gclient setdep -r src/third_party/depot_tools@aca984cbf105

The AutoRoll server is located here: https://autoroll.skia.org/r/depot-tools-chromium-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.



BUG=chromium:878117,chromium:694348
TBR=agable@chromium.org

Change-Id: Id3ba13f175eb098bbabd21b9c762561ca134af23
Reviewed-on: https://chromium-review.googlesource.com/1213447Reviewed-by: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: depot-tools-chromium-autoroll <depot-tools-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#589724}

remove skip for fast/js/string-prototype-properties.html and fast/js/date-proto-generic-invocation.html

Bug: v8:7961,v8:7958
Change-Id: Ib71d4084c850824b73c834997683d446f7b62781
Reviewed-on: https://chromium-review.googlesource.com/1212702Reviewed-by: Jungshik Shin <jshin@chromium.org>
Commit-Queue: Frank Tang <ftang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589723}

The code used to assume that a keyboard device name
must include the string "keyboard" in it.
CL at crrev.com/c/1074336 built on this wrong assumption
to detect whether to show external keyboard key remap
settings in the system keyboard settings.

This CL fixes this assumption.

BUG=1074336
TEST=manually, unit test.

Change-Id: I174173097e6da0159c655f724690060ebe74529a
Reviewed-on: https://chromium-review.googlesource.com/1214322Reviewed-by: Kevin Schoedel <kpschoedel@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589722}

Bug: 881212
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
Change-Id: I02462453e8f62286861c9e299d4c7a5dde612666
Reviewed-on: https://chromium-review.googlesource.com/1213877Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Commit-Queue: Dan Sanders <sandersd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589721}

This CL introduces the skeleton UI code for OfflineItems.
see https://docs.google.com/document/d/1xDRCoDYnOb9PvwJ8juSmG75jsE-YKzNomCMaoFtQWtQ/edit#

BUG=881499

Change-Id: Ie31f6bcc77c65a4343f2e5a0be54f3b9b5fdd5bc
Reviewed-on: https://chromium-review.googlesource.com/1211445
Commit-Queue: Min Qin <qinmin@chromium.org>
Reviewed-by: Shakti Sahu <shaktisahu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589720}

Connect selecting a script in the UI with the native side so that it can
be routed to the executor.

R=gogerald@chromium.org, szermatt@chromium.org

Bug: 806868
Change-Id: Icf85027c2e50a073d805dbcb3e99017ce66b5850
Reviewed-on: https://chromium-review.googlesource.com/1206373Reviewed-by: Ganggui Tang <gogerald@chromium.org>
Commit-Queue: Ganggui Tang <gogerald@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589719}

Bug: 877984
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Idcecd7ba8d49fa8045483f7b2309c3e3eecb3b92
Reviewed-on: https://chromium-review.googlesource.com/1211670
Commit-Queue: Mohammad Refaat <mrefaat@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589718}

This enables callers to avoid doing it themselves (centralizing the `memset` in
1 place, rather than duplicating it at every call site that wants it), and to
allow the PartitionAlloc implementation to avoid doing it itself if the
operating system has already zero'd the new page(s).

This is a re-land, with fixes, of
https://chromium-review.googlesource.com/c/chromium/src/+/1162825.

Bug: 864462,680657
TBR: ajwong,haraken
Change-Id: Icfe05bca82c79c8a8029db40b2902271d3d10347
Reviewed-on: https://chromium-review.googlesource.com/1214173Reviewed-by: Chris Palmer <palmer@chromium.org>
Commit-Queue: Chris Palmer <palmer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#589717}

https://skia.googlesource.com/skia.git/+log/24de64834600..24e8f58cfa9c


git log 24de64834600..24e8f58cfa9c --date=short --no-merges --format='%ad %ae %s'
2018-09-07 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader a062f321768d..3655209d86f4 (1 commits)
2018-09-07 reed@google.com Revert "Revert "add flag to soften the blow of removing a legacy api for flutter""
2018-09-07 bsalomon@google.com Preseve tangents when converting cubics->quads in GrAAHairlinePathRenderer
2018-09-07 borenet@google.com [infra] Revert broken recipe rolls, add test for missing patch_ref
2018-09-07 brianosman@google.com Add support for gray + colorspace to SkCodec
2018-09-07 bungeman@google.com Simplify FreeType glyph bounds.
2018-09-07 caryclark@google.com reland fix picture subclass destructor doc
2018-09-07 mtklein@google.com add clamp_gamut
2018-09-07 jvanverth@google.com Revert "add flag to soften the blow of removing a legacy api for flutter"
2018-09-07 borenet@google.com Add new autoroll service accounts to AUTHORS check bypass
2018-09-07 mtklein@google.com remove -k 0 from builds


Created with:
  gclient setdep -r src/third_party/skia@24e8f58cfa9c

The AutoRoll server is located here: https://autoroll.skia.org/r/skia-autoroll

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;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

BUG=chromium:847759
TBR=jvanverth@chromium.org

Change-Id: I5346f6bf867e5501abfe07bf4f1a78db070605b9
Reviewed-on: https://chromium-review.googlesource.com/1213446Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#589716}