Commit 76eacdb5 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/swiftshader 19a0081c68a9..62c8b1eda364 (1 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/19a0081c68a9..62c8b1eda364


git log 19a0081c68a9..62c8b1eda364 --date=short --no-merges --format='%ad %ae %s'
2019-05-18 hliatis@google.com Update third_party/llvm-7.0/Android.bp to match BUILD.gn


Created with:
  gclient setdep -r src/third_party/swiftshader@62c8b1eda364

The AutoRoll server is located here: https://autoroll.skia.org/r/swiftshader-chromium-autoroll

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:961729
TBR=swiftshader-team+autoroll@google.com

Change-Id: Ice36be5431bf33e592fd8e9cf382a711d8e59be7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1617651Reviewed-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@{#661159}
parent 78d18607
......@@ -149,7 +149,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling SwiftShader
# and whatever else without interference from each other.
'swiftshader_revision': '19a0081c68a9d95f5dbe8fb4dd190cf05d572317',
'swiftshader_revision': '62c8b1eda364c82241bfb8eaa795904cbc7335e6',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling PDFium
# 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