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

Roll src/third_party/shaderc/src df0e683b5835..f53792645f06 (2 commits)

https://chromium.googlesource.com/external/github.com/google/shaderc/+log/df0e683b5835..f53792645f06

git log df0e683b5835..f53792645f06 --date=short --first-parent --format='%ad %ae %s'
2020-01-15 rharrison@google.com Use the correct comparison when checking for not MSL (#960)
2020-01-15 dneto@google.com Support Vulkan 1.2 (#958)

Created with:
  gclient setdep -r src/third_party/shaderc/src@f53792645f06

If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/shaderc-chromium-autoroll
Please CC radial-bots+chrome-roll@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/+/master/autoroll/README.md

Bug: None
Tbr: radial-bots+chrome-roll@google.com
Change-Id: I350e0a47d5324cc8b24b5ab6ecc2b0f2efb8d7b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2003756Reviewed-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@{#732508}
parent f9c06ee6
......@@ -308,7 +308,7 @@ vars = {
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling feed
# and whatever else without interference from each other.
'shaderc_revision': 'df0e683b583580fcdf5670d05de76a82f39aedcb',
'shaderc_revision': 'f53792645f0696b8954cfdb3c213f96799dd89b2',
# Three lines of non-changing comments so that
# the commit queue can handle CLs rolling feed
# 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