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

Roll src/third_party/swiftshader ea1b0983c7b4..3c830834002a (1 commits)

https://swiftshader.googlesource.com/SwiftShader.git/+log/ea1b0983c7b4..3c830834002a


git log ea1b0983c7b4..3c830834002a --date=short --no-merges --format='%ad %ae %s'
2019-04-24 bclayton@google.com LLVMReactorDebugInfo: Remove REACTOR_LLVM_VERSION check


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

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/130460252
TBR=swiftshader-team+autoroll@chromium.org

Change-Id: I0a85f19176d60e263f52c8b7df24180563702609
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1582010Reviewed-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@{#653591}
parent 65046b8f
......@@ -145,7 +145,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': 'ea1b0983c7b43146e098498e41438075772da018',
'swiftshader_revision': '3c830834002af142bad878c79663833c95551461',
# 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