GitLab

This reverts commit a73dae7e.

Reasons for revert: This CL breaks jpeg_encode_accelerator_unittest
The test failed with a SIGTRAP.
After reverting the CL, the test passes.

TBR: dcastagna@chromium.org
Bug: b:111832630
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: If13254b68a0bbc08863cb477df13810a66874b30
Reviewed-on: https://chromium-review.googlesource.com/1152539
Commit-Queue: Matthew Cary <mattcary@chromium.org>
Reviewed-by: Matthew Cary <mattcary@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578648}

The current IdentityTestEnvironment APIs to wait for access token
requests and issue responses operate in a shotgun manner: when the next
access token request is received, the test API implementation issues a
response for *all* pending access token requests. However, unittests
that is targeted in an upcoming conversion requires more flexibility:
as the production code that it is testing interacts with multiple
accounts, the test issues access token requests for multiple accounts,
and then sequentially issues responses and checks that a specific flow
for each account in question was initiated in response to the specific
response. Moreover, one of these unittests issues responses in an
order different to the order in which the requests were made.

To accommodate porting of these tests, this CL adds the ability to wait
for an access token request for a given account and then issue a
response only for that account. If while waiting for a request from a
specific account a request for a *different* account is seen, the
waiting code forwards on the handling of the request for that other
account to the next iteration of the runloop; this allows for the case
where a test wants to handle requests for multiple accounts in an
order different to the order in which those requests were made.

We leave in a variant that does not take in the account ID and operates
as before, as this is convenient for the common case of tests that don't
care about this level of detail (usually because they are testing a
production flow that operates on the primary account).

Bug: 798699, 809923
Change-Id: I6b1d93efd47b1eba128ac0b62c833736700e5196
Reviewed-on: https://chromium-review.googlesource.com/1149876
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578647}

After r541507, requesting functor is not blocked until renderer side
generates a frame. However if functor is called without a frame, it
currently leaves the frame buffer untouched, which is a problem for
parts of the frame buffer that is otherwise untouched.

The ideal solution is to have functor draw the background color. But
hooking this up is relatively complicated.

Instead have java side draw the background color until UI thread
receives returned resources from render thread, which indicates that
parent side has received frames.

Bug: 864436
Change-Id: I8bbf5c6c1353138dff071ff9cfbf58eb6e217eb3
Reviewed-on: https://chromium-review.googlesource.com/1150779Reviewed-by: Tobias Sargeant <tobiasjs@chromium.org>
Commit-Queue: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578646}

https://chromium.googlesource.com/angle/angle.git/+log/604d873e1df5..21e9baf71e6e


git log 604d873e1df5..21e9baf71e6e --date=short --no-merges --format='%ad %ae %s'
2018-07-27 thomasanderson@chromium.org Roll Vulkan-Loader to a835880


Created with:
  gclient setdep -r src/third_party/angle@21e9baf71e6e

The AutoRoll server is located here: https://angle-chromium-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=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@chromium.org

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

TBR=zmo@chromium.org
NOTRY=true

BUG=868367
BUG=750896

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: If48cb102f9c217d5e4fcd5c86e2f94907619b10c
Reviewed-on: https://chromium-review.googlesource.com/1152991
Commit-Queue: Geoff Lang <geofflang@chromium.org>
Reviewed-by: Geoff Lang <geofflang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578644}

This test is flaking timeout on Linux (dbg), Mac (dbg), and Linux ASAN.

TBR=rmcilroy@chromium.org

Bug: 867982
Change-Id: I70037407985472c08a3912949a7687fbb78f5434
Reviewed-on: https://chromium-review.googlesource.com/1151764
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578643}

AppKit is eager to allow server-side dragging in the title bar area
(meaning marking the region as draggable at the window server level),
but Views currently decides on a click-by-click basis (see |-hitTest:|).
One AppKit requirement is that, for a view to block title bar dragging,
it needs to return YES from |-acceptsFirstResponder:|, even if it
doesn't actually accept first responder later. BridgedContentView
returned different values at different times, which made dragging
inconsistent. This was sidestepped by overriding |-[NSWindow
_copyDragRegion]|, but that method no longer exists on 10.14.

This change makes |-acceptsFirstResponder| always return YES and removes
the hack. A similar hack is left over to support 10.10. If this change
turns out to not be viable, an override like this should work instead:

    @implementation BrowserNativeWidgetWindow
    // …
    - (NSRect)_opaqueRectForWindowMoveWhenInTitlebar {
      return NSZeroRect;
    }
    //…
    @end

Bug: 855901
Change-Id: I4ef93f1bee1b2cc7b39fab0eec7fe82a526b61e4
Reviewed-on: https://chromium-review.googlesource.com/1152076Reviewed-by: Elly Fong-Jones <ellyjones@chromium.org>
Commit-Queue: Sidney San Martín <sdy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578642}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/7399ae5d..8c84d971

Please follow these instructions for assigning/CC'ing issues:
https://github.com/v8/v8/wiki/Triaging%20issues

Please close rolling in case of a roll revert:
https://v8-roll.appspot.com/
This only works with a Google account.

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel;luci.chromium.try:android_optional_gpu_tests_rel

TBR=hablich@chromium.org,v8-waterfall-sheriff@grotations.appspotmail.com

Change-Id: Idd259a0c11d9a21f16a2ac4a6606f99d7a135f99
Reviewed-on: https://chromium-review.googlesource.com/1152892Reviewed-by: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Commit-Queue: V8 Autoroller <v8-ci-autoroll-builder@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#578641}

Prior to this CL each replaced element type implemented its own clipping.
This CL refactors it so that a clip node will be applied in the common
path, ReplacedPainter::Paint(), so the specialized
XyzPainter::PaintReplaced() won't need to apply their own clips.

BUG=730284

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I4d30fa3a80dfe54d4729b17d1084cd685a8fb712
Reviewed-on: https://chromium-review.googlesource.com/1150866
Commit-Queue: Philip Rogers <pdr@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578640}

Don't test system impl as it doesn't always respond to interrupt.
Attempt to reduce race in test.

Bug: 866911
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester
Change-Id: I74dc6c4ffdec4654cb0e0ab2912fb54a8564d717
Reviewed-on: https://chromium-review.googlesource.com/1152988Reviewed-by: Helen Li <xunjieli@chromium.org>
Commit-Queue: Paul Jensen <pauljensen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578639}

This test is working correctly on other platforms.
Try enabling the test to verify that it's no longer flaky.

Bug: 797261
Change-Id: Id31748868eacb41fbc560a877eef22db3e6c29b1
Reviewed-on: https://chromium-review.googlesource.com/1143597Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Liquan (Max) Gǔ <maxlg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578638}

|webView:decidePolicyForNavigationAction| is called on subresources
load as well. Pending item and context should not be updated in this
case, otherwise it causes the incorrect CL to be displayed.

Bug: 865893, 866379
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Icd721c8044b32cb5088631812ffe2de3c95c9c1b
Reviewed-on: https://chromium-review.googlesource.com/1152112Reviewed-by: Kurt Horimoto <kkhorimoto@chromium.org>
Commit-Queue: Danyao Wang <danyao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578637}

CORSURLLoader uses network::ResourceRequest::request_initiator which
ignores iframe sandboxing, which is a bug. Let's add a simple test for
the behavior.

Bug: 867834
Change-Id: Ia45113503f98b3d18e31c785e703d29eee658d08
Reviewed-on: https://chromium-review.googlesource.com/1151167
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578636}

I moved the code from PaintClosingTabs() to a local lambda and refactored
the code that checks for the hovered states into a separate lambda. Now,
when closing a hovered tab (especially if you add --animation-duration-scale=4.0)
you can clearly see the closing and hovered tab paint with the lower tails
visible until it's gone. While less likley to happen, the code will also
ensure that if there are multiple tabs being closed with an active hover
in progress, they will paint along with the non-closing hovered tabs in
the correct order.

Bug: 867167
Change-Id: Id5d28ef51857390b3f7ec641a8a0c071ce562859
Reviewed-on: https://chromium-review.googlesource.com/1150218
Commit-Queue: Allen Bauer <kylixrd@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578635}

This is timing out consistently on the CQ Mac bot, and occasionally
on the waterfall.

TBR=tkent@chromium.org

Bug: 868317
Change-Id: I1e20fd05870f28ed238f8bda6fc82acf1f5b9168
Reviewed-on: https://chromium-review.googlesource.com/1152898Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578634}

Provide a "Enable tracing" option in the menu of the SystemWebViewShell,
to demo/test the new Tracing API functionality. This requires Android P
SDK which has been dropped upstream recently.

When "Enable tracing" is selected the tracing is started. The following
configuration is used:
- trace web-developer categories
- use continuous tracing i.e. a ring buffer

When the user un-checks "Enable tracing" in the menu the tracing is stopped
and the trace data is written to webview_tracing.json in the application
file directory. An alert dialog showing the number of bytes written is
shown upon completion.

Note:
The trace file can be pulled from the device using "adb pull" using the
relevant local directory, e.g.
$ adb pull /data/user/0/org.chromium.webview_shell/files/webview_tracing.json .

BUG=798101

Change-Id: I2a22fbf5f07f12e9c3eadfe9fb027c05b892c092
Reviewed-on: https://chromium-review.googlesource.com/1143820
Commit-Queue: Tim Volodine <timvolodine@chromium.org>
Reviewed-by: Richard Coles <torne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578633}

This reverts commit 453eba23.

Reason for revert: Failing Linux ASAN/LSAN bot: https://logs.chromium.org/logs/chromium/buildbucket/cr-buildbucket.appspot.com/8939853423518476256/+/steps/chromeos_unittests/0/logs/ServiceConnectionTest.BindModelProvider/0

Original change's description:
> Add basic ServiceConnection unit test
> 
> The is just testing that ServiceConnection::BindModelProvider returns
> successfully. The Mojo invitation won't go anywhere beyond the no-op
> FakeMachineLearningClient D-Bus client.
> 
> To make this test compile, I had to fix an #include from an
> overlooked file rename in an earlier CL ...
> 
> Bug: 863794
> 
> Change-Id: Ifd31fea950145561cd5954ae16e930b801bfe49b
> Reviewed-on: https://chromium-review.googlesource.com/1139942
> Commit-Queue: Andrew Moylan <amoylan@chromium.org>
> Reviewed-by: Ken Rockot <rockot@chromium.org>
> Reviewed-by: Dan Erat <derat@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#578329}

TBR=derat@chromium.org,rockot@chromium.org,amoylan@chromium.org

Change-Id: I9878dee8885c78f88c0af50e70e921861ab87663
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 863794
Reviewed-on: https://chromium-review.googlesource.com/1152371Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578632}

This implements the discovery of BluetoothRemoteGattCharacteristics for
WinRT.

Bug: 821766
Change-Id: Iba0cbe9f7bae4d5a4403bd12193077ad57358387
Reviewed-on: https://chromium-review.googlesource.com/1136310
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578631}

Since it's been a week after pages in top_real_world_mobile were
refreshed, delete the old pages and their corresponding expectations.

Bug: 852530
Change-Id: Ic4d9cb9503fa22dd2b73735404a60c69e2a8a2ba
Reviewed-on: https://chromium-review.googlesource.com/1151104
Commit-Queue: Amy Qiu <amyqiu@google.com>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#578630}

Record the results of the task UKM recording to ensure that we are not
dropping tasks anymore (we used to do so for OOPIFs).

R=eseckler@chromium.org,holte@chromium.org
BUG=866169

Change-Id: I814bd8f71e9e2c0ba6de75f861cb46ca1119aa31
Reviewed-on: https://chromium-review.googlesource.com/1150226
Commit-Queue: Alexander Timin <altimin@chromium.org>
Reviewed-by: Eric Seckler <eseckler@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578629}

This reverts commit f3f5b838.

Reason for revert: Breaks official build: https://crbug.com/868258

Original change's description:
> Reland "[ar] Do not refer to ARCore shim in APK merger"
> 
> This is a reland of 58e4a081
> 
> Original change's description:
> > [ar] Do not refer to ARCore shim in APK merger
> > 
> > This hard-coding should no longer be required.
> > 
> > Bug: 839191
> > Change-Id: Id44f0f19da6efcee90ef79ea3e241eb2a7ea5843
> > Reviewed-on: https://chromium-review.googlesource.com/1147706
> > Commit-Queue: Ian Vollick <vollick@chromium.org>
> > Reviewed-by: Richard Coles <torne@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#577662}
> 
> Bug: 839191
> Change-Id: I42c3d31c0cbe49c1fe2d68c55d0db18dcdc3381d
> Reviewed-on: https://chromium-review.googlesource.com/1151567
> Reviewed-by: Richard Coles <torne@chromium.org>
> Commit-Queue: Ian Vollick <vollick@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#578347}

TBR=vollick@chromium.org,torne@chromium.org

Change-Id: I1383b1330cb21619fe040ed420487fe33003101f
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 839191, 868258
Reviewed-on: https://chromium-review.googlesource.com/1152274Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Commit-Queue: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578628}

ModelAssociationManager used to DCHECK that all DataTypeControllers are
in a NOT_RUNNING state. This apparently assumes that it receives freshly
created DTCs, which isn't actually the case: ModelAssociationManager
gets destroyed during Sync shutdown, but the DTCs don't, so if Sync later
starts up again, there's no guarantee that the DTCs are NOT_RUNNING.

While we're here, also replace some iterator-based loops with range-based
loops.

Bug: 856179
Change-Id: I6a14cbe1955df11aea1c8796ae44b637ff777e58
Reviewed-on: https://chromium-review.googlesource.com/1152922Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578627}

TBR=dpranke@chromium.org

Bug: 868180
Change-Id: Ic9cb48f82954f102f60dd3e1b9c29bcca209f3bb
Reviewed-on: https://chromium-review.googlesource.com/1152566Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578626}

Bug: 866899
Cq-Include-Trybots: master.tryserver.chromium.perf:obbs_fyi
Change-Id: I9083c01776240859d0802ce0c09786a3d748daea
Reviewed-on: https://chromium-review.googlesource.com/1152485Reviewed-by: Juan Antonio Navarro Pérez <perezju@chromium.org>
Reviewed-by: Annie Sullivan <sullivan@chromium.org>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#578625}

Always submit a CompositorFrame on OnFirstSurfaceActivation even if
the fallback doesn't change.

Bug: 827242
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I560b5251a188eae2a83db384367e2201ffcce83b
Reviewed-on: https://chromium-review.googlesource.com/1152209
Commit-Queue: Saman Sami <samans@chromium.org>
Reviewed-by: kylechar <kylechar@chromium.org>
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578624}

Omnibox width was 10 characters (plus some extra for page actions and location bar bubbles), and is now 20 characters.

Bug: 849784
Change-Id: Iaacab5244b5f1c21156151f49e0405e844f09451
Reviewed-on: https://chromium-review.googlesource.com/1135147Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Tommy Li <tommycli@chromium.org>
Reviewed-by: Justin Donnelly <jdonnelly@chromium.org>
Commit-Queue: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578623}

Change-Id: If91c0fe7a5aec868cca22a132c32e1b2344e5440
Reviewed-on: https://chromium-review.googlesource.com/1152921Reviewed-by: Mugdha Lakhani <nator@chromium.org>
Commit-Queue: Peter Beverloo <peter@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578622}

Replaces the custom backlink from V8->Blink that was using a v8::External with a
GC-aware backpointer that is encapsulated in the CustomWrappableAdapter
interface.

CustomWrappableAdapter establishes a link from a given JavaScript object to the
Blink object inheriting from CustomWrappableAdapter. The link is known to
garbage collectors and thus the Blink object will be kept alive as long as the
JavaScript object is alive. The adapter can be used to model liveness across V8
and Blink component boundaries. In contrast to ScriptWrappable, there is no IDL
definitions required and the JavaScript object must not escape to user-visible
JavaScript.

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;luci.chromium.try:win_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Id9b6a046fd5e3f4c31ddf15894a9968701831e90
Bug: chromium:843903
Reviewed-on: https://chromium-review.googlesource.com/1145262
Commit-Queue: Michael Lippautz <mlippautz@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578621}

When a tab is closed using a gesture (i.e. overscroll action or long
press on the TabGrid button), the non-incognito BVC was selected even
if it has no Tab.

This leads to an issue as the BVC is very briefly presented during this
time, before being dismissed. But the -viewDidAppear: call is executed,
which leads to a situation where the BVC is marked as "active" even if
it is not presented on screen. The -viewWillDisappear: call is never
made.

This CL fixes it by setting the main BVC as active only if it contains
tabs.

Bug: 849937
Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I88f9a36247a7b5fc9ea34b686cc17850aca1615d
Reviewed-on: https://chromium-review.googlesource.com/1150533Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Reviewed-by: Mark Cogan <marq@chromium.org>
Commit-Queue: Gauthier Ambard <gambard@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578620}

Instead of the deprecated argumentless Int32Value and BooleanValue
functions, it now uses the Context versions which return MaybeLocals.
Since this is for testing, we just force the results to their respective
types and crash if not possible.

Change-Id: I4a1b83640bdd64e3d7b81c5e21e1c8e0e89eb900
Reviewed-on: https://chromium-review.googlesource.com/1151987Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Dan Elphick <delphick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578619}

https://chromium.googlesource.com/catapult.git/+log/a1e31db3c6b7..787a378926fb


git log a1e31db3c6b7..787a378926fb --date=short --no-merges --format='%ad %ae %s'
2018-07-27 sadrul@chromium.org rendering: Add pipeline metrics.


Created with:
  gclient setdep -r src/third_party/catapult@787a378926fb

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=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

BUG=chromium:855328
TBR=sullivan@chromium.org

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

Since the titles of the infobars have been shortened, the information
about where passwords are saved for syncing users is now added to the
body of the save and update passwords infobars.

Bug: 866461, 862269
Change-Id: Ic1231b1d8daaaa4a7f53730540b79439121b3ab1
Reviewed-on: https://chromium-review.googlesource.com/1146759
Commit-Queue: Ioana Pandele <ioanap@chromium.org>
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578617}

A change in when Skia calls glGenMipMaps() causes imperceptible image
diffs.

Bug: skia:8155
Change-Id: I176f6e68f6ff961f979311dbb9873ef1e7057283
Reviewed-on: https://chromium-review.googlesource.com/1152073Reviewed-by: Robert Phillips <robertphillips@google.com>
Commit-Queue: Brian Salomon <bsalomon@google.com>
Cr-Commit-Position: refs/heads/master@{#578616}

Various test APIs around IdentityManager currently DCHECK preconditions
when invoked (e.g., clearing the primary account DCHECKs that there is
a primary account). However, unittests for GCM that will shortly be
converted intentionally stress-test the system in various exceptional
ways, e.g., invoking the flow that the primary account was cleared when
there is no primary account. To accomodate porting those unittests
without having to reduce their coverage, this CL relaxes the constraints
on the relevant IdentityManager test APIs.

Bug: 798699, 809923
Change-Id: Ibe2db519d0e231ea707ad09b329d6abc6ad7a9d2
Reviewed-on: https://chromium-review.googlesource.com/1149864
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Sylvain Defresne <sdefresne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578615}

BUG=835860

Cq-Include-Trybots: luci.chromium.try:ios-simulator-full-configs;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: Ide83ee27d1a888a08787b8726c0e5cc80fe80f03
Reviewed-on: https://chromium-review.googlesource.com/1148018Reviewed-by: edchin <edchin@chromium.org>
Commit-Queue: Rohit Rao <rohitrao@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578614}

Using wpt-import in Chromium 8d361113.
With Chromium commits locally applied on WPT:
7dad0f17 "Added new Sec-Metadata Web Platform Tests."
408f60ca "Remove Shared Worker WPT for WebUSB"


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

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:
meade@chromium.org:
  external/wpt/web-animations

TBR=robertma

No-Export: true
Change-Id: I52462748674d7db6eefa708e280ccf67bc5d99eb
Reviewed-on: https://chromium-review.googlesource.com/1152706
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@{#578613}

Adds channel information ("stable", "beta", "dev", 'cannary") next to
the browser version.

BUG=chromium:849803
TEST=browser_tests --gtest_filter=*DeviceStatusCollector*

Change-Id: I30c4b78950ad1540169835bc4e295bc9ba0ea483
Reviewed-on: https://chromium-review.googlesource.com/1124162Reviewed-by: Pavol Marko <pmarko@chromium.org>
Reviewed-by: Julian Pastarmov <pastarmovj@chromium.org>
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Commit-Queue: Lutz Justen <ljusten@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578612}

BUG=836871

Change-Id: I278b34cb305a13a029e84eaaeec57144e2858678
Reviewed-on: https://chromium-review.googlesource.com/1149364Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Cr-Commit-Position: refs/heads/master@{#578611}

https://pdfium.googlesource.com/pdfium.git/+log/aa418e541589..b3bab6ce43ca


git log aa418e541589..b3bab6ce43ca --date=short --no-merges --format='%ad %ae %s'
2018-07-27 art-snake@yandex-team.ru Parse obj nums range within Hint tables for shared groups.


Created with:
  gclient setdep -r src/third_party/pdfium@b3bab6ce43ca

The AutoRoll server is located here: https://pdfium-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.


TBR=dsinclair@chromium.org

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

Building //media takes around 23 CPU minutes. A experimental
branch showed that this could be reduced, by using jumbo,
to around 9 CPU minutes. media/cast is the fourth largest part
of media and takes around 2 CPU minutes to compile without
jumbo.

This commit enables jumbo for media/cast.

Bug: 867350
Change-Id: Iaefb6e7ac95c1c7fab78478f879a8ba542f329d9
Reviewed-on: https://chromium-review.googlesource.com/1152807Reviewed-by: Chrome Cunningham (In Paris) <chcunningham@chromium.org>
Commit-Queue: Chrome Cunningham (In Paris) <chcunningham@chromium.org>
Cr-Commit-Position: refs/heads/master@{#578609}