GitLab

This used to fail a DCHECK when nested multicol was specified on a
fieldset at an outer fragmentainer boundary, but apart from that, it
worked fine, because BreakBeforeChildIfNeeded() correctly detects the
situation (abortion) and inserts a break before. Just move the DCHECK a
bit down.

No code changes are required for legends, as they are monolithic. Just
replace the TODO with a proper comment, and keep the DCHECK (the legend
test also passes without the code changes in this CL).

Bug: 829028
Change-Id: I62bf97f9bd04c185f86e93103f204cc6d872c438
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595288Reviewed-by: Alison Maher <almaher@microsoft.com>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837755}

Because paths are case-insensitive on Windows, the DM server
normalizes profile paths to lower-case when they are reported.
This breaks the Clear Browsing Data remote command because it uses
that path to find the profile into which it'll clear the data.

This CL makes it so the path is compared in a case-insensitive manner
on Windows in order to find the correct profile.

Bug: 1159450
Change-Id: I07ebb206049ee848e1aae9e2059c3c69a4b367d2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595728
Commit-Queue: anthonyvd <anthonyvd@chromium.org>
Reviewed-by: Nicolas Ouellet-Payeur <nicolaso@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837754}

https://chromium.googlesource.com/catapult.git/+log/f600415e9265..92c77100518e

2020-12-16 bsheedy@chromium.org Revert "Reland "Switch to vpython version of mock""

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/catapult-autoroll
Please CC skyostil@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:chromeos-kevin-rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Bug: chromium:1156832
Tbr: skyostil@google.com
Change-Id: Id7edbfdaf1b1bea09833490858e7bd3a00842328
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595696Reviewed-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@{#837753}

The RemoteCommand logic will not be supported server-side in the near
future so I'm removing it from M89.  I don't think we can remove it
from the protos or we will break back compat so for now the host
will just log an error message if it receives a remote command.

Change-Id: Ieee15b0d225f645dff40b297f6fc3cce5f887f4e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596109Reviewed-by: Yuwei Huang <yuweih@chromium.org>
Commit-Queue: Joe Downing <joedow@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837752}

This change loads the model from the file provided by the Opt Guide and
returns it via callback to any requestor of the model.

A future change will provide the model to the content translate driver
and the translate agent via mojo.

Bug: 1151406
Change-Id: If09871f3ad04a674d964a467586cfb0f24fd4708
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593589Reviewed-by: Trevor  Perrier <perrier@chromium.org>
Reviewed-by: Scott Little <sclittle@chromium.org>
Reviewed-by: Sophie Chang <sophiechang@chromium.org>
Commit-Queue: Michael Crouse <mcrouse@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837751}

Figured this would be a useful API extension while refactoring.

Bug: b/175360169
Change-Id: If6490aefacdb5110d3fe5dc423d311e6f7618c12
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2584434
Commit-Queue: Nic Hollingum <hollingum@google.com>
Reviewed-by: Daniel Ng <danielng@google.com>
Cr-Commit-Position: refs/heads/master@{#837750}

TBR=govind@chromium.org

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

In particular, add DCHECKs when an empty NIK is passed when sending a
report, or when verifying a signed exchange's cert (which can send a
report of another type). The DCHECK is only enabled when
require_network_isolation_key is set. Actually respecting the received
NIK is disabled by default, but all consumers outside the network
service should now always be passing a non-empty NIK when using these
APIs.

Bug: 993805, 1087091
Change-Id: I5f4eef6f9f7b3b4faaaedca62e110e695ccabf2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595630Reviewed-by: Lily Chen <chlily@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837748}

This CL disabled the following tests on Android.

* SingleClientTypedUrlsSyncTest.DeleteNonTyped
* SingleClientTypedUrlsSyncTest.TwoVisits
* SingleClientTypedUrlsSyncTest.DeleteTyped
* SingleClientTypedUrlsSyncTest.Sanity

TBR=mastiz@chromium.org

Bug: 1159479
Change-Id: I49a93df85f6e48bbd661e77e41c467787c4e8b68
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596119Reviewed-by: Salvador Guerrero <salg@google.com>
Commit-Queue: Salvador Guerrero <salg@google.com>
Cr-Commit-Position: refs/heads/master@{#837747}

This CL
* Adds a CartHandler mojo interface that will be used to provide info
  needed to render chrome cart module.
* Adds the basic HTML and JS code to render the skeleton of the cart
  module. More details will be added in later patches.
* Adds a dummy implementation of CartHandler that will later be hooked
  with cart backend infra to get real data.

Screenshot with fake data: https://drive.google.com/file/d/1WtYz9aEj0PKhiqn-eZupREv5WfQ0MA-7/view?usp=sharing&resourcekey=0-g9LEGFm9bLfl5HAtro0oUw

Bug: 1157892
Change-Id: Ic8dc20f4be347c97ff99d44717408ce5f182b765
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587099Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Alex Gough <ajgo@chromium.org>
Reviewed-by: Tibor Goldschwendt <tiborg@chromium.org>
Commit-Queue: Yue Zhang <yuezhanggg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837746}

Vulkan memory usage has spikes as a result of caches not
taking the full lifetime of GPU resources into account.

This introduces two limits for Vulkan memory to
mitigate the problem:

--vulkan-sync-cpu-memory-limit-mb - Triggers synchronization
with the CPU in order to allow unused resources to be
freed immediately.

--vulkan-heap-memory-limit-mb - Makes Vulkan allocations
fail.

These two limits provide an effective way to reduce the
harm of the problem. The soft limit affects GPU work
submission and trade performance for reducing spikes as
early as possible without causing a severe impact on
the user experience. The hard limit is immediate and
prevent spikes from causing greater harm to the rest of
the system.

No change in behavior unless new command line flags
are used.

Bug: 1158000
Change-Id: I8e990d71aac780426b0398510c147af295c54f89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587431Reviewed-by: Peng Huang <penghuang@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Reviewed-by: Wez <wez@chromium.org>
Reviewed-by: Daniele Castagna <dcastagna@chromium.org>
Reviewed-by: Emircan Uysaler <emircan@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: David Reveman <reveman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837745}

Change-Id: Iafa21bda8d69d50dd5f78667ab6d21c616748fd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595514Reviewed-by: Carlos IL <carlosil@chromium.org>
Commit-Queue: Emily Stark <estark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837744}

https://chrome-internal.googlesource.com/chrome/src-internal.git/+log/772ccd850137..0e7eec75ab9b

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 davidbienvenu@google.com,smcgruer@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chrome.try:linux-chromeos-chrome
Bug: None
Tbr: davidbienvenu@google.com,smcgruer@google.com
Change-Id: Ibb9eb2ef06bdc50daf382bab8c05480777284574
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595995Reviewed-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@{#837743}

This change only handles links but we will add support for images and images link later.

Bug: 1140387
Change-Id: I83289a9deefbe346343bc3649ffa2c015bd20ec5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2584604
Commit-Queue: Cheick Cisse <cheickcisse@google.com>
Reviewed-by: Sebastien Lalancette <seblalancette@chromium.org>
Reviewed-by: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837742}

Since holding space only supports a specific list of allowed volumes,
its welcome banner should only be shown on those volumes which the
feature supports.

Note that the holding space banner is also explicitly disallowed from
showing on Drive per UX request.

Bug: 1154347
Change-Id: I89e0c14ec9a6d1ec01700bd084e769d349243330
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2594314
Commit-Queue: David Black <dmblack@google.com>
Reviewed-by: Luciano Pacheco <lucmult@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837741}

https://crrev.com/ff530f772caac made explicit that this callback is a
RepeatedCallback. We forgot to change the associated Bind call.

Bug: 1152268
Change-Id: I1b9320ed117a2a2426e8a80ac02ea7ba41901fa7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595592
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Reviewed-by: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837740}

There are crashes in GetLastPresentedFrameMetadata(),
due to a null |current_frame_|. This is probably happening when a
pending call to VideoFrameCallbackRequesterImpl::OnExecution() runs
after HTMLVideoElement creates a new WebMediaPlayer, and the first frame
is not not yet available.

This CL fixes the issue by using a WeakPtrFactory to invalidate pending
OnExecution() calls, when HTMLMediaElement gets a new WebMediaPlayer.
VideoFrameCallbackRequesterImpl should automatically call
RequestVideoFrameCallback() on this new player when it is created,
rescheduling the OnExecution() calls when the first frame becomes
available.

Bug: 1158160
Change-Id: I4c4228aa9d9769f728d639a94f067ccf84eb1151
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2585917Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Sushanth Rajasankar <Sushraja@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#837739}

Change-Id: I1f42684060ee5416c8e68ad639e37f69b943c7e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2590868
Auto-Submit: Richard Coles <torne@chromium.org>
Reviewed-by: Nate Fischer <ntfschr@chromium.org>
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837738}

Clean up launched feature flag.

Bug: None
Change-Id: I205696223fd6db4136220f145c5237273df07037
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2590709Reviewed-by: Tao Wu <wutao@chromium.org>
Commit-Queue: Xiaohui Chen <xiaohuic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837737}

https://android.googlesource.com/platform/external/perfetto.git/+log/0c031adc5339..0da7da798b33

2020-12-16 treehugger-gerrit@google.com Merge "trace_to_text: add an option to convert perf profiles to pprof"

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/perfetto-chromium-autoroll
Please CC perfetto-bugs@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/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:linux-perfetto-rel
Bug: None
Tbr: perfetto-bugs@google.com
Change-Id: I7085cd5a81165187edfa1e24fa4197fb8401c429
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595693Reviewed-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@{#837736}

Bug: 1152282
Change-Id: I9f0e5c0082634d3389cd3af49cda522e08a0e8f9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2590058Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Dana Fried <dfried@chromium.org>
Commit-Queue: Yi Gu <yigu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837735}

Histogram records the number of pages scanned in a successful scan.

Bug: 1059779
Change-Id: I19b326432cfc4f8ff95b3f23354a3cd39a72b592
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2588648Reviewed-by: Jesse Doherty <jwd@chromium.org>
Reviewed-by: Jesse Schettler <jschettler@chromium.org>
Commit-Queue: Gavin Williams <gavinwill@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837734}

When the network process encounters an error when setting up the tunnel
connection, it sends that information to the proxy configurator. That
will determine a reasonable Retry-After value, either from headers, or a
random value between 1m-5m.

Also adds Histograms to track the responses from the proxy.

A Retry-After header is accepted on any non-200 response code since the
proxy is a Google owned service with its own protocol.

Bug: 1136114
Change-Id: If44786869268f22db7b836ebadf29b624c6cfd60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587713
Commit-Queue: Robert Ogden <robertogden@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837733}

Re-land includes missing headers directory.

This replaces several grouped dependencies with one meta-repo.
The meta-repo will allow us to group multiple inter-dependent
deps rolls into one single roll. This solves the problem of
separate rollers breaking because of the inter-dependencies.
It also allows ANGLE and Chrome to share common bits like the
README and .gitignore files.

Bug: angleproject:5390
Bug: 1153258
Change-Id: I22cefb1bfeeec656c2dbb173701a87a6db9cb8ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593888
Commit-Queue: Jamie Madill <jmadill@chromium.org>
Auto-Submit: Jamie Madill <jmadill@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837732}

Also removes ref counting since the dialog is never reused (plumbing
for this was added in r174683 but both current uses are one shots).

Bug: 1152274
Change-Id: I8ca68395f5fa0596d81af8abe92b536eb1129b89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593929
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837731}

Add missing sequence checks where the compiler complained.

Change-Id: I0b8a61b41720709d01d28796c57f71e4635dbcd5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2590325
Commit-Queue: Sigurður Ásgeirsson <siggi@chromium.org>
Reviewed-by: Joe Mason <joenotcharles@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837730}

PhoneHub features will be set to FeatureState::kNotSupportedByChromebook
if the current logged in user is secondary.

Fixed: 1156309
Change-Id: Iea97c13c3fa2fe9edc103b00df8aa21b9447cef0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2590492
Commit-Queue: Regan Hsu <hsuregan@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837729}

Bug: 915934
Change-Id: I0c67c1d1ddc446581783c3322be9da97652eb84f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595594Reviewed-by: Greg Kerr <kerrnel@chromium.org>
Commit-Queue: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837728}

This color reflected the current practice in Play Services, but doesn't
look good in dark mode. The default color works well for text and
changes automatically to match the theme.

BUG=1002262

Change-Id: Ib9d852f17eeec096ea4e11ce670782b2ecc6d702
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2596111
Commit-Queue: Adam Langley <agl@chromium.org>
Commit-Queue: Martin Kreichgauer <martinkr@google.com>
Auto-Submit: Adam Langley <agl@chromium.org>
Reviewed-by: Martin Kreichgauer <martinkr@google.com>
Cr-Commit-Position: refs/heads/master@{#837727}

Formatting is a left-over from the Polymer2->3 migration.

Bug: 965770
Change-Id: Ic9eb1bd3a1d9139f68866f606fe17cb14a3d4f4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2595522
Auto-Submit: dpapad <dpapad@chromium.org>
Reviewed-by: John Lee <johntlee@chromium.org>
Commit-Queue: John Lee <johntlee@chromium.org>
Commit-Queue: dpapad <dpapad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837726}

* Now that ExternalAuthUtils is provided as a singleton instance,
  remove AppHooks' instance and related methods.
* This is patch 5/5 for providing ExternalAuthUtils as a singleton
  instead of from AppHooks.

Change-Id: I4278d4a6663a1d8a48314ffa2b812df722e93e12
Bug: 1154371
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587240
Commit-Queue: Nick Burris <nburris@chromium.org>
Reviewed-by: Andrew Grieve <agrieve@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837725}

The kFrameTreeNodeStateReset value was removed in crrev.com/c/2536467,
and the value (36) was later on incorrectly reused for a different
NotRestoredReason, kNavigationCancelledWhileRestoring. This CL changes
the value for kNavigationCancelledWhileRestoring to 41 so that we
won't get confused on which reason was actually logged.

Change-Id: I776717c88a02920b429f1949048e3a0771aa17b1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2592282Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837724}

Some naming in ClientDiscardableSharedMemoryManager is inconsistent.
This CL addresses this issue.

Bug: 1157471
Change-Id: I5e76e44979706c6d4def9864686084f75dba4f49
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587788Reviewed-by: Peng Huang <penghuang@chromium.org>
Reviewed-by: Benoit L <lizeb@chromium.org>
Commit-Queue: Thiabaud Engelbrecht <thiabaud@google.com>
Cr-Commit-Position: refs/heads/master@{#837723}

The network health components are used both in //chrome and //chromeos.
Strings that are required in both locations need to be moved to
//chromeos to prevent a layering violation. This change adds a new
location for these shared strings and moves them there.

Bug: chromium:1142857
Change-Id: I2cb497ae5df82c9718f34c15ac939e0921c69174
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2586971
Commit-Queue: Trent Begin <tbegin@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837722}

Migrate uses of the relevant set_* functions on the sql::Database object
to use the new DatabaseOptions constructor instead.

This change should have no intended behavioral effect.

Bug: 1126968
Change-Id: Ia16c6612c254187e31951027cfb4284d494dde44
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2594287Reviewed-by: Victor Costan <pwnall@chromium.org>
Reviewed-by: Justin DeWitt <dewittj@chromium.org>
Commit-Queue: Shubham Aggarwal <shuagga@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#837721}

Bug: 1141261
Change-Id: I9161da382aa7e2ca9eb630c5b79a065862fccbc4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2593815Reviewed-by: Erik Chen <erikchen@chromium.org>
Commit-Queue: Darin Fisher <darin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837720}

BUG=none
TEST=none

Change-Id: Id233a340a9513fee590c76f35cf23a1395fbaf0c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2594427Reviewed-by: Allen Bauer <kylixrd@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837719}

BUG=None
TEST=try

Change-Id: I9ecee3fa64eb3192adcf62b8ce5e43324d04edf5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2594449Reviewed-by: Willie Koomson <wvk@google.com>
Commit-Queue: Yusuke Sato <yusukes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837718}

For all parameterized Storage tests added a new dimension:
encryption enabled/disabled - now the same
opening/writing/reading/reopending is tested with and without encryption.
Fixed few minor mistakes, found with the test.

Bug:b:170054326

Change-Id: I72df7e96b7163a5b1f7a3f43553b11ac73c15472
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587505
Commit-Queue: Leonid Baraz <lbaraz@chromium.org>
Reviewed-by: Zach Trudo <zatrudo@google.com>
Cr-Commit-Position: refs/heads/master@{#837717}

The new range is between 5ms to 5s.

The old range can't give us a good picture of the time it takes to
finish the GPU initialization on each platform.


Bug: 1153866
Change-Id: If52c1c50a9da7746d2a0ffa36b38bac1d72a9fc0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2590696Reviewed-by: Brian White <bcwhite@chromium.org>
Reviewed-by: Zhenyao Mo <zmo@chromium.org>
Commit-Queue: Maggie Chen <magchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837716}