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

Roll src/third_party/swiftshader 3971b19ba242..90cb260644cd (1 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/3971b19ba242..90cb260644cd


git log 3971b19ba242..90cb260644cd --date=short --no-merges --format='%ad %ae %s'
2019-05-28 bclayton@google.com Reactor: Fix all memory leaks with rr::DebugInfo.


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

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

Change-Id: I6e3b9720aa4e962e36613ae14ff1806d57f194b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1632807Reviewed-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@{#663959}
parent 88706c27
......@@ -154,7 +154,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': '3971b19ba24228787897efc59e265964b8b5a17f',
'swiftshader_revision': '90cb260644cdcdb81e87c6e3bf3ec5885eb23f3b',
# 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