Commit 7e53fc74 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Tint from 28ae1471bf2c to 66377ce9be54 (1 revision)

https://dawn.googlesource.com/tint.git/+log/28ae1471bf2c..66377ce9be54

2020-10-08 dj2@everburning.com Add Inspector to doc

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

Bug: None
Tbr: kainino@google.com
Change-Id: I154fe365544f11cd9a59070175ef325564c642e9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2461915Reviewed-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@{#815176}
parent c919b668
...@@ -357,7 +357,7 @@ vars = { ...@@ -357,7 +357,7 @@ vars = {
'ukey2_revision': '0275885d8e6038c39b8a8ca55e75d1d4d1727f47', 'ukey2_revision': '0275885d8e6038c39b8a8ca55e75d1d4d1727f47',
# the commit queue can handle CLs rolling feed # the commit queue can handle CLs rolling feed
# and whatever else without interference from each other. # and whatever else without interference from each other.
'tint_revision': '28ae1471bf2cfbd4e4ec3a0addcc0953d159a008', 'tint_revision': '66377ce9be54f4d34804cabc39c34237d517df4a',
# TODO(crbug.com/941824): The values below need to be kept in sync # TODO(crbug.com/941824): The values below need to be kept in sync
# between //DEPS and //buildtools/DEPS, so if you're updating one, # between //DEPS and //buildtools/DEPS, so if you're updating one,
......
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