Commit c000744b authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Skia from 6fd391a016f3 to 5d3314c53ce5 (1 revision)

https://skia.googlesource.com/skia.git/+log/6fd391a016f3..5d3314c53ce5

2020-08-29 mtklein@google.com overhaul blit_row_s32a_opaque()

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/skia-autoroll
Please CC mtklein@google.com on the revert to ensure that a human
is aware of the problem.

To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Cq-Include-Trybots: luci.chromium.try:android_optional_gpu_tests_rel;luci.chromium.try:linux-blink-rel;luci.chromium.try:linux-chromeos-compile-dbg;luci.chromium.try:linux_optional_gpu_tests_rel;luci.chromium.try:mac_optional_gpu_tests_rel;luci.chromium.try:win_optional_gpu_tests_rel
Cq-Do-Not-Cancel-Tryjobs: true
Bug: chromium:1088224
Tbr: mtklein@google.com
Change-Id: Icc5df01f2d6679dccab7cd3a44b81258db3f4e77
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2383611Reviewed-by: default avatarchromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com>
Cr-Commit-Position: refs/heads/master@{#802908}
parent 8b31363f
......@@ -195,7 +195,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling Skia
# and whatever else without interference from each other.
'skia_revision': '6fd391a016f3b4e4b6f4df43aee7e8120943c9cd',
'skia_revision': '5d3314c53ce5c966591f0b02349103f51f986e6e',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling V8
# and whatever else without interference from each other.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment