Commit 29b85c51 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll src/third_party/shaderc/src 6807a2568cda..f06a1962beff (1 commits)

https://chromium.googlesource.com/external/github.com/google/shaderc/+log/6807a2568cda..f06a1962beff

git log 6807a2568cda..f06a1962beff --date=short --first-parent --format='%ad %ae %s'
2019-11-26 9856269+sarahM0@users.noreply.github.com spvc: Fix spvc_spirv_cross_spvc_parser_tests failure by updating known_spvc_filures (#909)

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

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: I2129b3486511d21ebf65b42c5f53ff39c2acb3dc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1937348Reviewed-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@{#719290}
parent 2b31555e
......@@ -299,7 +299,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': '6807a2568cdaebd55194df61c2859adc0fcfe437',
'shaderc_revision': 'f06a1962beff94896008385929672e1ffec2dd82',
# 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