GitLab

This CL makes BVC's tabModel property synthesized, and changes all uses
of the previous backing ivar to uses of the property.

Change-Id: If75a5b72e0fd222d08a0aa8b7c493d07e404b24f
Reviewed-on: https://chromium-review.googlesource.com/c/1323556
Commit-Queue: Mark Cogan <marq@chromium.org>
Reviewed-by: edchin <edchin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606464}

Bug: 798719
Change-Id: Iee4735a21292c8de2d5f638358844a3b279f92d5
Reviewed-on: https://chromium-review.googlesource.com/c/1320193
Commit-Queue: David Bokan <bokan@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606463}

This is a reland of 3e5be326

The source location of pak resources collected for tests has been
updated to match the new location.

TBR=agrieve@chromium.org

Original change's description:
> Android: Unify pak resource generation for Chrome and Monochrome
>
> Previously, Monochrome used its own set of GN targets to package
> resources, analogous to the ones used for Chrome (some of which are the
> same used for non-Android platforms).  This change moves both variants
> to use matching sets of template-generated targets.
>
> Later, when bundle-specific native libraries are added, this common
> template can be reused again.
>
> BUG=874584
>
> Change-Id: Ia9c34cb0dfa8754207bdee146dbde47f9aca78d3
> Reviewed-on: https://chromium-review.googlesource.com/c/1318418
> Commit-Queue: Christopher Grant <cjgrant@chromium.org>
> Reviewed-by: agrieve <agrieve@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#606060}

Bug: 874584
Change-Id: Ifa3b02a3f87d757435d125eb0c5a15f01d5ca6e1
Reviewed-on: https://chromium-review.googlesource.com/c/1324412Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Eric Stevenson <estevenson@chromium.org>
Commit-Queue: Christopher Grant <cjgrant@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606462}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/e1f79644..82a57102

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: Ieda34914bd96bee6f7f217a8a016b2ce705e2efe
Reviewed-on: https://chromium-review.googlesource.com/c/1326421Reviewed-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@{#606461}

This makes it possible to use CSSPropertyRef to get instances which
represent aliases.

R=futhark@chromium.org

Change-Id: I6098c02678bb36bb08ecb28764893245e747a350
Reviewed-on: https://chromium-review.googlesource.com/c/1323111
Commit-Queue: Anders Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606460}

The pseudo-USS codepath now implements the same UMA metric as the legacy
codepath (SharedChangeProcessor), representing the time required to run
association per datatype (SyncableService::MergeDataAndStartSyncing()).

We are not only interested in the exact timings, but also the *number*
of them, which should be similar.

Bug: 870624
Change-Id: If734966e37cda71b9f2edde3ea4ef8fc4779073b
Reviewed-on: https://chromium-review.googlesource.com/c/1326143
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606459}

Bug: 893494
Change-Id: Ia1d28a678058ce949726e71f511f536482c2eee9
Tbr: emircan@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/c/1326461Reviewed-by: Patrik Höglund <phoglund@chromium.org>
Commit-Queue: Patrik Höglund <phoglund@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606458}

TBR: mahmadi@chromium.org
Change-Id: I0958a168f04de6c4a0564fa6b942c7780d37cde5
Reviewed-on: https://chromium-review.googlesource.com/c/1326155
Commit-Queue: Olivier Robin <olivierrobin@chromium.org>
Reviewed-by: Olivier Robin <olivierrobin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606457}

It will now default to USE_UPLOAD_RATES. We are planning to get rid of that field in the new API.

Change-Id: Idd7d7821d016ec13c0c7e5e03a26f94a52628d42
Reviewed-on: https://chromium-review.googlesource.com/c/1323706
Commit-Queue: Vincent Boisselle <vincb@chromium.org>
Reviewed-by: Roger McFarlane <rogerm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606456}

This add layout tests to ensure javascript code caching is working as
expected. This also adds virtual tests with (
--enable-features=IsolatedCodeCache --site-per-process) to test that the
isolated code cache is behaving as expected. These tests test that:
1. code cache is created on the second visit to the script
2. code cache is consumed on the third visit to the script
3. code cache for the same script resource is not reused if
requested from a different origin (for the virtual tests).

This also adds a timeout expectation for the failing tests.

Bug: chromium:879494
Change-Id: I4504da0fb0222f73bbf12e93d85e12a0717f8749
Reviewed-on: https://chromium-review.googlesource.com/c/1310173
Commit-Queue: Mythri Alle <mythria@chromium.org>
Reviewed-by: Alexei Filippov <alph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606455}

The instrumentation code outputs offsets relative to the start of text
as defined by a special symbol (linker_script_start_of_text). This
currently corresponds to the first symbol appearing in text, which
also happens to be the first SymbolInfo produced by
symbol_extractor. To protect against changes to the symbol_extractor
this change uses the special symbol for the dump offset base rather
than the lowest SymbolInfo offset seen.

Bug: 893981
Change-Id: Ia3d265ae56e6a3b7362abf177c9cbe8d2eda36fb
Reviewed-on: https://chromium-review.googlesource.com/c/1325989Reviewed-by: Egor Pasko <pasko@chromium.org>
Commit-Queue: Matthew Cary <mattcary@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606454}

BUG=b:118418068,b:118408452,b:64996728,b:77833131
TEST=Check the external camera is shown in settings.

Change-Id: I83604f5114d4dcd317c281cf63e9fd50ef619d9f
Reviewed-on: https://chromium-review.googlesource.com/c/1326342Reviewed-by: Ricky Liang <jcliang@chromium.org>
Commit-Queue: Shik Chen <shik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606453}

syncer::WriteNode::Drop() guarantees that if the entity hasn't been
committed to the server, the call gets ignored (i.e. the entity isn't
actually dropped).

Let's mimic the same behavior in the pseudo-USS codepath.
Unfortunately, in order to do so, interface ModelTypeChangeProcessor
needs to be extended.

A TODO is introduced to improve this implementation in the future, when
pseudo-USS is fully launched. This logic could be simplified a lot as
well as the overall complexity of the SyncableService (logic
implemented in DeleteDirectiveHandler) if everything was moved to
history's backend thread.

Bug: 870624
Change-Id: Ic064d809371c49f4281d986b4b30bdb3fa37844a
Reviewed-on: https://chromium-review.googlesource.com/c/1326001
Commit-Queue: Mikel Astiz <mastiz@chromium.org>
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606452}

Blink should be running, and contributing to, the filter-effects tests
https://github.com/web-platform-tests/wpt/tree/master/css/filter-effects

The tests currently in css-filter can then easily be moved to
filter-effects.

Change-Id: Ibf50ee79c5456573e76ec42deebdb7bc727612e4
Reviewed-on: https://chromium-review.googlesource.com/c/1325274
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606451}

https://skia.googlesource.com/skia.git/+log/fa8898747551..6d1df6d9c128


git log fa8898747551..6d1df6d9c128 --date=short --no-merges --format='%ad %ae %s'
2018-11-08 mtklein@google.com limit visibility of opts and optional targets


Created with:
  gclient setdep -r src/third_party/skia@6d1df6d9c128

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

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

This reverts commit 2cc1550c.

Reason for revert: Caused crashes
crbug.com/902832
crbug.com/902848

Original change's description:
> [Reland] Oilpan: Enable HeapCompaction for incremental marking
> 
> Enables HeapCompaction for kIncrementalIdleGC and kIncrementalV8FollowupGC.
> 
> Bug: 864425
> 
> 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
> Commit-Queue: Keishi Hattori <keishi@chromium.org>
> Cr-Original-Commit-Position: refs/heads/master@{#603477}
> Change-Id: I506868b5ea224714491fb4dfd9403e5311550255
> Reviewed-on: https://chromium-review.googlesource.com/c/1316954
> Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
> Reviewed-by: Kentaro Hara <haraken@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605608}

TBR=haraken@chromium.org,keishi@chromium.org,mlippautz@chromium.org

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

Bug: 864425
Change-Id: I864a985719c1c12bf4b56f05d228c6ff8450ef5f
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
Reviewed-on: https://chromium-review.googlesource.com/c/1326341Reviewed-by: Keishi Hattori <keishi@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Keishi Hattori <keishi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606449}

This is a reland of 31bcf8aa
which was a reland of 5528336d,
which was a reland of dd9df78c,
which was a reland of 7bd91635.

Relanding with no changes, seems that this wasn't the cause of
https://crbug.com/902832 after all.

Original change's description:
> Reland^3 "[blink] Control ScriptStreamer with ScriptResource"
>
> This is a reland of 5528336d, which
> was a reland of dd9df78c, which was
> a reland of 7bd91635.
>
> VR tests have been properly deflaked in https://crrev.com/c/1319715, this
> is otherwise unchanged.
>
> Original change's description:
> > Reland "Reland "[blink] Control ScriptStreamer with ScriptResource""
> >
> > This reverts commit c564235f.
> >
> > No changes from the original, VR flakes are caused by issues with
> > loadUrl and have been deflaked (see 894796 for details)
> >
> > Original change's description:
> > > Revert "Reland "[blink] Control ScriptStreamer with ScriptResource""
> > >
> > > This reverts commit dd9df78c.
> > >
> > > Reason for revert: Makes VR tests flaky (https://crbug.com/894796)
> > >
> > > Original change's description:
> > > > Reland "[blink] Control ScriptStreamer with ScriptResource"
> > > >
> > > > This is a reland of 7bd91635
> > > >
> > > > No changes from the original, revert reason is fixed with
> > > > https://chromium-review.googlesource.com/c/1283037
> > > >
> > > > Original change's description:
> > > > > [blink] Control ScriptStreamer with ScriptResource
> > > > >
> > > > > Move the ScriptStreamer control logic from ClassicPendingScript to
> > > > > ScriptResource. In the future, this will allow us to start streaming
> > > > > a ScriptResource before the ClassicPendingScript is available, e.g on
> > > > > preload.
> > > > >
> > > > > The ClassicPendingScript now only sends one "finished" callback, from
> > > > > ScriptResource. This callback is either when the streaming completes,
> > > > > or when there is no streaming and the ClassicPendingScript has told
> > > > > the ScriptResource that it doesn't intend to start streaming. In the
> > > > > long run, we want all scripts to go through the streaming interface,
> > > > > and we want ScriptResource to control when streaming starts, so the
> > > > > "no more streaming" call will disappear -- however it is necessary to
> > > > > maintain the current behaviour, and be able to control it with a
> > > > > runtime flag.
> > > > >
> > > > > Bug: chromium:865098
> > > > > Change-Id: I2c4cc16635a6538b7ff24a24463fe6f34efd8a2e
> > > > > Reviewed-on: https://chromium-review.googlesource.com/c/1181430
> > > > > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
> > > > > Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
> > > > > Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
> > > > > Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
> > > > > Cr-Commit-Position: refs/heads/master@{#599148}
> > > >
> > > > TBR=kouhei@chromium.org,kinuko@chromium.org
> > > >
> > > > Bug: chromium:865098
> > > > Change-Id: I0df324ef8e284f4d3d55a1721d71be5a66a3285c
> > > > Reviewed-on: https://chromium-review.googlesource.com/c/1286450
> > > > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
> > > > Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
> > > > Cr-Commit-Position: refs/heads/master@{#601143}
> > >
> > > TBR=kinuko@chromium.org,rmcilroy@chromium.org,haraken@chromium.org,hiroshige@chromium.org,kouhei@chromium.org,vogelheim@chromium.org,leszeks@chromium.org
> > >
> > > # Not skipping CQ checks because original CL landed > 1 day ago.
> > >
> > > Bug: chromium:865098
> > > Change-Id: Ibdbd7e80d0fcfacc84a73e83d165581c7f1d02d2
> > > Reviewed-on: https://chromium-review.googlesource.com/c/1297138
> > > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
> > > Reviewed-by: Ross McIlroy <rmcilroy@chromium.org>
> > > Cr-Commit-Position: refs/heads/master@{#602310}
> >
> > TBR=kinuko@chromium.org,rmcilroy@chromium.org,haraken@chromium.org,hiroshige@chromium.org,kouhei@chromium.org,vogelheim@chromium.org,leszeks@chromium.org
> >
> > # Not skipping CQ checks because original CL landed > 1 day ago.
> >
> > Bug: chromium:865098
> > Change-Id: I9794fe5366aa8cfc9291d53271ed680465b29a76
> > Reviewed-on: https://chromium-review.googlesource.com/c/1317566
> > Reviewed-by: Leszek Swirski <leszeks@chromium.org>
> > Commit-Queue: Leszek Swirski <leszeks@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#605295}
>
> TBR=kinuko@chromium.org,rmcilroy@chromium.org,haraken@chromium.org,hiroshige@chromium.org,kouhei@chromium.org,vogelheim@chromium.org
>
> Bug: chromium:865098
> Change-Id: I8d6101f51eb33b19ec332a06a310172b371b7fa4
> Reviewed-on: https://chromium-review.googlesource.com/c/1318923
> Commit-Queue: Leszek Swirski <leszeks@chromium.org>
> Reviewed-by: Leszek Swirski <leszeks@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605815}

TBR=kinuko@chromium.org,rmcilroy@chromium.org,haraken@chromium.org,hiroshige@chromium.org,kouhei@chromium.org,vogelheim@chromium.org

Bug: chromium:865098
Change-Id: I73854c4d524ab0cc8e08ef512c10334f0ab5ead4
Reviewed-on: https://chromium-review.googlesource.com/c/1325921Reviewed-by: Leszek Swirski <leszeks@chromium.org>
Commit-Queue: Leszek Swirski <leszeks@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606448}

https://android.googlesource.com/platform/external/perfetto.git/+log/ff46b65fdb14..de6267f6e213


git log ff46b65fdb14..de6267f6e213 --date=short --no-merges --format='%ad %ae %s'
2018-11-08 lalitm@google.com trace_processor: fix slice view for Android traces


Created with:
  gclient setdep -r src/third_party/perfetto@de6267f6e213

The AutoRoll server is located here: https://autoroll.skia.org/r/perfetto-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:119002659
TBR=perfetto-bugs@google.com

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

This flag overrides the default Blink value for content layer.

Sheriffs: This is a dry-run of the feature and will be reverted after
cycling through the waterfall and performance bots.

Tbr: jochen@chromium.org, lfg@chromium.org
Bug: 843903
Change-Id: Ie362301e4874198eb775346d051bf8267837aaf8
Reviewed-on: https://chromium-review.googlesource.com/c/1320970
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Hannes Payer <hpayer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606446}

This replaces a custom subclass of FakeSyncService with the standard
syncer::TestSyncService. It also removed another custom subclass that's
just not used at all.

Bug: 859874
Change-Id: I0ef20ca70a1fdc81649c856c287ed6f1432956f8
Reviewed-on: https://chromium-review.googlesource.com/c/1326149Reviewed-by: Vaclav Brozek <vabr@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606445}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/2c774c363516..63ae28d13da9


Created with:
  gclient setdep -r src-internal@63ae28d13da9

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: I7bcd30ddf6a80e058baf94d98035ae95668384d3
Reviewed-on: https://chromium-review.googlesource.com/c/1326323Reviewed-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@{#606444}

If we are changing :empty to match when there are whitespace children,
we need to know to what extent this affects existing content.

Bug: 447880
Change-Id: I53906fe6295f42cdc72d5ca6d6e58e1aa60786c3
Reviewed-on: https://chromium-review.googlesource.com/c/1326003
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606443}

This removes a bunch of methods/members that aren't used (anymore).

Bug: 859874
Change-Id: Ia3d0c3be3b1bfdaa9230a26e0ad44c9ea359bf43
Reviewed-on: https://chromium-review.googlesource.com/c/1326004Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606442}

Using wpt-import in Chromium 7a397415.
With Chromium commits locally applied on WPT:
270d4abd "ServiceWorker: Add new WPT tests to make sure to update a registration with different script type and identical script content."


Note to sheriffs: This CL imports external tests and adds
expectations for those tests; if this CL is large and causes
a few new failures, please fix the failures by adding new
lines to TestExpectations rather than reverting. See:
https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md

Directory owners for changes in this CL:
kojii@chromium.org, mstensho@chromium.org:
  external/wpt/css/CSS2

NOAUTOREVERT=true
TBR=robertma

No-Export: true
Change-Id: Ib28cea91f2861ffedc9562f3e9a5eeda6c0f7893
Reviewed-on: https://chromium-review.googlesource.com/c/1326223
Commit-Queue: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Reviewed-by: WPT Autoroller <wpt-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#606441}

This CL is a continuation of [1], where AdvancedProtectionStatusManager (production code)
was migrated from SigninManager and OAuth2TokenService to IdentityManager. At this time
the respective unittests are migrated.

The CL adds the adds/changes the following testing APIs:

- IdentityTestEnvironment::WaitForAccessTokenRequestIfNecessaryAndRespondWithToken
receives an extra (optional) parameter |id_token|, and forward it to
FakeProfileOAuth2TokenService::IssueAllTokensForAccount.
This allows the body of AdvancedProtectionStatusManagerTest::MakeOAuthTokenFetchSucceed
to be migrated flawlessly.

- IdentityTestEnvironment::UpdateAccountInfoForAccount. This method updates the account
information for a given known account, by calling AccountTrackerService::SeedAccountInfo.

[1] https://crrev.com/c/1250968

BUG=887266

Change-Id: Ica84fd299794552f2ae6957dfc6c7dde6bba7afa
Reviewed-on: https://chromium-review.googlesource.com/c/1308993
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Nathan Parker <nparker@chromium.org>
Reviewed-by: Jialiu Lin <jialiul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606440}

This CL only migrates DiceResponseHandler production code away from
SigninManager, leaves migration away from ProfileOAuth2TokenService
and unittests for a follow up step.

Note that the unittest c/b/signin/dice_response_handler_unittest.cc
was minimally updated to keep passing.

BUG=890790,902296

Change-Id: Iecdf43b80afe6514b7f19075c2bb62aadfbdbe4c
Reviewed-on: https://chromium-review.googlesource.com/c/1318550
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Colin Blundell <blundell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606439}

Bug: 739170
Change-Id: I147200074ddd29f49d89a246c2a3a9e6cee132d1
Reviewed-on: https://chromium-review.googlesource.com/c/1325987Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606438}

These bots often time out during clobber builds, blocking clang rolls.
Bump the -j number to those used by similar bots.

Bug: 903259
Change-Id: I4ea85b111faf9bf0a441c18730a6a8d0bee20d23
Reviewed-on: https://chromium-review.googlesource.com/c/1326153
Commit-Queue: Hans Wennborg <hans@chromium.org>
Reviewed-by: Takuto Ikuta <tikuta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606437}

Bug: 859874
Change-Id: I7416dee32bd2daf93976f2e63f397a76e9a30b72
Reviewed-on: https://chromium-review.googlesource.com/c/1326006Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606436}

Sometimes sites change forms after adding them. For example removing/
adding fields. This CL makes NewPasswordFormManager process this
situation, by updating |observed_form|, parsing it again and sending
new data to the renderer.

This first time this CL was uploaded on
https://chromium-review.googlesource.com/c/chromium/src/+/1326010 (Patch 1)
but it was reverted because of failures in
password_generation_interactive_uitest.cc. The reason of failures is that
no non-blacklisted confirmation because NewPasswordFormManager waits for
server response. This CL fixes that by turning off waiting of server
predictions.

TBR=isherman@chromium.org

Bug: 895411, 831123, 895788, 902805
Change-Id: I99174a73134c582a3975b1f06d797e61ec117855
Reviewed-on: https://chromium-review.googlesource.com/c/1326010Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Reviewed-by: Vaclav Brozek <vabr@chromium.org>
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606435}

This makes use of the helper IdentityTestEnvironmentProfileAdaptor.
In order to be able to construct the Profile object the same way as the
test originally was, and additional optional parameter was added to
IdentityTestEnvironmentProfileAdaptor::CreateProfileForIdentityTestEnvironment.

BUG=890783

Change-Id: I5c2a48dd4aa7e7377f8a7806717b513b7f27bfe0
Reviewed-on: https://chromium-review.googlesource.com/c/1301814Reviewed-by: Colin Blundell <blundell@chromium.org>
Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Commit-Queue: Antonio Gomes <tonikitoo@igalia.com>
Cr-Commit-Position: refs/heads/master@{#606434}

Currently disabling jumbo for a build target in a local build means
that you also disable jumbo for all other targets with the same local
name, and giving a fully qualified label as name won't work at
all. This patch changes the matching to be more flexible so that you
can supply both a local name (as before) but also a full path or
qualified name like //third_party/blink/renderer/core/svg:svg

Bug: 825240
Change-Id: I706e4d7c3f863a7996e576d36ddd62ac81b8cb12
Reviewed-on: https://chromium-review.googlesource.com/c/1323110
Commit-Queue: Daniel Bratell <bratell@opera.com>
Reviewed-by: Wojciech Dzierżanowski <wdzierzanowski@opera.com>
Cr-Commit-Position: refs/heads/master@{#606433}

Change-Id: I6017cfa22dd176e88b6b6e64a3f594173e2851a2
Reviewed-on: https://chromium-review.googlesource.com/c/1326141Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606432}

Bug: 894363
Change-Id: If32d6e9d3e968b1f063d2b2a59fc84975e34384c
Reviewed-on: https://chromium-review.googlesource.com/c/1325575Reviewed-by: Hans Wennborg <hans@chromium.org>
Commit-Queue: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606431}

The FormData -> PasswordForm parser can see multiple hints from the
server that a field is a new-password field. In particular, this
happens if those fields have the same signature. The parser only can
choose one new-parser field, and on that field, password generation is
offered. If this is any other than the first field, the user has
likely already thought of and typed their new password elsewhere.

Therefore, this CL makes sure that the first hinted new-password field
is marked as such by the parser.

Bug: 902700
Change-Id: Idb065e7391526036347feb586b2a702d74f431a9
Reviewed-on: https://chromium-review.googlesource.com/c/1325986Reviewed-by: Dominic Battré <battre@chromium.org>
Commit-Queue: Vaclav Brozek <vabr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606430}

This reverts commit 5cb9cc29.

Reason for revert: test PlatformThreadWinTest.SetBackgroundThreadModeFailsInIdlePriorityProcess which was added on this CL fails on some bots, 
https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Win7%20%2832%29%20Tests/40510

Original change's description:
> Base: Ensure that SetCurrentThreadPriority(BACKGROUND) sets CPU priority on Windows.
> 
> Previously, SetCurrentThreadPriority(BACKGROUND) did not affect CPU
> priority on Windows in a IDLE process when the
> "WindowsThreadModeBackground" feature was enabled. It only affected I/O
> and memory priorities.
> 
> With this CL, a second call to ::SetThreadPriority() is made to
> ensure that CPU priority is affected.
> 
> Bug: 901483
> Change-Id: I22640c8fa56eeec489fbf0fe516359b828e39541
> Reviewed-on: https://chromium-review.googlesource.com/c/1318438
> Commit-Queue: François Doray <fdoray@chromium.org>
> Reviewed-by: Gabriel Charette <gab@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#606200}

TBR=gab@chromium.org,fdoray@chromium.org

Change-Id: I6ea74d6d1fa14a7b668292e7c7ef75c5ace643e6
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 901483
Reviewed-on: https://chromium-review.googlesource.com/c/1325990Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606429}

Bug: 798719
Change-Id: I05c0bc89c3e842f005be57db2226b4188ee4da3b
Reviewed-on: https://chromium-review.googlesource.com/c/1320812Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: David Bokan <bokan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606428}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/5c68fccf..e1f79644

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: Ice2201b5d289351ae265b6151f3c505fed3f2f38
Reviewed-on: https://chromium-review.googlesource.com/c/1326222Reviewed-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@{#606427}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/538b8fbb4875..491b15b4a4a0


git log 538b8fbb4875..491b15b4a4a0 --date=short --no-merges --format='%ad %ae %s'
2018-11-08 hiroh@chromium.org license_lib.py: Hard-code license of yasm package
2018-11-08 dhanyaganesh@chromium.org repository.py: force-sync supported by default
2018-11-08 dhanyaganesh@chromium.org precq-launcher: move fields from args to kwargs


Created with:
  gclient setdep -r src/third_party/chromite@491b15b4a4a0

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: I3ee1da7578bdcaffd52036327f6e8ec663d5b124
Reviewed-on: https://chromium-review.googlesource.com/c/1325862Reviewed-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@{#606426}

This reverts commit 50ac3f62.

Reason for revert: it breaks ios_webview build https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/ios-webview/988

Original change's description:
> [ios] add manual fallback address cell
> 
> Will merge the cell_utils with card_cell after crrev/c/1303730 is merged.
> 
> Bug: 845472
> Change-Id: Iead98637aeaa8b7e3b0252057b8592ef4fff0529
> Reviewed-on: https://chromium-review.googlesource.com/c/1317853
> Commit-Queue: David Jean <djean@chromium.org>
> Reviewed-by: Eric Noyau <noyau@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#606423}

TBR=noyau@chromium.org,mahmadi@chromium.org,javierrobles@chromium.org,djean@chromium.org

Change-Id: Ib17331c289372d4ad6a1d46ba26906d63c2c3da8
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 845472
Reviewed-on: https://chromium-review.googlesource.com/c/1326152Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Commit-Queue: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606425}