Commit 2ee535ee authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/swiftshader 75b6f212c853..ae0f75063c10 (1 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/75b6f212c853..ae0f75063c10

git log 75b6f212c853..ae0f75063c10 --date=short --no-merges --format='%ad %ae %s'
2019-08-15 chrisforbes@google.com Add libyarn static library to Android build

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

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

Bug: chromium:b/139010488
Change-Id: I030e013b5fbd1123ec51b22de2e03d08d03931d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1755556Reviewed-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@{#687278}
parent 2f70782d
......@@ -161,7 +161,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': '75b6f212c8536b2fa0558b711b741eb60d9e2188',
'swiftshader_revision': 'ae0f75063c109d4619103fa8f8ea80545608dffc',
# 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