Roll src/third_party/skia bf87730:10cae83

Roll src/third_party/skia bf87730:10cae83

Summary of changes available at:
https://chromium.googlesource.com/skia/+log/bf87730..10cae83

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
TBR=halcanary@google.com

Commits in this roll:
10cae83 joshualitt@chromium.org Move determiniation of strokerect rects internal
7f69144 msarett@google.com Add nanobench tests for BitmapRegionDecoder
cc334b3 mtklein@chromium.org fix DM?
31459a4 benjaminwagner@google.com This file was supposed to be in https://codereview.chromium.org/1347143006/
aca31fe bsalomon@google.com Stop supporting HW dither
a16e8bc mtklein@chromium.org move mutex construction out of the benchmarks.
78041fa mdempsky@chromium.org Small cleanups to SkSmallAllocator
11edad9 joshualitt@chromium.org Fix for degenerate stroke rect
07ed41f mdempsky@chromium.org Fix possible integer overflow in SkTSearch's midpoint calculation
e73f1f6 egdaniel@google.com Prefer dual source/framebuffer fetch paths for GPU LCD.
7cbeaae bungeman@google.com Avoid CTFontCreateCopyWithAttributes.
59ea019 benjaminwagner@google.com Blacklist bleed_image on GalaxyS4.
a204ced joshualitt@google.com Revert of Fix for degenerate stroke rect (patchset #7 id:110001 of https://codereview.chromium.org/1359453002/ )
511684f joshualitt@chromium.org Fix for degenerate stroke rect

Committed: https://crrev.com/4be57da557544e360ab73add1c9a2828299725f8
Cr-Commit-Position: refs/heads/master@{#350242}

[skia-deps-roller, 2015-09-22 20:16:04]

The CQ bit was checked by skia-deps-roller@chromium.org

[skia-deps-roller, 2015-09-22 20:16:06]

This roll was created by the Blink AutoRollBot.
    http://www.chromium.org/blink/blinkrollbot

[commit-bot: I haz the power, 2015-09-22 20:16:59]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1355363002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1355363002/1

[commit-bot: I haz the power, 2015-09-22 21:49:48]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-09-22 22:09:26]

Patchset 1 (id:??) landed as
https://crrev.com/4be57da557544e360ab73add1c9a2828299725f8
Cr-Commit-Position: refs/heads/master@{#350242}

[Yuta Kitamura, 2015-09-23 02:42:57]

On 2015/09/22 at 22:09:26, commit-bot wrote:
> Patchset 1 (id:??) landed as
https://crrev.com/4be57da557544e360ab73add1c9a2828299725f8
> Cr-Commit-Position: refs/heads/master@{#350242}

This appeared to cause a massive baseline changes in Yosemite, just like
<https://codereview.chromium.org/1360923002/>.

https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Mac10_10/...

Are these changes expected? Should they get rebaselined again?

[jbroman, 2015-09-23 13:52:30]

On 2015/09/23 at 02:42:57, yutak wrote:
> On 2015/09/22 at 22:09:26, commit-bot wrote:
> > Patchset 1 (id:??) landed as
https://crrev.com/4be57da557544e360ab73add1c9a2828299725f8
> > Cr-Commit-Position: refs/heads/master@{#350242}
> 
> This appeared to cause a massive baseline changes in Yosemite, just like
> <https://codereview.chromium.org/1360923002/>.
> 
>
https://storage.googleapis.com/chromium-layout-test-archives/WebKit_Mac10_10/...
> 
> Are these changes expected? Should they get rebaselined again?

Those are the changes that were supposed to be rebaselined by my CL. Were these
failures after that CL landed (or after the rebaseline bot went through)?