GitLab

The MultiSourceMemoryPressureMonitor is the new default memory pressure
monitor and this class will eventually be merged with the
MemoryPressureMonitor one, in the meantime this change will allow
downcasting the fake monitor into a multi source monitor.

Change-Id: I6ccd1f196a6e50f1fa7f2a7a547fc326732f97aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1835161Reviewed-by: François Doray <fdoray@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703538}

Change-Id: I7be1eae82702d0576e6bcd701c985be97724c7dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1839279
Commit-Queue: Julian Watson <juwa@google.com>
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Auto-Submit: Julian Watson <juwa@google.com>
Reviewed-by: Nicholas Verne <nverne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703537}

Before the fix, when trying to edit an editable directory
in bookmarks, the font style is set to Google Sans. This fix
reset the style to be consistent with other bookmarks editing style

Bug: 1003551
Change-Id: I3339f9c07b6823c0a0ba32cdcd04f32ee6471705
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846038Reviewed-by: Theresa  <twellington@chromium.org>
Commit-Queue: Wenyu Fu <wenyufu@google.com>
Cr-Commit-Position: refs/heads/master@{#703536}

This CL adds guado-kernelnext to the import mode blacklist used by the
video_decode_accelerator(_perf)_tests. The blacklist makes sure the tests are
run in allocate mode on devices not supporting import mode. Currently only guado
is on the blacklist, this CL adds guado-kernelnext.

TEST=compiled video_decode_accelerator_tests

BUG=b:139841588

Change-Id: Icee92dffa9134d3da06542d130f522f5b7b48e4b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844751Reviewed-by: Hirokazu Honda <hiroh@chromium.org>
Commit-Queue: David Staessens <dstaessens@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703535}

Looks like they're not used.

Change-Id: I78acd0704c1d3caff98f54e9124f968ee65cd234
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845581Reviewed-by: Peter Kvitek <kvitekp@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Commit-Queue: Johannes Henkel <johannes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703534}

Tbr: nasko@chromium.org
Change-Id: Ief500917465b2cdf29f07ee627248aa7f3b9a2de
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1842752
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703533}

This enables code that tests the crash reporter subsystem to collect
crash dumps.

Bug: 983725
Change-Id: I9454fb24423a631f36fd01b56050deacde2219b8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1836661Reviewed-by: Ian Barkley-Yeung <iby@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Miriam Zimmerman <mutexlox@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703532}

Refactors most of the code from "PixelIntegrationTest" and
"CloudStorageIntegrationTestBase" into "SkiaGoldIntegrationTestBase",
deleting some old unused code in the process. "PixelIntegrationTest" now
only contains code specific to the tests invoked via the "pixel" test
type.

Bug: 1008524
Change-Id: Ibe8e80ea7a4e16becd889d1484738e1abbcf32bc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845951
Auto-Submit: Brian Sheedy <bsheedy@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703531}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/9ccec3700953..fa01042385e5


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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://skia-autoroll.corp.goog/r/src-internal-chromium-autoroll
Please CC jbudorick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chrome.try:linux-chromeos-chrome
TBR=jbudorick@google.com

Bug: chromium:None
Change-Id: Iaa90056863f31b38687dbf2af520f01a84f5776e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845708Reviewed-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@{#703530}

This change updates gen_include_files in the build.gn
to account for the files included in test code via
GEN_INCLUDE.

With this change, dependencies should now be expressed
correctly, and will pick up future updates to
axe-core.

gen_include_files are both read at compile time, and
included at runtime. This means they support compile
time directives like GEN and GEN_INCLUDE which can
generate code and include further files - and those
further files could have their own directives, and so on.

Bug: 984817
Change-Id: Iabde6f2c5c7c2c3dedb1c32e45c086e11ec6d4ae
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841575Reviewed-by: Hector Carmona <hcarmona@chromium.org>
Commit-Queue: Mike Jackson <mjackson@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#703529}

When a longhand value is omitted, the longhand should have the specific
initial value for the shorthand, not 'initial'.

Bug: 501673, 772772
Change-Id: I0986013e6785852861b79926dd0696314c758ff7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1839934Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703528}

This fixes the following error on Python 3:

Traceback (most recent call last):
  File "tools/flags/generate_expired_list.py", line 126, in <module>
    main()
  File "tools/flags/generate_expired_list.py", line 120, in main
    output = gen_expiry_file(sys.argv[0], sys.argv[1])
  File "tools/flags/generate_expired_list.py", line 107, in gen_expiry_file
    output += gen_file_body(list_flags.load_metadata(), get_chromium_version())
  File "tools/flags/generate_expired_list.py", line 96, in gen_file_body
    flags = list_flags.keep_expired_by(flags, mstone)
  File "/usr/local/google/home/cbiesinger/chromium/src/tools/flags/list_flags.py", line 46, in keep_expired_by
    return [f for f in flags if -1 != f['expiry_milestone'] <= mstone]
  File "/usr/local/google/home/cbiesinger/chromium/src/tools/flags/list_flags.py", line 46, in <listcomp>
    return [f for f in flags if -1 != f['expiry_milestone'] <= mstone]
TypeError: '<=' not supported between instances of 'int' and 'str'

Bug: 941669
Change-Id: Ia2c7cb7e618a1407d79c0a868358f88b579778b5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845583
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703527}

Because the media controls are not the target of the events, we do not benefit
from the built-in mechanism for preventDefault(). This change makes sure that we
follow preventDefault() when needed. Worth noting that because of when the event
is run, the website event handler may run after the media controls one.
Registering the event handlers before inserting the element to the tree should
guarantee the order.

Bug: 947373
Change-Id: Ic43a42ecbc370ddd57a4ccb6461878fce53f7275
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845775Reviewed-by: Tommy Steimel <steimel@chromium.org>
Commit-Queue: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703526}

The configuration is "generated" by copying the hand-written files to
the generated subdirectory. The LUCI project configuration must be
updated to point at the new location before the hand-written
configuration files can be removed in favor of being actually generated
by starlark.

Bug: 1011908
Change-Id: I81349a96876315045694df809ab1fbf6c28ce91d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845698
Auto-Submit: Garrett Beaty <gbeaty@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703525}

This is a reland of d6027891

It was pointed out as a suspicious CL for crbug.com/1008178 and reverted.
But, it turned out it's not related to the issue. So, it's relaned
without any change from the original CL.

Original change's description:
> Convert nacl.mojom to new Mojo types
>
> This CL converts NaClRendererHost and NaClExitControl
> to new Mojo types.
>
> It also updates ProvideExitControl from nacl.mojom
> and methods and members which implement it.
>
> Bug: 955171
> Change-Id: Ie6b875e07796b08818825474e8493e5f48072c3f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1810509
> Reviewed-by: Bill Budge <bbudge@chromium.org>
> Reviewed-by: Derek Schuff <dschuff@chromium.org>
> Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
> Reviewed-by: Sam McNally <sammc@chromium.org>
> Commit-Queue: Julie Kim <jkim@igalia.com>
> Cr-Commit-Position: refs/heads/master@{#697852}

TBR=bbudge@chromium.org,dschuff@chromium.org

Bug: 955171
Change-Id: I1024c06b573794a885f8ed856613ea27909e33a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844511
Commit-Queue: Julie Kim <jkim@igalia.com>
Reviewed-by: Oksana Zhuravlova <oksamyt@chromium.org>
Reviewed-by: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703524}

Bug: 945505
Change-Id: I0b3881acef1b32e3bb2e91dfc3d561ea085efd65
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845855Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703523}

TBR=govind@chromium.org

Change-Id: Id6724fba5b8ff5ed1eb82ce43b34ac20340330e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1844058Reviewed-by: Ben Mason <benmason@chromium.org>
Reviewed-by: Krishna Govind <govind@chromium.org>
Commit-Queue: Krishna Govind <govind@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703522}

Change-Id: I5ed097d771b141cd920fb6b9b4d4bc834c588d7f
Bug: 1009446
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1829464
Commit-Queue: Michael Thiessen <mthiesse@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: Edward Jung (EMEA) <edwardjung@chromium.org>
Reviewed-by: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Chris Palmer <palmer@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703521}

This change introduces keyboard navigation support by enabling the time columns
to receive focus via tabIndex.

Also for non-ampm columns an infinite like navigation behavior is implemented using
the following algorithm:
   - initial list of values is doubled so the column content is going to be: list1, list1
   - when selected value is the first item from the list and the user pressed ArrowUp the new
selected value is going to be the last item from the first list in order to have the previous
selected item right below the new one
   - similarly when the selected value is the last item from the second list and the user pressed
ArrowDown the new selected value is going to be the first item from the second list
   - this behavior is achieved by using scrollIntoView and scrollIntoViewIfNeeded which also take
care of properly aligning the items
   - this functionality if validated via time-picker-appearance-arrow(up|down)

Tests were added to validate the selection of a value using keyboard and for canceling
a selection.

Bug: 1004997
Change-Id: I99e54572804394b1a72a6c2b0d6fc65b2b26de20
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834894Reviewed-by: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Ionel Popescu <iopopesc@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#703520}

When navigating to an error page with the LoadPostCommitError() API,
we want to treat reload and back as they would work on a regular error
page. That is, they should reload the site displayed in the omnibox, and go
back from that navigation. Currently, they instead reload the error
page itself, and go back from there. This change corrects that behavior by
replacing the active entry with the post commit entry when showing an error
and replacing it back with the original entry on any navigation away, or
before a reload.

This CL does not address reload in post commit error pages if there is
no entry to replace the entry with.

Bug: 996942

Change-Id: Ic6a473d321f2e40c850c679e4e2a5cd37ebfdde9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1804575Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: John Delaney <johnidel@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Carlos IL <carlosil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703519}

https://skia.googlesource.com/skia.git/+log/38f0a4972a24..a718a61003d1

git log 38f0a4972a24..a718a61003d1 --date=short --no-merges --format='%ad %ae %s'
2019-10-07 egdaniel@google.com Enable preferring using primary CB over secondary CB.
2019-10-07 jvanverth@google.com Guard some more Metal code to support older versions.
2019-10-07 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2019-10-07 benjaminwagner@google.com Use integer patchset and issue variables.
2019-10-07 borenet@google.com Update go deps
2019-10-07 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC kjlubick@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=kjlubick@google.com

Bug: None
Change-Id: I1d51acceb321630d5c84f61578c5c2cbee38dce6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845707Reviewed-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@{#703518}

In follow up CLs, this VulkanInfo will be sent from viz process to
browser process and then displayed in about:gpu page.

Bug: 887018
Change-Id: Idde45c731aed65092fc384e529e8b5028c93e545
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845872Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703517}

Most files in this CL either use "Build" or "Test" components

See https://tinyurl.com/yxau5sc4 for context.

Bug: 977050
Change-Id: I1ab5e956e11553ad6ca548ac0bd4669daeb631ff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1808169Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Eric Foo <efoo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703516}

Optimizing email

Change-Id: I8d3bc4c77a10022f29d68fbcdb91c6f88327009d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1842952
Auto-Submit: Philip Rogers <pdr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703515}

Fix the last failing test and remove LayerTreeSettings
enable_surface_synchronization entirely.

Bug: 985009
Change-Id: I7369f926a4c1157d8c77ee19803400f34c485736
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1822845
Commit-Queue: kylechar <kylechar@chromium.org>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703514}

Currently, Switch Access looks for the menu panel each time it needs it.
Instead, we expect the node to be in the accessibility tree once its
javascript has loaded.

Bug: None
Change-Id: Ic48a3110c1c9ce40ab6581bf78c782b3f2a9d17e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841503Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
Commit-Queue: Anastasia Helfinstein <anastasi@google.com>
Cr-Commit-Position: refs/heads/master@{#703513}

Use --vmodule=dice_turn_sync_on_helper=2 to enable this log message.

It's possible that user cloud policies which are fetched during sign-in
process may block sign-in in the end. It's not easy to debug under this
situation because these policies will be removed right after sign-in is
terminated. And chrome://policy page will never show these policies.

Print policy values into log helps developers to understand policy values
change user cloud policies are merged.

Bug: 991322
Change-Id: I9b2d4358ec32f86b7fc3e5f2e3d06c4511f62a2d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1835020Reviewed-by: Mihai Sardarescu <msarda@chromium.org>
Commit-Queue: Owen Min <zmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703512}

NOTIFICATION_PROFILE_DESTROYED was only used for normal (on the record)
profiles. But normal profiles aren't destroyed until browser shutdown,
and are destroyed after SafeBrowsingService is destroyed, so there is
no need to listen to this notification.

NOTIFICATION_PROFILE_ADDED can be replaced with
ProfileManagerObserver::OnProfileAdded.

Also, delegate between the two constructors (prod and test), so
code needn't be duplicated between them.

Bug: 268984
Change-Id: Iab614421b7c51136ccae79a45d00f8ee709a73b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1832883
Commit-Queue: Evan Stade <estade@chromium.org>
Reviewed-by: Greg Thompson <grt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703511}

https://chromium.googlesource.com/chromium/tools/depot_tools.git/+log/107c97c8377d..3306bbe476fd

git log 107c97c8377d..3306bbe476fd --date=short --no-merges --format='%ad %ae %s'
2019-10-07 ehmaldonado@chromium.org depot_tools: Remove buildbucket.py
2019-10-07 recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com Roll recipe dependencies (trivial).
2019-10-07 raul@tambre.ee gclient_utils: buffer output as bytestrings in Annotated
2019-10-07 raphael.kubo.da.costa@intel.com download_from_google_storage: Decode string passed to re.search()
2019-10-07 raphael.kubo.da.costa@intel.com download_from_google_storage: Do not call decode() on a string twice

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/depot-tools-chromium-autoroll
Please CC agable@chromium.org on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

TBR=agable@chromium.org

Bug: chromium:984182,chromium:984182,chromium:1007872,chromium:984182,chromium:1007872
Change-Id: I0c124ecc2fb9d1eda0e129fedee04c7195c4a2cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845574Reviewed-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@{#703510}

Right now in FrameSequenceTracker::ReportMetrics, we compare the
throughput of the main thread vs the compositor thread, and report
the one with smaller throughput as the SlowerThread. There is an error
in the logic of determining which one is the slower thread. In
particular, currently we didn't consider the case where the compositor
and the main thread having the same throughput.

This CL fixes the error, and added a unit test.

Bug: None
Change-Id: Ib90b625665f508a8dab610a9ab07f90f6c4f1c58
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838354
Commit-Queue: Xida Chen <xidachen@chromium.org>
Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703509}

https://webrtc.googlesource.com/src.git/+log/7c06777ab088..a639f7a24477

git log 7c06777ab088..a639f7a24477 --date=short --no-merges --format='%ad %ae %s'
2019-10-07 chromium-webrtc-autoroll@webrtc-ci.iam.gserviceaccount.com Roll chromium_revision 10156469..5ac2340a (703248:703358)

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

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/webrtc-chromium-autoroll
Please CC webrtc-chromium-sheriffs-robots@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

TBR=webrtc-chromium-sheriffs-robots@google.com

Bug: chromium:None
Change-Id: I5bd1ca42505b573376b283efca952525efb9047c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845705Reviewed-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@{#703508}

This is a pure refactor.

Bug: None
Change-Id: I6b527024ef2a3d79b6c86e8c66b7d9c4853afd68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841740Reviewed-by: Akihiro Ota <akihiroota@chromium.org>
Commit-Queue: Anastasia Helfinstein <anastasi@google.com>
Cr-Commit-Position: refs/heads/master@{#703507}

This reverts commit d99ef40d.

Reason for revert: Causes browser crashes
https://bugs.chromium.org/p/chromium/issues/detail?id=1011879

TBR=kinuko@chromium.org

Original change's description:
> [code caching] Handle small data with a single read/write
>
> - Many small reads and writes are observed, especially with the JavaScript
>   code cache. Detect these and write all data into the entry's stream 0,
>   and clear stream 1. When reading, detect the entry size and for small
>   data, skip the stream 1 read and copy the data from the stream 0 read.
> - Changes the stream 0 data (again) to a header with response time and
>   data size. The data size, while not strictly necessary right now, will
>   be needed if we implement de-duplication of identical entries stored by
>   multiple origins. We can add the code hash to this header, and the size
>   field will disambiguate between small entries and large de-duplicated
>   entries where we use the hash as a key to the data.
> - This change should make small reads faster than before, as synchronous
>   completion of stream 0 reads is observed. Otherwise, there should be no
>   change in performance.
> - Renames the buffers and completion callbacks to reflect small/large data
>   distinction.
>
> Bug: chromium:992991
> Change-Id: I6fb5337ef1e4148dd9f300f0a8c85acb401be62e
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1834562
> Commit-Queue: Bill Budge <bbudge@chromium.org>
> Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
> Reviewed-by: Mythri Alle <mythria@chromium.org>
> Reviewed-by: Maks Orlovich <morlovich@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#702667}

TBR=bbudge@chromium.org,kinuko@chromium.org,mythria@chromium.org,morlovich@chromium.org

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

Bug: chromium:992991
Change-Id: Ieae20ed3ad7646ca09e088accd90fbd7cbda2bdc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845576
Commit-Queue: Bill Budge <bbudge@chromium.org>
Reviewed-by: Bill Budge <bbudge@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703506}

This change adds a throttling service for Crostini, CrostiniThrottle.
This class is a KeyedService that holds observers and throttles the
VM on a change in observer state. Currently the class it is inactive
since it holds no observers and is not instantiated anywhere.

Bug: 997397
Test: Run CrostiniThrottleTest unit test
Change-Id: I344075908abc6c86f311e2c25f5c7ebead25fa42
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1836086
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Nicholas Verne <nverne@chromium.org>
Reviewed-by: Yusuke Sato <yusukes@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703505}

The CL that uses this in freezing will follow.

Bug: 999594
Change-Id: I8dd17798ce4f707e99d57d0e9aec6d9da91d5f88
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846091
Commit-Queue: Sébastien Marchand <sebmarchand@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703504}

Bug: 1011413
Change-Id: Ief7b8e89b6834dc3c69358c137dfd6544073a630
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1841895
Commit-Queue: David Maunder <davidjm@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703503}

Bug: 1011937
Change-Id: I0e04b43f160f60a5750a241fa6113360932e557a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1842674Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703502}

https://chromium.googlesource.com/angle/angle.git/+log/6acfca3ad3e3..2682b5a02d16

git log 6acfca3ad3e3..2682b5a02d16 --date=short --no-merges --format='%ad %ae %s'
2019-10-07 jmadill@chromium.org Documentation maintenance.
2019-10-07 jmadill@chromium.org Roll angle-internal with new GLES 1.0 fixes.
2019-10-07 bsheedy@chromium.org Reland "Add export_targets.py to presubmit"

Created with:
  gclient setdep -r src/third_party/angle@2682b5a02d16

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/angle-chromium-autoroll
Please CC geofflang@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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

CQ_INCLUDE_TRYBOTS=luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
TBR=geofflang@google.com

Bug: chromium:1003151
Change-Id: Id27d80e406b89e10d16f78df9a971be67deb2d41
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1845702Reviewed-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@{#703501}

Currently emulator fyi bots have test failing due to the missing avd-config
files.
This CL adds them to the BUILD.gn

Bug: 922145
Change-Id: Ide614113094585999b0370d219f55bd319f123b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1846037Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Haiyang Pan <hypan@google.com>
Cr-Commit-Position: refs/heads/master@{#703500}

Bug: 1007204
Change-Id: Ic6bea1eef809db4e995040d4bee82ea05aa57c7f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1838978Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Commit-Queue: Yulun Wu <yulunwu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#703499}