GitLab

Implements support for the [ShareMessageOrder] attribute on mojom method
parameters and struct fields. If the field or parameter is a
pending_receiver or pending_remote type (or a container of one of those
types), its handle will be attached to the encompassing serialized
message with the new MOJO_APPEND_MESSAGE_DATA_HANDLE_FLAG_SPLICE flag
set, meaning that interface pipe will begin to share message ordering
with the sending pipe after message transmission.

This support should be sufficient to fully replace usage of associated
interfaces while eliminating all bindings-layer encoding and routing
support for multiplexed pipes.

See bug for design doc link.

Bug: 941809
Change-Id: I5629497705e4e747f9d63ef8198091d7917a41a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548611
Commit-Queue: Ken Rockot <rockot@google.com>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648747}

PatchService is needed for component updater, because
'DeltaUpdateOpPatch::DoRun' calls 'patch::Patch', the underlying service
for 'patch::Patch' is PatchService.

Change-Id: Ic2397ffe38d92ec7ffb8e4fa2e88fc99f5382791
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1543261
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648746}

Currently InProgressDownloadManager is created in DownloadManagerImpl.
However, for content layer, we don't need to create the in-progress DB.
As a result, This CL move InProgressDownloadManager creation to Chrome layer,
it also allows us to construct the SimpleFactoryKey from the profile,
which can later be used to create the SimpleDownloadManagerCoordinator.

BUG=942770

Change-Id: I8f020f2685dd0d6972c56ab1225b440c3c73051b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1555010Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648745}

SkiaRenderer's handling of AA edges is slightly different (up to 10
difference in the RGB values), but perceptually close enough. Add images
specific to SkiaRenderer to the tests AntiAliasing and
AntiAliasingPerspective.

Bug: 947055
Change-Id: If7e9571ec6a038d28786b23e21870ea5a4312146
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553879Reviewed-by: Jonathan Backer <backer@chromium.org>
Commit-Queue: Sean Gilhuly <sgilhuly@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648744}

This is a reland of afff956d

Fixes some trivial uninitialized value bugs only caught by MSAN after
landing. PS1 is the original CL, PS2 is the diff which fixes the bugs.

Original change's description:
> [mojo-core] Support pipe splicing
>
> This change allows message pipes to be "spliced" into other message
> pipes, unifying their message queues while retaining their logical
> independence for routing of written messages.
>
> This is supported by adding an array of per-handle options and flags to
> MojoAppendMessageDataOptions. If a handle is marked with
> MOJO_APPEND_MESSAGE_DATA_HANDLE_FLAG_SPLICE when appended to a message,
> sending that message will effectively cause the handle and its peer to
> be spliced into the sending pipe.
>
> See bug for design doc link.
>
> Bug: 941809
> Change-Id: I191fb4df4c1586bcee91a3ccf595d76869451e7b
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548145
> Commit-Queue: Ken Rockot <rockot@google.com>
> Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#648579}

Bug: 941809
Change-Id: Ia66fa98810fae88023c71b50e5b6fd3862c4474e
TBR: oksamyt@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558190Reviewed-by: Ken Rockot <rockot@google.com>
Commit-Queue: Ken Rockot <rockot@google.com>
Cr-Commit-Position: refs/heads/master@{#648743}

https://skia.googlesource.com/skia.git/+log/09d022cbb8a6..7656b2c18ce8


git log 09d022cbb8a6..7656b2c18ce8 --date=short --no-merges --format='%ad %ae %s'
2019-04-08 reed@google.com Revert "Revert "Move localmatrix routines to shaderbase, no need to be public.""
2019-04-08 ethannicholas@google.com fixed ArithmeticImageFilter input type
2019-04-08 nigeltao@google.com Update Wuffs version
2019-04-08 mtklein@google.com fm_bot: look for and explain too-late flags
2019-04-08 reed@google.com Reland "Revert "Move localmatrix routines to shaderbase, no need to be public.""
2019-04-08 robertphillips@google.com Reduce the number of flush entry points


Created with:
  gclient setdep -r src/third_party/skia@7656b2c18ce8

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=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=egdaniel@chromium.org

Change-Id: I8873153c71294acab33472611b0e3eb8d9d50b3b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558211Reviewed-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@{#648742}

__has_feature is not available in GCC (and that is the reason why
we have HAS_FEATURE macro). So use HAS_FEATURE instead.

BUG=chromium:819294

Change-Id: I41923ff93a69107b160a5f1a5eb4c3056d53300d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554666
Commit-Queue: José Dapena Paz <jose.dapena@lge.com>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648741}

Reland of https://chromium-review.googlesource.com/1020720.

Launching child processes blocks shutdowns. 12% of shutdown hangs on
Windows are caused by this. This CL makes the process launcher sequence
CONTINUE_ON_SHUTDOWN on Windows instead of BLOCK_SHUTDOWN to prevent
these hangs.

There a DCHECKs in place to ensure that CONTINUE_ON_SHUTDOWN tasks
don't access state that is teared down by AtExitManager, local tests
didn't reveal any problem and manual inspection didn't reveal any
access to global state from the process launcher sequence.

https://chromium-review.googlesource.com/1020720 will ensure that
there are no leftover processes on bots with this change, unlike when
this change first landed.

Bug: 830954
Change-Id: If89cfab59698c6b2c827cadd599490e3f5a52e66
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1549478Reviewed-by: Jochen Eisinger <jochen@chromium.org>
Commit-Queue: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648740}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/cfc84d9bdd36..fa0935506a93


Created with:
  gclient setdep -r src-internal@fa0935506a93

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.

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=huangs@chromium.org,battre@chromium.org,collinbaker@chromium.org,tasak@chromium.org

Change-Id: Ieff955611838529a15fa684d959f0cf1b648396c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557891Reviewed-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@{#648739}

Chrome OS displays different types of notifications for Primary and
Secondary Account errors. Primary Account errors and notifications
should be given a higher priority than Secondary Account errors since
the Primary Account is used for Sync and other important System
services.

We can generalize this for other platforms too and prioritize all
Primary Account errors over Secondary Account errors.

Bug: 940419
Test: components_unittests --gtest_filter="*SigninErrorControllerTest*"
Change-Id: I59f6341bb315439f799a11feaae7e7369236903a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1547737Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: David Roger <droger@chromium.org>
Commit-Queue: Kush Sinha <sinhak@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648738}

This reverts commit a3c69dac.

Reason for revert: causing mac failure

Original change's description:
> Apply outline-offset for interested video
> 
> Updates the interest ring UX for video with spatial navigation.
> 
> Bug: None
> Change-Id: Id5a5ac5860859710be8959b1c1923c5982831fd5
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554820
> Reviewed-by: Rune Lillesveen <futhark@chromium.org>
> Commit-Queue: Ian Vollick <vollick@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#648691}

TBR=vollick@chromium.org,pdr@chromium.org,mlamouri@chromium.org,futhark@chromium.org

Change-Id: I40363bd695c72130b271d204f5218c8df361ff9c
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: None
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557750Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648737}

The command parameter can contain not ascii characters
which will not be decoded correctly by fromCharCode.
Using TextDecoder will be more robust to decode the
string.

Bug: 950538
Change-Id: Ia7495c328582585ab8d47038b3c0bd192a40fe37
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556848
Commit-Queue: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648736}

This ensures that it's not possible to lose more than 5
minutes worth of module inspection.

Bug: 932267
Change-Id: Ifdb7e75aaddf01b0e1a07888f65da8cf381e8045
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1542467
Commit-Queue: Patrick Monette <pmonette@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Chris Hamilton <chrisha@chromium.org>
Reviewed-by: Gabriel Charette <gab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648735}

The primary motivation of CL is that the //content/renderer/devtools/
is not related to devtools and hence should be moved.

This CL removes //content/renderer/devtools/ and moves it to
//content/renderer.

Bug: 950171
Change-Id: Id8083f2ef76cbdf70506963d48e38173f552cd1e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557480Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Abhijeet Kandalkar <abhijeet@igalia.com>
Cr-Commit-Position: refs/heads/master@{#648734}

Many chrome.extension methods are directly aliased to their
chrome.runtime counterparts. If the chrome.runtime object has a custom
getter that throws on access, trying to access the chrome.extension
variant will trigger it. Protect against this by checking the result
of the Get() in GetAliasedFeature().

Add regression tests in both a targeted unit test and an end-to-end
browser test.

Bug: 949170
Change-Id: I7405953a7ce735fe7d5fa055de8a5d97a1fbe1db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553804
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648733}

This CL modernizes style and removes repetitive code.

Bug: 929449
Test: display_unittests
Change-Id: I55e360d833a5dae345c071f0ba431cd89d68f39e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553504Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Auto-Submit: Dominik Laskowski <domlaskowski@chromium.org>
Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648732}

Bug: None
Change-Id: Iced96fabe17a47d9b24171bc0a323761836fec99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556781
Auto-Submit: Niels Möller <nisse@chromium.org>
Reviewed-by: Henrik Grunell <grunell@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648731}

In August 2013, Adam Barth wrote an overview of the WTF::String type[1]
and associated classes. Now that we prefer to keep docs in the tree,
move it into Blink's platform/wtf/text directory as a README.

The following edits were made to the doc:

* Markdown formatting (headers, italics, code)
* Updated StringImpl flag count/descriptions
* Updated method names with new casing/spelling.
* Dropped discussion of String::Append() (removed)
* Dropped #blink IRC channel reference


[1] https://docs.google.com/document/d/1kOCUlJdh2WJMJGDf-WoEQhmnjKLaOYRbiHz5TiGJl14/edit?usp=sharing

Change-Id: I6e6c92ef21d32f647487e0558c3fdf66cd7f7e51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1555003
Auto-Submit: Joshua Bell <jsbell@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648730}

Re-encode several extensions as CRX3.

Bug: 740715
Change-Id: I9953fb3fbd98e5076a5bc470e1e6edc114493e2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1515690Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648729}

Empty lists in features files are generally bad, since the features
code in extensions checks lists (like the allowlist) for whether it's
empty, and assumes "empty" means "unspecified". Make empty lists in
features files a compiler error for all keys except 'dependencies'.
('dependencies' is valid, since a child feature may want to override
the dependency list of the parent to be empty.)

Bug: None
Change-Id: Ib6c9db1e7740d5f42556bde79f62f806d7e8619b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553175Reviewed-by: Karan Bhatia <karandeepb@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648728}

This is a reland of fab66bae

Includes necessary change to luci-scheduler.cfg and updated docs.

Original change's description:
> Add new ANGLE Linux and Mac tester configs.
>
> These configs will replace linux_angle_rel_ng and mac_angle_rel_ng.
> They initially mirror the configuration but will soon be updated to
> run only the subsets of tests that are most relevant to ANGLE. This
> should reduce flakiness in ANGLE and reduce load for Chrome.
>
> Also updates related configuration files to include linux-angle-rel
> and mac-angle-rel.
>
> Bug: 822310
> Change-Id: I2b40ed45f5d9e105c088ab166bd2207c96280151
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1551463
> Reviewed-by: John Budorick <jbudorick@chromium.org>
> Reviewed-by: Kenneth Russell <kbr@chromium.org>
> Commit-Queue: Jamie Madill <jmadill@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#647854}

Bug: 822310
Tbr: jbudorick@chromium.org
Change-Id: Iaeeffc7b089b05d379bb353d627d13b39fd43704
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554296
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648727}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/de64cb214d81..36589c6fccb2


git log de64cb214d81..36589c6fccb2 --date=short --no-merges --format='%ad %ae %s'
2019-04-08 evanhernandez@chromium.org controller: Pass correct cwd to commands.py


Created with:
  gclient setdep -r src/third_party/chromite@36589c6fccb2

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.

CQ_INCLUDE_TRYBOTS=luci.chromium.try:chromeos-kevin-rel
TBR=chrome-os-gardeners@chromium.org

Change-Id: Ic3216a1f8ed0ea5f4e8ccd03a6893d7aaab8f04e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558210Reviewed-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@{#648726}

- Moves the AutoFillEditItem/Cell implementation into TableViewTextEditItem.
- Renames AutoFillEditItemUnittest to TableViewTextEditItemUnittest
- AutoFillEditItem is now a subclass of TableViewTextEditItem.
- Moves the edit_icon resources from autofill to tableview.

Screenshot:
https://drive.google.com/open?id=1VERKBwioAvqjNhk3j3AWA9DNuW7OxgMJ


Bug: 945478
Change-Id: I4d6633d7c26ca8f0b5a0f009549a1f77ec8753d1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554281Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Reviewed-by: Moe Ahmadi <mahmadi@chromium.org>
Commit-Queue: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648725}

external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/counter-styles-3/symbols-function.html
also fails on Linux and release builds. Labeling the bug as failing there as
well.

TBR=mstensho@chromium.org

Bug: 935689
Change-Id: I3b3b0c5330594bfd6df1a9b77a912d928b776862
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1558230Reviewed-by: Dominic Battré <battre@chromium.org>
Commit-Queue: Dominic Battré <battre@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648724}

As some of those writes are ignored by PrepareTarget, they end up being to
before the buffer's base, which messes with the expansion calculations
before getting the "exit when length == 0" case; but those writes do not
expand, so they can exit before the expansion handling.

Bug: 946538
Change-Id: I9afd9371b16e4d80a5e1f11ec739e49a688bcef5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554780Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Maks Orlovich <morlovich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648723}

https://webrtc.googlesource.com/src.git/+log/59e875ce18bb..e9d2b4efdd5d


git log 59e875ce18bb..e9d2b4efdd5d --date=short --no-merges --format='%ad %ae %s'
2019-04-08 jeroendb@webrtc.org Revert "Remove old audio device implementation."
2019-04-08 orphis@webrtc.org Revert "Remove TaskQueue constructor that uses GlobalTaskQueueFactory"
2019-04-08 eladalon@webrtc.org Rename EncoderKeyFrameCallback back to EncoderRtcpFeedback
2019-04-08 eladalon@webrtc.org Give VideoSendStreamImpl access to RTP timestamps
2019-04-08 kthelgason@webrtc.org Remove old audio device implementation.
2019-04-08 sprang@webrtc.org Update VideoStreamEncoder to use new VideoEncoder::SetRates() method.
2019-04-08 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision baccefbc..7987ebdc (648532:648632)
2019-04-08 eladalon@webrtc.org Add RtpSequenceNumberMap::InsertFrame()
2019-04-08 asapersson@webrtc.org Remove unused members in VCMJitterEstimator.
2019-04-08 nisse@webrtc.org Delete placeholder code for Windows Media Foundation capturer.
2019-04-08 eladalon@webrtc.org Fix timeout in rtcp_receiver_fuzzer - limit input length
2019-04-08 kron@webrtc.org Fix potential bug due to malformed input
2019-04-08 kuddai@google.com Change PlayoutLatency setLatency zero-threshold value.
2019-04-08 titovartem@google.com Add stream labels into PeerConnection level smoke test.
2019-04-08 nisse@webrtc.org Move enum VideoType out of common_types.h
2019-04-08 titovartem@google.com Fix naming in NetworkEmulationManager: endpoint_controller -> endpoint_container
2019-04-08 kron@webrtc.org Make UDP receive buffer size configurable via field trial
2019-04-08 benwright@webrtc.org Added FrameDecryptorInterface::Result constructor and IsOk() member function.
2019-04-07 mbonadei@webrtc.org Implement DefaultAudioQualityAnalyzer.
2019-04-07 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 58ec016f..baccefbc (648432:648532)
2019-04-06 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 0a611f37..58ec016f (648329:648432)
2019-04-05 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 37663bcc..0a611f37 (648215:648329)
2019-04-05 benwright@webrtc.org Add Result FrameDecryptorInterface::Decrypt
2019-04-05 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision f91f8258..37663bcc (648096:648215)
2019-04-05 srte@webrtc.org Using simulated time for GoogCC tests.
2019-04-05 gustaf@webrtc.org AEC3: Enable usage of external delay estimator
2019-04-05 philipel@webrtc.org Tune VideoCodecTestLibvpx.TemporalLayersVP8 thresholds.
2019-04-05 srte@webrtc.org Running scenario quality unit tests in simulated time.
2019-04-05 danilchap@webrtc.org Remove TaskQueue constructor that uses GlobalTaskQueueFactory


Created with:
  gclient setdep -r src/third_party/webrtc@e9d2b4efdd5d

The AutoRoll server is located here: https://autoroll.skia.org/r/webrtc-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:None,chromium:none,chromium:None,chromium:948469,chromium:949020,chromium:939340,chromium:None,chromium:None,chromium:None,chromium:None,chromium:b/130016532,chromium:none
TBR=webrtc-chromium-sheriffs-robots@google.com

Change-Id: I47cf11c55e2695f3d95d4e9109726ab7477a85f0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557892Reviewed-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@{#648722}

The script still works with Python 2.
There are no intended behaviour changes.

Bug: 941669
Change-Id: I9d0d56b95eccc82da7820347877f4df0339ff731
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556773
Auto-Submit: Raul Tambre <raul@tambre.ee>
Commit-Queue: Asanka Herath <asanka@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648721}

[Explore sites][Touchless]: Ensure that category title will always be visible when a site has focus.

Bug: 944258
Change-Id: I7bae69cad28c93affd08afcb8646dfc52ec0e4de
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1550002Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Commit-Queue: Justin DeWitt <dewittj@chromium.org>
Commit-Queue: Cathy Li <chili@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648720}

Bug: 881076
Change-Id: I4b6172fb454138a622a1beb671c5c54a51171390
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1548067
Auto-Submit: Joshua Pawlicki <waffles@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Commit-Queue: Joshua Pawlicki <waffles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648719}

Bug: 944754
Change-Id: I653d8dc62723ddf631dfd2ef78b14e4675c1ca63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1553542Reviewed-by: Evan Stade <estade@chromium.org>
Commit-Queue: Jochen Eisinger <jochen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648718}

https://swiftshader.googlesource.com/SwiftShader.git/+log/edab510dfad8..eba396cc66d3


git log edab510dfad8..eba396cc66d3 --date=short --no-merges --format='%ad %ae %s'
2019-04-08 bclayton@google.com Rename 'unittests' to 'gles-unittest'


Created with:
  gclient setdep -r src/third_party/swiftshader@eba396cc66d3

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-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.

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=swiftshader-team+autoroll@chromium.org

Change-Id: Ic4700466e08ad379206afcdb10bb26fedb9984d9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557986Reviewed-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@{#648717}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/eec47f93..c796dae2

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: I8235e1ecd3a5aa77374dea39e69d7a952accf52c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557788Reviewed-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@{#648716}

The root cause should be fixed in crrev.com/c/1553501 . This CL simply
enables the test.

Bug: 845879
Change-Id: I396396ef661501855a1f3082449f8a1caa246eaf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1555251Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Commit-Queue: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648715}

Bug: 641225
Change-Id: I743d0ef2269935e76ce26ee874b4e15f35c50fd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1067603
Commit-Queue: Steven Valdez <svaldez@chromium.org>
Reviewed-by: Steven Valdez <svaldez@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648714}

This matches the HostResolverManager behavior where all requests get
silently cancelled if the manager is destroyed. Now if a
ContextHostResolver is destroyed, all requests created by that resolver
get silently cancelled, leaving requests from other resolvers alone.

Motivation:
For DoH, need to ensure that if a context (and its per-context resolver)
are destroyed, any requests potentially using that context for DoH are
cancelled. Previously, DoH always used the "primary" context and we took
special care to cancel all DNS requests on destruction of that context,
but DoH will soon use any context from the per-context resolvers.

Bug: 934402
Change-Id: I99d087bdd17ac8e2bd54efa4c425e63abf0568ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1549897Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Eric Orth <ericorth@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648713}

This CL updates wpr files for leak detection.

Change-Id: Ibac5224621fb0ceee65f68888afa0480602ae396
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1554464Reviewed-by: Keishi Hattori <keishi@chromium.org>
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648712}

The AutoRoll server is located here: https://autoroll.skia.org/r/fuchsia-sdk-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.


CQ_INCLUDE_TRYBOTS=luci.chromium.try:fuchsia-arm64-cast;luci.chromium.try:fuchsia-x64-cast
TBR=cr-fuchsia+bot@chromium.org

Change-Id: I88eb3a84fe94f81d7d1ec9d75c336911ada37a01
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1557987Reviewed-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@{#648711}

Bug: 944079
Change-Id: If6b80ec575b38423e66832061bb239f67f24df93
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1541816
Commit-Queue: Moe Ahmadi <mahmadi@chromium.org>
Reviewed-by: anthonyvd <anthonyvd@chromium.org>
Reviewed-by: Mike Dougherty <michaeldo@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648710}

This CL adds another field predicted_scroll_update_delta to keeps the
scroll delta after prediction. And also updates the AverageLag to
take the predicted_scroll_update_delta into account.

Bug: 946212
Change-Id: I1ba2bc5bd644c630d53d7f02d6ab4c4c4259f09b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1549346
Commit-Queue: Ella Ge <eirage@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648709}

Bug: chromium:854385
Change-Id: Iae271e42cea733464730e7560b7caa52f57860f4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1556844
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#648708}