GitLab

Previously they were guarded by #ifndef NDEBUG because paint record
dumping was only available in debug build.

Now still guard by DCHECK_IS_ON() so that we won't build them into
official releases.

Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I22886cd7a7fc1ef34069944534c6be79af63f757
Reviewed-on: https://chromium-review.googlesource.com/941419Reviewed-by: Philip Rogers <pdr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539927}

Summary of changes available at:
https://chromium.googlesource.com/v8/v8/+log/86431ec7..d5002715

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

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

CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.android:android_optional_gpu_tests_rel

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

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

New interface method PreviewsDecider::IsURLAllowedForPreview() checks
a URL against the local blacklist and optimization hints whitelist if
applicable. This reduced check is now used on the committed URL for
NoScript (refactor from using ShouldAllowPreviewAtEct() at commit time).
This reduces the preview logging cruft that the current commit time
check adds.


Bug: 816964
Change-Id: I2e81d06d3397cd3f3f7727f658ee8818c22e122c
Reviewed-on: https://chromium-review.googlesource.com/922459Reviewed-by: Peter Williamson <petewil@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Doug Arnett <dougarnett@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539925}

Add a command line flag to enable (local) WebRTC event logging.
The flag takes as argument the directory into which the logs
will be saved.

If the flag is used, enabling/disabling (local) WebRTC event
logging from chrome://webrtc-internals will not be possible. The
only way to change that is to restart the browser without the
command line flag.

As a drive-by, this CL removes an unnecessary check for
WebRtcEventLogManager nullness, by making sure it would not be
null in unit tests, regardless of timing.

Bug: 815199
Change-Id: Ib8c732546c30645be823f1bdb6ad7fca8d423d26
Reviewed-on: https://chromium-review.googlesource.com/941322
Commit-Queue: Elad Alon <eladalon@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539924}

Bug: catapult:#4229
Change-Id: I2c7f90eac3f99178ea7729f3bfa14a44120d621f
Reviewed-on: https://chromium-review.googlesource.com/940267
Commit-Queue: Ethan Kuefner <eakuefner@chromium.org>
Reviewed-by: Ned Nguyen <nednguyen@google.com>
Cr-Commit-Position: refs/heads/master@{#539923}

Add comments to show how to get the discrete time constant value for
the formula for setTargetAtTime.

No code changes at all.

Change-Id: I6af196475671e030c665e5a968c18579bc8f7e83
Reviewed-on: https://chromium-review.googlesource.com/940455Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539922}

text-editor-formatter.js is no longer timing out on windows:
https://test-results.appspot.com/dashboards/flakiness_dashboard.html#testType=webkit_layout_tests&tests=http%2Ftests%2Fdevtools%2Feditor%2Ftext-editor-formatter.js

While slow, the slowest run is 5s which is equal to the slowest mac
run. This patch removes the timeout expectation.

Bug: 781428
Change-Id: I707171e7a32224dc915570e692d33bf86d08d120
Reviewed-on: https://chromium-review.googlesource.com/941409Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539921}

This CL moves implementation files for Ozone X11 into a more appropriate
location in ui/ozone/platform/x11, instead of ui/platform_window/x11.

Bug: 707406
Change-Id: If5673cc5283bb523eb5b8b1a8aa4d0b97133ea94
Reviewed-on: https://chromium-review.googlesource.com/941481Reviewed-by: Sadrul Chowdhury <sadrul@chromium.org>
Commit-Queue: kylechar <kylechar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539920}

The content-length related member variables occurring in a few classes
(SaveFileResourceHandler and SaveItem) is not used. Removing it. Also
now passing the correct content-description (it was always empty).
A few minor clean-ups as well.
This work is in preparation of changing that code to use the network
service.

Bug: 816644
Change-Id: I14f999fc3ce5b0bb77ecf9e1d35311ef7704db8a
Reviewed-on: https://chromium-review.googlesource.com/938386
Commit-Queue: Jay Civelli <jcivelli@chromium.org>
Reviewed-by: Min Qin <qinmin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539919}

1. Report more components. A component ID is copied from
https://omahaconsole.corp.google.com
2. Reorder items in component_map to be consistent with protobuf.

BUG=b:73814897
TEST=chrome compiles.

Change-Id: Ia24c7a8cb63e7e42c6aa0ca2655d51b5d4e9e3b5
Reviewed-on: https://chromium-review.googlesource.com/939849Reviewed-by: Alexei Svitkine <asvitkine@chromium.org>
Reviewed-by: Joshua Pawlicki <waffles@chromium.org>
Commit-Queue: Xiaochu Liu <xiaochu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539918}

When long press on a draggable item to start dragging with touch,
we should receive a touchcancel event.
This CL changes it to not suppress pointercancel event when doing
drag and drop.

Bug: 708278
Change-Id: I754cf86dfce37f33164b797edb1f8a05acb82c9b
Reviewed-on: https://chromium-review.googlesource.com/939649Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Commit-Queue: Ella Ge <eirage@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539917}

Legacy layout erroneously sets box-sizing:border-box on non-table
elements that have display:table when the element has a specified %
height. Only <table> elements should have box-sizing:border-box.

Bug: 598134
Change-Id: I66a4a6380ca60a88516a63d3df84faabd709d4c0
Reviewed-on: https://chromium-review.googlesource.com/940561
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539916}

AudioOutputDevice currently expects all responses to be asynchronous,
and this change also simplifies the code a bit.

Bug: 816348
Change-Id: I66d51184f2553043578dda17a5cb7aeebb809a20
Reviewed-on: https://chromium-review.googlesource.com/937721
Commit-Queue: Max Morin <maxmorin@chromium.org>
Reviewed-by: Olga Sharonova <olka@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539915}

Bug: 489301

Change-Id: I268767b48fae92c492165744e1f15389b082a33b
Reviewed-on: https://chromium-review.googlesource.com/938752
Commit-Queue: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539914}

Fix double-click word select for steady state elisions.

This bug is caused by the fact that we change the text in response to
a double-click on the second mousedown. That confuses the double click
word select logic, which saves the range into a member variable.

There's no way for the selection controller to get the correct selected
word except for us to inject an offset into it...

Bug: 797354
Change-Id: I464d405920de7dfcbc317ed9ecbe8b664b920f8d
Reviewed-on: https://chromium-review.googlesource.com/940603
Commit-Queue: Tommy Li <tommycli@chromium.org>
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Reviewed-by: Michael Wasserman <msw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539913}

DataUse.MessageSize.<ServiceName> histogram is recorded for each service.
This histogram is used sparingly. Since there are more services, this
per service histogram is not needed.

Bug: 732638
Change-Id: I0d6a54ec4037da6692d8a5dcb7a537641aa111c1
Reviewed-on: https://chromium-review.googlesource.com/742690
Commit-Queue: rajendrant <rajendrant@chromium.org>
Reviewed-by: Steven Holte <holte@chromium.org>
Reviewed-by: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539912}

Change the multibuffer code to preload 1/32th of the normal preload
when "preload=metadata" is used. This should work around problems
that occur because WMPI says we have enough data while the demuxer
may still be filling buffers.

For a lot of videos, this means we'll be preloading 64k.

Bug: 814328
Change-Id: Iae6945d63bf8298975eb51eda22b16189c7658df
Reviewed-on: https://chromium-review.googlesource.com/937997
Commit-Queue: Fredrik Hubinette <hubbe@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539911}

Spec: https://quirks.spec.whatwg.org/#the-percentage-height-calculation-quirk

It is bug compatible with Legacy. Two test results are interesting:

external/wpt/quirks/percentage-height-calculation.html

Here we pass/fail same tests except for one extra pass, and one extra fail.
Failure is <table>, due to invalidation

fast/block/basic/quirk-percent-height-table-cell.html

This is an overconstrained <td>. I think that NG rendering is correct, and it
matches FF.

Bug: 635619
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I572571428c98fbd95abfea7539ca0ab6d16bbc06
Reviewed-on: https://chromium-review.googlesource.com/940335
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539910}

This CL add a new flag "Enable command line on non-rooted devices" to
chrome://flags. If changed, it will set a flag in Chrome SharedPreferences.
And when CommandLineInitUtil starts, it checks whether an alternative
command line file could be used when:
1. The current build is "eng" or "userdebug" or
2. adb is enable and this is the debug app or
3. The flag is enable in SharedPreferences.

Bug: 784947
Change-Id: I0ee0d2eadbc8b2f1b49b5e5959f7e72f8feda80d
Reviewed-on: https://chromium-review.googlesource.com/861285Reviewed-by: Yaron Friedman <yfriedman@chromium.org>
Reviewed-by: Ted Choc <tedchoc@chromium.org>
Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Lei Tian <ltian@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539909}

This changes the filtered computed-style-map to being pre-populated.

This shouldn't have any performance difference for the paint api, but
should have increased performance for the layout api.

Additionally this allows style for anonymous boxes to exist. Before we
always had a Node->ComputedStyleMap, however with the layout api it is
possible for access the style for an anonymous box.

Bug: 726125
Change-Id: I2820001f158ac0938a277af491a05f1a72b8c734
Reviewed-on: https://chromium-review.googlesource.com/937905
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539908}

FormDataParserMultipart contract says that "*OCTET" part of body is read
 and passed as string of bytes. In case header has filename, octet part
 is ignored - store filename instead.
Actual code doesn't implement it. It led to situation when octet data
 were read and were put as string to base::Value. That led to DCHECK as far
 as string value must be utf-8 string.
The same problem occurs with FormDataParserUrlEncoded, where encoded part
 can be as utf-8 string or binary data.

Bug: 813561
Change-Id: I453e5767e44334535253d1bd3fa4e857c2d3a3ff
Reviewed-on: https://chromium-review.googlesource.com/910848Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Reviewed-by: Vaclav Brozek <vabr@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539907}

Bug: 810433
Change-Id: I59aa22cefec747e16993e7f747a02087b80f6aac
Reviewed-on: https://chromium-review.googlesource.com/935684
Commit-Queue: Becky Zhou <huayinz@chromium.org>
Reviewed-by: Bernhard Bauer <bauerb@chromium.org>
Reviewed-by: Theresa <twellington@chromium.org>
Reviewed-by: Jesse Doherty <jwd@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539906}

This CL:
1. Introduce |Tracked/HostChildURLLoaderFactoryBundle| to track
   and post updates to cloned bundles in the event of Network
   Service crash.
2. Add browser tests to make sure WebWorkers and frames from
   'window.open()' can load URL after crash.

Related Discussions:
https://groups.google.com/a/chromium.org/forum/#!topic/network-service-dev/iWk6Dt9_GA0

Bug: 780956
Change-Id: I3d0b585757e957949d9c4816799ffaa19045ac97
Reviewed-on: https://chromium-review.googlesource.com/912276Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Chong Zhang <chongz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539905}

CastWebContentsComponent.start() is called everytime when saying "OKG,
play next" before the media app is stopped by a voice command. Because
we lose the reference to the old intent receiver, the
old one has no chance to unregister from LocalBroadcastManager, which
would cause memory leak.

Change-Id: Ie16fb82c220c48c5410cf57a6d829b2984880d95
Bug: b/73789608
Test: cast_shell_junit_tests
Reviewed-on: https://chromium-review.googlesource.com/933581Reviewed-by: Luke Halliwell <halliwell@chromium.org>
Commit-Queue: Zhiheng(Vincent) Li <vincentli@google.com>
Cr-Commit-Position: refs/heads/master@{#539904}

The initial upload patch of this CL is the same as:
https://chromium-review.googlesource.com/c/chromium/src/+/877512

This reland CL addresses comments at:
https://chromium-review.googlesource.com/c/chromium/src/+/877512/19

The initial upload patch of this CL uses empty credential to indicate
that URLRequest::CancelAuth() needs to be called, which is incorrect
because empty credentials are valid. The latest patch of this CL
contains the fix for this issue.

TBR=jam@chromium.org, tsepez@chromium.org

Bug: 783990
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_mojo
Change-Id: Ifdbab56badaf3e13b5f15f5aa0d31cfb764325c6
Reviewed-on: https://chromium-review.googlesource.com/938960
Commit-Queue: Jun Cai <juncai@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Reviewed-by: Asanka Herath <asanka@chromium.org>
Reviewed-by: Jun Cai <juncai@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539903}

Network traffic annotation tag is added to
SpdyStreamRequest::StartRequest and is kept with the stream for all
subsequent socket writes.

Bug: 656607
Change-Id: Id106621ec54af003d174ea875564b049bc8f0e4a
Reviewed-on: https://chromium-review.googlesource.com/936481
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Ryan Hamilton <rch@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539902}

Bug: 808486
Change-Id: Icb5491be8b04afa9935147f64c43a08877e34a73
Reviewed-on: https://chromium-review.googlesource.com/900306Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: Jacob Dufault <jdufault@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539901}

The function HasSetTargetConverged was too restrictive and would
continue to say the setTargetAtTime event was not converged even
though the increment was so small as make no change in the value.

Thus, adjust the criteria so that if the increment is too small to
affect the value, consider the event has having converged.

There's also a bug in HandleAllEventsInThePast where setTargetAtTime
has converged and we've updated the default value but the timeline
would return the old default value instead of the new converged
default value.

A couple of tests needed to be updated due to the change in the
convergence criterion.

Ran the test https://jsfiddle.net/8vo0gbav/52/ and the CPU now no
longer goes to 100% as it did without this change.

Bug: 813504
Change-Id: I506b31289b5b40380147d231d8b2ea41785d6600
Reviewed-on: https://chromium-review.googlesource.com/940273Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Raymond Toy <rtoy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539900}

As the preliminary step to resolve issue chromedriver:2222, modify
the build script to archive the PDB file from each Windows build.

Bug: chromedriver:2222
Change-Id: Ic8641eae20349ff436e0d1ec7ded1968fd97d4a6
Reviewed-on: https://chromium-review.googlesource.com/940169Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539899}

Adds entrys to .vpython for peakutils and scipy. These are used by the
VR latency test.

Bug: 816641
Change-Id: Ia9a76166c6014cde0bec4fa648fdd270a83089c7
Reviewed-on: https://chromium-review.googlesource.com/940333Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Brian Sheedy <bsheedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539898}

TBR=mlamouri@chromium.org

Bug: 709181, 817382
Change-Id: Ic64c1c3a0971c24efe459515c720cc6248205195
Reviewed-on: https://chromium-review.googlesource.com/941363Reviewed-by: Miguel Casas <mcasas@chromium.org>
Commit-Queue: Miguel Casas <mcasas@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539897}

Setting 'AutoConnect' to true during configuration causes Shill to
attempt to connect immediately after configuration which breaks
the notification logic. By default Shill will set AutoConenct to
true on the first successful connect if not explicitly set to false.

This also adds yet more / better logging.

Bug: 809902
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: Ibace61a761b7adf7b5c87e8db93d54d3b3942a48
Reviewed-on: https://chromium-review.googlesource.com/940338
Commit-Queue: Steven Bennetts <stevenjb@chromium.org>
Reviewed-by: Alexander Alekseev <alemate@chromium.org>
Reviewed-by: Toni Barzic <tbarzic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539896}

This method is for relying parties to determine whether they can create
a new credential using a user-verifying platform authenticator.

Bug: 803842
Change-Id: I523e61612bf5a13841473cca83be12d2b83767d0
Reviewed-on: https://chromium-review.googlesource.com/910036
Commit-Queue: Kim Paulhamus <kpaulhamus@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539895}

When dispatching mouse events to an OOPIF on android, the coordinates
need to be relative to browser windows, while on desktop they are
relative to the frame.

Change-Id: I2953e42457b4ac3395edcf4db53f2c8780047260
Reviewed-on: https://chromium-review.googlesource.com/941401Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539894}

The OOPIF test is flaky on Windows due to issue chromedriver:2198,
which causes ChromeDriver not waiting for frames to fully load.
This CL adds a workaround to that issue.

Change-Id: I87c37a4c756b8a836d7d3861addb54e8bd03e853
Reviewed-on: https://chromium-review.googlesource.com/939905Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Reviewed-by: Caleb Rouleau <crouleau@chromium.org>
Commit-Queue: John Chen <johnchen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539893}

Bug: 740993
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_layout_ng
Change-Id: I38981d061a410067921984516eb9f1894762e8ca
Reviewed-on: https://chromium-review.googlesource.com/940563Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539892}

https://skia.googlesource.com/skia.git/+log/db1e5c6474c1..dabef9dddd4f

$ git log db1e5c647..dabef9ddd --date=short --no-merges --format='%ad %ae %s'
2018-02-27 benjaminwagner Omit Chromecast test that seems to OOM.
2018-02-28 robertphillips Revert "Move atlas manager creation to GrContext derived classes"
2018-02-28 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 360098d5c..2f3a0dc5c (3 commits)
2018-02-27 bsalomon Refactor GrCaps::renderTargetWritePixelsSupported to support for some GL workarounds
2018-02-27 robertphillips Move atlas manager creation to GrContext derived classes
2018-02-27 skcms-skia-autoroll Roll skia/third_party/externals/skcms/ e496333d5..40a19927b (1 commit)
2018-02-27 angle-skia-autoroll Roll skia/third_party/externals/angle2/ 06a87ec83..360098d5c (3 commits)
2018-02-27 robertphillips Fission GrAtlasGlyphCache in two
2018-02-27 benjaminwagner Switch Win10 ShuttleC bots to new Windows image.
2018-02-27 benjaminwagner Switch Win10 AlphaR2 bots to new Windows image.
2018-02-27 reed date recent version bump for path serialization
2018-02-27 reed fix crasher in path-->region
2018-02-17 halcanary SkQP: optionally build make_universal_apk with debug on.
2018-02-27 egdaniel Fix unit tests that were causes vulkan unitialized memory warnings in validation
2018-02-27 egdaniel Make sure we add render target mem barriers after any last second copies
2018-02-26 benjaminwagner Upgrade Win Intel Haswell/Broadwell GPU drivers.
2018-02-27 mtklein prepare Google3 for the return of SkOpts_hsw.cpp
2018-02-27 caryclark avoid divide in pathopsquad
2018-02-27 caryclark updated includes
2018-02-27 kjlubick Tweak API fuzzers to run better in libfuzzer
2018-02-27 caryclark work on skimageinfo
2018-02-26 reed keep points as floats until after clipping
2018-02-27 reed limit crash small steps in 1dpatheffect

Created with:
  roll-dep src/third_party/skia


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;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
TBR=benjaminwagner@chromium.org

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

https://chromium.googlesource.com/angle/angle.git/+log/2f3a0dc5cbc2..d444255a779b

$ git log 2f3a0dc5c..d444255a7 --date=short --no-merges --format='%ad %ae %s'
2018-02-27 jmadill Refactor signal utils into Observer pattern.

Created with:
  roll-dep src/third_party/angle


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

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

Bug: 786559
Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet
Change-Id: I5819eab242ec2864d9bdc261868871179e80c8a3
Reviewed-on: https://chromium-review.googlesource.com/906951Reviewed-by: Helen Li <xunjieli@chromium.org>
Commit-Queue: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539889}

The following tests are failing on Android Chromium build bot.
Tests are disabled.
Some of these tests are flaky.

Bug: chromedriver:2286
Change-Id: I44a7fa01a4e2d909d78f2749a8f7f5ecdf8c34e5
Reviewed-on: https://chromium-review.googlesource.com/941420Reviewed-by: John Chen <johnchen@chromium.org>
Commit-Queue: Artur Khachatryan <khachatryan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539888}