Commit 86ca21a6 authored by chromium-autoroll's avatar chromium-autoroll Committed by Commit Bot

Roll Dawn from 83fe1bc34d80 to 8a9919980f54 (3 revisions)

https://dawn.googlesource.com/dawn.git/+log/83fe1bc34d80..8a9919980f54

2020-07-08 cwallez@chromium.org Don't leak buffers if MapAtCreation fails.
2020-07-08 cwallez@chromium.org Fix MSVC compilation.
2020-07-08 tommek@google.com Adding Queue::WriteTexture

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: chromium:1103154
Tbr: cwallez@google.com
Change-Id: I11ee7c9d876f7dc4d9e034602c8640628b8c3b4d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2288572Reviewed-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@{#786492}
parent c2093bd3
......@@ -318,7 +318,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': '83fe1bc34d80040a479978acb76a60c5db769b63',
'dawn_revision': '8a9919980f5417cd3df6e1bf6d9a3dc53762ad18',
# 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