GitLab

Enable views_mus_unittests on both lsan/asan and on msan, it should pass now.

Enable ozone_unittests and wayland_client_perftests on just msan
(they don't pass on lsan/asan yet).

With this, linux_chromeos_rel_specific_gtests_asan_bringup is identical to
linux_chromeos_rel_specific_gtests and can be removed, and because of _that_,
chromium_memory_chromiumos_asan_gtests is identical to linux_chromeos_rel_gtests
and can also be removed.

As a consequence, tests added to the cros rel bots will be added to the
memory bots automatically going forward.

TBR=kbr

Bug: 843511
Bug: 855580,855588,855584,855585,855583
Change-Id: I6a28ebae4c9005ce508f8caef07679a1bb50285c
Reviewed-on: https://chromium-review.googlesource.com/1112957Reviewed-by: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569949}

history_item.h is used in 1900+ compilation units, and this CL reduces
estimated pre-processed size of history_item.h from 5.78MB to 2.03MB.

Bug: 242216
Change-Id: I1db28440031fd826349278febd2ffa79af58f1ca
Reviewed-on: https://chromium-review.googlesource.com/1111774Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569948}

Now matching go/crostini-strings.

Bug: 849900
Change-Id: I019c4888b4e54df177158a0c566a6477088aca74
Reviewed-on: https://chromium-review.googlesource.com/1111742Reviewed-by: Ben Wells <benwells@chromium.org>
Commit-Queue: Nicholas Verne <nverne@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569947}

Disabling flaky test on mac

TBR=bbudge@chromium.org

BUG=707068

Change-Id: Ib401bfa6ef15e336fdcbe6ae231b97ec7c6cfdd9
Reviewed-on: https://chromium-review.googlesource.com/1112890Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569946}

When --ipc-dump-directory=DIR is passed, outgoing Mojo messages from
the renderer are written to:

DIR/INTERFACE_NAME/CONNECTOR_ID/NUM.METHOD_NAME.mojomsg

Where INTERFACE_NAME is the interface name of the message,
CONNECTOR_ID is a random number unique to each instance of a Connector,
METHOD_NAME is the the name of the method being called, and
NUM is a number used for ordering messages for a single connector.

Bug: 607649

Change-Id: I5b8735d3ca94707c6033563cb8dcc21e0f815ac3
Reviewed-on: https://chromium-review.googlesource.com/1070550Reviewed-by: Martin Barbella <mbarbella@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Commit-Queue: Oliver Chang <ochang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569945}

VisibleContentRect() and VisibleContentSize() are based on
scroll_offset_ (which is always (0, 0)), and Size() with scrollbars
possible excluded -- but there are no scrollbars any more. Replace
all of the calls with Size().

BUG=823365
TBR=dmazzoni@chromium.org

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ieb41515bf53e20762aca9f81df413ebb397c9f5d
Reviewed-on: https://chromium-review.googlesource.com/1112067
Commit-Queue: Stefan Zager <szager@chromium.org>
Reviewed-by: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569944}

The AutoRoll server is located here: https://fuchsia-sdk-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:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: Ie51e83301a9a31d16193d0c20d4f37ba5b25c664
Reviewed-on: https://chromium-review.googlesource.com/1113024
Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#569943}

According to spec[1], when document object doesn't have browsing
context, it should throw a "SecurityError" DOMException.

[1] https://html.spec.whatwg.org/multipage/origin.html#dom-document-domain

BUG=850432

Change-Id: Ibc12decadb2405bb5f3b190d60ad65e1ee21303b
Reviewed-on: https://chromium-review.googlesource.com/1112937Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569942}

This creates safer code overall.
If start and end AXPositions are invalid for any reason we didn't contemplate, the browser doesn't crash but returns an AXRange that is explicitly marked invalid.
It's also a nice workaround until CSS decorations are supported in AXPosition.

TBR=dmazzoni@chromium.org, aleventhal@chromium.org

Bug: 852266
Change-Id: I94db8aeda296690a842b674ea27743dc573205d7
Reviewed-on: https://chromium-review.googlesource.com/1112968Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569941}

These updated strings were provided by UX.

This CL is almost identical to jordynass@'s CL here:
https://chromium-review.googlesource.com/c/chromium/src/+/1112899

I copied it and am submitting it as a separate CL since all strings
are supposed to be landed before the week starting 6/25.

TBR=dpapad@chromium.org

Bug: 824568
Change-Id: I2eed76d0ace964947974eb7399354cb8a08bda9a
Reviewed-on: https://chromium-review.googlesource.com/1113017Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: Ryan Hansberry <hansberry@chromium.org>
Commit-Queue: Kyle Horimoto <khorimoto@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569940}

Also moves it's coordinator to history and creates HistoryClearBrowsingDataLocalCommands delegate.

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

This reverts commit 3bcc71d8.

Reason for revert: appears to break official builds due to how the cipd variable is flattened.

Original change's description:
> Add luci-go tool to be fetched via CIPD
>
> Do not remove the adhoc mechanism on GCS that predates CIPD yet, as the recipes
> need to be updated.
>
> Change analyze to not ignore changes to isolate.
>
> R=​tandrii@chromium.org
>
> Bug: 851596
> Change-Id: Ic068db83dea4c3a0f17b55181de523b16c9838a5
> Reviewed-on: https://chromium-review.googlesource.com/1097623
> Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
> Reviewed-by: Andrii Shyshkalov <tandrii@chromium.org>
> Reviewed-by: John Budorick <jbudorick@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#569688}

TBR=maruel@chromium.org,tandrii@chromium.org,ehmaldonado@chromium.org,jbudorick@chromium.org

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

No-Presubmit: true
Bug: 851596
Change-Id: I3717c6b0ebf68b08908037850d122727e41bf192
Reviewed-on: https://chromium-review.googlesource.com/1112823
Commit-Queue: John Budorick <jbudorick@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569938}

On Win, ARIA switches are equivalent to toggle buttons.
We need to expose both the pressed and checked states instead of only checked.
This fixes NVDA's announcement of the toggling of switches to on, whilst minimally affecting Jaws.
Jaws now reads "<switch name> on pressed" instead of "<switche name> on".
R=aleventhal@chromium.org, suproteem@chromium.org
Bug: 844021
Tested: manually with Jaws and NVDA, browser tests


Change-Id: I9ce4936002bf1a3cf0b99c73a73385c0a32ff3fc
Reviewed-on: https://chromium-review.googlesource.com/1101849
Commit-Queue: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569937}

Bug: 855588
Test: ozone_unittests
Change-Id: I29ca5cc777d1e835bb2279959d9a390e2475025d
Reviewed-on: https://chromium-review.googlesource.com/1112961
Commit-Queue: Nico Weber <thakis@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Antonio Gomes <tonikitoo@igalia.com>
Cr-Commit-Position: refs/heads/master@{#569936}

Change-Id: I5bfa51b5f9d16c1580febab4542be6aac3ccec5a
Reviewed-on: https://chromium-review.googlesource.com/1104898
Commit-Queue: Rob Buis <rbuis@igalia.com>
Reviewed-by: David Benjamin <davidben@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569935}

https://skia.googlesource.com/skia.git/+log/5f0cc0e06651..ebf160f308b6


git log 5f0cc0e06651..ebf160f308b6 --date=short --no-merges --format='%ad %ae %s'
2018-06-24 allanmac@google.com Clean starting point for interop. VK will let us dodge this entirely.


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

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=jcgregorio@chromium.org

Change-Id: Ia4b2dd22f3f40cfe05e2fa98991ebfc92435400c
Reviewed-on: https://chromium-review.googlesource.com/1112997Reviewed-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@{#569934}

Following bot results are included.
7073 7075 7077 7083 7086 7097 7102 7104 7105 7106 7115

15 lines were removed and 2 lines were deflaked by consecutive
results since 7029.

TBR=eae@chromium.org, mstensho@chromium.org
NOTRY=true

Bug: 591099
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: Ifbabcb71dc1c5aca51aea561b4d2b7b38b8e651f
Reviewed-on: https://chromium-review.googlesource.com/1110180
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569933}

Using wpt-import in Chromium 66c85500.

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

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

TBR=robertma

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

This CL renames the method OnRenderFrameMetadataChanged to
OnRenderFrameMetadataChangedAfterActivation and introduces a new
method: OnRenderFrameMetadataChangedBeforeActivation.

OnRenderFrameMetadataChangedBeforeActivation is called as soon as the
RenderFrameMetadata arrives in the browser process.

OnRenderFrameMetadataChangedAfterActivation is called after the corresponding
frame token arrives from Viz. This frame token corresponds to a surface
activation.

The BeforeActivation method will be used by Surface Sync for Android to
update the overscroll controller which controls the glow effect when
scrolling.

This effect should be roughly synchronized with the renderer but does
not have to be exactly synchronized as that introduces a lot of overhead.

Bug: 672962
Change-Id: I6c1ac68c6a65f0c074dfe519311ecdb83908d76b
Reviewed-on: https://chromium-review.googlesource.com/1112074
Commit-Queue: Fady Samuel <fsamuel@chromium.org>
Reviewed-by: Saman Sami <samans@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569931}

Bug: 729800
Change-Id: Ie216054a92e223c29120226b645b2c10b208dde0
Reviewed-on: https://chromium-review.googlesource.com/1073080Reviewed-by: Victor Costan <pwnall@chromium.org>
Commit-Queue: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569930}

This change introduces the possibility to query a FidoBleDevice whether
or not it is currently in pairing mode. In accordance with the CTAP spec
this is done by looking at the advertisment data flags if possible, and
falling back to investigating service data if required.

Bug: 763303
Change-Id: I373151a10d63e83ca2ac57f7b53c1269b9d60cfc
Reviewed-on: https://chromium-review.googlesource.com/1096234Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: James Hawkins <jhawkins@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Commit-Queue: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569929}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/3cb3fb81..fa532590

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,machenbach@chromium.org,kozyatinskiy@chromium.org,sergiyb@chromium.org

Change-Id: Ief67196bf237f06ffe129819398cc4b400372683
Reviewed-on: https://chromium-review.googlesource.com/1112948Reviewed-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@{#569928}

HardwareDisplayPlaneManagerUnittest allocated CTMs with new,
while they are deleted with free.
This patch fixes that so that we can run ozone_unittests with
asan on trybots.

Bug: 855588
Test: ozone_unittests
Change-Id: If5827d38b34cb8df2f56c770e8f9d28c587c022a
Reviewed-on: https://chromium-review.googlesource.com/1112964Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569927}

ChromeLauncherController is resetting the virtual keyboard when the
active user changes. However, the SessionController (which is already
in ash) can have an observer that can listen to the same event. By
making the VirtualKeyboardController a SessionObserver, we can move
the keyboard reset to the other process to make it mustash-friendly.

Bug: 826391
Change-Id: I70b622105c3bf6dd415b1eee5f0521a38b6d1bf1
Reviewed-on: https://chromium-review.googlesource.com/1100672
Commit-Queue: Blake O'Hare <blakeo@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569926}

https://skia.googlesource.com/skia.git/+log/7454cbdd1596..5f0cc0e06651


git log 7454cbdd1596..5f0cc0e06651 --date=short --no-merges --format='%ad %ae %s'
2018-06-24 skia-recreate-skps@skia-swarming-bots.iam.gserviceaccount.com Update SKP version


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

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=jcgregorio@chromium.org

Change-Id: I86cc73faa5e8270a7e61977a6a876f78763ad82a
Reviewed-on: https://chromium-review.googlesource.com/1112927Reviewed-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@{#569925}

Updating testing filters for the Mojo Android FYI bot.

Surface Sync is a new consistent failure.
Viz Android are failures that occur on all Viz platforms, and are now confirmed
on Android as well.

TBR=fsamuel@chromium.org
TEST=surface_sync_content_browsertests, viz_content_browsertests

Bug: 849746
Change-Id: Id1ba7e03aa28f28b21e59c694a7cb6f39b9d843c
Reviewed-on: https://chromium-review.googlesource.com/1112966Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569924}

# This is an automated release commit.
# Do not revert without consulting chrome-pmo@google.com.
NOAUTOREVERT=true
TBR=mmoss@chromium.org

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

This implements shared style for the updated UI.

Major changes:
1) oobe-dialog slot="header" replaced with two slots: "title" and "subtitle".
2) shared oobe_dialog_parameters.css removed, all parameters are styled
in oobe-dialog CSS.
3) All dialogs could be displayed both full-screen or windowed.
4) If any dialog is full-screen, all subsequent will also be displayed
with full-screen style.
5) Elements hosting oobe-dialogs must implement OobeDialogHostBehavior.

Bug: 852034,852043, 852041

Cq-Include-Trybots: luci.chromium.try:closure_compilation
Change-Id: Id282d2f3385def8fc6a376bc85fc32734653e466
Reviewed-on: https://chromium-review.googlesource.com/1111025
Commit-Queue: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Wenzhao (Colin) Zang <wzang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569922}

CrOS Camera app needs to be whitelisted to use fileManagerPrivate API to show the taken photo/video under Downloads/ and be notified for their changes under Downloads/.

BUG=854551

Change-Id: I0ef7654db7b1ac504e051bf64ef9c30e0cb375a4
Reviewed-on: https://chromium-review.googlesource.com/1109674Reviewed-by: Ben Wells <benwells@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Commit-Queue: yuli <yuli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569921}

https://skia.googlesource.com/skia.git/+log/c2cc67b5c3a7..7454cbdd1596


git log c2cc67b5c3a7..7454cbdd1596 --date=short --no-merges --format='%ad %ae %s'
2018-06-23 egdaniel@google.com Add legacy flag for vulkan interface for flutter.


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

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: If5faf5a8623477e838e8d7df978057f3785c7b76
Reviewed-on: https://chromium-review.googlesource.com/1112141Reviewed-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@{#569920}

For SPv175, we use a display item type instead of the paint phase.

Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I1dfaf54f832e5179b96601bf9654b59a90d7df34
Reviewed-on: https://chromium-review.googlesource.com/1111686
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Tien-Ren Chen <trchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569919}

Also removed the stale expectation files on mac

TBR=thakis@chromium.org

Bug: 855222
Change-Id: Iaaaebfcb5dc00c0d1c42f3a2ecbb5bbfcbbbf57c
Reviewed-on: https://chromium-review.googlesource.com/1112949Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569918}

The AutoRoll server is located here: https://fuchsia-sdk-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:fuchsia_arm64_cast_audio;luci.chromium.try:fuchsia_x64_cast_audio
TBR=cr-fuchsia+bot@chromium.org

Change-Id: If07f02931603c49223106373ebf039ab48f30cae
Reviewed-on: https://chromium-review.googlesource.com/1112947
Commit-Queue: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Reviewed-by: Fuchsia SDK Autoroller <fuchsia-sdk-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#569917}

This reverts commit 981a543f.

Reason for revert:
These tests have been failing since they were added:
https://ci.chromium.org/buildbot/chromium.webkit/WebKit%20Linux%20Trusty%20Leak/20683

Original change's description:
> [CSS Env Vars] Add some WPT tests
> 
> Adds some WPT tests to test env() with @supports as well
> as fallback values.
> 
> BUG=825890
> 
> Change-Id: I071f5c2582f8056fe39b4a50ab62140d579c577d
> Reviewed-on: https://chromium-review.googlesource.com/1111023
> Reviewed-by: Rune Lillesveen <futhark@chromium.org>
> Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
> Commit-Queue: Becca Hughes <beccahughes@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#569852}

TBR=mlamouri@chromium.org,beccahughes@chromium.org,futhark@chromium.org

Change-Id: I32fbe3682558bdd2d117c8f647750e5d8bcbf740
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 825890
Reviewed-on: https://chromium-review.googlesource.com/1112982Reviewed-by: Nico Weber <thakis@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569916}

https://chromium.googlesource.com/chromiumos/chromite.git/+log/1deead13f98b..abae09e75336


git log 1deead13f98b..abae09e75336 --date=short --no-merges --format='%ad %ae %s'
2018-06-23 vapier@chromium.org pylintrc: drop unused warnings
2018-06-23 xixuan@chromium.org chromeos_config: Add enable_skylab_hw_tests for migration.
2018-06-23 dgarrett@google.com commands: RunBranchUtilTest -> RunLocalTryjob


Created with:
  gclient setdep -r src/third_party/chromite@abae09e75336

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



BUG=chromium:None,chromium:854862,chromium:None
TBR=chrome-os-gardeners@chromium.org

Change-Id: I75ca467c1b3140a61ac4a5d38292e541ad0d23d8
Reviewed-on: https://chromium-review.googlesource.com/1112140Reviewed-by: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Commit-Queue: Chromite Chromium Autoroll <chromite-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#569915}

Current Cancel operation on FidoHidDevice does not conform to behavior
defined by the CTAP spec. More specifically, CTAP spec mandates that once
Cancel operation is invoked, all pending transactions must be deleted
and cancel command must be sent before any remaining transactions. This
is not how current FidoHidDevice works. Currently FidoHidDevice will
simply add Cancel command packet into a queue and wait for prior
transaction to finish before sending Cancel command to the device.

Bug: 833806
Change-Id: I66f67e1ff36aa724c0340fd6630a941da911921b
Reviewed-on: https://chromium-review.googlesource.com/1111617
Commit-Queue: Jun Choi <hongjunchoi@chromium.org>
Reviewed-by: Jan Wilken Dörrie <jdoerrie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569914}

This reverts commit 5e32cab2.

Reason for revert: The cause of the failures has (hopefully) been fixed.

Original change's description:
> Disable several failing blink_perf.parser stories on Nexus 5X webview
> 
> NOTRY=true
> TBR=nednguyen@chromium.org
> 
> Bug: 851539
> Change-Id: Ia51f717aa8c7ca47b47007fa4aa5077767a86e91
> Reviewed-on: https://chromium-review.googlesource.com/1095676
> Commit-Queue: Charlie Andrews <charliea@chromium.org>
> Reviewed-by: Charlie Andrews <charliea@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#566043}

Bug: 851539
Change-Id: I69b8f51a4e91171448f6d61c052168deaa3dc222
Reviewed-on: https://chromium-review.googlesource.com/1112181Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#569913}

Also enabled gl_image_native_pixmap.cc on Fuchisa. ExportHandle() is
currently stubbed as NOTIMPLEMENTED.

Bug: 852011, 766360
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: I2978a320fef928f32b3ff27473c593293a8168d6
Reviewed-on: https://chromium-review.googlesource.com/1112592Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Michael Spang <spang@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569912}

https://pdfium.googlesource.com/pdfium.git/+log/b59b36610e39..27d3aa2ed234


git log b59b36610e39..27d3aa2ed234 --date=short --no-merges --format='%ad %ae %s'
2018-06-23 thestig@chromium.org Fix some nits from commit 27cf78d8.


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

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: Idff059fc4113b6ed1958ead821952a1b3261bcd1
Reviewed-on: https://chromium-review.googlesource.com/1112231Reviewed-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@{#569911}

Bug: 855269
Change-Id: I8ab4534f2ede8c0b8d2f3348309046ee0de9d164
Reviewed-on: https://chromium-review.googlesource.com/1112043Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569910}