Commit 042610e4 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Dawn from d42713de7aa3 to 2b6b0f45ff05 (2 revisions)

https://dawn.googlesource.com/dawn.git/+log/d42713de7aa3..2b6b0f45ff05

2020-11-05 enrico.galli@intel.com Add support for Tint's HLSL writer as a Toggle
2020-11-05 dawn-autoroll@skia-public.iam.gserviceaccount.com Roll Tint from 77f7bb5b005d to 795bf4c71637 (10 revisions)

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

Cq-Include-Trybots: luci.chromium.try:dawn-linux-x64-deps-rel;luci.chromium.try:dawn-mac-x64-deps-rel;luci.chromium.try:dawn-win10-x64-deps-rel;luci.chromium.try:dawn-win10-x86-deps-rel
Bug: None
Tbr: cwallez@google.com
Change-Id: I19d761e101fd14c5993d49a6a89a6a99c80268de
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2522000Reviewed-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@{#824681}
parent 4d8b4c00
......@@ -329,7 +329,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.
'dawn_revision': 'd42713de7aa3227f1feb405beddac4e37051b679',
'dawn_revision': '2b6b0f45ff0597a847d0da25485dce9e2278ee80',
# 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