GitLab

This reverts commit 37bd8dbf.

Reason for revert: browser test failures
ExtensionStorageMonitorTest.ThrottleNotifications
ExtensionStorageMonitorTest.DisableForInstalledExtensions
ExtensionStorageMonitorTest.DoubleInitialThreshold
ExtensionStorageMonitorTest.UnderThreshold
ExtensionStorageMonitorTest.TwoHostedAppsInSameOrigin
ExtensionStorageMonitorTest.HostedAppTemporaryFilesystem
ExtensionStorageMonitorTest.UserDisabledNotifications
ExtensionStorageMonitorTest.ExceedInitialThreshold

first failed build https://uberchromegw.corp.google.com/i/chromium.memory/builders/Linux%20CFI/builds/4334

Original change's description:
> Use NotificationDisplayService for ExtensionStorageMonitor notification.
> 
> Bug: 783018
> Change-Id: If8fe05a25344ce61f5388e13b2d65a58aa24e5ae
> Reviewed-on: https://chromium-review.googlesource.com/816051
> Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
> Reviewed-by: Nick Carter <nick@chromium.org>
> Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
> Commit-Queue: Evan Stade <estade@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#522872}

TBR=stevenjb@chromium.org,nick@chromium.org,rdevlin.cronin@chromium.org,estade@chromium.org

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

Bug: 783018
Change-Id: Ia32a0edadd1858c024a67ef80f247edfc1a4d04e
Reviewed-on: https://chromium-review.googlesource.com/817297Reviewed-by: Maxim Kolosovskiy <kolos@chromium.org>
Commit-Queue: Maxim Kolosovskiy <kolos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523063}

This organizes the code in a more logical way, and makes it easier to
assign owners to V4L2.

BUG=chromium:792790
TEST=made sure Chromium built successfully for Chrome OS, on both x86
and ARM platforms

Cq-Include-Trybots: master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Change-Id: Ib6189acb9c054b20c7b83474347ffc2e160436fc
Reviewed-on: https://chromium-review.googlesource.com/813438Reviewed-by: Kuang-che Wu <kcwu@chromium.org>
Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523062}

This is an additional disabling to https://chromium-review.googlesource.com/c/chromium/src/+/818889.

TBR=hajimehoshi@chromium.org
NOTRY=true

Bug: 793578
Change-Id: Ic5fded66e1003c155e932dac943c83e6325ece55
Reviewed-on: https://chromium-review.googlesource.com/818890Reviewed-by: Hajime Hoshi <hajimehoshi@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523061}

This CL intends to fix a memory leak that is caused by a reference cycle (ScriptRunner -> ScriptRunner).
Memory leak happens with ClassicPendingScript over page navigation with https://binomo.com, the case which a script is loaded but never finishes streaming (i.e. ScriptStreamer::StreamingComplete is never called).
This leads to a memory leak because streamer_done_ which has ScriptStreamer in a closure never gets released.

Bug: 785173
Change-Id: I901bdf134dabaa5d32a090b3490e77d5292ffae0
Reviewed-on: https://chromium-review.googlesource.com/758306Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuzu Saijo <yuzus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523060}

This patch makes OverflowAlignment to be an enum class for better type safety.

Bug: 684966
Signed-off-by: Zhuoyu Qian <zhuoyu.qian@samsung.com>
Change-Id: I03a7b2083ed19b70316074dd36a52a82114e10df
Reviewed-on: https://chromium-review.googlesource.com/818672Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523059}

TBR=hajimehoshi@chromium.org
NOTRY=true

Bug: 793672, 793638, 793634
Change-Id: I9eb80f8ea1712792604bcdba5d5782e2acc0a111
Reviewed-on: https://chromium-review.googlesource.com/818889Reviewed-by: Hajime Hoshi <hajimehoshi@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523058}

The following changes are made:
 - For many non-Swarmed tasks:
   - Remove merge script, as this is only used with Swarming.
   - Add explicit:
     "can_use_on_swarming_builders": false
 - Add output_links to chrome_public_test_apk on Oreo Phone Tester.
 - Remove redundant "shards: 1" from telemetry_perf_unittests on x86
   Cloud Tester.

These are all no-ops. With them, this file can be autogenerated with
100% fidelity.

BUG=662541
TBR=dpranke@chromium.org, jbudorick@chromium.org, bpastene@chromium.org

Change-Id: I9a5f1e0eebfe5da694f4c30a372e74f9757d593d
Reviewed-on: https://chromium-review.googlesource.com/818635Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523057}

Converts NavigatorUserMediaSuccessCallback and
NavigatorUserMediaErrorCallback into callback functions as
the spec specifies.

Bug: 569301, 658073
Change-Id: I0b866348f53981d202055fdb141ade00842b051a
Reviewed-on: https://chromium-review.googlesource.com/789212Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523056}

This patch implements wrapper-tracing for PerformanceObserver.
Surprisingly it's not been traced...

The path from the root to PerformanceObserver (and its callback) is:
    Window / WorkerGlobalScope
    => Supplementable
    => Supplement
    => DOMWindowPerformance / WorkerGlobalScopePerformance
    => Performance / WorkerPerformance
    => PerformanceBase
    => PerformanceObserver

Also makes PerformanceObserver::Deliver check if the execution
context is available or not, because it's possible that, when the
timer fires, the execution context is already gone (thus no one is
running wrapper-tracing, i.e. the underlying callback is already
gone).

Bug: 792844
Change-Id: I3b7c7604795e2b56e8b507e4a418729750508501
Reviewed-on: https://chromium-review.googlesource.com/817134Reviewed-by: Hitoshi Yoshida <peria@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523055}

MailtoURLRewriter was intended to be the abstract interface when there
are more than one implementation of MailtoURLRewriters. Now that the other
implementations have been deprecated, there's only one and the two
can be collapsed into a single class.

The term, MailtoURLRewriter, feels too close to URLRewriter which already
has an unrelated meaning, so the collapsed class is given a new name,
MailtoHandlerManager, at the same time.

Bug: 767315
Cq-Include-Trybots: master.tryserver.chromium.mac:ios-simulator-cronet;master.tryserver.chromium.mac:ios-simulator-full-configs
Change-Id: I964c176bb93a49f265116d3e3c384763a2cf4709
Reviewed-on: https://chromium-review.googlesource.com/806651
Commit-Queue: Peter Lee <pkl@chromium.org>
Reviewed-by: Eugene But <eugenebut@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523054}

KURL(NullURL(), const String&) is equivalent to KURL(const String&) when
the String argument is guaranteed to be non-null String.

As a bonus, adding const to KURL declarations where possible.

Bug: 
Change-Id: Icecf33753837e1d59366d8960ca27954164689bc
Reviewed-on: https://chromium-review.googlesource.com/790194
Commit-Queue: Takeshi Yoshino <tyoshino@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523053}

Traffic anntation auditor is refactoring to be prepared for running on
partial set of files. In this CL 4 changes are made:
1- Selection of files that need process is updated so that git would be
   called only if path_filters are not presented or they include
   directories.
2- Unittests are ignored when files are filtered to make tests faster.
3- Hash code collision and repeated errors are separated.
4- All tests related to IDs are moved from TrafficAnnotationAuditor to
   the new class TrafficAnnotationIDChecker to make further aggregation
   of existing and new annotations easier.

Bug: 656607
Change-Id: Ifdcc2cdaa9802414c62dce1fa9f54a3eab0f40d1
Reviewed-on: https://chromium-review.googlesource.com/805755Reviewed-by: Martin Šrámek <msramek@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523052}

M63 stable was released and we've not heard any issue about the removal of
/deep/ from any web sites.  Let's remove the runtime flags.

TBR=haraken

Bug: 489954
Change-Id: Ie7831904824e3a08e3e121004bdecabb0871e850
Reviewed-on: https://chromium-review.googlesource.com/818678
Commit-Queue: Hayato Ito <hayato@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Takayoshi Kochi <kochi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523051}

Following bot results are included.
2441 2442 2444 2446 2447 2449

This is the 2nd maintance and bots are still flaky that no defalke was
ran yet.

TBR=eae@chromium.org
NOTRY=true

Bug: 591099
Change-Id: I1ea528ed94fd42332b5519187d048dbbe9095892
Reviewed-on: https://chromium-review.googlesource.com/818852
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523050}

All the use sites of WTF::Function are gone. Let's remove it!

Bug: 771087
Change-Id: I4b0b82f96c92461c505dd342bb480762242736a4
Reviewed-on: https://chromium-review.googlesource.com/816641
Commit-Queue: Yuta Kitamura <yutak@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Taiju Tsuiki <tzik@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523049}

OnKeyboardBoundsChanging is being split into several more specific
methods that have a stronger contract of how they are being used by the
implementer. More information about why this is being done is in the
associated bug.

OnKeyboardAppearanceChanging is called when any time the keyboard's
bounds or availability changes and has a struct as its parameter that
includes several properties of the keyboard appearance.

Currently the IME Bridge does not support any additional params other
than the bounds and then uses the bounds to check if the keyboard is
available by checking for empty bounds. I've opened b/70251261 to
change this, since empty bounds can still mean the keyboard is
available. The KeyboardStateDescriptor struct contains a boolean that
indicates if the keyboard is truly available for use. This value needs
to be plumbed into the ime bridge.

Bug: 786290
Change-Id: I256c348418ec792879e2687064b1a16468432908
Reviewed-on: https://chromium-review.googlesource.com/778740Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Commit-Queue: Blake O'Hare <blakeo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523048}

https://chromium.googlesource.com/catapult.git/+log/d624b3ced2c8..665b8b46209c

$ git log d624b3ced..665b8b462 --date=short --no-merges --format='%ad %ae %s'
2017-12-04 yuzus Throw an error when memory leak is found

Created with:
  roll-dep src/third_party/catapult


The AutoRoll server is located here: https://catapult-roll.skia.org

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=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I9a49c0773bc7b7e6360967a8b78fad76c6425fa9
Reviewed-on: https://chromium-review.googlesource.com/817660
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523047}

This CL doesn't add a test because this case depends on timing and it's
difficult to reproduce it artificially.

Bug: 792364
Change-Id: I00f1e7fe24860e3652ee98371e40b0e798e2e0aa
Reviewed-on: https://chromium-review.googlesource.com/813141
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523046}

When first party IME is terminated unexpectedly, IME api will receive
extension unload event and unregister all IMEs' components of the
extension. Then the IMEs' menu on shelf will disappear.
Although OS restart the first party IME extension at once, however,
the IME menus can't be recovered.

First party IME has more complicated initlization process other than
the normal extension. Should not remove its states when it is crashed.

Adds a condition in OnExtensionUnload to gurad not to unregister
the first party IMEs. And records the extension id, then re-activate
the extension when it reloads.

Bug: 775507,788247,786273,761714
Change-Id: I08731d2da82278483b843907aacb8256e0325e88
Reviewed-on: https://chromium-review.googlesource.com/803415
Commit-Queue: Shu Chen <shuchen@chromium.org>
Commit-Queue: Yingbing Wu <wuyingbing@chromium.org>
Reviewed-by: Shu Chen <shuchen@chromium.org>
Reviewed-by: Yuichiro Hanada <yhanada@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523045}

TBR=govind@chromium.org

Change-Id: If48ff8bce682fb21660672ca57fe5d88ddf3dfaa
Reviewed-on: https://chromium-review.googlesource.com/817497Reviewed-by: chrome-release-bot@chromium.org <chrome-release-bot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523044}

This is part of efforts to replace base::ThreadTaskRunnerHandle::Get()
with other appropriate task runners in the renderer.

Bug: 786332
Change-Id: I3e7a8b88dbb85c1af56554507ec71f87e64a3d89
Reviewed-on: https://chromium-review.googlesource.com/807762Reviewed-by: Alexander Timin <altimin@chromium.org>
Reviewed-by: Pavel Feldman <pfeldman@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523043}

This change is a speculative fix for the linux 64 buildbots due to a
GPU failure.

Bug: 
Change-Id: I09360fab81128f8109503f6d3afe67d4ecc43eaf
Reviewed-on: https://chromium-review.googlesource.com/818740Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523042}

Bug: 779444
Change-Id: I7bb353e31a10cd43a910de1cd4282e23309caf5e
Reviewed-on: https://chromium-review.googlesource.com/788640Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523041}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/14f3b83e..917ba969

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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Ic05af7974cbd534be3ae5e70d4de41eac3befc5b
Reviewed-on: https://chromium-review.googlesource.com/817964Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523040}

This CL changes the message displayed by the lightweight first run dialog from
"By continuing, you agree to Chrome’s Terms of Service and Privacy Notice."
to
"{{app_name}} will open in Chrome. By continuing, you agree to Chrome’s Terms
of Service and Privacy Notice."

Currently, the lightweight FRE is only displayed for WebAPKs. The {{app_name}}
is the WebAPK's short_name

BUG=787939

Change-Id: Ib7359b8facc5992f0d74fea357f1c1320e3e4b6e
Reviewed-on: https://chromium-review.googlesource.com/796936
Commit-Queue: Peter Kotwicz <pkotwicz@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Yusuf Ozuysal <yusufo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523039}

TBR=marcheu@chromium.org

Change-Id: Ia318d67edc7417c687aeaf8da0f6979aa47ddcff
Reviewed-on: https://chromium-review.googlesource.com/818785
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Reviewed-by: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523038}

Use overscroll-behavior css property on viewport defining element to
control overscroll action. This patch enables control over
rubber-banding.
Details can be found at https://wicg.github.io/overscroll-behavior/

This is implemented by recording the overscroll_behavior value at the
first overscrolled GestureScrollUpdate inside
InputScrollElasticityScroller, because main thread reports
overscroll_behavior only when overscroll happens. For all the events in
that gesture afterwards, we don't allow overscrolling if that axis has
OverscrollBehaviorTypeNone.

Bug: 785963
Change-Id: Ib9caae38c89e3993d3618e9b8273e3d799afccc6
Reviewed-on: https://chromium-review.googlesource.com/795450Reviewed-by: ccameron <ccameron@chromium.org>
Reviewed-by: Charlie Reis <creis@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523037}

Clone() and Equals() for blink variant mojo structs containing arrays or
maps do not currently compile. While custom clone and equals traits
exist for WTF::Vector and WTF::HashMap, they aren't included by the
appropriate headers and also don't compile.

Fix compilation for the mojo::CloneTraits and mojo::EqualsTraits
specializations for WTF::Vector and WTF::HashMap.

Add an include of wtf_clone_equals_util.h to generated .mojom-blink.h
files.

Add a regression test.

Change-Id: I06ecf7ccaf0207f29be34465e7a778b63767f4a4
Reviewed-on: https://chromium-review.googlesource.com/816640Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Sam McNally <sammc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523036}

Adds support for AXEventGenerator in AutomationAXTreeWrapper, but to
be very conservative and safe, only uses it to fire "load complete"
events for now. Those events are really important and have both very
broad test coverage already, and are also easy to verify in manual tests.

In subsequent changes we'll switch over more and more events to come
from AXEventGenerator.

Bug: 699438
Change-Id: I30486c96689cc83dc24d8443b32dc4ee9069702b
Reviewed-on: https://chromium-review.googlesource.com/797214
Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523035}

Bug: None
Change-Id: I824dccf02a07a56d5f26f365e562d56d6640d05c
Reviewed-on: https://chromium-review.googlesource.com/816654Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Commit-Queue: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523034}

Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: I392aa805b7d62816624cd944113c2132832dcf09
Bug: 779444
Reviewed-on: https://chromium-review.googlesource.com/706883
Commit-Queue: Sam McNally <sammc@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523033}

From discussion on chromium-dev, it was decided to remove 'chrome' namespace.

BUG=289619
R=pkasting@chromium.org
Signed-off-by: zhuoyu.qian <zhuoyu.qian@samsung.com>
Change-Id: Ib61db08cbd4bd14886bd1cd895dbb490e3fb0086
Reviewed-on: https://chromium-review.googlesource.com/778720Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523032}

The following changes were made:
 - On "Android VR Tests":
   - Alphabetize step names by name, when test was identical.
   - Add a missing "merge" script from one step.
 - On a few bots, remove useless swarming parameters when
   "can_use_on_swarming_builders" was false.
 - Made telemetry_unittests run serially, as on other waterfalls.
 - Alphabetized step names on "Site Isolation Android".

With these changes, this waterfall's JSON can be autogenerated with
100% fidelity.

BUG=662541
TBR=dpranke@chromium.org, bpastene@chromium.org, jbudorick@chromium.org

Change-Id: I9df67955cfe1ac61338c5cfef290e7231fc6dd0f
Reviewed-on: https://chromium-review.googlesource.com/818741Reviewed-by: Kenneth Russell <kbr@chromium.org>
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523031}

Bug: 788828
Change-Id: I5874bb6e4a283a3049a94c0f66292101dfa5cec7
Reviewed-on: https://chromium-review.googlesource.com/794514
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523030}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/f33ef156..14f3b83e

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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: I85d589c9243124f01f81ac01a947be2d3a7694c9
Reviewed-on: https://chromium-review.googlesource.com/817387Reviewed-by: v8 autoroll <v8-autoroll@chromium.org>
Commit-Queue: v8 autoroll <v8-autoroll@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523029}

Test: alt+shift+s, search right/left to battery status. Verify no 'labeltext' in output.
Bug: 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I24734e58a4835e60c26de2966e4133ce4c84b3b3
Reviewed-on: https://chromium-review.googlesource.com/815389Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: David Tseng <dtseng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523028}

This way, we make the client behavior match the setup we have
now, so that we can stop relying on server-side configs for UKM
behavior going forward.

BUG=793441

Change-Id: I14322821c69b30f8a8148d262f7e11f0c518a0f4
Reviewed-on: https://chromium-review.googlesource.com/817579Reviewed-by: Bryan McQuade <bmcquade@chromium.org>
Commit-Queue: Alexei Svitkine <asvitkine@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523027}

The "device:sensors" interfaces have been removed from the device
service and replaced by the "device:generic_sensor" interface.

Bug: 721427
Change-Id: I23164b54e09897c7bef3c6c57d37ac99b68acf06
Reviewed-on: https://chromium-review.googlesource.com/818488Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523026}

R=kbr@chromium.org, jbudorick@chromium.org
BUG=662541

Change-Id: I4c308056fcb7a411edf6d6b5e50ac29f49fdc5a8
Reviewed-on: https://chromium-review.googlesource.com/818725
Commit-Queue: Kenneth Russell <kbr@chromium.org>
Reviewed-by: Kenneth Russell <kbr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523025}

~StreamMixer could be called before Start().

Bug: internal b/69562112
Test: on device
Change-Id: I6376f6aebdc1c0f8ac8ad469e433be079b10ff98
Reviewed-on: https://chromium-review.googlesource.com/818735
Commit-Queue: Gaofeng Huang <gfhuang@chromium.org>
Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Cr-Commit-Position: refs/heads/master@{#523024}