GitLab

This test is timing out (flaky 50%) on macOS 10.10 and 10.13.

TBRing rakina@ for review and sunyunjia@ (owner of bug).

TBR=rakina@chromium.org,sunyunjia@chromium.org

Bug: 827209
Change-Id: I2818f917ccc88d9275014ed8971edb6469638856
Reviewed-on: https://chromium-review.googlesource.com/1174901Reviewed-by: Chris Mumford <cmumford@chromium.org>
Commit-Queue: Chris Mumford <cmumford@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582983}

Changes:
Assign generic container role to SearchResultSuggestionChipView to
replace default button role, so that inner SuggestionChipView can be
found by ChromeVox.

Bug: 872943
Change-Id: I3a09dd9a76d11f9523b807fa5291f1aade38f84e
Reviewed-on: https://chromium-review.googlesource.com/1171598Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: Weidong Guo <weidongg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582982}

@IntDef/@StringDef annotation are preferred way for declaring
set of String/int values.

1. they need less space in APK than enum, see
https://developer.android.com/topic/performance/reduce-apk-size#remove-enums
2. they give more control over allowed values than "static final" values

Main goal of patch is writing "static final" values, enum
and some classes in one common @IntDef/@StringDef form:

1. with @IntDef/@StringDef first, @Retention second
   and related @interface third
2. with values inside @interface
3. with NUM_ENTRIES declaring number of entries if necessary
4. with comment about numbering from 0 without gaps when necessary
5. with @Retention(RetentionPolicy.SOURCE)
6. without "static final" in the @interface

Change-Id: Id545ccd53b49f2fd808c2d6ab32409de73c445d0
Reviewed-on: https://chromium-review.googlesource.com/1172127Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Commit-Queue: Marcin Wiącek <marcin@mwiacek.com>
Cr-Commit-Position: refs/heads/master@{#582981}

In |window.print()| code path for Android, we have the call stack like
this:

  PrintJobWorker::GetSettingsWithUI() ->
  PrintingContextAndroid::AskUserForSettings() ->
  PrintingContext.showPrintDialog() (Java)

We have set |callback_| in |PrintingContextAndroid| to be
|PrintJobWorker::GetSettingsDone()|, but didn't call it in later stage
unless something fails.

This CL makes |PrintingControllerImpl| call
|PrintingContext.showSystemDialogDone()| no matter what happens. This is
because the first |GetSettingsWithUI()| for |window.print()| on Android
is only to wake up |PrintManager| to start printing job. We will set
the real settings in later |GetSettingsWithUI()| call.

Bug: 863297
Change-Id: I3be0a3dceab134db7a47e0c1b48ccd1802e74447
Reviewed-on: https://chromium-review.googlesource.com/1162754Reviewed-by: Changwan Ryu <changwan@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Commit-Queue: Shimi Zhang <ctzsm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582980}

The fixes a hole that is present in the bottom toolbar when the
horizontal tab switcher is not enabled. It also makes it easier to
reach the new tab button which we expect to be more used than the
toggle button.

Change-Id: I7fa5bc192516d956a78704c4d90e2d656abd856c
Reviewed-on: https://chromium-review.googlesource.com/1170193Reviewed-by: Ted Choc <tedchoc@chromium.org>
Commit-Queue: Pedro Amaral <amaralp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582979}

This will enable:
 - New context menu UI for:
  - Application icons
  - Shelf context menus
  - Desktop context menus

Note:
 - Removed tests whose functionality were already being tested.
   - MouseContextMenu already tests whether the ink drop is being
     shown, so there is no need for
     ShelfButtonShowsInkDropHighlightOnMenuShow.

Bug: 871843
Change-Id: I4c92ae52f75b25bc9edd1dd67778c4785d8f4058
Reviewed-on: https://chromium-review.googlesource.com/1170985Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Alex Newcomer <newcomer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582978}

Clear individual Gaia password hash by monitoring account removal events.
If it is the removal of a primary account (a.k.a chrome signin account),
remove all Gaia hashes, otherwise, just remove individual Gaia password
hashes.

Renamed a couple of functions in PasswordStore to make them more readable.
Changes in chrome_password_protection_service.cc are merely refactoring,
no behavioral change.

Bug: 844134
Change-Id: Idab2d375bb24ce2cdf568372b8b5ae283ac28169
Reviewed-on: https://chromium-review.googlesource.com/1171516
Commit-Queue: Jialiu Lin <jialiul@chromium.org>
Reviewed-by: Vadym Doroshenko <dvadym@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582977}

Bug: 835029
Change-Id: I16d97c659054f135456131866962d78aa68e18ac
Reviewed-on: https://chromium-review.googlesource.com/1173319Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Commit-Queue: Yue Cen <rsgingerrs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582976}

Grant screen access to web application and revoke it depending on
whether a web application can be shown on the screen. Only show a web
application when screen access has been granted.

Bug: internal b/112164384
Test: manual
Change-Id: I654f3a69395c1a84e33f38a84d52ba45060d96e2
Reviewed-on: https://chromium-review.googlesource.com/1164641Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: James West <jameswest@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582975}

If a fullscreen element was requested fullscreen user scrolling is
largely disabled on other layers. The overscroll would get reported
to java and it would attempt then to scroll the root layer. Add
checks whether the inner viewport scroll node is actually user
scrollable.

BUG=873626

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: If527ae57641df19b683027f35a8494d3c482a066
Reviewed-on: https://chromium-review.googlesource.com/1173324Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582974}

This reverts commit e1b21dc7.

Reason for revert:
  1) No longer needed
  2) Slowing down omnibox

Original change's description:
> Add memory metric to trace event to investigate omnibox performance
>
> Adding estimated memory usage to the quick history provider.
> it is suspected to be slow and cause jank on UI thread when memory usage
> is high.
>
> These metrics will be received with slow-reports and will help to
> investigate some jank on UI thread.
>
> R=​mpearson@chromium.org
>
> Bug: 868419
> Change-Id: I344f84ec00f318fdb9db63c5b464b119a9d5e3eb
> Reviewed-on: https://chromium-review.googlesource.com/1156847
> Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
> Reviewed-by: Mark Pearson <mpearson@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#579919}

TBR=mpearson@chromium.org,etienneb@chromium.org

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

Bug: 868419
Change-Id: I96785874209368579844e9c55052bc53de12a5a8
Reviewed-on: https://chromium-review.googlesource.com/1174692Reviewed-by: Mark Pearson <mpearson@chromium.org>
Commit-Queue: Etienne Bergeron <etienneb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582973}

Add a toggle to the sound content settings page to toggle
unified autoplay. Also adds a pref to store the user's
preference.

BUG=865548

Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: I8d2ac3ee3bb15d8daccef1f3a120b028b92e189a
Reviewed-on: https://chromium-review.googlesource.com/1145760
Commit-Queue: Becca Hughes <beccahughes@chromium.org>
Reviewed-by: Michael Giuffrida <michaelpg@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582972}

This has been off by default since M67 and is actually dead in M69.

Tbr: thakis@chromium.org
Bug: 832676
Change-Id: Iba63da4b6c0d12fea4356bc5173b19ae46d4c510
Reviewed-on: https://chromium-review.googlesource.com/1172791Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Elly Fong-Jones <ellyjones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582971}

BUG=873080
TEST=as in bug

Change-Id: Icd75715ac42789c84870967b11c9917a972ae086
Reviewed-on: https://chromium-review.googlesource.com/1173342
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Sidney San Martín <sdy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582970}

Some AppCache unit tests incorrectly use GURL() to get an URL with a
unique origin (different from other origins in the test). The way this
works may change in the future, so tests should use real origins
instead.

This CL also cleans up some lifecycle issues in the files touched by
the change.

Bug: 768460
Change-Id: Iaff5228f599209f3803c0374abcd53720e9906a9
Reviewed-on: https://chromium-review.googlesource.com/1174103Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582969}

Console Commands and Results no longer show a repeat count bubble.
It was possible to get consecutive Commands using expressions
starting with 'await', which collapsed when they should not.

Screenshot: https://imgur.com/a/8iOkL9p

Bug: 871940
Change-Id: I1dc2306d13c1511daa92fcd678520f3e8706e853
Reviewed-on: https://chromium-review.googlesource.com/1173265Reviewed-by: Andrey Lushnikov <lushnikov@chromium.org>
Commit-Queue: Erik Luo <luoe@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582968}

If there are no suggestions, the touch bar will show an empty
NSCandidateListTouchBarItem. Instead of showing that, the browser
window touch bar should appear if there are no suggestions.

TextSuggestionsTouchBarControllerTest.MakeTouchBar was modified to
test that a text suggestions touch bar is not created if there are
no suggestions.

Bug: 717553
Change-Id: I2eb3286e5a96b97bb8d7737ddf6db352698804b8
Reviewed-on: https://chromium-review.googlesource.com/1173407Reviewed-by: Sarah Chan <spqchan@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Commit-Queue: Tessa Nijssen <tnijssen@google.com>
Cr-Commit-Position: refs/heads/master@{#582967}

BrowserPluginGuest disables navigate_on_drag_drop for all browser plugin
guests. For mime handlers navigating on default drag drops is desirable.
After the mime handler is attached, update the web preferences to
re-enable navigate_on_drag_drop so unhandled drag drops onto mime
handlers result in navigations similar to other web content.

Bug: 819761
Change-Id: I5b0165be1d8c52538b189194fc9cbca9c86d96a7
Reviewed-on: https://chromium-review.googlesource.com/1173944
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Ehsan Karamad <ekaramad@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582966}

Developers should include bubble_dialog_delegate_view.h instead.

This is part 3 of 3 for aligning BubbleDialogDelegateView with its
filename.

BUG=873422

Change-Id: Ifd33203baf4d057c476026394d2833d0701e25e3
Reviewed-on: https://chromium-review.googlesource.com/1171919
Commit-Queue: Robert Liao <robliao@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582965}

Change-Id: Ia20886e1d26800e084ee63ef7604c7083e3479f1
Reviewed-on: https://chromium-review.googlesource.com/1170840Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582964}

https://skia.googlesource.com/skia.git/+log/d4322a8630bc..32c7d4dfcdca


git log d4322a8630bc..32c7d4dfcdca --date=short --no-merges --format='%ad %ae %s'
2018-08-14 swiftshader-skia-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com Roll third_party/externals/swiftshader 378c434627aa..80ab360d2622 (1 commits)
2018-08-14 mtklein@google.com add dstAT param to xform steps


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

The AutoRoll server is located here: https://autoroll.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.blink:linux_trusty_blink_rel;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=kjlubick@chromium.org

Change-Id: I368e81da43b77ddaf306cd452ef1ab5ed2035a8d
Reviewed-on: https://chromium-review.googlesource.com/1174791Reviewed-by: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: skia-chromium-autoroll <skia-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#582963}

Bug: none
Change-Id: Ie9e3a47ec63d493c34e844ad0d99b97dcb8c3a7b
Reviewed-on: https://chromium-review.googlesource.com/1169830
Commit-Queue: Asanka Herath <asanka@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582962}

The sources for validation_test_data was being listed as a directory rather than
a list of files. This is incorrect -- directories cannot be listed as sources
for the copy command in GN. This in turn caused isolate.py to think that the
file .../data/validation was a dependency, which then caused isolate.py to throw
an error since .../data/validation is a directory, not a file.

This CL explicitly lists all file dependencies.

Bug: 873208
Change-Id: I02ee6b28016bf36a612cd44079080274fcbf3744
Reviewed-on: https://chromium-review.googlesource.com/1171111Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582961}

   - Discards events produced by additional fingers during a cast side
     swipe gesture.
   - Rework unit tests to use GMock, and add test for the multiple fingers.

Bug: internal b/112314035
Test: on device and unit tests
Change-Id: I8c8c33299521e3e05ec9d196d835e0f0c5f04563
Reviewed-on: https://chromium-review.googlesource.com/1174566Reviewed-by: Alex Sakhartchouk <alexst@chromium.org>
Commit-Queue: Ryan Daum <rdaum@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582960}

Bug: 856621

Change-Id: I8bae0dff5d006338a682becb8e4fdb331bc81f77
Reviewed-on: https://chromium-review.googlesource.com/1169627
Commit-Queue: Chris Lu <thegreenfrog@chromium.org>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582959}

Now a widget is created after a (sub)frame and per-frame task runner
can be passed. However a widget is destroyed not before a frame, which
is inconsistent. We want to make it consistent by making a widget before
a frame, and in this case, per-frame task runner would no longer be
available.

This CL makes RenderView always use a thread-local task runner instead.
This CL introduces 'cleanup' task runner for cleaning up. We aim to
V8 executions on the default task runner and other thread-local task
runners, but V8 execution is inevitable on the cleanup phase. Then
this CL separates such tasks on the new task runner.

Change-Id: I5513e005796f9589eb269c526c2e6ae2b79c8dfd
Reviewed-on: https://chromium-review.googlesource.com/1164873Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Hajime Hoshi <hajimehoshi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582958}

Tests were using WeakPersistent<T> from stack directly. This does not
work anymore as soon as unified garbage collections also traverse the
stack to find wrappers.

Bug: chromium:843903
Change-Id: I1f93d631c7a6e0798903111416507e9fabd90f16
Reviewed-on: https://chromium-review.googlesource.com/1174538
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582957}

Bug: 778306
Change-Id: Ic4b1df90df4c3ab7402b58019401a65d61c1abaa
Reviewed-on: https://chromium-review.googlesource.com/1174097Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Wei-Yin Chen (陳威尹) <wychen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582956}

Adjust casing for 'desc', 'switch' and 'mpath'. Remove a duplicate
'animateColor'.

BUG=868861

Change-Id: I19256547abea3028791de402e354c47eee8ce949
Reviewed-on: https://chromium-review.googlesource.com/1174261
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582955}

In order to support permissions for Background Fetch, the
RenderFrameHost should be made available. The binding is done from
RenderFrameHostImpl now, with RendererInterfaceBinders left as
a fallback (to register from service worker contexts for example).

Bug: 692647
Change-Id: I3e12b60f410ba104601c68392a07fe24da1cc220
Reviewed-on: https://chromium-review.googlesource.com/1172785Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Rayan Kanso <rayankans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582954}

There were a number of circular and incorrect dependencies between
targets in this directory. With this change, I've largely fixed the
issues by moving things to vr_base. I did, however, move ButtonState
from UiInputManager to PlatformController.

I've also removed vr_base_export.h, which turned out to be
unnecessary.

Bug: 871811
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:linux_vr;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Change-Id: I7ee1d5c410c4098c6284dba8a3f565e6b460f34a
Reviewed-on: https://chromium-review.googlesource.com/1171667Reviewed-by: agrieve <agrieve@chromium.org>
Reviewed-by: Christopher Grant <cjgrant@chromium.org>
Reviewed-by: Aldo Culquicondor <acondor@chromium.org>
Commit-Queue: Ian Vollick <vollick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582953}

TBR=kbr@chromium.org

Bug: 872102
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
Change-Id: Ieea7f9d1947975333ce2f2b174f947da44202c3d
Reviewed-on: https://chromium-review.googlesource.com/1174693
Commit-Queue: Fernando Serboncini <fserb@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582952}

And configure libc++ to force inline ABI-hidden functions, as was its behaviour
before r338122. Without this, the symbol tables of Mach-O binaries grow
significantly due to including multiple definitions of these functions.

Bug: 866225, 870907, 872926
Change-Id: I4382e9de57fc79b3baff3d329e338887cb4b133b
Reviewed-on: https://chromium-review.googlesource.com/1174546
Commit-Queue: Hans Wennborg <hans@chromium.org>
Commit-Queue: Reid Kleckner <rnk@chromium.org>
Reviewed-by: Reid Kleckner <rnk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582951}

Followup to http://crrev.com/c/1157549

Bug: 868545
Cq-Include-Trybots: luci.chromium.try:linux_mojo
Change-Id: Ib1ab6a824beb147d4aab717aaaf878daf7439b4b
Reviewed-on: https://chromium-review.googlesource.com/1171548Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Clark DuVall <cduvall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582950}

BlobReader is thread-unsafe, so an instance must always be used in the
same sequence.

Change-Id: Ibce3b2f1ad25b4c2a4cc04a5e4cb248a52e3a9bc
Reviewed-on: https://chromium-review.googlesource.com/1174015Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Commit-Queue: Daniel Murphy <dmurph@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582949}

Move motivated by IppValidator chrome service that needs it.

Bug: chromium:831913
Test: base_unitttests pass and manual printing succeeds
Change-Id: Ia333819b30b2ea5953d1e219be799e89105e29cb
Reviewed-on: https://chromium-review.googlesource.com/1164538Reviewed-by: Sean Kau <skau@chromium.org>
Commit-Queue: Luum Habtemariam <luum@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582948}

Using wpt-import in Chromium c6163d95.
With Chromium commits locally applied on WPT:
7dad0f17 "Added new Sec-Metadata Web Platform Tests."


Build: https://ci.chromium.org/buildbot/chromium.infra.cron/wpt-importer/22711

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:
msisov@igalia.com:
  external/wpt/webvtt
tdresser@chromium.org:
  external/wpt/navigation-timing

NOAUTOREVERT=true
TBR=raphael.kubo.da.costa@intel.com

No-Export: true
Change-Id: I6e64b4a5d4566e6663cd2a9647702d32cbe05f40
Reviewed-on: https://chromium-review.googlesource.com/1174694
Commit-Queue: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Reviewed-by: Blink WPT Bot <blink-w3c-test-autoroller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582947}

These are histograms that have not been viewed in the last 6 months, but still
report data on the Stable channel. Set these histograms to stop being recorded
for Chrome releases after 2018-08-30. We will file bugs via Monorail (crbug)
reminding owners about the approaching histogram expiry – initially 30 days
prior to expiry, and also with follow-up alerts. The metrics dashboards will
also display a warning for anyone viewing a soon-to-expire histogram.

Owners and/or users of these histograms: Please comment on this CL if you think
that any affected histogram should not have an expiry date set! This should be
uncommon.

Otherwise, there are a few options going forward:
  * If the histogram is no longer needed, please send a follow-up CL to delete
    the recording code and to mark the histogram as <obsolete>. (You can also
    remove the expiry date in the same CL.)
  * If you want to set a different expiry date, please send a follow-up CL to do
    so.
  * If neither of the above apply, then keep an eye out for Monorail bugs as the
    histogram expiry date approaches.
For more info on how unused histograms are identified, see
https://goto.google.com/uma-unused-histograms-cleanup

Bug: 850539
Change-Id: I7d7e2967caa586a221b50a64b5769c281777e4df
Reviewed-on: https://chromium-review.googlesource.com/1126324Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Gayane Petrosyan <gayane@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582946}

This no longer needs to be a CHECK and is being seen sufficiently often
that we should really convert it to a DCHECK.

Bug: 873945
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ia014c9d1721ae6dbba71fe01d00d35412ee58701
Reviewed-on: https://chromium-review.googlesource.com/1174702Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: James MacLean <wjmaclean@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582945}

It's passing in perf tryjobs.

Bug: 787001
Change-Id: Ie9a74b141d6dd610a1bfab3d9d9ea79b40dafc48
TBR: tdresser@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1174632Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Annie Sullivan <sullivan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#582944}