GitLab

https://chromium.googlesource.com/chromiumos/chromite.git/+log/a82d0a22067f..e5f282cb55b2


git log a82d0a22067f..e5f282cb55b2 --date=short --no-merges --format='%ad %ae %s'
2018-08-16 chrome-bot@chromium.org Update config settings by config-updater.


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

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.


TBR=chrome-os-gardeners@chromium.org

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

TBR=wjmaclean@chromium.org

Bug: 874976
Change-Id: I6973e2de0fb52dbfe5cec8319a02507736603243
Reviewed-on: https://chromium-review.googlesource.com/1178476Reviewed-by: Xida Chen <xidachen@chromium.org>
Reviewed-by: James MacLean <wjmaclean@chromium.org>
Commit-Queue: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583825}

In the field we are seeing a small percentage of exceptions while trying to
schedule a task with JobScheduler.  The invalid argument exception is
complaining that we haven't registerd our scheduler component properly,
but we believe that we have.  This seems to happen on older OSs that have
been more heavily modified.  Since we have limited means of debugging these,
we'll catch the error and return failure instead.

Bug: 831911
Change-Id: I8c8c376a24744d786e87bf30a8c4ab914f13e5be
Reviewed-on: https://chromium-review.googlesource.com/1171873Reviewed-by: Tommy Nyquist <nyquist@chromium.org>
Reviewed-by: Carlos Knippschild <carlosk@chromium.org>
Commit-Queue: Peter Williamson <petewil@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583824}

Presently, CertVerifier::Verify() takes a series of per-verification
flags that express the ways in which certificate verification may be
configured. However, these flags represent overall verifier-wide
configuration, in that they are tied to user preferences or enterprise
policies. These flags are plumbed through the layers by virtue of
SSLConfig, but generally do not change between verifications.

As part of making the verification configuration opaque to callers,
move the flags from being something passed in each verifier-call to
something that is implicitly handled on the CertVerifier, via the
CertVerifier::Config. All verifications started will share the same
configuration, while allowing callers to focus on the per-verification
parameters that are unique (such as the hostname or certificate).
This sets the stage for moving the CRLSet in as explicit CertVerifier
configuration, rather than passed-per-call, as well as to having the
socket pools more intelligently respond to these configuration changes.

Originally landed in https://chromium-review.googlesource.com/c/chromium/src/+/1122709

TBR: zea@chromium.org, kinuko@chromium.org, torne@chromium.org, mfoltz@chromium.org, sergeyu@chromium.org, xunjieli@chromium.org, pmarko@chromium.org
Bug: 848277, 854635
Change-Id: Ie113be88c88d86a5abbff200aa623b97bca461a3
Cq-Include-Trybots: luci.chromium.try:linux_mojo;master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Reviewed-on: https://chromium-review.googlesource.com/1177801
Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Eric Roman <eroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583823}

Change-Id: I42740095792d5a1db12399950e856d927d17143b
Reviewed-on: https://chromium-review.googlesource.com/1178245Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583822}

Cloud Print preferences are removed from the persistent storage list for
incognito mode.
After this CL, if these preferences are changed from incognito mode,
they are only stored in memory and won't affect user profile.

Bug: 861722
Change-Id: I601f41f611a81c2a5dccc712dba7f5e5626c923a
Reviewed-on: https://chromium-review.googlesource.com/1176810
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Lei Zhang <thestig@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583821}

ClientControlledShellSurface does not use it.

Bug: b:77972398
Test: exo_unittests
Change-Id: I42a5be08d94b12a2fa2d15792d297bae236a76b1
Reviewed-on: https://chromium-review.googlesource.com/1176655Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583820}

Update ScrollTimeline to use post-snapped scroll offsets instead of pre-snapped
one. This fixes jitter when scroll-linked worklet animation is trying to
position items against the scroll offset.

Background:
Scrolling layers are pixel snapped which means they are shifted so that
they get aligned to pixel boundaries. This means that the raw scroll offset
of a scrolling layer is not exactly what is display on the screen.

The snapping is done by adjusting the effective transform of the associated
TransformNode for this scrolling element.

Previously ScrollTimeline would use raw scroll offset to compute its time.
This patch introduces a new method on the ScrollTree that will use the info
from TransformNode to calculate an effective scroll offset that represents the
post-snapped position of the scrolling node.

Bug: 585458
Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I30bb052d8cfef8a32ec1a613921d7594bef3c982
Reviewed-on: https://chromium-review.googlesource.com/1153583
Commit-Queue: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Ali Juma <ajuma@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583819}

We don't have enough capacity for layout tests in 10.13, and the fall
back triggering isn't working sufficiently (crbug.com/871453)

The 10.12 pool w/ 8086:0a2e GPUs has plenty of spare capacity, and
flashing them up to 10.13 isn't going to happen soon (crbug.com/873421).

Meanwhile, pending times are getting out of hand on ios-sim and
mac_chromium_rel_ng bots. So this temporarily moves layout tests
fully back to 10.12

That should free up plenty of 10.13 capacity. According to my SQL'ing,
the 10.13 pool ran ~8100 bot hours of tests yesterday; and layout tests
on mac_chromium_rel_ng accounted for ~1000 of them. (LMK if you want
my queries and I can link them.)

# No-try to help unblock mac_chromium_rel_ng
NOTRY=true

Bug: 854874
Change-Id: Ibd708f795d1df67de74cebf3f955ff175c00c0f3
Reviewed-on: https://chromium-review.googlesource.com/1175243
Commit-Queue: Ben Pastene <bpastene@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583818}

ClientControlledShellSurface does not use the configure protocol.

Bug: b:77972398
Test: exo_unittests
Change-Id: I87f7be2e385c7184e7c717ccf5f0d41921c80e36
Reviewed-on: https://chromium-review.googlesource.com/1164552Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Commit-Queue: Dominik Laskowski <domlaskowski@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583817}

Use network quality tracker instead of network quality estimator (NQE)
to obtain network quality in offline pages.

Network quality tracker can provide network service when network
service is enabled as well as when network service is disabled.

Bug: 819244
Change-Id: I0b2bad429c1e7745759a1172fb1fbaa843dd8b8b
Reviewed-on: https://chromium-review.googlesource.com/1171863Reviewed-by: Helen Li <xunjieli@chromium.org>
Reviewed-by: Cathy Li <chili@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583816}

Previously, -updateTextSelection:range:offset: could receive an invalid
range from WebContentsTextObserver::DidChangeTextSelection(). This
invalid range would then cause a crash in -requestSuggestions.

A check has been added to -updateTextSelection:range:offset: to make
sure that a selection with an invalid range is not passed to
-requestSuggestions. This should prevent future crashes.

TextSuggestionsTouchBarControllerTest.InvalidRange tests that an
invalid range does not crash the controller and is handled
properly.

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

This CL adds a README.md file to the tools/fuchsia/comparative_tester/
directory, explaining how all the scripts interact with each other, and
how they should be used.

Change-Id: Ib9f668fb09f5fa1ba50d6da396251b2c8113d4a5
Reviewed-on: https://chromium-review.googlesource.com/1176366
Commit-Queue: Stephan Stross <stephanstross@google.com>
Reviewed-by: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583814}

Split all IO thread code into a separate helper class. Now there is no
refcounting, so ownership is clearer. Now only the helper class has a
WeakPtrFactory, so WeakPtrs are only used on the IO thread.

BUG=873529

Change-Id: I326aa6f69839c193507df4c63250aa1560bbd0ef
Reviewed-on: https://chromium-review.googlesource.com/1177444
Commit-Queue: Lei Zhang <thestig@chromium.org>
Reviewed-by: Robbie McElrath <rmcelrath@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583813}

Changes a "if" to a "DCHECK".

Change-Id: I17cbe0efee059bbc76ca85cacd395f57b1ac41a2
Reviewed-on: https://chromium-review.googlesource.com/1178224Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Katie Dektar <katie@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583812}

This migrates all NetworkChangeNotifier usages in
components/data_reduction_proxy/core/browser to the new
NetworkConnectionTracker, which will work with the network service
enabled.

Bug: 868005
Change-Id: Ia81ebef073b72f9baa3e97550451ad92c4aac2aa
Reviewed-on: https://chromium-review.googlesource.com/1157345
Commit-Queue: Robbie McElrath <rmcelrath@chromium.org>
Reviewed-by: Doug Arnett <dougarnett@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583811}

Bug: 874703
Change-Id: I63bc492d44f230ced991d6525ae43ede1e6a8359
Reviewed-on: https://chromium-review.googlesource.com/1176826Reviewed-by: Eric Karl <ericrk@chromium.org>
Reviewed-by: Khushal <khushalsagar@chromium.org>
Commit-Queue: Khushal <khushalsagar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583810}

https://pdfium.googlesource.com/pdfium.git/+log/5f4cd74d2693..f956badf3dd2


git log 5f4cd74d2693..f956badf3dd2 --date=short --no-merges --format='%ad %ae %s'
2018-08-16 hnakashima@chromium.org Add a way to save a barcode generated bitmap to a .png.
2018-08-16 tsepez@chromium.org Remove more optional args in core/
2018-08-16 hnakashima@chromium.org Optimize rendering of two dimensional barcodes: deduplicate regions.


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

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.



BUG=chromium:872907
TBR=dsinclair@chromium.org

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

After https://chromium-review.googlesource.com/c/chromium/src/+/1145066,
which adds an STL-compatible interface to EnumSet and EnumSet::Iterator,
replace all uses of the previous iteration interface with a range-based
for loop. This allows eventual removal of the old interface altogether.

Also, replace existing usage of |arraysize| with |base::Size|, since the
former was deprecated.

This is CL part 1 of 2.

Bug: 860435
Change-Id: Ida43a641fd24f567be162ae5e18665e2ea7e39f6
Reviewed-on: https://chromium-review.googlesource.com/1146819
Commit-Queue: David Davidović <davidovic@google.com>
Reviewed-by: vitaliii <vitaliii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583808}

The tests failed because of different graphics layer structures about
ChildContainmentLayer and AncestorClippingLayer which are intentionally
not created by BGPT, so rebaseline them.

Bug: 854196
Cq-Include-Trybots: luci.chromium.try:linux-blink-gen-property-trees;luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: I96223cc733ff0a1e792d4660e8e667a7d9e17460
Reviewed-on: https://chromium-review.googlesource.com/1178628Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583807}

R=twellington@chromium.org

Change-Id: I074521c0835fe6d71cfa19fef359cd2f6bd42db9
Reviewed-on: https://chromium-review.googlesource.com/1178561Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Siddhartha S <ssid@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583806}

Bug: None
Change-Id: I1e86c4a52bb3f0eca8c896b5e23664ab1ca1f505
Reviewed-on: https://chromium-review.googlesource.com/1178629
Commit-Queue: Chase Phillips <cmp@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583805}

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

https://chromium.googlesource.com/angle/angle.git/+log/6e5bf36ff50f..3394a73db973


git log 6e5bf36ff50f..3394a73db973 --date=short --no-merges --format='%ad %ae %s'
2018-08-16 tobine@google.com Refactor of EGL SwapBuffers validation


Created with:
  gclient setdep -r src/third_party/angle@3394a73db973

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: I7f68c3ea7c114ece23c85bf2245218b57a138162
Reviewed-on: https://chromium-review.googlesource.com/1178626Reviewed-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@{#583803}

We recenttly changed the track sizing algorithm so that it considers the
offsets added by the Content Alignment properties. The change in r566412
introduce intermediate steps in the track sizing algorithm so that
inline-axis Content Distribution accounts for the row tracks sizes
computed in the next step.

However, we were adding the Content Distribution offsets for any column
track, but we should do it only for the tracks with spanning items. This
error led to the mentioned bugs and this change fixes them.

Bug: 871230, 871242
Change-Id: I8ac789ccacc2e5a51bfafd7820ed08e96a31e58b
Reviewed-on: https://chromium-review.googlesource.com/1176803Reviewed-by: Sergio Villar <svillar@igalia.com>
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Cr-Commit-Position: refs/heads/master@{#583802}

https://webrtc.googlesource.com/src.git/+log/74ed734d717a..b005087a8cac


git log 74ed734d717a..b005087a8cac --date=short --no-merges --format='%ad %ae %s'
2018-08-16 titovartem@webrtc.org Add replacements for all FakeNetworkPipe ctors.
2018-08-16 jonasolsson@webrtc.org Reimplement rtc::ToString and rtc::FromString without streams.
2018-08-16 buildbot@webrtc.org Roll chromium_revision 7e9f692e..04aa516a (583557:583667)


Created with:
  gclient setdep -r src/third_party/webrtc@b005087a8cac

The AutoRoll server is located here: https://webrtc-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:linux_chromium_archive_rel_ng;master.tryserver.chromium.mac:mac_chromium_archive_rel_ng

BUG=chromium:None
TBR=webrtc-chromium-sheriffs-robots@google.com

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

In order to prevent MacTouchId and BLE system UI dialog from appearing
prior to user explictly selecting which transport type to use,
ChromeAuthenticatorRequestDelegate should be able to "lazily" dispatch
WebAuthN request to FidoAuthenticators. Add logic trigger request from
embedder layer.

Bug: 866601
Change-Id: Iec3e16c2c87423c7af101e529f1a12ade62652ee
Reviewed-on: https://chromium-review.googlesource.com/1175418
Commit-Queue: Jun Choi <hongjunchoi@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583800}

Placing a vectordrawable as the android:drawable is not allowed, so we have to bind it in onBindView

Bug: 874723
Change-Id: I20cf9856ca83bb5786da7223c828b9bb5679ba8e
Reviewed-on: https://chromium-review.googlesource.com/1178311Reviewed-by: Theresa <twellington@chromium.org>
Commit-Queue: Sophie Chang <sophiechang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583799}

This reverts commit 6090d226.

Reason for revert: culprit CL is being reverted in https://chromium-review.googlesource.com/c/chromium/src/+/1178841

Original change's description:
> Disabling failing blink_perf.image_decoder stories on Win.
> 
> Bug: 874810
> Change-Id: I11ff44a55b4f2b14b8ba0a4ab5bb4e0f54cd8ef8
> TBR: nednguyen@google.com
> NOTRY: true
> Reviewed-on: https://chromium-review.googlesource.com/1177882
> Reviewed-by: Annie Sullivan <sullivan@chromium.org>
> Commit-Queue: Annie Sullivan <sullivan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#583658}

TBR=sullivan@chromium.org

Change-Id: Ia80a8b6809d909fff687bd12cace06fe447eb141
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 874810
Reviewed-on: https://chromium-review.googlesource.com/1178861Reviewed-by: Ned Nguyen <nednguyen@google.com>
Commit-Queue: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#583798}

Color.parse is quite expensive, resulted in 7 seconds wait for a million entries.
We can just cache parsed colors provided there are just few dozens of them.

Also move gl.get* operations out of the main draw routine as they known to be expensive.

BUG=874116

Change-Id: I6b02210a1dd1d2b9e8ef9d9931ee3eebd0087872
Reviewed-on: https://chromium-review.googlesource.com/1178579Reviewed-by: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Commit-Queue: Aleksey Kozyatinskiy <kozyatinskiy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583797}

Sister CL to crrev.com/c/1176279 -- this CL folds
V4L2SliceVideoDecodeAccelerator::DecodeSurface() into callers.

This simplifies extracting CreateSurface() and SurfaceReady()
into an interface, in turn allowing better unit testing.

Bug: 875005
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: I07d6934316cac629b2e78e2e96b66a19864bdd9e
Reviewed-on: https://chromium-review.googlesource.com/1178322Reviewed-by: Dan Sanders <sandersd@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583796}

Also removed the confirm reject screen upon UX's request.

Bug: b/78190629
Test: Manual Test
Change-Id: If2f97cb5e8302932fa96e0378ac3fd760d49feae
Reviewed-on: https://chromium-review.googlesource.com/1176588Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Xiaohui Chen <xiaohuic@chromium.org>
Commit-Queue: Yue Li <updowndota@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583795}

The models are the means by which the UI share its state with other
components. PlatformController should remain unknown to the UI.

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: I48a917b2e144843173102494fe1b764cd30883f4
Reviewed-on: https://chromium-review.googlesource.com/1177894Reviewed-by: Ian Vollick <vollick@chromium.org>
Commit-Queue: Aldo Culquicondor <acondor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583794}

The documentation referred to RFC4913, which has nothing to do with IP
addresses. RFC4193 appears to be the correct RFC to cite.

Bug: 873490
Change-Id: I606f20af8027f252dcef90726032c7723f62d0de
Reviewed-on: https://chromium-review.googlesource.com/1174962Reviewed-by: Derek Cheng <imcheng@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Commit-Queue: Nick Harper <nharper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583793}

Instead of providing an object that creates fake framebuffers in tests,
create fake GbmBuffers and import them into the fake DrmDevice.

Reland: Fixup empty modifiers case for modeset buffers by moving it into
GbmDevice.

Bug: 869206
Test: ozone_unittests
Change-Id: I2ba134a7e1556a4d177e6e9aaa5265f0c7f6e9b7
Reviewed-on: https://chromium-review.googlesource.com/1178308Reviewed-by: Daniel Nicoara <dnicoara@chromium.org>
Commit-Queue: Michael Spang <spang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583792}

We have no plans to standardize this for the time being, so let's remove
it.

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

This CL introduces a new checkbox that will be enabled only for users on the
google.com domain. This checkbox is only shown if we detect that the google
internal user is trying to file feedback related to bluetooth.

This CL only introduces the UI changes. Once the platforms-side changes land
to collect bluetooth logs for Google internal users, I'll send a follow on CL
that gathers those logs and attaches them to the feedback report.

R=afakhry@chromium.org

Bug: 872403
Change-Id: I937ddf8002373a861fbe5252ce37570c9f2a2f63
Reviewed-on: https://chromium-review.googlesource.com/1166594Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: Toni Baržić <tbarzic@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Wenzhao (Colin) Zang <wzang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583790}

AudioRenderer interface is being replaced with AudioOut. Updated
//media and //chromecast to use the new interface. Also fixed a crash
in FIDL interface handler.

Bug: 873676
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: Ib0f9963fb7b39033bb89a0945a4b8eb5616594cc
Reviewed-on: https://chromium-review.googlesource.com/1175240Reviewed-by: Xiaohan Wang <xhwang@chromium.org>
Reviewed-by: Kenneth MacKay <kmackay@chromium.org>
Commit-Queue: Sergey Ulanov <sergeyu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583789}

Bug: 870020
Change-Id: Ic0173972f01d506d5e8b18b8c6de629ecc6b6a6e
Reviewed-on: https://chromium-review.googlesource.com/1159188Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Commit-Queue: Aaron Leventhal <aleventhal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583788}

https://chromium.googlesource.com/catapult.git/+log/ed63b1319414..3d85a23b6c18


git log ed63b1319414..3d85a23b6c18 --date=short --no-merges --format='%ad %ae %s'
2018-08-16 dtu@chromium.org [dashboard] Update bug link in README.md.
2018-08-16 anthonyalridge@google.com Fix bug in dot plotter for labels with invalid characters.


Created with:
  gclient setdep -r src/third_party/catapult@3d85a23b6c18

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:866423
TBR=sullivan@chromium.org

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