GitLab

Adds xiyuan and mukai

BUG=none
TEST=none

Change-Id: I1bdbc6251e3e3967dd05bda84b7c498527e0ff95
Reviewed-on: https://chromium-review.googlesource.com/c/1279233Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599400}

As channel IDs are disabled by default. It is no longer necessary to
copy keys from the sign-in profile to the user profile on first login.
Removing this now (rather than waiting for channel ID support to be
removed entirely unblocks issue 792678 as no interface for migrating
channel IDs needs to be added to the Network Service.

Bug: 875053
Change-Id: Ia3abef8fa396e41890d8c2ba8fb9083cbcecc71b
Reviewed-on: https://chromium-review.googlesource.com/c/1265998Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Nick Harper <nharper@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599399}

This reverts commit 40fd334b.

Reason for revert: It breaks the "official symbols" upload step, see
crbug.com/894991

Original change's description:
> win: Pass /pdbaltpath:%_PDB% to the linker every time we pass /DEBUG.
> 
> The linker by defaults writes the absolute path to the corresponding pdb
> into executables it creates (if /DEBUG is passed).
> 
> /pdbaltpath:%_PDB% tells it to instead just write the basename of the pdb
> into the executable, which makes the build more reproducible:
> 
> 1. Different build directories no longer cause the part of the exe that contains
>    the pdb path to be different.
> 
> 2. More subtly, the pdb file contains offsets into the executable, and if the
>    pdb path has different lengths on different systems, the pdb file will be
>    different due to the absolute pdb path in the executable.  lld-link sets the
>    UUID of the pdb to the hash of the pdb file contents, and the UUID of the
>    pdb is also stored in the executable.  So this is also one of the parts
>    needed to make the pdb output deterministic.
> 
> (Note that while link.exe has supported /pdbaltpath:%_PDB% for a long time,
> lld-link learned about %_PDB% only very recently, and this CL depends on the
> clang roll https://chromium-review.googlesource.com/c/1271718.)
> 
> Bug: 330260
> Change-Id: If4c505ababa46ed4f51330521ff09f12f6840a47
> Reviewed-on: https://chromium-review.googlesource.com/c/1273475
> Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
> Commit-Queue: Nico Weber <thakis@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#598940}

TBR=thakis@chromium.org,brucedawson@chromium.org

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 330260
Change-Id: Iecb3de9f19f9d4e3932784ba9e68b00001bb8986
Reviewed-on: https://chromium-review.googlesource.com/c/1279225Reviewed-by: Bruce Dawson <brucedawson@chromium.org>
Reviewed-by: Sébastien Marchand <sebmarchand@chromium.org>
Commit-Queue: Bruce Dawson <brucedawson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599398}

Even if this doesn't fix the vector out-of-bounds bug, which I think it would, it is certainly the correct way that AXNodeObject::Markers() should have been written in the first place.

Bug: 889746
Change-Id: Ib58c52213d719321eb975fb1070d83ccfa3cd376
TBR: dmazzoni@chromium.org, aboxhall@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/1277579
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599397}

Merge internal change: 216930277

R=rch@chromium.org

Change-Id: If113650503df293c56bc2aa3be67d0e37df7aa02
Reviewed-on: https://chromium-review.googlesource.com/c/1278966Reviewed-by: Ryan Hamilton <rch@chromium.org>
Commit-Queue: Victor Vasiliev <vasilvv@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599396}

The Keyboard Shortcut Viewer hits this condition -- now it has
a toplevel widget with child content window, and when the mouse
pointer comes to the content window's area, it is unexpectedly
selected, but the toplevel one should be selected.

BUG=863728
TEST=manually, and the new test case covers

Change-Id: I9962114c6b14df412148cf9e6545f32fc5eaa845
Reviewed-on: https://chromium-review.googlesource.com/c/1272089Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Jun Mukai <mukai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599395}

Undoing the first custom link action (i.e. the action that initializes
custom links) will now uninitialize custom links.
Screencast: https://screencast.googleplex.com/cast/NTM5NDQzOTE1MzM4NTQ3Mnw3MDNkZTY0Yy1hZQ

Bug: 881256
Change-Id: I8d77fef71b581d5b6b81ce369d21afd8eb717c31
Reviewed-on: https://chromium-review.googlesource.com/c/1272137
Commit-Queue: Kristi Park <kristipark@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599394}

Fixes the ordering between ContentClient::OnServiceManagerConnected()
and ServiceManagerConnection::Start() in ChildThreadImpl and
UtilityThreadIMpl, ensuring embedders can register their own ConnectionFilters
prior to incoming interface requests being dispatched on the IO thread.

Bug: 894369
Change-Id: Ibaa9290904f1c5004b53111aec687385e4e80a9d
Reviewed-on: https://chromium-review.googlesource.com/c/1279172Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599393}

https://chromium.googlesource.com/catapult.git/+log/c8b97e37ec9c..99b88b0a2d58


git log c8b97e37ec9c..99b88b0a2d58 --date=short --no-merges --format='%ad %ae %s'
2018-10-12 simonhatch@chromium.org Pinpoint - Merge bugs with same root cause.
2018-10-12 benjhayden@chromium.org Change deprecation warnings in /api/alerts to errors.
2018-10-12 benjhayden@chromium.org Cache report names, test suites, and descriptors in v2spa service worker
2018-10-12 chiniforooshan@chromium.org Telemetry: process all rendering pipeline events
2018-10-12 benjhayden@chromium.org Cache session ids in v2spa service worker.
2018-10-12 benjhayden@chromium.org Fix links in rollback.md
2018-10-12 benjhayden@chromium.org Add KeyValueCacheRequest for v2spa service worker.
2018-10-12 benjhayden@chromium.org Add ts_mon metrics to common/timing.py
2018-10-12 benjhayden@chromium.org Add CacheRequestBase for v2spa service worker.
2018-10-12 nednguyen@google.com [Telemetry] Add --test-filter flag that support exact matching of multiple tests
2018-10-12 sadrul@chromium.org rendering: Generate metrics at the 95%ile.
2018-10-12 pasko@chromium.org androidStartupMetric: re-introduce First Contentful Paint
2018-10-12 chrishtr@chromium.org Clean up categories to match current tracing in Blink.
2018-10-11 jbudorick@chromium.org Revert "Enable orderfile memory optimization in benchmarks"
2018-10-11 benjhayden@chromium.org Add task queue for v2spa service worker.
2018-10-11 benjhayden@chromium.org Remove unnecessary file dashboard/test/index.html
2018-10-11 perezju@chromium.org [soundwave] Allow points with missing r_chromium
2018-10-11 chiniforooshan@chromium.org Telemetry: migrate frame_times & percentage_smooth
2018-10-11 ulan@chromium.org [tracing] Restore the minimum mutator utilization metric.
2018-10-11 seanmccullough@chromium.org [chromeperf] add prefix to wct script so tests get found.
2018-10-11 pasko@chromium.org Enable orderfile memory optimization in benchmarks


Created with:
  gclient setdep -r src/third_party/catapult@99b88b0a2d58

The AutoRoll server is located here: https://autoroll.skia.org/r/catapult-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=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:840872,chromium:893199,chromium:867060,chromium:894261,chromium:894287,chromium:886621,chromium:893514,chromium:758566,chromium:879526,chromium:890757,chromium:892385,chromium:877660,chromium:758566
TBR=sullivan@chromium.org

Change-Id: I469ed20d66790fa12e290ad65e2ea51c16cfdba7
Reviewed-on: https://chromium-review.googlesource.com/c/1279078Reviewed-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@{#599392}

This is a reland of 6d83f4b9

Original change's description:
> macOS V2 Sandbox: Report correct sandbox profile for nacl-loader.
>
> The nacl loader process, used only on macOS, currently tries to load an
> invalid profile type under the V2 sandbox. This loads the correct type.
>
> Bug: 892554
> Change-Id: I7b2733db426e3c91181b1f375d791d2918ac6763
> Reviewed-on: https://chromium-review.googlesource.com/c/1268671
> Reviewed-by: Robert Sesek <rsesek@chromium.org>
> Reviewed-by: Derek Schuff <dschuff@chromium.org>
> Reviewed-by: Greg Kerr <kerrnel@chromium.org>
> Reviewed-by: Tom Sepez <tsepez@chromium.org>
> Commit-Queue: Greg Kerr <kerrnel@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#598380}

TBR: rsesek@chromium.org,dschuff@chromium.org,tsepez@chromium.org

Bug: 892554
Change-Id: Ic9cd4da3a17f2a6d36b3ed7145762baf22d8c7f4
Reviewed-on: https://chromium-review.googlesource.com/c/1279201Reviewed-by: Derek Schuff <dschuff@chromium.org>
Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599391}

Added a few more checks to verify the presence of MR dialog before performing different actions.
Also, reorder the test case to avoid the failure of terminating tests affect the next run.

Change-Id: Id5321e1af99e15863158879d323dcd37419197a2
Reviewed-on: https://chromium-review.googlesource.com/c/1278948
Commit-Queue: Clifford Cheng <cliffordcheng@chromium.org>
Reviewed-by: Takumi Fujimoto <takumif@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599390}

Bug: 893386
Change-Id: Id6de56514183945879f4cf6ffdca7ad7beeae3d7
Reviewed-on: https://chromium-review.googlesource.com/c/1279189Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599389}

Change-Id: I3527a04050501edc405f7b1a075c52f81901d9ab
Reviewed-on: https://chromium-review.googlesource.com/c/1279196Reviewed-by: Sam Maier <smaier@chromium.org>
Commit-Queue: Eric Stevenson <estevenson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599388}

Use wtf_size_t when dealing with WTF types.

BUG=879657

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I473e021de35dd792a5d9522bad146e38a6a334f9
Reviewed-on: https://chromium-review.googlesource.com/c/1274188
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599387}

Bug: 721403
Change-Id: If3cae7ab4e1122b98411076d3f72c6088f184c71
Reviewed-on: https://chromium-review.googlesource.com/c/1279227Reviewed-by: Eric Roman <eroman@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599386}

When the view properties event arrives before the view metrics event, we
get a wildly incorrect surface size due to use of an unitialized scale
factor.

We're already checking if it's nonzero before deciding the size, so
initialize it to zero so that this check can work.

Bug: 861853
Test: run_ozone_demo --ozone-platform=scenic --enable-vulkan

Change-Id: I6049e05992b1041ee1f63b1f293f1ac2013c82b0

Reviewed-on: https://chromium-review.googlesource.com/c/1279286Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599385}

R=cmasso@chromium.org

Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I33c673691866d770feb1ad0e8322d4f1ca144ddc
Reviewed-on: https://chromium-review.googlesource.com/c/1279295Reviewed-by: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599384}

BUG=none
TEST=none

Change-Id: If6677be34230f148b0299739325992a174c339ac
Reviewed-on: https://chromium-review.googlesource.com/c/1279235Reviewed-by: Robert Liao <robliao@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599383}

After we enabled flag of NoHoverAfterLayoutChangeEnabled, we did not
see any improvement of the HitTest count, now we do not update the
mouse cursor as well to see if we get any improvement.

We will update the hover effect and mouse cursor after the layout is
changed in a following patch.

Bug: 877132
Change-Id: Ie8e56df652e2b04add2880cb75aa28f52bb92e56
Reviewed-on: https://chromium-review.googlesource.com/c/1274201Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599382}

This code is only used in OOBE so it is safe to just remove it.

Bug: 890367
Change-Id: I54130cc3c115c1a1356a045f443a8a19962686f8
Reviewed-on: https://chromium-review.googlesource.com/c/1279162Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599381}

Bug: 875439
Change-Id: If6c56a4c634ce685a4e1ab93660ae95db7d90716
Reviewed-on: https://chromium-review.googlesource.com/c/1274599Reviewed-by: Mark Pearson <mpearson@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599380}

Add an install warning for the case when an extension requests optional
permissions that are also listed as required permissions. Currently,
only do this for API permissions; a follow-up will handle host
permissions.

Bug: 859959
Change-Id: Ic9dc1a834e3e597aa12fe4136f4f087c6295400f
Reviewed-on: https://chromium-review.googlesource.com/c/1265118
Commit-Queue: Kelvin Jiang <kelvinjiang@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599379}

Bug: 860286
Change-Id: Iec7cf205d6b240cb54b113690e61414e12685df9
Reviewed-on: https://chromium-review.googlesource.com/c/1278160Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
Commit-Queue: Joel Einbinder <einbinder@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599378}

Fix crashes caused by |url_checker_for_testing_| not being initialized
properly.

Additionally, construct UrlValidityChecker with NoDestructor instead of
a global LazyInstance. We prefer to leak singletons to avoid
unnecessary work at shutdown. Also simplify UrlValidityChecker by
passing TickClock, which provides cleaner timeout and duration testing.

Bug: 894742
Change-Id: I468f76e07dc6f551a8515d8416d0c67f5f2035a1
Reviewed-on: https://chromium-review.googlesource.com/c/1277959
Commit-Queue: Kristi Park <kristipark@chromium.org>
Reviewed-by: Mathieu Perreault <mathp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599377}

This is a reland of c8d0d447

Original change's description:
> Use transfer buffer for small transfer cache entries
> 
> OOP-R in RasterImplementation currently allocates the entire free space
> available in the transfer buffer so that it doesn't have to measure
> first then serialize and can just optimistically serialize into that
> space.  This means that other transfer buffer consumers can't use it,
> and are instead forced to use mapped memory.  This turns out to not
> be very efficient for large numbers of small allocations.
> 
> To sidestep this problem, small transfer cache entries are serialized
> into the heap when encountered.  Then when raster is complete, it
> shrinks the transfer buffer down to the correct size and these small
> transfer cache entries are added after it.  Then the commands for these
> entries are submitted first before raster.
> 
> For example, for three transfer cache tasks (A B C) and one raster (R)
> the transfer buffer and ring buffer will look like this:
> 
>     transfer buffer ring buffer: R A B C
>     command buffer: A B C R
> 
> This patch also loosens the restriction on gpu::RingBuffer that there
> can be only one in use block at any time.  This leads to potential
> exhaustion issues because the ring buffer won't reallocate while there
> are in use blocks.  To avoid this, this optimization is only used when
> there is room in the ring buffer without waiting.
> 
> An alternative to this patch would have been to have yet another
> transfer buffer only for the transfer cache or to rewrite oopr
> serialization, but both of those are more invasive solutions.
> 
> On OSX, on the rendering.desktop telemetry benchmark, on the story
> web_animation_value_type_path, this results in the following results:
> 
> gpu-r:
>   raster cpu time: 2.011ms
>   gpu cpu time: 12.891ms
>   total time: 14.902ms
> 
> oop-r:
>   raster cpu time: 7.314ms <- the bug
>   gpu cpu time: 3.804ms
>   total time: 11.118ms
> 
> oop-r + this patch:
>   raster cpu time: 0.812ms
>   gpu cpu time: 3.901ms
>   total time: 4.713ms
> 
> Bug: 804380, 877168
> 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;master.tryserver.blink:linux_trusty_blink_rel
> Change-Id: I586cbca2acb13b8de7d3490c5eb5d6b415f6eda5
> Reviewed-on: https://chromium-review.googlesource.com/c/1262955
> Commit-Queue: enne <enne@chromium.org>
> Reviewed-by: Antoine Labour <piman@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#597654}

Bug: 804380, 877168
Change-Id: I5c7b0d3b43c0c6f57eb7e5a9c43b4b8ecb22518a
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;master.tryserver.blink:linux_trusty_blink_rel
Reviewed-on: https://chromium-review.googlesource.com/c/1277949
Commit-Queue: enne <enne@chromium.org>
Reviewed-by: Antoine Labour <piman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599376}

      It should go away once the "old way" is removed.

Binary-Size: Increase is temporary due to a "new way" / "old way" refactoring.
Bug: 781870
Change-Id: I0425be19fddd9d198e71ed5e6a884b7077f9ffdf
Reviewed-on: https://chromium-review.googlesource.com/c/1263283
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599375}

This reverts commit 677ab843.

Reason for revert: Landing the original rebaseline patch, together with the missing android-specific baselines.

Original change's description:
> Revert "Layout test text dump rebaseline using Element.innerText part 1"
> 
> This reverts commit 90115af8.
> 
> Reason for revert: caused layout test failures on Android:
> 
> * compositing/geometry/bounds-ignores-hidden.html
> * compositing/images/clip-on-directly-composited-image.html
> * crypto/random-values.html
> * crypto/subtle/importKey-badParameters.html
> 
> Original change's description:
> > Layout test text dump rebaseline using Element.innerText part 1
> > 
> > This patch changes tests in the following directories to use
> > Element.innerText for text dump:
> > 
> > accessibility/
> > animations/
> > battery-status/
> > bindings/
> > clipboard/
> > compositing/
> > crypto/
> > 
> > Most of this patch is mechanical rebaseline, except:
> > - Some LayoutNG-specific baselines become redundant and are
> >   removed
> > - One test is turned into failure with LayoutNG flag due to
> >   LayoutNG innerText bug with ellipsis (crbug.com/873957).
> > 
> > Bug: 887148
> > Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
> > Change-Id: Idf28a2696b4824f3fd845c7392b588544e8de1d3
> > Reviewed-on: https://chromium-review.googlesource.com/c/1239165
> > Reviewed-by: Kent Tamura <tkent@chromium.org>
> > Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#599052}
> 
> TBR=yosin@chromium.org,tkent@chromium.org,xiaochengh@chromium.org
> 
> Change-Id: I0018e928bd9789c95c2d923b35296f1f82fd41c4
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 887148, 894841
> Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
> Reviewed-on: https://chromium-review.googlesource.com/c/1278931
> Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
> Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#599255}

TBR=yosin@chromium.org,tkent@chromium.org,xiaochengh@chromium.org

Change-Id: Id023167a88b7d92fab1fcfd1a51fbd6cfb59ba12
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 887148, 894841
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Reviewed-on: https://chromium-review.googlesource.com/c/1279183
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599374}

This CL replaces internal 664674

Bug: 866147
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: Ic7099581b50efb59ec71d6efc518ea7a3be15429
Reviewed-on: https://chromium-review.googlesource.com/c/1273821
Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org>
Reviewed-by: Peter Lee <pkl@chromium.org>
Reviewed-by: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599373}

Not a new regression, just the same one from 10.13.

TBR: kbr@chromium.org
Bug: 871872
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: I161690817b84569ff692e374f6d58a26ca1012db
Reviewed-on: https://chromium-review.googlesource.com/c/1279160Reviewed-by: James Darpinian <jdarpinian@chromium.org>
Commit-Queue: James Darpinian <jdarpinian@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599372}

Bug: 894583
Change-Id: I7c1011ab2f8acffbe93b7523c6839f481f733ae7
Reviewed-on: https://chromium-review.googlesource.com/c/1279203Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599371}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/f9da224859f3..908f8fb5026a


git log f9da224859f3..908f8fb5026a --date=short --no-merges --format='%ad %ae %s'
2018-10-12 vapier@chromium.org paygen: paygen_build_lib: convert to gs.LS
2018-10-12 gmx@chromium.org minnie: enable new tcmalloc


Created with:
  gclient setdep -r src/third_party/chromite@908f8fb5026a

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: Ifb6398b0ccdbc291936a10949c55c649ad69d9d1
Reviewed-on: https://chromium-review.googlesource.com/c/1279088Reviewed-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@{#599370}

This CL updates the UI to show a badge icon in the app menu icon
whenever the user is running Chrome on a currently unsupported Android
version.  This badge in the app menu is only displayed once, until the
user taps the app menu icon. If the user does in fact get a new version,
the badge state is reset, and will be shown again. The current behavior
for out of date users stays the same as before (once per cold start).

In addition, a new menu item is displayed at the top of the menu that
explains that Chrome is unable to update. Nothing happens when you tap
the menu item in the case of an unsupported OS version.

The new menu item and the new warning message in About Chrome will
always be displayed when the user is in this state, regardless of
whether the app menu has already been tapped (which removes the badge).

This CL also updates the UI in Settings - About Chrome to show a new
message and a warning icon when the user is running Chrome on an
unsupported version of the Android OS.

By default, Jelly Bean is considered unsupported after this CL, but this
can be overridden from the variations framework.

It is possible to use command line flags or chrome://flags for
testing the different states, though that does not impact the
About Chrome screen.

Binary-Size: This CL adds new assets and the minimal code required.
Bug: 847940
Change-Id: If128e1692b66c5804928183718000aaf1e2ffaa6
Reviewed-on: https://chromium-review.googlesource.com/c/1243167
Commit-Queue: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599369}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/4bc3c99c2672..5f31aded4251


Created with:
  gclient setdep -r src-internal@5f31aded4251

The AutoRoll server is located here: https://autoroll-internal.skia.org/r/src-internal-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=mmoss@chromium.org

Change-Id: Ifa96df39ee76b855b8b35e23d3874070d86b61b2
Reviewed-on: https://chromium-review.googlesource.com/c/1279073Reviewed-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@{#599368}

Bug: 894622
Change-Id: I26e56c110a35ec21ba34ddc3064a2832184c9c96
Reviewed-on: https://chromium-review.googlesource.com/c/1277690Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ehsan Chiniforooshan <chiniforooshan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599367}

This is a mechanical change.

It introduces ProtocolParser and ProtocolSerializer abstract classes
to allow different protocols in the future. Only the XML implementation
of these classes is provided in this changelist.

Bug: 848505
Change-Id: I4bda0f92f5b676f0f0eaca7dc841c8dca9c282ad
Reviewed-on: https://chromium-review.googlesource.com/c/1278476
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599366}

No change in behavior, just making it explicit how CQ is treating
this builder.

R=ehmaldonado, jbudorick

Bug: 893955
Change-Id: I367748688d5eefa69e582c04089191ea9710a842
Reviewed-on: https://chromium-review.googlesource.com/c/1279168Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599365}

Bug: 828031
Change-Id: I1d4bdb235ad9d93df0653215c7c5928c471b6c16
Reviewed-on: https://chromium-review.googlesource.com/c/1277693Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599364}

This has not been used for a long time and App Store regulations no
longer approves of the use of this type of app rating requests.

Bug: 863559
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I3aa5eb6a190d0577ff202b527c58566702a9ff18
Reviewed-on: https://chromium-review.googlesource.com/c/1278532Reviewed-by: Justin Cohen <justincohen@chromium.org>
Commit-Queue: Peter Lee <pkl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599363}

Previously, the HTTP Auth Cache was implemented as a list of auth
entries, which was searched linearly for a matching entry upon lookup.
This change converts the cache to a multimap keyed on the origin, which
is expected to provide faster lookups in cases where there are no
matching entries for a given origin (which is the majority of cases).
This will also allow for a higher cache size limit without a linear
increase in lookup time, hence the cache size limit is raised from 10 to
20. This is expected to lower the rate of evictions upon adding entries.
Obsolete histograms which no longer apply to the new implementation are
also removed.

Bug: 757116, 614108
Change-Id: Iabd2104b2d1c38d474450978a712039819b038e6
Reviewed-on: https://chromium-review.googlesource.com/c/1273820
Commit-Queue: Lily Chen <chlily@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599362}

ios12-beta-simulator.json
ios12-sdk-device.json
ios12-sdk-simulator.json

CIPD packages:
  infra_internal/ios/xcode/mac  10o35n
  infra_internal/ios/xcode/ios  10o35n

Bug: 894202
Cq-Include-Trybots: luci.chromium.try:ios-simulator-cronet;luci.chromium.try:ios-simulator-full-configs
Change-Id: I3ef7bd7221911e0759c754f67d5764e66442ca7d
Reviewed-on: https://chromium-review.googlesource.com/c/1273822
Commit-Queue: Lindsay Pasricha <lindsayw@chromium.org>
Reviewed-by: Justin Cohen <justincohen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#599361}